Resource details
This resource file is part of the dataset Réseau urbain Zest.
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, 19 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-07 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 2 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id trip_id 32009_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id trip_id 32012_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Warnings
vehicle_id not populated W002 19 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- entity ID 35 does not have a vehicle_id
- entity ID 38 does not have a vehicle_id
- entity ID 44 does not have a vehicle_id
- entity ID 56 does not have a vehicle_id
- entity ID 57 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 | 679 | 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. | 10 | 8 times (27 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 8 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-07 at 20:50 Europe/Paris.
vehicle_positions (4) 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-06-07 at 20:50 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "747",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 44.090049743652344,
"longitude": 7.593616962432861
},
"timestamp": "1749309436",
"trip": {
"routeId": "25",
"scheduleRelationship": "SCHEDULED",
"tripId": "32016_0"
},
"vehicle": {
"label": "197129"
}
}
},
{
"id": "818",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 43.75710678100586,
"longitude": 7.449223041534424
},
"timestamp": "1749322195",
"trip": {
"routeId": "22",
"scheduleRelationship": "SCHEDULED",
"tripId": "13190_0"
},
"vehicle": {
"label": "242037"
}
}
},
{
"id": "820",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 43.774940490722656,
"longitude": 7.505667209625244
},
"timestamp": "1749322046",
"trip": {
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"tripId": "28120_0"
},
"vehicle": {
"label": "139355"
}
}
},
{
"id": "821",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 43.75145721435547,
"longitude": 7.432310104370117
},
"timestamp": "1749321382",
"trip": {
"routeId": "13",
"scheduleRelationship": "SCHEDULED",
"tripId": "27606_0"
},
"vehicle": {
"label": "197137"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1749322200"
}
}