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
❌92 errors, 30 warnings
Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-09 at 08:10 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 30 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 RCR52 trip_id 11132 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id RCR62 trip_id 11322 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id RCR46 trip_id 11016 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id RCR901 trip_id 11248 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id RCR49 trip_id 11324 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 30 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id RCR52 route_id B does not exist in the GTFS data routes.txt
- vehicle_id RCR62 route_id B does not exist in the GTFS data routes.txt
- vehicle_id RCR46 route_id C1 does not exist in the GTFS data routes.txt
- vehicle_id RCR901 route_id A does not exist in the GTFS data routes.txt
- vehicle_id RCR49 route_id B does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 30 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id RCR52 stop_id crehopd1 does not exist in GTFS data stops.txt
- vehicle_id RCR62 stop_id crepasc2 does not exist in GTFS data stops.txt
- vehicle_id RCR46 stop_id nogexup4 does not exist in GTFS data stops.txt
- vehicle_id RCR901 stop_id cregara1 does not exist in GTFS data stops.txt
- vehicle_id RCR49 stop_id monzola does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 2 errors
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 RCR901 at (49.33396,2.463376) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id RCR162 at (49.188408,2.4597142) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
Warnings
schedule_relationship not populated W009 30 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 11132 does not have a schedule_relationship
- trip_id 11322 does not have a schedule_relationship
- trip_id 11016 does not have a schedule_relationship
- trip_id 11248 does not have a schedule_relationship
- trip_id 11324 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 30 | 1 times (100 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 30 | 1 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 30 | 1 times (100 % 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 | 1 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 30 | 1 times (100 % of validations) |
GTFS-RT feed content
Could not decode the GTFS-RT feed.
The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.