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
❌3 errors, 3 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-26 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
trip direction_id does not match GTFS data E024 3 errors
GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt
Sample errors
- GTFS-rt vehicle_id zenbus:Vehicle:5149698287468544:LOC trip_id ATOUMOD036:ServiceJourney:4789093536890880x3:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt vehicle_id zenbus:Vehicle:5124157735960576:LOC trip_id ATOUMOD036:ServiceJourney:4884764134735872x0:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt vehicle_id zenbus:Vehicle:5903739505344512:LOC trip_id ATOUMOD036:ServiceJourney:5365269825323008x2:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
Warnings
schedule_relationship not populated W009 3 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD036:ServiceJourney:4789093536890880x3:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4884764134735872x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:5365269825323008x2: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 | 190 | 29 times (97 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 190 | 29 times (97 % 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. | 28 | 16 times (53 % of validations) |
| E052 | Each vehicle should have a unique ID | 21 | 16 times (53 % of validations) |
| E050 | All timestamps must be less than the current time | 7 | 7 times (23 % 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. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-27 at 01:46 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 2025-07-27 at 01:46 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1753573602"
}
}