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, 9 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-31 at 08:08 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 60 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 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
Warnings
timestamp not populated W001 2 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 60 does not have a timestamp
- vehicle_id 54 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 12 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 6 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 2c61ca2f-3976-4643-a5de-35c86a314462 does not have a schedule_relationship
- trip_id 9bb232b1-b6bd-407c-b40d-0eddd2870d3a does not have a schedule_relationship
- trip_id 8cc89595-5360-49fd-ab8a-af60a414efdc does not have a schedule_relationship
- trip_id f9db1194-258a-42e8-94da-86e787440ad6 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 | 324 | 22 times (92 % 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. | 34 | 19 times (79 % of validations) |
| W001 | Timestamps should be populated for all elements | 33 | 18 times (75 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 14 | 14 times (58 % 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. | 10 | 8 times (33 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-31 at 22:31 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-01-31 at 22:31 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1769895093"
}
}