gtfs-rt Transport open dataset - Extension GTFS-RT : Mises à jour de trajet for Réseau urbain Léo

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

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

❌247 errors, 52 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-09 at 08:00 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 19 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 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 4-10066395137 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 4-10116988929 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 4-10117251074 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 4-10117316612 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 19 errors

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

Sample errors

route_id B32_1 does not exist in the GTFS data routes.txt
route_id 600 does not exist in the GTFS data routes.txt
route_id 603 does not exist in the GTFS data routes.txt
route_id 603 does not exist in the GTFS data routes.txt
route_id 603 does not exist in the GTFS data routes.txt

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

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

Sample errors

trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id SBVBAIL1 does not exist in GTFS data stops.txt
trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id SBVEMAT1 does not exist in GTFS data stops.txt
trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHIEMAT1 does not exist in GTFS data stops.txt
trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id SBVEMAT2 does not exist in GTFS data stops.txt
trip_id 4-10066395137 stop_id 3159 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 47 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 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 arrival_time 08:11:18 (1765264278) is equal to previous stop arrival_time 08:11:18 (1765264278) - times must increase between two sequential stops
trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 arrival_time 08:11:18 (1765264278) is equal to previous stop departure_time 08:11:18 (1765264278) - times must increase between two sequential stops
trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 departure_time 08:11:18 (1765264278) is equal to previous stop departure_time 08:11:18 (1765264278) - times must increase between two sequential stops
trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 departure_time 08:11:18 (1765264278) is equal to previous stop arrival_time 08:11:18 (1765264278) - times must increase between two sequential stops
trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 43 arrival_time 08:12:18 (1765264338) is equal to previous stop arrival_time 08:12:18 (1765264338) - times must increase between two sequential stops

Warnings

timestamp not populated W001 37 errors

Timestamps should be populated for all elements

Sample errors

trip_id 15601{05_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 17768{04_2}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 15418{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 17986{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp

vehicle_id not populated W002 15 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 4-10117316612 does not have a vehicle_id
trip_id 4-10117316611 does not have a vehicle_id
trip_id 4-10116988931 does not have a vehicle_id
trip_id 4-10117316610 does not have a vehicle_id
trip_id 4-10117316609 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	346	25 times (83 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	346	25 times (83 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	3 476	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 621	25 times (83 % of validations)
W001	Timestamps should be populated for all elements	813	25 times (83 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	209	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.	16	9 times (30 % 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 (3 % of validations)

GTFS-RT feed content

Entities

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


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