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
❌17 errors, 205 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-03 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 6197546b12e1a90001a39c19 trip_id 2630470308 at (47.937298,0.2370136) 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 63f5e0bcc3ec9f5bce4d4d3a trip_id 2612043903 at (46.316833,-0.4719583) 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 87 trip_id 2588379604 at (47.49633,-0.609918) 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 12 trip_id 2610228508 at (47.33581,-1.796987) 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 13 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:2607394602 has vehicle.id 39 which is used by more than one vehicle in the feed
- entity ID RTVP:T:2607360303 has vehicle.id 41 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:2624617504 has vehicle.id 97 which is used by more than one vehicle in the feed
Warnings
schedule_relationship not populated W009 205 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 2614086201 does not have a schedule_relationship
- trip_id 2630587906 does not have a schedule_relationship
- trip_id 2629523706 does not have a schedule_relationship
- trip_id 2629524301 does not have a schedule_relationship
- trip_id 2644387105 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,767 | 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. | 89 | 23 times (79 % of validations) |
| E052 | Each vehicle should have a unique ID | 128 | 17 times (59 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-03-04 at 05:02 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-03-04 at 05:02 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1772596943"
}
}