Resource details
GTFS-RT (protobuff) global, regroupant les horaires aux arrêts, la position des véhicules et les perturbations.
This resource file is part of the dataset Réseaux urbain MOCA.
Download availability
Learn more
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
❌96 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:16 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 6 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 trip_id 6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 65c9ff65ad72f5762dead966 trip_id 5 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 6 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 6 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 route_id 2 does not exist in the GTFS data routes.txt
- vehicle_id 65c9ff65ad72f5762dead966 route_id 1 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 2 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 83 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 stop_id 30049 does not exist in GTFS data stops.txt
- vehicle_id 65c9ff65ad72f5762dead966 stop_id 30005 does not exist in GTFS data stops.txt
- trip_id 5 stop_id 30030 does not exist in GTFS data stops.txt
- trip_id 5 stop_id 30029 does not exist in GTFS data stops.txt
- trip_id 5 stop_id 30038 does not exist in GTFS data stops.txt
VehiclePosition and TripUpdate ID pairing mismatch E047 1 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id 5 and vehicle_id 65c9ff65ad72f5762dead966 pairing in VehiclePositions does not match trip_id 3 and vehicle_id 65c9ff65ad72f5762dead966 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Warnings
ID in one feed missing from the other W003 2 errors
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 1 is in TripUpdates but not in VehiclePositions feed
- trip_id 3 is in TripUpdates but not in VehiclePositions feed
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 | 100 | 9 times (100 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 100 | 9 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 656 | 9 times (100 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 64 | 9 times (100 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 10 | 6 times (67 % of validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 81 | 5 times (56 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-12-22 at 03:44 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2024-12-22 at 03:44 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1734835467"
}
}