Resource details

File name: Horaires temps-réel de la station de ski Valmorel (GTFS-RT)
Format: gtfs-rt

Les spécifications du format GTFS-RT sont disponibles ici : https://developers.google.com/transit/gtfs-realtime/

This resource file is part of the dataset Navettes saisonnières Valmobus.

Download availability

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

1 error, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-13 at 09:06 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_update times are not increasing E022 1 error

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id 4882363717779456:2 stop_sequence 11 arrival_time 09:02:21 (1744527741) is equal to previous stop departure_time 09:02:21 (1744527741) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 4882363717779456:2 does not have a vehicle_id

ID in one feed missing from the other W003 1 error

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

Sample errors
  • trip_id 4882363717779456:2 is in TripUpdates but not in VehiclePositions feed
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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 7 7 times (26 % 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 7 7 times (26 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 8 3 times (11 % 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. 1 1 times (4 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-16 at 19:56 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-04-16 at 19:56 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "2.0", "timestamp": "1744826187" } }