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
❌2 errors, 13 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-13 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position outside agency coverage area E028 1 error
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 19 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 58 trip_id 844a4fb6-5bde-4da0-b1e8-e4ad95d6b9d0 at (49.15343,6.855801) 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 1 error
Timestamps should be populated for all elements
Sample errors
- vehicle_id 19 does not have a timestamp
schedule_relationship not populated W009 12 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id a3771287-b9c4-4265-85e0-5d753a3bedbb does not have a schedule_relationship
- trip_id 9bb232b1-b6bd-407c-b40d-0eddd2870d3a does not have a schedule_relationship
- trip_id f9db1194-258a-42e8-94da-86e787440ad6 does not have a schedule_relationship
- trip_id 8cdb3360-1b74-4c36-89ff-e9bdc46f0b78 does not have a schedule_relationship
- trip_id b5a9c3e7-ce32-4d64-a5a3-349a977a85c8 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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 204 | 17 times (81 % 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 | 11 times (52 % of validations) |
| W001 | Timestamps should be populated for all elements | 18 | 11 times (52 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 11 | 11 times (52 % 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. | 9 | 9 times (43 % 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.