Resource details
This resource file is part of the dataset Navettes hivernales de l'Alpe d'Huez.
Download availability
Learn more
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
❌4 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-08-12 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 4 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 4925065148760064:1 stop_sequence 36 arrival_time 09:39:08 (1786520348) is less than previous stop departure_time 09:39:21 (1786520361) - times must increase between two sequential stops
- trip_id 4925065148760064:1 stop_sequence 41 arrival_time 09:44:14 (1786520654) is less than previous stop departure_time 09:44:15 (1786520655) - times must increase between two sequential stops
- trip_id 4925065148760064:1 stop_sequence 44 arrival_time 09:47:22 (1786520842) is less than previous stop departure_time 09:47:30 (1786520850) - times must increase between two sequential stops
- trip_id 4925065148760064:1 stop_sequence 45 arrival_time 09:48:10 (1786520890) is less than previous stop departure_time 09:48:16 (1786520896) - times must increase between two sequential stops
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 73 | 10 times (33 % 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. | 3 | 3 times (10 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 4 | 3 times (10 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 | 2 times (7 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 2 | 1 times (3 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 2 | 1 times (3 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 4 | 1 times (3 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-08-13 at 07:21 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-08-13 at 07:21 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1786598460"
}
}