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
❌3 errors, 18 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-10-26 at 08:24 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
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 190 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 8 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 57 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 3 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 190 does not have a timestamp
- vehicle_id 8 does not have a timestamp
- vehicle_id 57 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 2 min 38 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 a69a4ae5-2ec8-46e8-a2eb-239df667cdf4 does not have a schedule_relationship
- trip_id fdb4bd47-5c19-477f-a767-bb5677bcf5a6 does not have a schedule_relationship
- trip_id 3c230d4c-ca01-49a7-a6a8-e7265e820f08 does not have a schedule_relationship
- trip_id b8bf9c53-0406-4801-bf60-b5412b1dea8c does not have a schedule_relationship
- trip_id 30f82adf-8721-4ae0-9865-e029b75a1bc2 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 |
|---|---|---|---|
| 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. | 71 | 25 times (83 % of validations) |
| W001 | Timestamps should be populated for all elements | 71 | 25 times (83 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 439 | 25 times (83 % 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.