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-09-27 at 09:05 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 9505 does not have a schedule_relationship
- trip_id 27076 does not have a schedule_relationship
- trip_id 9928 does not have a schedule_relationship
- trip_id 2404 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 | 101 | 26 times (87 % of validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 2 | 2 times (7 % 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. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-27 at 21:43 Europe/Paris.
vehicle_positions (3) 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-09-27 at 21:43 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:2413",
"vehicle": {
"currentStopSequence": 7,
"position": {
"bearing": 185.0,
"latitude": 49.09885787963867,
"longitude": 2.5311379432678223
},
"stopId": "ROISPO1",
"timestamp": "1759002202",
"trip": {
"routeId": "AIREBUS",
"tripId": "2413"
},
"vehicle": {
"id": "KOI201128"
}
}
},
{
"id": "VM:27202",
"vehicle": {
"currentStopSequence": 4,
"position": {
"bearing": 202.0,
"latitude": 49.181365966796875,
"longitude": 2.457634449005127
},
"stopId": "LAMRSM1",
"timestamp": "1759002202",
"trip": {
"routeId": "CIEL",
"tripId": "27202"
},
"vehicle": {
"id": "KOI212028"
}
}
},
{
"id": "VM:2425",
"vehicle": {
"currentStopSequence": 5,
"position": {
"bearing": 271.0,
"latitude": 49.14319610595703,
"longitude": 2.456759452819824
},
"stopId": "LAMGRA2",
"timestamp": "1759002202",
"trip": {
"directionId": 1,
"routeId": "AIREBUS",
"tripId": "2425"
},
"vehicle": {
"id": "KOI193041"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1759002206"
}
}