Resource details

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

Les mises à jour des trajets vous informent des fluctuations d’horaires. Elles sont délivrées au format GTFS-realtime, voir https://developers.google.com/transit/gtfs-realtime/guides/trip-updates?hl=fr.

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

Download availability

2025-03-05
99.3%
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
100%
2025-03-14
100%
2025-03-15
100%
2025-03-16
100%
2025-03-17
99.3%
2025-03-18
100%
2025-03-19
100%
2025-03-20
100%
2025-03-21
100%
2025-03-22
100%
2025-03-23
100%
2025-03-24
100%
2025-03-25
100%
2025-03-26
100%
2025-03-27
100%
2025-03-28
100%
2025-03-29
100%
2025-03-30
100%
2025-03-31
100%
2025-04-01
100%
2025-04-02
100%
2025-04-03
100%
2025-04-04
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

100 errors, 7 warnings

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

Errors

Sequential stop_time_update times are not increasing E022 100 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 23-10-2-B-084301 stop_id 650 arrival_time 09:01:34 (1743663694) is less than previous stop departure_time 09:01:42 (1743663702) - times must increase between two sequential stops
  • trip_id 23-10-2-B-084301 stop_id 650 departure_time 09:01:34 (1743663694) is less than previous stop departure_time 09:01:42 (1743663702) - times must increase between two sequential stops
  • trip_id 23-10-2-B-084301 stop_id 857 arrival_time 09:14:31 (1743664471) is less than previous stop arrival_time 09:14:40 (1743664480) - times must increase between two sequential stops
  • trip_id 23-10-2-B-084301 stop_id 857 arrival_time 09:14:31 (1743664471) is less than previous stop departure_time 09:14:40 (1743664480) - times must increase between two sequential stops
  • trip_id 23-10-2-B-084301 stop_id 857 departure_time 09:14:31 (1743664471) is less than previous stop departure_time 09:14:40 (1743664480) - times must increase between two sequential stops

Warnings

vehicle_id not populated W002 7 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 23-5B-2-B-054601 does not have a vehicle_id
  • trip_id 23-6-5-B-080001 does not have a vehicle_id
  • trip_id 23-7-7-B-063101 does not have a vehicle_id
  • trip_id 23-L-3-B-090101 does not have a vehicle_id
  • trip_id 23-5B-19-B-073000 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 864 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 152 30 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 03:32 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-04-04 at 03:32 Europe/Paris. You can look at the GTFS-RT documentation.

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