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

❌266 errors, 42 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:14 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 16 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 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 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 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 15372{B30_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 15376{B33_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 16 errors

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

Sample errors

route_id A33_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 B32_1 does not exist in the GTFS data routes.txt
route_id B30_1 does not exist in the GTFS data routes.txt
route_id B33_1 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 150 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 84 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}-24U_PSC_LMCJVSDF_03_LMWJV stop_sequence 41 arrival_time 08:18:18 (1734679098) is equal to previous stop arrival_time 08:18:18 (1734679098) - times must increase between two sequential stops
trip_id 15438{03_4}-24U_PSC_LMCJVSDF_03_LMWJV stop_sequence 41 arrival_time 08:18:18 (1734679098) is equal to previous stop departure_time 08:18:18 (1734679098) - times must increase between two sequential stops
trip_id 15438{03_4}-24U_PSC_LMCJVSDF_03_LMWJV stop_sequence 41 departure_time 08:18:18 (1734679098) is equal to previous stop departure_time 08:18:18 (1734679098) - times must increase between two sequential stops
trip_id 15438{03_4}-24U_PSC_LMCJVSDF_03_LMWJV stop_sequence 41 departure_time 08:18:18 (1734679098) is equal to previous stop arrival_time 08:18:18 (1734679098) - times must increase between two sequential stops
trip_id 15438{03_4}-24U_PSC_LMCJVSDF_03_LMWJV stop_sequence 43 arrival_time 08:19:18 (1734679158) is equal to previous stop arrival_time 08:19:18 (1734679158) - times must increase between two sequential stops

Warnings

timestamp not populated W001 34 errors

Timestamps should be populated for all elements

Sample errors

trip_id 15438{03_4}-24U_PSC_LMCJVSDF_03_LMWJV does not have a timestamp
trip_id 15036{04_2}-24U_PSC_LMCJVSDF_03_LMWJV does not have a timestamp
trip_id 15081{01_2}-24U_PSC_LMCJVSDF_03_LMWJV does not have a timestamp
trip_id 15419{03_4}-24U_PSC_LMCJVSDF_03_LMWJV does not have a timestamp
trip_id 15541{02_2}-24U_PSC_LMCJVSDF_03_LMWJV does not have a timestamp

vehicle_id not populated W002 8 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-10083303428 does not have a vehicle_id
trip_id 4-10083303427 does not have a vehicle_id
trip_id 4-10083172355 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	283	24 times (83 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	283	24 times (83 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	3 206	24 times (83 % of validations)
W001	Timestamps should be populated for all elements	647	24 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 736	23 times (79 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	171	23 times (79 % 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.	29	17 times (59 % 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 2024-12-22 at 04:03 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-12-22 at 04:03 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1734836624"
  }
}