Resource details
Fichier complémentaire au GTFS-RT permettant de connaître la position des véhicules.
This resource file is part of the dataset Réseau urbain Orizo.
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
❌87 errors, 86 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-10-16 at 09:16 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 86 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 22306 stop_id 1476 does not exist in GTFS data stops.txt
- vehicle_id 24328 stop_id 1710 does not exist in GTFS data stops.txt
- vehicle_id 12181 stop_id 2448 does not exist in GTFS data stops.txt
- vehicle_id 11299 stop_id 2415 does not exist in GTFS data stops.txt
- vehicle_id 70587 stop_id 1437 does not exist in GTFS data stops.txt
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 24343 trip_id 6238059-26-27-08LaV27-Semaine-00 at (43.942833,4.793923) 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 86 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 6245210-26-27-09LaV27-Semaine-00 does not have a schedule_relationship
- trip_id 6251178-26-27-16LaV27-Semaine-00 does not have a schedule_relationship
- trip_id 6266323-26-27-CZILaS27-Lun-Sam-00 does not have a schedule_relationship
- trip_id 6238026-26-27-07LaV27-Semaine-00 does not have a schedule_relationship
- trip_id 6241975-26-27-12LaV27-Semaine-00 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 | 2,251 | 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. | 72 | 27 times (90 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1,536 | 21 times (70 % 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.