Resource details

File name: Extension GTFS-RT : Mises à jour de trajet
Format: gtfs-rt

Les mises à jour de trajet représentent des fluctuations dans les horaires

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

Download availability

2025-11-23
100%
2025-11-24
100%
2025-11-25
100%
2025-11-26
100%
2025-11-27
100%
2025-11-28
100%
2025-11-29
100%
2025-11-30
100%
2025-12-01
100%
2025-12-02
100%
2025-12-03
100%
2025-12-04
100%
2025-12-05
100%
2025-12-06
100%
2025-12-07
100%
2025-12-08
100%
2025-12-09
100%
2025-12-10
100%
2025-12-11
100%
2025-12-12
100%
2025-12-13
100%
2025-12-14
100%
2025-12-15
100%
2025-12-16
100%
2025-12-17
100%
2025-12-18
100%
2025-12-19
100%
2025-12-20
100%
2025-12-21
100%
2025-12-22
100%
2025-12-23
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

131 errors, 23 warnings

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 5 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • trip_id 4-10066395137 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 4-10066657282 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 4-10066657284 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 4-10066657283 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 4-10066395139 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 5 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id 600 does not exist in the GTFS data routes.txt
  • route_id 600 does not exist in the GTFS data routes.txt
  • route_id 600 does not exist in the GTFS data routes.txt
  • route_id 600 does not exist in the GTFS data routes.txt
  • route_id 600 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 55 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • trip_id 4-10066395137 stop_id 3159 does not exist in GTFS data stops.txt
  • trip_id 4-10066395137 stop_id 3160 does not exist in GTFS data stops.txt
  • trip_id 4-10066395137 stop_id 3161 does not exist in GTFS data stops.txt
  • trip_id 4-10066395137 stop_id 3162 does not exist in GTFS data stops.txt
  • trip_id 4-10066395137 stop_id 3163 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 65 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 19717{01_3}-25U_PVS_LMCJVSDF_01_LMWJV stop_sequence 9 arrival_time 07:46:59 (1766386019) is equal to previous stop arrival_time 07:46:59 (1766386019) - times must increase between two sequential stops
  • trip_id 19717{01_3}-25U_PVS_LMCJVSDF_01_LMWJV stop_sequence 9 arrival_time 07:46:59 (1766386019) is equal to previous stop departure_time 07:46:59 (1766386019) - times must increase between two sequential stops
  • trip_id 19717{01_3}-25U_PVS_LMCJVSDF_01_LMWJV stop_sequence 9 departure_time 07:46:59 (1766386019) is equal to previous stop departure_time 07:46:59 (1766386019) - times must increase between two sequential stops
  • trip_id 19717{01_3}-25U_PVS_LMCJVSDF_01_LMWJV stop_sequence 9 departure_time 07:46:59 (1766386019) is equal to previous stop arrival_time 07:46:59 (1766386019) - times must increase between two sequential stops
  • trip_id 19717{01_3}-25U_PVS_LMCJVSDF_01_LMWJV stop_sequence 13 arrival_time 07:49:59 (1766386199) is equal to previous stop arrival_time 07:49:59 (1766386199) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 1 error

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 19678{04_2}-25U_PVS_LMCJVSDF_01_LMWJV stop_sequence 27 departure_time 08:08:09 (1766387289) is less than the same stop arrival_time 08:09:56 (1766387396) - departure time must be equal to or greater than arrival time

Warnings

timestamp not populated W001 20 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 19717{01_3}-25U_PVS_LMCJVSDF_01_LMWJV does not have a timestamp
  • trip_id 19846{03_4}-25U_PVS_LMCJVSDF_01_LMWJV does not have a timestamp
  • trip_id 19759{01_3}-25U_PVS_LMCJVSDF_01_LMWJV does not have a timestamp
  • trip_id 19728{01_3}-25U_PVS_LMCJVSDF_01_LMWJV does not have a timestamp
  • trip_id 19678{04_2}-25U_PVS_LMCJVSDF_01_LMWJV does not have a timestamp

vehicle_id not populated W002 3 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 4-10066657284 does not have a vehicle_id
  • trip_id 4-10066657283 does not have a vehicle_id
  • trip_id 4-10066395139 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 356 25 times (83 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 356 25 times (83 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 3,574 25 times (83 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1,615 25 times (83 % of validations)
W001 Timestamps should be populated for all elements 815 25 times (83 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 221 25 times (83 % 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. 18 11 times (37 % 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 2 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-23 at 05:08 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-12-23 at 05:08 Europe/Paris. You can look at the GTFS-RT documentation.

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