Resource details
Flux GTFS RT du réseau Aléop Pays de la Loire : Position des véhicules
This resource file is part of the dataset Réseau interurbain Aléop - Pays de la Loire.
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, 49 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-23 at 08:08 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 2 errors
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.
Sample errors
- vehicle.id 693301366cc1837bc10599cd trip_id 2596721802 at (47.022453,-1.0525266) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 6320b1db09dda81a65381ced trip_id 2596719705 at (47.455498,-0.5696384) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
schedule_relationship not populated W009 49 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 2628380102 does not have a schedule_relationship
- trip_id 2628380008 does not have a schedule_relationship
- trip_id 2628381317 does not have a schedule_relationship
- trip_id 2628384202 does not have a schedule_relationship
- trip_id 2628183705 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 | 2,837 | 27 times (93 % 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. | 84 | 20 times (69 % of validations) |
| E052 | Each vehicle should have a unique ID | 133 | 16 times (55 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-23 at 22:02 Europe/Paris.
vehicle_positions (2) 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-02-23 at 22:02 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "RTVP:V:63f5e0cd34b0273ad9d006c0",
"vehicle": {
"currentStatus": "STOPPED_AT",
"currentStopSequence": 3,
"position": {
"latitude": 46.30918502807617,
"longitude": -0.4708887040615082
},
"stopId": "79NIORbrocR",
"timestamp": "1771880571",
"vehicle": {
"id": "63f5e0cd34b0273ad9d006c0",
"label": "623",
"licensePlate": "GL380YN"
}
}
},
{
"id": "RTVP:T:2628656529",
"vehicle": {
"position": {
"latitude": 47.30409622192383,
"longitude": -1.485124945640564
},
"timestamp": "1771880567",
"trip": {
"directionId": 0,
"routeId": "360",
"startDate": "20260223",
"tripId": "2628656529"
},
"vehicle": {
"id": "11",
"label": "133161",
"licensePlate": "CX-873-LP"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771880574"
}
}