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
❌15 errors, 164 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-06 at 08:06 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 5 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 627e5dd5176a2897a44dde8d trip_id 2630587901 at (47.97543,0.22014) 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 88 trip_id 2607394305 at (47.95781,-0.903987) 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 35 trip_id 2607394905 at (47.88196,-1.022045) 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 84 trip_id 2607394401 at (48.073326,-0.770205) 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 65 trip_id 2607394902 at (47.924934,-0.803565) 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 10 errors
Each vehicle should have a unique ID
Sample errors
- entity ID RTVP:T:2636784013 has vehicle.id 37 which is used by more than one vehicle in the feed
- entity ID RTVP:T:2607395001 has vehicle.id 70 which is used by more than one vehicle in the feed
- entity ID RTVP:T:2629381902 has vehicle.id 26 which is used by more than one vehicle in the feed
- entity ID RTVP:T:2628773018 has vehicle.id 91 which is used by more than one vehicle in the feed
- entity ID RTVP:T:2610228504 has vehicle.id 72 which is used by more than one vehicle in the feed
Warnings
schedule_relationship not populated W009 164 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 2614086202 does not have a schedule_relationship
- trip_id 2630587810 does not have a schedule_relationship
- trip_id 2630587902 does not have a schedule_relationship
- trip_id 2630470308 does not have a schedule_relationship
- trip_id 2629523106 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,319 | 20 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. | 63 | 14 times (70 % of validations) |
| E052 | Each vehicle should have a unique ID | 124 | 14 times (70 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-07 at 01:28 Europe/Paris.
vehicle_positions (0) 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-07 at 01:28 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770424112"
}
}