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
❌58 errors, 32 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-15 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 15 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id zenbus:Vehicle:4827031276617728:LOC trip_id ATOUMOD036:ServiceJourney:4971360863387648x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:5116569904480256:LOC trip_id ATOUMOD036:ServiceJourney:5198893567442944x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:4845661980721152:LOC trip_id ATOUMOD036:ServiceJourney:5804140358795264x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:6425351405174784:LOC trip_id ATOUMOD036:ServiceJourney:6676591728918528x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:5143869253484544:LOC trip_id ATOUMOD036:ServiceJourney:4819710769102848x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 15 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id zenbus:Vehicle:4827031276617728:LOC route_id ATOUMOD036:Line:5234256377806848:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:5116569904480256:LOC route_id ATOUMOD036:Line:5229274752614400:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:4845661980721152:LOC route_id ATOUMOD036:Line:5515601163321344:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:6425351405174784:LOC route_id ATOUMOD036:Line:5326622602297344:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:5143869253484544:LOC route_id ATOUMOD036:Line:5466936700829696:LOC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 8 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id zenbus:Vehicle:4827031276617728:LOC stop_id FR:14371:ZE:4719534813478912:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:5116569904480256:LOC stop_id FR:14654:ZE:4552085111570432:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:4845661980721152:LOC stop_id FR:14654:ZE:5367940187684864:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:6425351405174784:LOC stop_id FR:14421:ZE:4571333879922688:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:4805219226484736:LOC stop_id FR:14273:ZE:6241784200953856:ATOUMOD036 does not exist in GTFS data stops.txt
trip direction_id does not match GTFS data E024 17 errors
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:4992214909321216x1:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
- GTFS-rt vehicle_id zenbus:Vehicle:4837584246145024:LOC trip_id ATOUMOD036:ServiceJourney:4510726359089152x0:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
- GTFS-rt vehicle_id zenbus:Vehicle:5087464869855232:LOC trip_id ATOUMOD036:ServiceJourney:4719204071636992x2:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt vehicle_id zenbus:Vehicle:5149698287468544:LOC trip_id ATOUMOD036:ServiceJourney:5087107212115968x3:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt vehicle_id zenbus:Vehicle:5166415361343488:LOC trip_id ATOUMOD036:ServiceJourney:5056100031266816x2:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
Vehicle position far from trip shape E029 2 errors
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.
Sample errors
- vehicle.id zenbus:Vehicle:5166415361343488:LOC trip_id ATOUMOD036:ServiceJourney:5056100031266816x2:LOC at (49.14824,0.225588) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id zenbus:Vehicle:4874355910639616:LOC trip_id ATOUMOD036:ServiceJourney:5456241129160704x0:LOC at (49.14568,0.246729) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
vehicle.id is not unique E052 1 error
Each vehicle should have a unique ID
Sample errors
- entity ID VM:ATOUMOD036:ServiceJourney:5056100031266816x2:LOC has vehicle.id zenbus:Vehicle:5166415361343488:LOC which is used by more than one vehicle in the feed
Warnings
schedule_relationship not populated W009 32 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD036:ServiceJourney:4971360863387648x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:5198893567442944x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:5804140358795264x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4992214909321216x1:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4510726359089152x0: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 | 282 | 21 times (70 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 487 | 21 times (70 % 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. | 44 | 19 times (63 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 205 | 18 times (60 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 205 | 18 times (60 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 118 | 18 times (60 % of validations) |
| E052 | Each vehicle should have a unique ID | 20 | 14 times (47 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-15 at 23:15 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-12-15 at 23:15 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:ATOUMOD036:ServiceJourney:4719204071636992x27:LOC",
"vehicle": {
"currentStopSequence": 24,
"position": {
"latitude": 49.148399353027344,
"longitude": 0.2591690123081207
},
"stopId": "FR:14366:ZE:17240004:ATOUMOD036",
"timestamp": "1765832665",
"trip": {
"directionId": 1,
"routeId": "ATOUMOD036:Line:5131776580124672:LOC",
"tripId": "ATOUMOD036:ServiceJourney:4719204071636992x27:LOC"
},
"vehicle": {
"id": "zenbus:Vehicle:5149698287468544:LOC"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1765836905"
}
}