Resource details

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Zest.

Download availability

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

21 errors, 21 warnings

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 21 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id trip_id 27824_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 28593_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 27825_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 28492_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 27550_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 21 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 1561831 does not have a vehicle_id
  • entity ID 1564361 does not have a vehicle_id
  • entity ID 1565168 does not have a vehicle_id
  • entity ID 1565801 does not have a vehicle_id
  • entity ID 1566253 does not have a vehicle_id
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 433 27 times (90 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 433 27 times (90 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-15 at 21:17 Europe/Paris.

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

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-05-15 at 21:17 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "1624790", "vehicle": { "current_status": "IN_TRANSIT_TO", "position": { "latitude": 43.75297164916992, "longitude": 7.432386875152588 }, "timestamp": "1715798290", "trip": { "trip_id": "27586_0" }, "vehicle": { "label": "197147" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1715800651" } }