Resource details

Download availability

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%
2024-07-20
100%
2024-07-21
100%
2024-07-22
100%
2024-07-23
100%
2024-07-24
100%
2024-07-25
100%
2024-07-26
100%
2024-07-27
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

⚠️2 warnings

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

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 5103279946072064: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 5103279946072064: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 5 5 times (17 % 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 4 times (13 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 4 4 times (13 % 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. 2 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-07-27 at 02:11 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 4 992 seconds. Try to update your feed at most every 30 seconds.

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 2024-07-27 at 02:11 Europe/Paris. You can look at the GTFS-RT documentation.

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