Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
TripUpdate
VehiclePosition
Alert
This resource file is part of the dataset Réseau urbain Réso.
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
❌9 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-13 at 08:11 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 2 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 693feded82c2cf7eb6c46ee0 trip_id 39-5117116480 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 39-5117116480 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 2 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 693feded82c2cf7eb6c46ee0 route_id 305 does not exist in the GTFS data routes.txt
- route_id 305 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 5 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 693feded82c2cf7eb6c46ee0 stop_id 1423 does not exist in GTFS data stops.txt
- trip_id 39-5117116480 stop_id 1423 does not exist in GTFS data stops.txt
- trip_id 39-5117116480 stop_id 5795 does not exist in GTFS data stops.txt
- trip_id 39-5117116480 stop_id 6768 does not exist in GTFS data stops.txt
- trip_id 39-5117116480 stop_id 6771 does not exist in GTFS data stops.txt
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 |
|---|---|---|---|
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 11 | 6 times (21 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 6 | 3 times (10 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 5 | 2 times (7 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 5 | 2 times (7 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 23 | 2 times (7 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 25 | 2 times (7 % of validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 1 | 1 times (3 % 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.