Resource details
Position GPS temps réel des véhicules
This resource file is part of the dataset Réseau urbain Bibus.
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, 174 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-03 at 09:06 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 3 errors
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.
Sample errors
- vehicle.id 268435809 trip_id 16551056 at (48.378048,-4.529246) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 268435624 trip_id 16550524 at (48.391304,-4.4852023) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 268436078 trip_id 17114237 at (48.440086,-4.4270525) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
timestamp not populated W001 87 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 268436457 does not have a timestamp
- vehicle_id 268435651 does not have a timestamp
- vehicle_id 268436458 does not have a timestamp
- vehicle_id 268435581 does not have a timestamp
- vehicle_id 268435612 does not have a timestamp
schedule_relationship not populated W009 87 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 16561262 does not have a schedule_relationship
- trip_id 16550432 does not have a schedule_relationship
- trip_id 16561195 does not have a schedule_relationship
- trip_id 16550462 does not have a schedule_relationship
- trip_id 16551353 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 2 643 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 643 | 30 times (100 % 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. | 48 | 21 times (70 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 93 | 6 times (20 % 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. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-04 at 03:37 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 2025-04-04 at 03:37 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743730648"
}
}