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
⚠️56 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-04 at 08:05 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle speed is unrealistic W004 8 errors
vehicle.position.speed has an unrealistic speed that may be incorrect
Sample errors
- vehicle.id 2224 speed of 37.0 m/s (82.77 mph) is unrealistic
- vehicle.id 2277 speed of 42.0 m/s (93.95 mph) is unrealistic
- vehicle.id 2235 speed of 39.0 m/s (87.24 mph) is unrealistic
- vehicle.id 2233 speed of 37.0 m/s (82.77 mph) is unrealistic
- vehicle.id 2185 speed of 71.0 m/s (158.82 mph) is unrealistic
schedule_relationship not populated W009 48 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 130387{C_567}-2025_09_PS_PP_001_LMWJVS does not have a schedule_relationship
- trip_id 131510{D_561}-2025_09_PS_PP_001_LMWJVS does not have a schedule_relationship
- trip_id 131346{B_558}-2025_09_PS_PP_001_LMWJVS does not have a schedule_relationship
- trip_id 131302{B_558}-2025_09_PS_PP_001_LMWJV does not have a schedule_relationship
- trip_id 131308{B_558}-2025_09_PS_PP_001_LMWJVS 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 | 37 | 9 times (75 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 206 | 8 times (67 % 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. | 2 | 1 times (8 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-05 at 05:57 Europe/Paris.
vehicle_positions (1) 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 2025-11-05 at 05:57 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "RTVP:T:131298{B_558}-2025_09_PS_PP_001_LMWJVS",
"vehicle": {
"currentStopSequence": 7,
"position": {
"bearing": 90.0,
"latitude": 47.58955001831055,
"longitude": 1.2996309995651245,
"speed": 33.0
},
"stopId": "BLDTROUA",
"timestamp": "1762318633",
"trip": {
"directionId": 0,
"routeId": "B",
"tripId": "131298{B_558}-2025_09_PS_PP_001_LMWJVS"
},
"vehicle": {
"id": "2277",
"label": "2193",
"licensePlate": "GA-003-YE"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1762318639"
}
}