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

❌234 errors, 37 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-03 at 09:07 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 11 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-10066591745 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-10066591747 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

GTFS-rt route_id does not exist in GTFS data E004 11 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 129 errors

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

Sample errors

trip_id 4-10066591745 stop_id 3190 does not exist in GTFS data stops.txt
trip_id 4-10066591745 stop_id 3191 does not exist in GTFS data stops.txt
trip_id 4-10066591745 stop_id 3192 does not exist in GTFS data stops.txt
trip_id 4-10066591745 stop_id 3193 does not exist in GTFS data stops.txt
trip_id 4-10066591745 stop_id 3194 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 82 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 15420{03_4}-24U_PSC_LMCJVSDF_04_LMWJV stop_sequence 34 arrival_time 09:07:39 (1743664059) is equal to previous stop arrival_time 09:07:39 (1743664059) - times must increase between two sequential stops
trip_id 15420{03_4}-24U_PSC_LMCJVSDF_04_LMWJV stop_sequence 34 arrival_time 09:07:39 (1743664059) is equal to previous stop departure_time 09:07:39 (1743664059) - times must increase between two sequential stops
trip_id 15420{03_4}-24U_PSC_LMCJVSDF_04_LMWJV stop_sequence 34 departure_time 09:07:39 (1743664059) is equal to previous stop departure_time 09:07:39 (1743664059) - times must increase between two sequential stops
trip_id 15420{03_4}-24U_PSC_LMCJVSDF_04_LMWJV stop_sequence 34 departure_time 09:07:39 (1743664059) is equal to previous stop arrival_time 09:07:39 (1743664059) - times must increase between two sequential stops
trip_id 15420{03_4}-24U_PSC_LMCJVSDF_04_LMWJV stop_sequence 38 arrival_time 09:12:39 (1743664359) is equal to previous stop arrival_time 09:12:39 (1743664359) - 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 17790{04_2}-24U_PSC_LMCJVSDF_04_LMWJV stop_sequence 5 departure_time 08:56:38 (1743663398) is less than the same stop arrival_time 08:57:00 (1743663420) - departure time must be equal to or greater than arrival time

Warnings

timestamp not populated W001 29 errors

Timestamps should be populated for all elements

Sample errors

trip_id 15420{03_4}-24U_PSC_LMCJVSDF_04_LMWJV does not have a timestamp
trip_id 17925{01_3}-24U_PSC_LMCJVSDF_04_LMWJV does not have a timestamp
trip_id 17770{04_2}-24U_PSC_LMCJVSDF_04_LMWJV does not have a timestamp
trip_id 18001{01_3}-24U_PSC_LMCJVSDF_04_LMWJV does not have a timestamp
trip_id 15514{02_2}-24U_PSC_LMCJVSDF_04_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-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
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1 761	27 times (90 % of validations)
W001	Timestamps should be populated for all elements	842	27 times (90 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	399	26 times (87 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	399	26 times (87 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	4 314	26 times (87 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	259	26 times (87 % 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.	22	13 times (43 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 03:24 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-04-04 at 03:24 Europe/Paris. You can look at the GTFS-RT documentation.


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