Resource details

File name: GTFS RT Position véhicules temps réel réseau ALEOP Pays de la Loire
Format: gtfs-rt

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

2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
100%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
100%
2026-01-13
100%
2026-01-14
100%
2026-01-15
100%
2026-01-16
100%
2026-01-17
100%
2026-01-18
100%
2026-01-19
100%
2026-01-20
100%
2026-01-21
100%
2026-01-22
100%
2026-01-23
100%
2026-01-24
100%
2026-01-25
100%
2026-01-26
100%
2026-01-27
100%
2026-01-28
100%
2026-01-29
100%
2026-01-30
100%
2026-01-31
100%
2026-02-01
100%
2026-02-02
100%
2026-02-03
100%
Learn more
We test this resource download availability every hour by making an HTTP 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

21 errors, 171 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-03 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Vehicle position far from trip shape E029 10 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 619755e890a4ad0001437273 trip_id 2629524301 at (47.96991,0.2262383) 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 6842f7e3c808574dce1a1e4a trip_id 2630602504 at (47.11363,-1.5364352) 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 8 trip_id 2588379601 at (47.7165,-1.142922) 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 19 trip_id 2607362506 at (48.20651,-0.826542) 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 4 trip_id 2607362502 at (48.222164,-0.868767) 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 11 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:2607394903 has vehicle.id 70 which is used by more than one vehicle in the feed
  • entity ID RTVP:T:2636784011 has vehicle.id 95 which is used by more than one vehicle in the feed
  • entity ID RTVP:T:2628656514 has vehicle.id 24 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

Warnings

schedule_relationship not populated W009 171 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 2629523706 does not have a schedule_relationship
  • trip_id 2630587810 does not have a schedule_relationship
  • trip_id 2629523106 does not have a schedule_relationship
  • trip_id 2629524301 does not have a schedule_relationship
Validate this GTFS-RT now

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 1,997 18 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. 50 12 times (67 % of validations)
E052 Each vehicle should have a unique ID 106 12 times (67 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-03 at 22:12 Europe/Paris.

vehicle_positions (2) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-02-03 at 22:12 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "RTVP:V:63fe12bd58fe51bea197d110", "vehicle": { "currentStopSequence": 5, "position": { "latitude": 46.33515167236328, "longitude": -0.502791702747345 }, "stopId": "85BENErichR", "timestamp": "1770153131", "vehicle": { "id": "63fe12bd58fe51bea197d110", "label": "627", "licensePlate": "GL727ZA" } } }, { "id": "RTVP:T:2628656427", "vehicle": { "position": { "latitude": 47.26100158691406, "longitude": -1.5174620151519775 }, "timestamp": "1770153134", "trip": { "directionId": 1, "routeId": "360", "startDate": "20260203", "tripId": "2628656427" }, "vehicle": { "id": "25", "label": "133193", "licensePlate": "GX-7W-SM" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1770153134" } }