Resource details

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éseaux interurbains Aléop - Pays de la Loire.

Download availability

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

Validation details

4 errors, 47 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-07-18 at 09:05 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 6320b1db09dda81a65381e0f trip_id 401|23636522:T1|6:56:00 at (47.707302,-1.362765) 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 6320b1db09dda81a65381ced trip_id 408|23636547:T3|9:06:00 at (47.21573,-0.9929975) 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 6320b1db09dda81a6538291e trip_id 421|23636553:T2|9:02:00 at (47.182606,-1.078362) 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 63e64b99dbe722e3b6cf59d1 trip_id 402|23487280:T2|9:10:00 at (47.671803,-0.240816) 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 47 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 212|23984589:T3|8:20:00 does not have a schedule_relationship
  • trip_id 210|23984586:T1|8:00:00 does not have a schedule_relationship
  • trip_id 216|23984595:T4|9:00:00 does not have a schedule_relationship
  • trip_id 218|23984600:T1|8:25:00 does not have a schedule_relationship
  • trip_id 312|23800017:T6|7:45: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 1 115 27 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. 65 21 times (78 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-07-19 at 02:15 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-07-19 at 02:15 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "1.0", "timestamp": "1721348101" } }