Resource details
This resource file is part of the dataset Réseau urbain Forbus.
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
❌5 errors, 17 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-28 at 09:06 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 1 error
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 47 stop_id STP-CEUROP02 does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 3 errors
The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.
Sample errors
- vehicle.id 43 at (49.12424,6.774659) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 37 at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 54 at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Vehicle position far from trip shape E029 1 error
The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.
Sample errors
- vehicle.id 47 trip_id 2d378fef-be47-46ce-89b9-19322a75ddd7 at (49.18052,6.888155) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
timestamp not populated W001 2 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 37 does not have a timestamp
- vehicle_id 54 does not have a timestamp
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 889 min 44 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 14 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id cbd50a64-ce1c-4856-b2a0-32a86d3f21a3 does not have a schedule_relationship
- trip_id 0e20fad9-616e-41ad-a6ad-a1db1a037071 does not have a schedule_relationship
- trip_id 2d378fef-be47-46ce-89b9-19322a75ddd7 does not have a schedule_relationship
- trip_id a087e810-7216-4b3a-8963-1717b3942fa9 does not have a schedule_relationship
- trip_id 58695927 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 |
|---|---|---|---|
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 25 | 25 times (86 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 232 | 19 times (66 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 19 | 13 times (45 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 18 | 7 times (24 % of validations) |
| W001 | Timestamps should be populated for all elements | 17 | 7 times (24 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 | 2 times (7 % 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.