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
❌614 errors, 160 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-27 at 08:18 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 470 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 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 arrival_time 08:19:14 (1764227954) is equal to previous stop arrival_time 08:19:14 (1764227954) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 arrival_time 08:19:14 (1764227954) is equal to previous stop departure_time 08:19:14 (1764227954) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 departure_time 08:19:14 (1764227954) is equal to previous stop departure_time 08:19:14 (1764227954) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 departure_time 08:19:14 (1764227954) is equal to previous stop arrival_time 08:19:14 (1764227954) - times must increase between two sequential stops
- trip_id ebc39ad1-bce6-43aa-bea3-f6c05ef5827b stop_sequence 27 arrival_time 08:22:27 (1764228147) is equal to previous stop arrival_time 08:22:27 (1764228147) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 3 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 8eb60bf2-e9af-4c92-aa89-f1ba3ab0eaac stop_sequence 2 departure_time 08:18:09 (1764227889) is less than the same stop arrival_time 08:18:26 (1764227906) - departure time must be equal to or greater than arrival time
- trip_id 3ca92c7d-1298-4599-9345-0386f3d0040a stop_sequence 25 departure_time 11:39:27 (1764239967) is less than the same stop arrival_time 11:40:27 (1764240027) - departure time must be equal to or greater than arrival time
- trip_id f570359b-7224-4ffe-8b90-853813fa8c29 stop_sequence 25 departure_time 18:37:27 (1764265047) is less than the same stop arrival_time 18:38:27 (1764265107) - departure time must be equal to or greater than arrival time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 135 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 176797-2020-_ABCDSN-Semaine-01 stop_sequence 25 has stop_id 1041 R but GTFS stop_sequence 25 has stop_id 01005R - stop_ids should be the same
- GTFS-rt trip_id 176797-2020-_ABCDSN-Semaine-01 stop_sequence 26 has stop_id 01005R but GTFS stop_sequence 26 has stop_id 01010R - stop_ids should be the same
- GTFS-rt trip_id 176797-2020-_ABCDSN-Semaine-01 stop_sequence 27 has stop_id 01010R but GTFS stop_sequence 27 has stop_id 01000R - stop_ids should be the same
- GTFS-rt trip_id 176797-2020-_ABCDSN-Semaine-01 stop_sequence 28 has stop_id 01000R but GTFS stop_sequence 28 has stop_id 01050R - stop_ids should be the same
- GTFS-rt trip_id 176797-2020-_ABCDSN-Semaine-01 stop_sequence 29 has stop_id 01050R but GTFS stop_sequence 29 has stop_id 01040R - 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 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
- GTFS-rt trip_id 9c5e35b5-3d28-4ed8-83f7-df0deb134bf7 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 89 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 176859-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176876-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176740-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id ebc39ad1-bce6-43aa-bea3-f6c05ef5827b does not have a timestamp
- trip_id 190971-2020-MulScol-L-Ma-J-V-00 does not have a timestamp
vehicle_id not populated W002 71 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 176748-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176745-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176742-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176721-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176718-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. | 8 734 | 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. | 61 | 24 times (80 % of validations) |
| W001 | Timestamps should be populated for all elements | 1 800 | 24 times (80 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 445 | 24 times (80 % 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 | 2 458 | 23 times (77 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 92 | 22 times (73 % 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 | 15 | 15 times (50 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-28 at 00:44 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-11-28 at 00:44 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764287099"
}
}