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, 12 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-24 at 08:11 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 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.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 197 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 3 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 54 does not have a timestamp
- vehicle_id 21 does not have a timestamp
- vehicle_id 197 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 3 min 1 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 8 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id b5a9c3e7-ce32-4d64-a5a3-349a977a85c8 does not have a schedule_relationship
- trip_id 28e0fc94-9e42-46d3-9d77-a4981a6ab4b1 does not have a schedule_relationship
- trip_id bc706336-e4e1-4606-8404-9d7d2a16812c does not have a schedule_relationship
- trip_id 8cc89595-5360-49fd-ab8a-af60a414efdc does not have a schedule_relationship
- trip_id 9bb232b1-b6bd-407c-b40d-0eddd2870d3a 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 | 307 | 24 times (83 % 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. | 44 | 22 times (76 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 21 | 21 times (72 % of validations) |
| W001 | Timestamps should be populated for all elements | 40 | 20 times (69 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-25 at 05:00 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-02-25 at 05:00 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1771992010"
}
}