Resource details

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 station Tignes.

Download availability

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

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

Warnings

vehicle_id not populated W002 2 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 890120003:3 does not have a vehicle_id
  • trip_id 5099232283328512:2 does not have a vehicle_id

ID in one feed missing from the other W003 2 errors

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 890120003:3 is in TripUpdates but not in VehiclePositions feed
  • trip_id 5099232283328512: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 15 9 times (38 % 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 15 9 times (38 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 3 3 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-09-07 at 14:23 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 43 200 seconds. Try to update your feed at most every 30 seconds.

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-09-07 at 14:23 Europe/Paris. You can look at the GTFS-RT documentation.

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