Resource details
This resource file is part of the dataset Réseau urbain Grandole Mobilités.
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 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-07 at 09:03 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 5 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- entity ID 13 does not have a vehicle_id
- entity ID 14 does not have a vehicle_id
- entity ID 15 does not have a vehicle_id
- entity ID 16 does not have a vehicle_id
- entity ID 17 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 | 272 | 25 times (83 % 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. | 13 | 10 times (33 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 | 1 times (3 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-07 at 11:15 Europe/Paris.
vehicle_positions (5) 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 2026-04-07 at 11:15 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "29",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.09474182128906,
"longitude": 5.491139888763428
},
"timestamp": "1775553296",
"trip": {
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"tripId": "10313"
},
"vehicle": {
"label": "229037"
}
}
},
{
"id": "30",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.080780029296875,
"longitude": 5.46872615814209
},
"timestamp": "1775553296",
"trip": {
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"tripId": "10312"
},
"vehicle": {
"label": "229038"
}
}
},
{
"id": "31",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.08958435058594,
"longitude": 5.4872331619262695
},
"timestamp": "1775553296",
"trip": {
"routeId": "2",
"scheduleRelationship": "SCHEDULED",
"tripId": "20310"
},
"vehicle": {
"label": "209027"
}
}
},
{
"id": "32",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.05928421020508,
"longitude": 5.412649154663086
},
"timestamp": "1775553296",
"trip": {
"routeId": "2",
"scheduleRelationship": "SCHEDULED",
"tripId": "20311"
},
"vehicle": {
"label": "209028"
}
}
},
{
"id": "33",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.09754180908203,
"longitude": 5.509833812713623
},
"timestamp": "1775553296",
"trip": {
"routeId": "3",
"scheduleRelationship": "SCHEDULED",
"tripId": "30308"
},
"vehicle": {
"label": "209127"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775553301"
}
}