Resource details

File name: Données en temps réel au format GTFS-RT (TripUpdate)
Format: gtfs-rt

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

  • TripUpdate

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

Download availability

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

163 errors, 168 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-03-25 at 08:01 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 7 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 1-712441882-22.1-LM_____ does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-712704032-22.1-LM_____ does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-712376334-22.1-LM_____ does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-712638492-22.1-LM_____ does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-695861249-10-_M_____ does not exist in the GTFS data and does not have schedule_relationship of ADDED

Sequential stop_time_update times are not increasing E022 156 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 1-691666964 stop_sequence 22 arrival_time 08:10:02 (1742886602) is equal to previous stop arrival_time 08:10:02 (1742886602) - times must increase between two sequential stops
  • trip_id 1-691666964 stop_sequence 22 arrival_time 08:10:02 (1742886602) is equal to previous stop departure_time 08:10:02 (1742886602) - times must increase between two sequential stops
  • trip_id 1-691666964 stop_sequence 22 departure_time 08:10:02 (1742886602) is equal to previous stop departure_time 08:10:02 (1742886602) - times must increase between two sequential stops
  • trip_id 1-691666964 stop_sequence 22 departure_time 08:10:02 (1742886602) is equal to previous stop arrival_time 08:10:02 (1742886602) - times must increase between two sequential stops
  • trip_id 1-691470340 stop_sequence 12 arrival_time 08:10:12 (1742886612) is equal to previous stop arrival_time 08:10:12 (1742886612) - times must increase between two sequential stops

Warnings

timestamp not populated W001 89 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 1-691666964 does not have a timestamp
  • trip_id 1-712441882-22.1-LM_____ does not have a timestamp
  • trip_id 1-691470340 does not have a timestamp
  • trip_id 1-712638495 does not have a timestamp
  • trip_id 1-744882182 does not have a timestamp

vehicle_id not populated W002 79 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-712704032-22.1-LM_____ does not have a vehicle_id
  • trip_id 1-712376334-22.1-LM_____ does not have a vehicle_id
  • trip_id 1-712638492-22.1-LM_____ does not have a vehicle_id
  • trip_id 1-779747337 does not have a vehicle_id
  • trip_id 1-779616258 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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 3 568 24 times (80 % of validations)
W001 Timestamps should be populated for all elements 2 037 24 times (80 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 794 24 times (80 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 209 22 times (73 % 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. 5 5 times (17 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-03-25 at 22:10 Europe/Paris.

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

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