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
❌6 errors, 83 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-20 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 4 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 6320b1db09dda81a65381ced trip_id 2596719705 at (47.45509,-0.5690348) 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 67 trip_id 2607193103 at (47.532017,-0.61445) 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 101 trip_id 2628773026 at (47.366894,-1.609187) 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 94 trip_id 2610228508 at (47.302467,-1.844695) 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 is not unique E052 2 errors
Each vehicle should have a unique ID
Sample errors
- entity ID RTVP:T:2629382101 has vehicle.id 35 which is used by more than one vehicle in the feed
- entity ID RTVP:T:2628655601 has vehicle.id 46 which is used by more than one vehicle in the feed
Warnings
schedule_relationship not populated W009 83 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 2628381318 does not have a schedule_relationship
- trip_id 2628183610 does not have a schedule_relationship
- trip_id 2628381317 does not have a schedule_relationship
- trip_id 2628183704 does not have a schedule_relationship
- trip_id 2629292724 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 | 3,146 | 28 times (97 % 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. | 86 | 21 times (72 % of validations) |
| E052 | Each vehicle should have a unique ID | 154 | 19 times (66 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-21 at 00:04 Europe/Paris.
vehicle_positions (1) 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-21 at 00:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "RTVP:T:2628656429",
"vehicle": {
"position": {
"latitude": 47.40386962890625,
"longitude": -1.3772720098495483
},
"timestamp": "1771628621",
"trip": {
"directionId": 1,
"routeId": "360",
"startDate": "20260220",
"tripId": "2628656429"
},
"vehicle": {
"id": "67",
"label": "183215",
"licensePlate": "FC-975-FZ"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771628699"
}
}