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

2025-10-04
100%
2025-10-05
100%
2025-10-06
100%
2025-10-07
100%
2025-10-08
100%
2025-10-09
100%
2025-10-10
100%
2025-10-11
100%
2025-10-12
100%
2025-10-13
100%
2025-10-14
100%
2025-10-15
100%
2025-10-16
100%
2025-10-17
100%
2025-10-18
100%
2025-10-19
100%
2025-10-20
98.8%
2025-10-21
100%
2025-10-22
100%
2025-10-23
100%
2025-10-24
100%
2025-10-25
100%
2025-10-26
100%
2025-10-27
100%
2025-10-28
100%
2025-10-29
100%
2025-10-30
100%
2025-10-31
100%
2025-11-01
100%
2025-11-02
100%
2025-11-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

⚠️3 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-01 at 08:09 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

schedule_relationship not populated W009 3 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 26|25819352:T1|8:20:00 does not have a schedule_relationship
  • trip_id 07|25819343:T1|8:10:00 does not have a schedule_relationship
  • trip_id 13|25890785:T1|8:20:00 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 2 122 29 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 23 times (79 % of validations)
E052 Each vehicle should have a unique ID 31 15 times (52 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-04 at 00:17 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 2025-11-04 at 00:17 Europe/Paris. You can look at the GTFS-RT documentation.

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