Resource details

File name: Mise à jour des trajets en temps réel (GTFS-RT)
Format: gtfs-rt

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

Download availability

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

Validation details

66 errors, 13 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-13 at 09:11 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 4 errors

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

Sample errors
  • trip_id 191 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 191 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 193 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 193 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 4 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id TAD does not exist in the GTFS data routes.txt
  • route_id TAD does not exist in the GTFS data routes.txt
  • route_id TAD does not exist in the GTFS data routes.txt
  • route_id TAD does not exist in the GTFS data routes.txt

Sequential stop_time_update times are not increasing E022 58 errors

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id 191 stop_sequence 39 arrival_time 06:49:09 (1749790149) is less than previous stop arrival_time 07:54:47 (1749794087) - times must increase between two sequential stops
  • trip_id 191 stop_sequence 39 arrival_time 06:49:09 (1749790149) is less than previous stop departure_time 07:54:58 (1749794098) - times must increase between two sequential stops
  • trip_id 191 stop_sequence 39 departure_time 06:49:15 (1749790155) is less than previous stop departure_time 07:54:58 (1749794098) - times must increase between two sequential stops
  • trip_id 191 stop_sequence 39 departure_time 06:49:15 (1749790155) is less than previous stop arrival_time 07:54:47 (1749794087) - times must increase between two sequential stops
  • trip_id 191 stop_sequence 88 arrival_time 07:26:05 (1749792365) is less than previous stop arrival_time 09:13:15 (1749798795) - times must increase between two sequential stops

Warnings

timestamp not populated W001 13 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 191 does not have a timestamp
  • trip_id 191 does not have a timestamp
  • trip_id 86807812-4fb5-40bd-bb28-d9d9ff8dc426 does not have a timestamp
  • trip_id 667 does not have a timestamp
  • trip_id 7b404ead-e694-4f56-ac78-2df3f7ea645a 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 262 30 times (100 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 61 27 times (90 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 61 27 times (90 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1 692 24 times (80 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 3 3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-13 at 22:26 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-06-13 at 22:26 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1749846385" } }