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
❌144 errors, 25 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-01 at 08:02 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 6 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 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066722817 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066722818 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066722818 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066788355 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 6 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id B32_1 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 84 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id SBVBAIL1 does not exist in GTFS data stops.txt
- trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id SBVEMAT1 does not exist in GTFS data stops.txt
- trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHIEMAT1 does not exist in GTFS data stops.txt
- trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id SBVEMAT2 does not exist in GTFS data stops.txt
- trip_id 4-10066722817 stop_id 2863 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 46 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 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 arrival_time 08:16:18 (1764573378) is equal to previous stop arrival_time 08:16:18 (1764573378) - times must increase between two sequential stops
- trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 arrival_time 08:16:18 (1764573378) is equal to previous stop departure_time 08:16:18 (1764573378) - times must increase between two sequential stops
- trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 departure_time 08:16:18 (1764573378) is equal to previous stop departure_time 08:16:18 (1764573378) - times must increase between two sequential stops
- trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 departure_time 08:16:18 (1764573378) is equal to previous stop arrival_time 08:16:18 (1764573378) - times must increase between two sequential stops
- trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 43 arrival_time 08:17:18 (1764573438) is equal to previous stop arrival_time 08:17:18 (1764573438) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 errors
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 17788{04_2}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 19 departure_time 08:01:00 (1764572460) is less than the same stop arrival_time 08:01:05 (1764572465) - departure time must be equal to or greater than arrival time
- trip_id 18000{01_3}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 14 departure_time 08:00:55 (1764572455) is less than the same stop arrival_time 08:01:46 (1764572506) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 24 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 15650{05_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 17972{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 17768{04_2}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 15418{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4-10066788356 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 | 332 | 24 times (80 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 332 | 24 times (80 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 409 | 24 times (80 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 455 | 24 times (80 % of validations) |
| W001 | Timestamps should be populated for all elements | 772 | 24 times (80 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 194 | 24 times (80 % 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. | 12 | 8 times (27 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-01 at 22:25 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-01 at 22:25 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764624352"
}
}