Resource details
Horaires Temps Réels du réseau A Citadina
This resource file is part of the dataset Réseau urbain A Citadina.
Download availability
Learn more
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
❌21 errors, 7 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-04 at 09:13 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 5 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_0 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_3 stop_id Scola M&T Marcellesi does not exist in GTFS data stops.txt
- alert entity ID alert:67c164df399724db61fa2fde stop_id Scola M&T Marcellesi does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2 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 MARINA_3 stop_sequence 25 arrival_time 08:59:12 (1743749952) is less than previous stop arrival_time 09:30:50 (1743751850) - times must increase between two sequential stops
- trip_id MARINA_3 stop_sequence 25 arrival_time 08:59:12 (1743749952) is less than previous stop departure_time 09:30:50 (1743751850) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 10 errors
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_3 stop_sequence 1 doesn't have arrival or departure
- trip_id MARINA_3 stop_sequence 2 doesn't have arrival or departure
- trip_id MARINA_3 stop_sequence 3 doesn't have arrival or departure
- trip_id PRUNEDDU_2 stop_sequence 0 doesn't have arrival or departure
- trip_id PRUNEDDU_2 stop_sequence 1 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_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
- 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_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
Warnings
ID in one feed missing from the other W003 7 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_4 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
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 | 113 | 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 | 85 | 29 times (97 % 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 | 70 | 28 times (93 % 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 | 85 | 26 times (87 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 14 | 7 times (23 % 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.