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, 22 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-10 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position outside agency coverage area E028 2 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 21 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 14 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
Warnings
timestamp not populated W001 2 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 21 does not have a timestamp
- vehicle_id 14 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 1 min 41 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 19 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 9bb232b1-b6bd-407c-b40d-0eddd2870d3a does not have a schedule_relationship
- trip_id b5a9c3e7-ce32-4d64-a5a3-349a977a85c8 does not have a schedule_relationship
- trip_id 2da0bf15-3ba9-47fe-853b-98492c1d0798 does not have a schedule_relationship
- trip_id 69c3bac2-fa43-4dca-bc91-7116997f4688 does not have a schedule_relationship
- trip_id 34c3fb41-8084-47dd-9a38-be8c459e3897 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 | 360 | 24 times (86 % 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. | 43 | 21 times (75 % of validations) |
| W001 | Timestamps should be populated for all elements | 41 | 20 times (71 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 18 | 18 times (64 % 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. | 8 | 6 times (21 % 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.