Resource details
Données position des véhicules en temps réel, au format GTFS-RT PROTOBUF, du réseau AXO
This resource file is part of the dataset Réseau urbain AXO.
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
❌2 errors, 16 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-08 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position outside agency coverage area E028 1 error
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.
Sample errors
- vehicle.id RCR13 at (-5.983856,-1.3630812) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Vehicle position far from trip shape E029 1 error
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 RCR59 trip_id 13014 at (49.264973,2.4711533) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
schedule_relationship not populated W009 16 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 13090 does not have a schedule_relationship
- trip_id 13014 does not have a schedule_relationship
- trip_id 13009 does not have a schedule_relationship
- trip_id 13204 does not have a schedule_relationship
- trip_id 13246 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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 654 | 27 times (90 % 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. | 26 | 17 times (57 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 161 | 5 times (17 % 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. | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-09 at 04:16 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-11-09 at 04:16 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1762658185"
}
}