Resource details
This resource file is part of the dataset Réseau urbain TGL.
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
❌310 errors, 101 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-18 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 208 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 cae0fbd7-394d-48cc-8c86-41aa467deb72 stop_sequence 39 arrival_time 09:29:59 (1758180599) is equal to previous stop arrival_time 09:29:59 (1758180599) - times must increase between two sequential stops
- trip_id cae0fbd7-394d-48cc-8c86-41aa467deb72 stop_sequence 39 arrival_time 09:29:59 (1758180599) is equal to previous stop departure_time 09:29:59 (1758180599) - times must increase between two sequential stops
- trip_id cae0fbd7-394d-48cc-8c86-41aa467deb72 stop_sequence 39 departure_time 09:29:59 (1758180599) is equal to previous stop departure_time 09:29:59 (1758180599) - times must increase between two sequential stops
- trip_id cae0fbd7-394d-48cc-8c86-41aa467deb72 stop_sequence 39 departure_time 09:29:59 (1758180599) is equal to previous stop arrival_time 09:29:59 (1758180599) - times must increase between two sequential stops
- trip_id 176776-2020-_ABCDSN-Semaine-01 stop_sequence 25 arrival_time 09:10:08 (1758179408) is equal to previous stop departure_time 09:10:08 (1758179408) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 96 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 176776-2020-_ABCDSN-Semaine-01 stop_sequence 5 has stop_id 1041A but GTFS stop_sequence 5 has stop_id 01005 - stop_ids should be the same
- GTFS-rt trip_id 176776-2020-_ABCDSN-Semaine-01 stop_sequence 6 has stop_id 01005 but GTFS stop_sequence 6 has stop_id 01010A - stop_ids should be the same
- GTFS-rt trip_id 176776-2020-_ABCDSN-Semaine-01 stop_sequence 7 has stop_id 01010A but GTFS stop_sequence 7 has stop_id 01000A - stop_ids should be the same
- GTFS-rt trip_id 176776-2020-_ABCDSN-Semaine-01 stop_sequence 8 has stop_id 01000A but GTFS stop_sequence 8 has stop_id 01050A - stop_ids should be the same
- GTFS-rt trip_id 176776-2020-_ABCDSN-Semaine-01 stop_sequence 9 has stop_id 01050A but GTFS stop_sequence 9 has stop_id 01040A - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 6 errors
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Sample errors
- GTFS-rt trip_id 176776-2020-_ABCDSN-Semaine-01 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 349a5998-1249-4675-a887-c57b59a57c7c contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id b1290f90-21fd-4e05-aa17-47bcdcf16bef contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id c6dd3725-7faa-44ae-9a9b-3e71e3d76fdd contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 30b080b0-b9d8-4db9-bcd9-9cbd037bb3bc contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 56 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 176863-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176742-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id cae0fbd7-394d-48cc-8c86-41aa467deb72 does not have a timestamp
- trip_id 176776-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176714-2020-_ABCDSN-Semaine-01 does not have a timestamp
vehicle_id not populated W002 45 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 77121a10-2fec-43c5-b6a1-34dc453e7241 does not have a vehicle_id
- trip_id c623f81c-5482-45c3-aec8-c78046779660 does not have a vehicle_id
- trip_id 182882-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 182873-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 182872-2020-_ABCDSN-Semaine-01 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 |
---|---|---|---|
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 5 179 | 27 times (87 % of validations) |
W001 | Timestamps should be populated for all elements | 1 284 | 27 times (87 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 011 | 27 times (87 % of validations) |
E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 1 474 | 18 times (58 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 89 | 18 times (58 % 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. | 34 | 15 times (48 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-18 at 21:36 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-18 at 21:36 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1758224197"
}
}