Resource details

File name: Horaires Temps Réels
Format: gtfs-rt

Horaires Temps Réels du réseau A Citadina

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

Download availability

2025-12-14
97%
2025-12-15
86.8%
2025-12-16
90%
2025-12-17
88%
2025-12-18
83.7%
2025-12-19
94.2%
2025-12-20
99.6%
2025-12-21
89.1%
2025-12-22
84.1%
2025-12-23
84.7%
2025-12-24
94.5%
2025-12-25
94.7%
2025-12-26
89.9%
2025-12-27
98.7%
2025-12-28
96.2%
2025-12-29
91.1%
2025-12-30
90.1%
2025-12-31
95.8%
2026-01-01
96%
2026-01-02
95.2%
2026-01-03
98.3%
2026-01-04
95.9%
2026-01-05
84.6%
2026-01-06
81.6%
2026-01-07
81.6%
2026-01-08
89.2%
2026-01-09
45.2%
2026-01-10
98.6%
2026-01-11
88.5%
2026-01-12
84%
2026-01-13
79.5%
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

1 error, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-13 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_time_update doesn't have arrival or departure E043 1 error

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors
  • trip_id MARINA_0 stop_sequence 1 doesn't have arrival or departure

Warnings

ID in one feed missing from the other W003 2 errors

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 MARINA_0_0 is in TripUpdates but not in VehiclePositions feed
  • trip_id PRUNEDDU_0 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
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 51 23 times (79 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 53 22 times (76 % of validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 40 21 times (72 % of validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 53 17 times (59 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 34 8 times (28 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.