gtfs-rt Transport open dataset - GTFS RT Position véhicules temps réel réseau ALEOP Pays de la Loire for Réseau interurbain Aléop - Pays de la Loire

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

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

❌2 errors, 62 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-17 at 08:11 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 12 trip_id 2610228508 at (47.330963,-1.792823) 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 21 trip_id 2628655601 at (47.269745,-1.501342) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Warnings

schedule_relationship not populated W009 62 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 2628183610 does not have a schedule_relationship
trip_id 2628381318 does not have a schedule_relationship
trip_id 2628381317 does not have a schedule_relationship
trip_id 2629292724 does not have a schedule_relationship
trip_id 2628381320 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	3,287	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	177	19 times (66 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-18 at 02:35 Europe/Paris.

vehicle_positions (0) 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-18 at 02:35 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1771378510"
  }
}