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
❌498 errors, 147 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-20 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 370 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:34 (1763623174) is equal to previous stop arrival_time 08:19:34 (1763623174) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 arrival_time 08:19:34 (1763623174) is equal to previous stop departure_time 08:19:34 (1763623174) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 departure_time 08:19:34 (1763623174) is equal to previous stop departure_time 08:19:34 (1763623174) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 departure_time 08:19:34 (1763623174) is equal to previous stop arrival_time 08:19:34 (1763623174) - times must increase between two sequential stops
- trip_id ebc39ad1-bce6-43aa-bea3-f6c05ef5827b stop_sequence 17 arrival_time 08:03:58 (1763622238) is equal to previous stop arrival_time 08:03:58 (1763622238) - 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 d3525cf6-5cc7-4697-9b63-1546088dddc8 start_time is 07:45:00 and GTFS initial arrival_time is 07:49:00 - times do not match
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 ebc39ad1-bce6-43aa-bea3-f6c05ef5827b stop_sequence 15 departure_time 08:01:58 (1763622118) is less than the same stop arrival_time 08:02:01 (1763622121) - departure time must be equal to or greater than arrival time
- trip_id 3ca92c7d-1298-4599-9345-0386f3d0040a stop_sequence 25 departure_time 11:33:58 (1763634838) is less than the same stop arrival_time 11:34:58 (1763634898) - departure time must be equal to or greater than arrival time
- trip_id f570359b-7224-4ffe-8b90-853813fa8c29 stop_sequence 25 departure_time 18:31:58 (1763659918) is less than the same stop arrival_time 18:32:58 (1763659978) - 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 120 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 176791-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 176791-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 176791-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 176791-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 176791-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 4 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 176791-2020-_ABCDSN-Semaine-01 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
- 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
Warnings
timestamp not populated W001 83 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 176859-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176791-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 0b3e3cf1-cc4b-42a1-b01e-880e3e605ae9 does not have a timestamp
- trip_id 176876-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176711-2020-_ABCDSN-Semaine-01 does not have a timestamp
vehicle_id not populated W002 64 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 4c63dd69-2e0c-4d5a-8390-268faac3c3ff does not have a vehicle_id
- trip_id 182884-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 182878-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 182875-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 182863-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. | 7 317 | 24 times (80 % of validations) |
| W001 | Timestamps should be populated for all elements | 1 576 | 24 times (80 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 267 | 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. | 62 | 23 times (77 % 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 981 | 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 | 74 | 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 | 11 | 11 times (37 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-21 at 04:20 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-21 at 04:20 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1763695206"
}
}