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
❌241 errors, 67 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-19 at 11:22 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 236 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 c623f81c-5482-45c3-aec8-c78046779660 stop_sequence 31 arrival_time 11:33:16 (1750325596) is equal to previous stop arrival_time 11:33:16 (1750325596) - times must increase between two sequential stops
- trip_id c623f81c-5482-45c3-aec8-c78046779660 stop_sequence 31 arrival_time 11:33:16 (1750325596) is equal to previous stop departure_time 11:33:16 (1750325596) - times must increase between two sequential stops
- trip_id c623f81c-5482-45c3-aec8-c78046779660 stop_sequence 31 departure_time 11:33:16 (1750325596) is equal to previous stop departure_time 11:33:16 (1750325596) - times must increase between two sequential stops
- trip_id c623f81c-5482-45c3-aec8-c78046779660 stop_sequence 31 departure_time 11:33:16 (1750325596) is equal to previous stop arrival_time 11:33:16 (1750325596) - times must increase between two sequential stops
- trip_id c623f81c-5482-45c3-aec8-c78046779660 stop_sequence 39 arrival_time 11:38:16 (1750325896) is equal to previous stop arrival_time 11:38:16 (1750325896) - 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 197a3a4b-a1cd-43ec-8c30-726265be0b56 start_time is 15:41:00 and GTFS initial arrival_time is 15:45: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 3ca92c7d-1298-4599-9345-0386f3d0040a stop_sequence 25 departure_time 11:32:57 (1750325577) is less than the same stop arrival_time 11:33:57 (1750325637) - departure time must be equal to or greater than arrival time
- trip_id cead8083-2af8-4cb1-bec2-35ae920505da stop_sequence 13 departure_time 16:19:00 (1750342740) is less than the same stop arrival_time 16:20:00 (1750342800) - 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:00 (1750350660) is less than the same stop arrival_time 18:32:00 (1750350720) - departure time must be equal to or greater than arrival time
GTFS-rt stop_sequence not found in GTFS data E051 1 error
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 197a3a4b-a1cd-43ec-8c30-726265be0b56 contains stop_sequence 12 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 39 errors
Timestamps should be populated for all elements
Sample errors
- trip_id bcc85a62-61ad-48b9-a36a-98b2f26be1ca does not have a timestamp
- trip_id 182868-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id c68f508f-fc3c-4b31-8fd2-ee28d98b6313 does not have a timestamp
- trip_id 176746-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id c623f81c-5482-45c3-aec8-c78046779660 does not have a timestamp
vehicle_id not populated W002 28 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 176853-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176844-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176842-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176835-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176832-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. | 1 130 | 5 times (100 % of validations) |
| W001 | Timestamps should be populated for all elements | 250 | 5 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 192 | 5 times (100 % 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. | 5 | 3 times (60 % 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 | 1 | 1 times (20 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 1 | 1 times (20 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-15 at 23:55 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-07-15 at 23:55 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1752616508"
}
}