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éseaux interurbains Aléop - Pays de la Loire.
Download availability
Learn more
We test this resource download availability every hour by making an HTTPHEAD 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
❌3 errors, 44 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-18 at 09:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 3 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 61e00a2b522a5d34584c04a3 trip_id 217|20945734:T6|8:10:00 at (47.993748,0.199171) 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 619753ae3596e80001970256 trip_id 211|20945721:T9|8:10:00 at (48.002907,0.193355) 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 63fe12af9d0fa13205b002e4 trip_id 540|17465965:T2|8:15:00 at (46.46144,-1.170215) 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 44 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 209|20945717:T5|8:02:00 does not have a schedule_relationship
- trip_id 216_E|20945730:T6|8:20:00 does not have a schedule_relationship
- trip_id 217|20945734:T6|8:10:00 does not have a schedule_relationship
- trip_id 207|20945713:T7|7:58:00 does not have a schedule_relationship
- trip_id 215|19129169:T10|7:50:00 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 | 648 | 19 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. | 19 | 9 times (47 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-18 at 22:36 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 2024-05-18 at 22:36 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1716064616"
}
}