transport.data.gouv.fr transport.data.gouv.fr

Resource details

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

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-08-31
99.7%
2025-09-01
99.7%
2025-09-02
100%
2025-09-03
99.6%
2025-09-04
99.6%
2025-09-05
99.6%
2025-09-06
100%
2025-09-07
99.5%
2025-09-08
99.6%
2025-09-09
99.6%
2025-09-10
99.3%
2025-09-11
99.5%
2025-09-12
99.6%
2025-09-13
99.6%
2025-09-14
99.5%
2025-09-15
99.5%
2025-09-16
99.5%
2025-09-17
99.5%
2025-09-18
99.6%
2025-09-19
100%
2025-09-20
100%
2025-09-21
99.5%
2025-09-22
99.4%
2025-09-23
99.4%
2025-09-24
99.5%
2025-09-25
99.4%
2025-09-26
99.5%
2025-09-27
99.5%
2025-09-28
99.4%
2025-09-29
99.5%
2025-09-30
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

❌9 errors, 6 warnings

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

Errors

GTFS-rt stop_id does not exist in GTFS data E011 4 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • trip_id PRUNEDDU_2 stop_id Scola M&T Marcellesi does not exist in GTFS data stops.txt
  • trip_id PRUNEDDU_3 stop_id Scola M&T Marcellesi does not exist in GTFS data stops.txt
  • trip_id PRUNEDDU_1 stop_id Scola M&T Marcellesi does not exist in GTFS data stops.txt
  • trip_id PRUNEDDU_0_0 stop_id Scola M&T Marcellesi does not exist in GTFS data stops.txt

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 PRUNEDDU_1 stop_sequence 25 doesn't have arrival or departure

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 4 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors
  • GTFS-rt trip_id PRUNEDDU_2 stop_sequence 3 has stop_id Scola M&T Marcellesi but GTFS stop_sequence 3 has stop_id Scola M&T Marcellesi - stop_ids should be the same
  • GTFS-rt trip_id PRUNEDDU_3 stop_sequence 3 has stop_id Scola M&T Marcellesi but GTFS stop_sequence 3 has stop_id Scola M&T Marcellesi - stop_ids should be the same
  • GTFS-rt trip_id PRUNEDDU_1 stop_sequence 3 has stop_id Scola M&T Marcellesi but GTFS stop_sequence 3 has stop_id Scola M&T Marcellesi - stop_ids should be the same
  • GTFS-rt trip_id PRUNEDDU_0_0 stop_sequence 3 has stop_id Scola M&T Marcellesi but GTFS stop_sequence 3 has stop_id Scola M&T Marcellesi - stop_ids should be the same

Warnings

ID in one feed missing from the other W003 6 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 PRUNEDDU_0_0 is in TripUpdates but not in VehiclePositions feed
  • trip_id MARINA_1 is in TripUpdates but not in VehiclePositions feed
  • trip_id MARINA_2 is in TripUpdates but not in VehiclePositions feed
  • trip_id PRUNEDDU_1 is in TripUpdates but not in VehiclePositions feed
  • trip_id MARINA_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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 125 30 times (100 % 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 120 30 times (100 % 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 182 30 times (100 % 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 107 28 times (93 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 5 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-30 at 04:33 Europe/Paris.

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

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-09-30 at 04:33 Europe/Paris. You can look at the GTFS-RT documentation.

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