Resource details

Format: gtfs-rt

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

Download availability

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%
2024-05-16
100%
2024-05-17
100%
2024-05-18
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

1 error, 4 warnings

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

Errors

Vehicle position far from trip shape E029 1 error

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.

Sample errors
  • vehicle.id zenbus:Vehicle:903620003:LOC trip_id 5135449066569728:0 at (43.1024,-0.030719) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Warnings

vehicle_id not populated W002 2 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 4887703256563712:1 does not have a vehicle_id
  • trip_id 5123755699339264: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 4887703256563712:1 is in TripUpdates but not in VehiclePositions feed
  • trip_id 5123755699339264: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
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. 48 21 times (70 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 55 21 times (70 % 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 55 21 times (70 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 6 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-19 at 00:54 Europe/Paris.

trip_updates (1) vehicle_positions (1) service_alerts (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 2024-05-19 at 00:54 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "zenbus:Vehicle:886990014:LOC", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 24, "position": { "latitude": 43.21588897705078, "longitude": 0.09098900109529495 }, "stop_id": "zenbus:StopPoint:SP:906880002:LOC", "timestamp": "1716072871", "trip": { "route_id": "zenbus:Line:834720008:LOC", "start_date": "20240518", "start_time": "18:46:00", "trip_id": "6284954572947456:7" }, "vehicle": { "id": "zenbus:Vehicle:886990014:LOC" } } }, { "id": "20240518:906860020:7", "trip_update": { "stop_time_update": [ { "schedule_relationship": "SKIPPED", "stop_id": "zenbus:StopPoint:SP:888850013:LOC", "stop_sequence": 20 }, { "schedule_relationship": "SKIPPED", "stop_id": "zenbus:StopPoint:SP:678710010:LOC", "stop_sequence": 21 }, { "schedule_relationship": "SKIPPED", "stop_id": "zenbus:StopPoint:SP:884950013:LOC", "stop_sequence": 22 }, { "schedule_relationship": "SKIPPED", "stop_id": "zenbus:StopPoint:SP:892900012:LOC", "stop_sequence": 23 }, { "arrival": { "time": "1716073870" }, "departure": { "time": "1716073880" }, "stop_id": "zenbus:StopPoint:SP:906880002:LOC", "stop_sequence": 24 } ], "timestamp": "1716072873", "trip": { "route_id": "zenbus:Line:834720008:LOC", "start_date": "20240518", "start_time": "18:46:00", "trip_id": "6284954572947456:7" }, "vehicle": { "id": "zenbus:Vehicle:886990014:LOC" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1716072873" } }