Resource details
This resource file is part of the dataset Réseau urbain Figeac - Le Bus.
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
❌5 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-07 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 5 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 4827579222589440:1 stop_sequence 9 arrival_time 09:19:14 (1786087154) is less than previous stop departure_time 09:19:25 (1786087165) - times must increase between two sequential stops
- trip_id 4827579222589440:1 stop_sequence 10 arrival_time 09:19:48 (1786087188) is less than previous stop departure_time 09:20:12 (1786087212) - times must increase between two sequential stops
- trip_id 4827579222589440:1 stop_sequence 12 arrival_time 09:21:09 (1786087269) is less than previous stop departure_time 09:21:23 (1786087283) - times must increase between two sequential stops
- trip_id 4827579222589440:1 stop_sequence 13 arrival_time 09:21:46 (1786087306) is less than previous stop departure_time 09:22:09 (1786087329) - times must increase between two sequential stops
- trip_id 4827579222589440:1 stop_sequence 15 arrival_time 09:23:16 (1786087396) is less than previous stop departure_time 09:23:22 (1786087402) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 5935872313655296:3 does not have a vehicle_id
ID in one feed missing from the other W003 1 error
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 5935872313655296:3 is in TripUpdates but not in VehiclePositions feed
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 149 | 20 times (67 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 3 | 3 times (10 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 3 | 3 times (10 % 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. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-07 at 20:22 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-08-07 at 20:22 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1786126937"
}
}