Resource details
Download availability
Learn more
We test this resource download availability every hour by making an HTTPHEAD
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
❌2 811 errors, 1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2023-11-29 at 08:06 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 106 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 3769905-B-PS-2324A-10-Semaine-00 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3769906-B-PS-2324A-10-Semaine-00 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3769897-B-PS-2324A-10-Semaine-00 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3769898-B-PS-2324A-10-Semaine-00 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3769798-B-PS-2324A-11-Semaine-00 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 106 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 10B does not exist in the GTFS data routes.txt
- route_id 10B does not exist in the GTFS data routes.txt
- route_id 10A does not exist in the GTFS data routes.txt
- route_id 10A does not exist in the GTFS data routes.txt
- route_id 11 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 2 506 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 3769905-B-PS-2324A-10-Semaine-00 stop_id 2623 does not exist in GTFS data stops.txt
- trip_id 3769905-B-PS-2324A-10-Semaine-00 stop_id 2542 does not exist in GTFS data stops.txt
- trip_id 3769905-B-PS-2324A-10-Semaine-00 stop_id 2601 does not exist in GTFS data stops.txt
- trip_id 3769905-B-PS-2324A-10-Semaine-00 stop_id 3074 does not exist in GTFS data stops.txt
- trip_id 3769905-B-PS-2324A-10-Semaine-00 stop_id 2201 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 93 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 3769906-B-PS-2324A-10-Semaine-00 stop_id 2601 arrival_time 08:05:46 (1701241546) is equal to previous stop arrival_time 08:05:46 (1701241546) - times must increase between two sequential stops
- trip_id 3769906-B-PS-2324A-10-Semaine-00 stop_id 2601 arrival_time 08:05:46 (1701241546) is equal to previous stop departure_time 08:05:46 (1701241546) - times must increase between two sequential stops
- trip_id 3769906-B-PS-2324A-10-Semaine-00 stop_id 2601 departure_time 08:05:46 (1701241546) is equal to previous stop departure_time 08:05:46 (1701241546) - times must increase between two sequential stops
- trip_id 3769906-B-PS-2324A-10-Semaine-00 stop_id 2601 departure_time 08:05:46 (1701241546) is equal to previous stop arrival_time 08:05:46 (1701241546) - times must increase between two sequential stops
- trip_id 3769906-B-PS-2324A-10-Semaine-00 stop_id 3074 arrival_time 08:05:46 (1701241546) is equal to previous stop arrival_time 08:05:46 (1701241546) - 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 3769437-B-PS-2324A-16-Semaine-00 does not have a vehicle_id
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 | 2 455 | 30 times (100 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 2 457 | 30 times (100 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 59 506 | 30 times (100 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 797 | 30 times (100 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 39 | 23 times (77 % 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.