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
❌43 errors, 97 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-04 at 09:13 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 43 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 19538489 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 19522190 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 19522201 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 19538745 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 19538437 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Warnings
vehicle_id not populated W002 11 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 19538745 does not have a vehicle_id
- trip_id 19538859 does not have a vehicle_id
- trip_id 19538490 does not have a vehicle_id
- trip_id 19522248 does not have a vehicle_id
- trip_id 19522224 does not have a vehicle_id
schedule_relationship not populated W009 86 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 19538489 stop_id malilot1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 19538489 does not have a schedule_relationship
- trip_id 19522190 stop_id canegli2 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 19522190 does not have a schedule_relationship
- trip_id 19522201 stop_id sjgstad1 (and potentially more for this trip) does not have a schedule_relationship
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 |
---|---|---|---|
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 326 | 29 times (97 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 242 | 29 times (97 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 324 | 9 times (30 % of validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-05 at 02:04 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2024-05-05 at 02:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1714867480"
}
}