Resource details
Les mises à jour de trajet représentent des fluctuations dans les horaires
This resource file is part of the dataset Réseau urbain Léo.
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
❌124 errors, 18 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-06 at 08:00 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 4 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 4-10066395139 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10083368964 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066657284 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066657283 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 4 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 600 does not exist in the GTFS data routes.txt
- route_id 601 does not exist in the GTFS data routes.txt
- route_id 600 does not exist in the GTFS data routes.txt
- route_id 600 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 44 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 4-10066395139 stop_id 3159 does not exist in GTFS data stops.txt
- trip_id 4-10066395139 stop_id 3160 does not exist in GTFS data stops.txt
- trip_id 4-10066395139 stop_id 3161 does not exist in GTFS data stops.txt
- trip_id 4-10066395139 stop_id 3162 does not exist in GTFS data stops.txt
- trip_id 4-10066395139 stop_id 3163 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 71 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 15483{03_4}-25U_PSC_LMCJVSDF_01_S stop_sequence 36 arrival_time 08:01:22 (1765004482) is equal to previous stop arrival_time 08:01:22 (1765004482) - times must increase between two sequential stops
- trip_id 15483{03_4}-25U_PSC_LMCJVSDF_01_S stop_sequence 36 arrival_time 08:01:22 (1765004482) is equal to previous stop departure_time 08:01:22 (1765004482) - times must increase between two sequential stops
- trip_id 15483{03_4}-25U_PSC_LMCJVSDF_01_S stop_sequence 36 departure_time 08:01:22 (1765004482) is equal to previous stop departure_time 08:01:22 (1765004482) - times must increase between two sequential stops
- trip_id 15483{03_4}-25U_PSC_LMCJVSDF_01_S stop_sequence 36 departure_time 08:01:22 (1765004482) is equal to previous stop arrival_time 08:01:22 (1765004482) - times must increase between two sequential stops
- trip_id 15483{03_4}-25U_PSC_LMCJVSDF_01_S stop_sequence 38 arrival_time 08:02:22 (1765004542) is equal to previous stop arrival_time 08:02:22 (1765004542) - times must increase between two sequential stops
trip start_time does not match first GTFS arrival_time E023 1 error
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Sample errors
- GTFS-rt trip_id 15483{03_4}-25U_PSC_LMCJVSDF_01_S start_time is 07:15:00 and GTFS initial arrival_time is 07:14:00 - times do not match
Warnings
timestamp not populated W001 16 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 15458{03_4}-25U_PSC_LMCJVSDF_01_S does not have a timestamp
- trip_id 15483{03_4}-25U_PSC_LMCJVSDF_01_S does not have a timestamp
- trip_id 17876{01_3}-25U_PSC_LMCJVSDF_01_S does not have a timestamp
- trip_id 15570{02_2}-25U_PSC_LMCJVSDF_01_S does not have a timestamp
- trip_id 15599{02_2}-25U_PSC_LMCJVSDF_01_S does not have a timestamp
vehicle_id not populated W002 2 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4-10066657284 does not have a vehicle_id
- trip_id 4-10066657283 does not have a vehicle_id
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 | 331 | 25 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 331 | 25 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 410 | 25 times (83 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 580 | 25 times (83 % of validations) |
| W001 | Timestamps should be populated for all elements | 787 | 25 times (83 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 197 | 25 times (83 % 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. | 14 | 9 times (30 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-06 at 22:30 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-12-06 at 22:30 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1765056613"
}
}