Resource details

File name: Données Urbaines Temps Réel
Format: gtfs-rt

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

Download availability

2025-03-05
100%
2025-03-06
99.3%
2025-03-07
100%
2025-03-08
100%
2025-03-09
100%
2025-03-10
99.4%
2025-03-11
99.3%
2025-03-12
100%
2025-03-13
100%
2025-03-14
100%
2025-03-15
96%
2025-03-16
81.2%
2025-03-17
99.4%
2025-03-18
99.3%
2025-03-19
91.6%
2025-03-20
96.7%
2025-03-21
99.3%
2025-03-22
100%
2025-03-23
99.3%
2025-03-24
100%
2025-03-25
99.3%
2025-03-26
99.3%
2025-03-27
99.3%
2025-03-28
91.8%
2025-03-29
99.3%
2025-03-30
100%
2025-03-31
100%
2025-04-01
100%
2025-04-02
99.3%
2025-04-03
99.3%
2025-04-04
99.2%
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. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

⚠️2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-04 at 09:05 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 64024{L01_1}-25UrbS_T25_LMWJV 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 64024{L01_1}-25UrbS_T25_LMWJV 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 52 24 times (83 % 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 52 24 times (83 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 6 5 times (17 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 4 4 times (14 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 22:23 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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 2025-04-04 at 22:23 Europe/Paris. You can look at the GTFS-RT documentation.

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