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, 20 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-16 at 09:05 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 217 at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 56 at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.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 217 does not have a timestamp
- vehicle_id 56 does not have a timestamp
schedule_relationship not populated W009 18 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id b6102267-9fcf-49ea-a94c-cd37c92b7fc4 does not have a schedule_relationship
- trip_id 565d485f-683a-4150-bbe7-4e34ec0784b7 does not have a schedule_relationship
- trip_id 94c299ec-b41c-4c67-808d-98ad9909e81f does not have a schedule_relationship
- trip_id 87dffe7f-c8ce-4e70-9b9b-237bc7c333f5 does not have a schedule_relationship
- trip_id ab7ee290-2bd6-4522-a5d7-933d94cf2450 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 | 484 | 24 times (80 % 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. | 144 | 23 times (77 % of validations) |
| W001 | Timestamps should be populated for all elements | 55 | 22 times (73 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 16 | 16 times (53 % 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.