Resource details
File name:
Position des véhicules au format GTFS-RT
Format: gtfs-rt
This resource file is part of the dataset Réseau urbain Zest.
Download availability
2025-07-09
100%
2025-07-10
100%
2025-07-11
100%
2025-07-12
100%
2025-07-13
100%
2025-07-14
100%
2025-07-15
100%
2025-07-16
100%
2025-07-17
100%
2025-07-18
100%
2025-07-19
100%
2025-07-20
100%
2025-07-21
100%
2025-07-22
100%
2025-07-23
100%
2025-07-24
100%
2025-07-25
100%
2025-07-26
100%
2025-07-27
100%
2025-07-28
100%
2025-07-29
100%
2025-07-30
100%
2025-07-31
100%
2025-08-01
100%
2025-08-02
100%
2025-08-03
100%
2025-08-04
100%
2025-08-05
100%
2025-08-06
100%
2025-08-07
86.3%
2025-08-08
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
⚠️24 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-08 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 24 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- entity ID 41 does not have a vehicle_id
- entity ID 44 does not have a vehicle_id
- entity ID 52 does not have a vehicle_id
- entity ID 54 does not have a vehicle_id
- entity ID 61 does not have a vehicle_id
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 |
---|---|---|---|
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 648 | 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. | 3 | 3 times (10 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 3 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-08-09 at 01:16 Europe/Paris.
vehicle_positions (1) 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-08-09 at 01:16 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "1016",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 43.95766067504883,
"longitude": 7.520753860473633
},
"timestamp": "1754668358",
"trip": {
"routeId": "25",
"scheduleRelationship": "SCHEDULED",
"tripId": "32155_0"
},
"vehicle": {
"label": "227010"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1754695013"
}
}