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-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%
2025-11-23
100%
2025-11-24
100%
2025-11-25
100%
2025-11-26
100%
2025-11-27
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

272 errors, 53 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-27 at 08:12 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 21 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 15345{B10_1}-24I_PSC_LMCJVSDF_03_LMWJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 14736{A33_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 15374{B31_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 15372{B30_1}-24I_PSC_LMCJVSDF_03_LMJV 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 21 errors

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

Sample errors
  • route_id B10_1 does not exist in the GTFS data routes.txt
  • route_id A33_1 does not exist in the GTFS data routes.txt
  • route_id B32_1 does not exist in the GTFS data routes.txt
  • route_id B31_1 does not exist in the GTFS data routes.txt
  • route_id B30_1 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id 14736{A33_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHELVAB1 does not exist in GTFS data stops.txt
  • trip_id 14736{A33_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHEMONT2 does not exist in GTFS data stops.txt
  • trip_id 14736{A33_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHEMABR2 does not exist in GTFS data stops.txt
  • trip_id 14736{A33_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHESLAV2 does not exist in GTFS data stops.txt
  • trip_id 14736{A33_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHESCDB1 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 76 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 17908{01_3}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 22 arrival_time 06:50:33 (1764222633) is less than previous stop arrival_time 08:05:37 (1764227137) - times must increase between two sequential stops
  • trip_id 17908{01_3}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 22 arrival_time 06:50:33 (1764222633) is less than previous stop departure_time 08:05:54 (1764227154) - times must increase between two sequential stops
  • trip_id 17908{01_3}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 22 departure_time 06:50:41 (1764222641) is less than previous stop departure_time 08:05:54 (1764227154) - times must increase between two sequential stops
  • trip_id 17908{01_3}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 22 departure_time 06:50:41 (1764222641) is less than previous stop arrival_time 08:05:37 (1764227137) - times must increase between two sequential stops
  • trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 43 arrival_time 08:13:36 (1764227616) is equal to previous stop arrival_time 08:13:36 (1764227616) - times must increase between two sequential stops

Warnings

timestamp not populated W001 41 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 17908{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
  • trip_id 15345{B10_1}-24I_PSC_LMCJVSDF_03_LMWJV does not have a timestamp
  • trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
  • trip_id 17788{04_2}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
  • trip_id 18000{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp

vehicle_id not populated W002 12 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
  • trip_id 4-10066657282 does not have a vehicle_id
  • trip_id 4-10066657281 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 333 24 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 333 24 times (80 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 3 431 24 times (80 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1 442 24 times (80 % of validations)
W001 Timestamps should be populated for all elements 774 24 times (80 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 202 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. 11 7 times (23 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-27 at 22:31 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-27 at 22:31 Europe/Paris. You can look at the GTFS-RT documentation.

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