Resource details

File name: Temps réel TGL au format GTFS-RT
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain TGL.

Download availability

2025-10-23
100%
2025-10-24
100%
2025-10-25
100%
2025-10-26
100%
2025-10-27
100%
2025-10-28
100%
2025-10-29
100%
2025-10-30
100%
2025-10-31
100%
2025-11-01
100%
2025-11-02
100%
2025-11-03
100%
2025-11-04
100%
2025-11-05
100%
2025-11-06
100%
2025-11-07
100%
2025-11-08
100%
2025-11-09
100%
2025-11-10
100%
2025-11-11
100%
2025-11-12
100%
2025-11-13
100%
2025-11-14
100%
2025-11-15
100%
2025-11-16
100%
2025-11-17
100%
2025-11-18
100%
2025-11-19
100%
2025-11-20
100%
2025-11-21
100%
2025-11-22
100%
Learn more
We test this resource download availability every hour by making an HTTP 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

299 errors, 109 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-22 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_update times are not increasing E022 243 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 26a96eae-bd17-46f9-92dc-109c9d5ffeae stop_sequence 30 arrival_time 08:30:02 (1763796602) is equal to previous stop arrival_time 08:30:02 (1763796602) - times must increase between two sequential stops
  • trip_id 26a96eae-bd17-46f9-92dc-109c9d5ffeae stop_sequence 30 arrival_time 08:30:02 (1763796602) is equal to previous stop departure_time 08:30:02 (1763796602) - times must increase between two sequential stops
  • trip_id 26a96eae-bd17-46f9-92dc-109c9d5ffeae stop_sequence 30 departure_time 08:30:02 (1763796602) is equal to previous stop departure_time 08:30:02 (1763796602) - times must increase between two sequential stops
  • trip_id 26a96eae-bd17-46f9-92dc-109c9d5ffeae stop_sequence 30 departure_time 08:30:02 (1763796602) is equal to previous stop arrival_time 08:30:02 (1763796602) - times must increase between two sequential stops
  • trip_id 6786da8b-9766-4b91-837d-78065ea6bf6e stop_sequence 19 departure_time 08:02:39 (1763794959) is equal to previous stop departure_time 08:02:39 (1763794959) - 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 6786da8b-9766-4b91-837d-78065ea6bf6e stop_sequence 19 departure_time 08:02:39 (1763794959) is less than the same stop arrival_time 08:02:58 (1763794978) - departure time must be equal to or greater than arrival time
  • trip_id bb3c4974-915f-4c67-99e2-d7a2bbdffc7f stop_sequence 25 departure_time 11:39:00 (1763807940) is less than the same stop arrival_time 11:40:00 (1763808000) - 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 52 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 4d834578-3b28-4346-bdee-729f96e35db7 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 4d834578-3b28-4346-bdee-729f96e35db7 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 4d834578-3b28-4346-bdee-729f96e35db7 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 4d834578-3b28-4346-bdee-729f96e35db7 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 4d834578-3b28-4346-bdee-729f96e35db7 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 2 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 53a00efb-f63f-40a3-ba57-8b35f9bf62a1 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 6301e411-af19-405b-9dde-c49af42d024a contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip

Warnings

timestamp not populated W001 59 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 176711-2020-_ABCDSN-Semaine-01 does not have a timestamp
  • trip_id 177011-2020-_ABCDSN-Samedi-01 does not have a timestamp
  • trip_id 176740-2020-_ABCDSN-Semaine-01 does not have a timestamp
  • trip_id 26a96eae-bd17-46f9-92dc-109c9d5ffeae does not have a timestamp
  • trip_id 6786da8b-9766-4b91-837d-78065ea6bf6e does not have a timestamp

vehicle_id not populated W002 50 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id b38319dc-db4b-4182-ace1-4b9d06c8900e does not have a vehicle_id
  • trip_id 79c4007f-3a45-4241-baf5-40ed57ed7949 does not have a vehicle_id
  • trip_id 8374af01-32ff-487a-8c3f-8d701f7cbe83 does not have a vehicle_id
  • trip_id b13ecfa2-6cee-4f13-b435-dcecca7cd64d does not have a vehicle_id
  • trip_id f068053b-9b7f-45ed-8395-f01499fdf4ff does not have a vehicle_id
Validate this GTFS-RT now

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 704 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. 65 24 times (80 % of validations)
W001 Timestamps should be populated for all elements 1 649 24 times (80 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 328 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 101 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 78 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 12 12 times (40 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-23 at 00:50 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-11-23 at 00:50 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1763855404" } }