Resource details
Données position des véhicules en temps réel, au format GTFS-RT PROTOBUF, du réseau Aire’MOB
This resource file is part of the dataset Réseau urbain et interurbain Aire’MOB.
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
⚠️4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-28 at 09:03 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
schedule_relationship not populated W009 4 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 2404 does not have a schedule_relationship
- trip_id 9505 does not have a schedule_relationship
- trip_id 9928 does not have a schedule_relationship
- trip_id 27076 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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 105 | 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. | 5 | 5 times (17 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-28 at 15:48 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-28 at 15:48 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:2408",
"vehicle": {
"currentStopSequence": 7,
"position": {
"bearing": 85.0,
"latitude": 49.01163101196289,
"longitude": 2.5307223796844482
},
"stopId": "ROISPO1",
"timestamp": "1751118504",
"trip": {
"routeId": "AIREBUS",
"tripId": "2408"
},
"vehicle": {
"id": "KOI201152"
}
}
},
{
"id": "VM:2409",
"vehicle": {
"currentStopSequence": 1,
"position": {
"bearing": 192.0,
"latitude": 49.189430236816406,
"longitude": 2.409705638885498
},
"stopId": "GOUCDS1",
"timestamp": "1751118504",
"trip": {
"routeId": "AIREBUS",
"tripId": "2409"
},
"vehicle": {
"id": "KOI233070"
}
}
},
{
"id": "VM:2420",
"vehicle": {
"currentStopSequence": 6,
"position": {
"bearing": 48.0,
"latitude": 49.1661376953125,
"longitude": 2.447977066040039
},
"stopId": "CHTGAR1",
"timestamp": "1751118504",
"trip": {
"directionId": 1,
"routeId": "AIREBUS",
"tripId": "2420"
},
"vehicle": {
"id": "KOI201120"
}
}
},
{
"id": "VM:9930",
"vehicle": {
"currentStopSequence": 21,
"position": {
"bearing": 334.0,
"latitude": 49.19947052001953,
"longitude": 2.4609568119049072
},
"stopId": "CHTLEF2",
"timestamp": "1751118096",
"trip": {
"directionId": 1,
"routeId": "DUC",
"tripId": "9930"
},
"vehicle": {
"id": "KOI209145"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1751118515"
}
}