Resource details
Position des véhicules
This resource file is part of the dataset Réseau urbain Mistral.
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
❌93 errors, 33 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-07 at 09:06 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 1 error
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 735 stop_id TO0BUS does not exist in GTFS data stops.txt
Header timestamp should be greater than or equal to all other timestamps E012 90 errors
No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp
Sample errors
- vehicle_id 4 timestamp 1744009579 is greater than the header
- vehicle_id 6 timestamp 1744009579 is greater than the header
- vehicle_id 8 timestamp 1744009579 is greater than the header
- vehicle_id 12 timestamp 1744009569 is greater than the header
- vehicle_id 13 timestamp 1744009569 is greater than the header
Vehicle position far from trip shape E029 2 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 517 trip_id 4882610 at (43.1153,5.8753) 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 768 trip_id 4906378 at (43.1098,6.1109) 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
vehicle speed is unrealistic W004 33 errors
vehicle.position.speed has an unrealistic speed that may be incorrect
Sample errors
- vehicle.id 13 speed of 43.0 m/s (96.19 mph) is unrealistic
- vehicle.id 15 speed of 62.0 m/s (138.69 mph) is unrealistic
- vehicle.id 30 speed of 57.0 m/s (127.51 mph) is unrealistic
- vehicle.id 36 speed of 45.0 m/s (100.66 mph) is unrealistic
- vehicle.id 37 speed of 35.0 m/s (78.29 mph) is unrealistic
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 |
|---|---|---|---|
| E012 | No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp | 1 695 | 30 times (100 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 902 | 30 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 92 | 24 times (80 % 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. | 14 | 11 times (37 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-08 at 00:32 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-08 at 00:32 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1744065165"
}
}