Resource details

File name: Position des véhicules en temps réel (GTFS-RT)
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Transp’Or.

Download availability

2024-08-17
100%
2024-08-18
98.9%
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
99.3%
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
99.7%
2024-09-04
100%
2024-09-05
100%
2024-09-06
100%
2024-09-07
100%
2024-09-08
100%
2024-09-09
100%
2024-09-10
99.5%
2024-09-11
100%
2024-09-12
100%
2024-09-13
100%
2024-09-14
99.6%
2024-09-15
100%
2024-09-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.

Validation details

2 errors, 1 warning

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

Errors

Vehicle position far from trip shape E029 2 errors

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 51 trip_id e8512a1a-da64-41d8-8e7c-978cb6e79b2c at (43.610813,3.929654) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 13 trip_id 191 at (43.62446,4.011269) 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

timestamp not populated W001 1 error

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 76 does not have a timestamp
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
W001 Timestamps should be populated for all elements 16 12 times (75 % 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. 10 7 times (44 % of validations)
E023 For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip 2 1 times (6 % of validations)
E052 Each vehicle should have a unique ID 1 1 times (6 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 1 1 times (6 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-09-16 at 21:14 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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-09-16 at 21:14 Europe/Paris. You can look at the GTFS-RT documentation.

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