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
❌3 errors, 105 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-19 at 08:03 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 41 trip_id 2607193102 at (47.458496,-0.56312) 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 40 trip_id 2607364001 at (48.066418,-0.756773) 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 1 error
Each vehicle should have a unique ID
Sample errors
- entity ID RTVP:T:2628655509 has vehicle.id 46 which is used by more than one vehicle in the feed
Warnings
schedule_relationship not populated W009 105 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 2629523506 does not have a schedule_relationship
- trip_id 2612144602 does not have a schedule_relationship
- trip_id 2643279706 does not have a schedule_relationship
- trip_id 2614086103 does not have a schedule_relationship
- trip_id 2637849306 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,227 | 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. | 83 | 21 times (72 % of validations) |
| E052 | Each vehicle should have a unique ID | 160 | 19 times (66 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-19 at 23:38 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-19 at 23:38 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771540734"
}
}