Resource details
GTFS-RT (protobuff) de la position des véhicules
This resource file is part of the dataset Réseau urbain Astrobus.
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
❌1 error, 1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-24 at 09:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
trip direction_id does not match GTFS data E024 1 error
GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt
Sample errors
- GTFS-rt vehicle_id zenbus:Vehicle:5166415361343488:LOC trip_id ATOUMOD036:ServiceJourney:4925782146154496x0:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
Warnings
schedule_relationship not populated W009 1 error
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD036:ServiceJourney:4925782146154496x0:LOC 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 |
---|---|---|---|
E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 159 | 30 times (100 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 159 | 30 times (100 % 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. | 18 | 13 times (43 % of validations) |
E052 | Each vehicle should have a unique ID | 12 | 12 times (40 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-08-24 at 19:08 Europe/Paris.
vehicle_positions (2) 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-08-24 at 19:08 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:ATOUMOD036:ServiceJourney:5306245549391872x5:LOC",
"vehicle": {
"currentStopSequence": 2,
"position": {
"latitude": 49.13859176635742,
"longitude": 0.23060700297355652
},
"stopId": "FR:14366:ZE:660040002:ATOUMOD036",
"timestamp": "1756055264",
"trip": {
"directionId": 1,
"routeId": "ATOUMOD036:Line:5131776580124672:LOC",
"tripId": "ATOUMOD036:ServiceJourney:5306245549391872x5:LOC"
},
"vehicle": {
"id": "zenbus:Vehicle:5166415361343488:LOC"
}
}
},
{
"id": "VM:ATOUMOD036:ServiceJourney:4925782146154496x5:LOC",
"vehicle": {
"currentStopSequence": 26,
"position": {
"latitude": 49.13983917236328,
"longitude": 0.2287919968366623
},
"stopId": "FR:14366:ZE:660040002:ATOUMOD036",
"timestamp": "1756054783",
"trip": {
"directionId": 1,
"routeId": "ATOUMOD036:Line:4809340465709056:LOC",
"tripId": "ATOUMOD036:ServiceJourney:4925782146154496x5:LOC"
},
"vehicle": {
"id": "zenbus:Vehicle:5166415361343488:LOC"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1756055320"
}
}