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éseau urbain Hobus.
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
❌122 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-01-23 at 08:10 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 4 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 67515ef7cb498f5037dede09 trip_id 58 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 56 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 58 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 55 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 4 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 67515ef7cb498f5037dede09 route_id A does not exist in the GTFS data routes.txt
- route_id A does not exist in the GTFS data routes.txt
- route_id A does not exist in the GTFS data routes.txt
- route_id A does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 64 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 67515ef7cb498f5037dede09 stop_id 28 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 2 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 4 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 6 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 8 does not exist in GTFS data stops.txt
stop_time_update doesn't have arrival or departure E043 49 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id 56 stop_sequence 0 doesn't have arrival or departure
- trip_id 56 stop_sequence 1 doesn't have arrival or departure
- trip_id 56 stop_sequence 2 doesn't have arrival or departure
- trip_id 56 stop_sequence 3 doesn't have arrival or departure
- trip_id 56 stop_sequence 4 doesn't have arrival or departure
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 58 and vehicle_id 67515ef7cb498f5037dede09 pairing in VehiclePositions does not match trip_id 55 and vehicle_id 67515ef7cb498f5037dede09 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 55 is in TripUpdates but not in VehiclePositions feed
- trip_id 56 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 | 57 | 7 times (88 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 57 | 7 times (88 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 957 | 7 times (88 % 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 | 33 | 6 times (75 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 8 | 5 times (63 % 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 | 366 | 4 times (50 % 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.