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
❌246 errors, 32 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-15 at 09:14 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 10 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-10066526209 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066395137 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066395137 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-10066722820 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 10 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 600 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
- route_id 600 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 145 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 4-10066526209 stop_id 3178 does not exist in GTFS data stops.txt
- trip_id 4-10066526209 stop_id 3179 does not exist in GTFS data stops.txt
- trip_id 4-10066526209 stop_id 3180 does not exist in GTFS data stops.txt
- trip_id 4-10066526209 stop_id 3181 does not exist in GTFS data stops.txt
- trip_id 4-10066526209 stop_id 3182 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 80 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 4-10066526209 stop_sequence 14 arrival_time 06:55:06 (1757912106) is less than previous stop arrival_time 08:58:07 (1757919487) - times must increase between two sequential stops
- trip_id 4-10066526209 stop_sequence 14 arrival_time 06:55:06 (1757912106) is less than previous stop departure_time 08:58:07 (1757919487) - times must increase between two sequential stops
- trip_id 4-10066526209 stop_sequence 14 departure_time 07:00:19 (1757912419) is less than previous stop departure_time 08:58:07 (1757919487) - times must increase between two sequential stops
- trip_id 4-10066526209 stop_sequence 14 departure_time 07:00:19 (1757912419) is less than previous stop arrival_time 08:58:07 (1757919487) - times must increase between two sequential stops
- trip_id 15440{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 26 arrival_time 09:17:38 (1757920658) is equal to previous stop arrival_time 09:17:38 (1757920658) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 5634{N_1}-25U_PSC_LMCJVSDF_01_LMWJVS stop_sequence 12 departure_time 09:14:11 (1757920451) is less than the same stop arrival_time 09:14:19 (1757920459) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 26 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 15420{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 17770{04_2}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 18001{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 4-10066526209 does not have a timestamp
- trip_id 15440{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
vehicle_id not populated W002 6 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4-10066722820 does not have a vehicle_id
- trip_id 4-10066722819 does not have a vehicle_id
- trip_id 4-10066526211 does not have a vehicle_id
- trip_id 4-10066788354 does not have a vehicle_id
- trip_id 4-10066788353 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 |
---|---|---|---|
W001 | Timestamps should be populated for all elements | 677 | 32 times (100 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 746 | 31 times (97 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 314 | 27 times (84 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 314 | 27 times (84 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 765 | 27 times (84 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 239 | 26 times (81 % 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 | 12 times (38 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-16 at 03:46 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-09-16 at 03:46 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1757987176"
}
}