Resource details
GTFS-RT Données temps réel du réseau urbain Azalys de BLOIS - position véhicules
This resource file is part of the dataset Réseau urbain Azalys.
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
⚠️17 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-03 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle speed is unrealistic W004 4 errors
vehicle.position.speed has an unrealistic speed that may be incorrect
Sample errors
- vehicle.id 2165 speed of 31.0 m/s (69.35 mph) is unrealistic
- vehicle.id 2277 speed of 28.0 m/s (62.63 mph) is unrealistic
- vehicle.id 2232 speed of 38.0 m/s (85.00 mph) is unrealistic
- vehicle.id 2238 speed of 29.0 m/s (64.87 mph) is unrealistic
schedule_relationship not populated W009 13 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 141036-KBLOIS2526-BLOIS_E-Semaine-12 does not have a schedule_relationship
- trip_id 137671-KBLOIS2526-BLOIS_E-Semaine-12 does not have a schedule_relationship
- trip_id 140842-KBLOIS2526-BLOIS_E-Semaine-12 does not have a schedule_relationship
- trip_id 140869-KBLOIS2526-BLOIS_E-Semaine-12 does not have a schedule_relationship
- trip_id 140870-KBLOIS2526-BLOIS_E-Semaine-12 does not have a schedule_relationship
Previous validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 101 | 28 times (93 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 322 | 27 times (90 % of validations) |
| E012 | No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp | 12 | 11 times (37 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 10 | 10 times (33 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 8 | 8 times (27 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 5 | 1 times (3 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 5 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-04 at 00:11 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-08-04 at 00:11 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785795098"
}
}