transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: GTFS-RT
Format: gtfs-rt

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

Download availability

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

Validation details

❌776 errors, 1 warning

Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-12 at 09:04 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 27 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 3892028-B-PS-2324B-10DI-Dimanche does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3892045-B-PS-2324B-10DI-Dimanche does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3842119-B-PS-2324B-11DI-Dimanche does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3842095-B-PS-2324B-12DI-Dimanche does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3841706-B-PS-2324B-16DI-Dimanche 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 31 errors

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

Sample errors
  • route_id 10 does not exist in the GTFS data routes.txt
  • route_id 10 does not exist in the GTFS data routes.txt
  • route_id 11 does not exist in the GTFS data routes.txt
  • route_id 12 does not exist in the GTFS data routes.txt
  • route_id 16 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id 3892028-B-PS-2324B-10DI-Dimanche stop_id 3016 does not exist in GTFS data stops.txt
  • trip_id 3892028-B-PS-2324B-10DI-Dimanche stop_id 2339 does not exist in GTFS data stops.txt
  • trip_id 3892028-B-PS-2324B-10DI-Dimanche stop_id 2707 does not exist in GTFS data stops.txt
  • trip_id 3892028-B-PS-2324B-10DI-Dimanche stop_id 2840 does not exist in GTFS data stops.txt
  • trip_id 3892028-B-PS-2324B-10DI-Dimanche stop_id 2364 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 6 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 3841857-B-PS-2324B-04DI-Dimanche stop_id 2888 arrival_time 09:25:01 (1715498701) is less than previous stop arrival_time 09:25:28 (1715498728) - times must increase between two sequential stops
  • trip_id 3841857-B-PS-2324B-04DI-Dimanche stop_id 2888 arrival_time 09:25:01 (1715498701) is less than previous stop departure_time 09:25:28 (1715498728) - times must increase between two sequential stops
  • trip_id 3841857-B-PS-2324B-04DI-Dimanche stop_id 2888 departure_time 09:25:01 (1715498701) is less than previous stop departure_time 09:25:28 (1715498728) - times must increase between two sequential stops
  • trip_id 3841857-B-PS-2324B-04DI-Dimanche stop_id 2888 departure_time 09:25:01 (1715498701) is less than previous stop arrival_time 09:25:28 (1715498728) - times must increase between two sequential stops
  • trip_id 3910049-T-PS-2324A-TDIGPT1-Diman stop_id 1011 departure_time 09:04:25 (1715497465) is less than previous stop departure_time 09:04:38 (1715497478) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 3842119-B-PS-2324B-11DI-Dimanche 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 1 887 28 times (97 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 1 893 28 times (97 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 45 882 28 times (97 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 2 526 28 times (97 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 31 16 times (55 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 22 1 times (3 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.