Resource details
This resource file is part of the dataset Réseau urbain Kicéo.
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
❌3,167 errors, 1,280 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-28 at 08:07 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 22 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 chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:b4c75824-d6d6-40be-a33b-9b0675a2b79d:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:67309930-e07e-49b6-afc5-46c916cff303:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id chouette:VehicleJourney:b63ae62c-dd08-4c0a-b966-8df89fe347b1:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 22 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id CAT56Scol60375 does not exist in the GTFS data routes.txt
- route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
- route_id CAT56Ligne604 does not exist in the GTFS data routes.txt
- route_id BSAScol61137 does not exist in the GTFS data routes.txt
- route_id BSALigne611 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 152 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.14593 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.14597 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.25055 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id bre_vannes_2024_2025.14585 does not exist in GTFS data stops.txt
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC stop_id keoskol.11214710 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2,853 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 2-121765929 stop_sequence 34 arrival_time 08:15:35 (1769584535) is equal to previous stop arrival_time 08:15:35 (1769584535) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 arrival_time 08:15:35 (1769584535) is equal to previous stop departure_time 08:15:35 (1769584535) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:15:35 (1769584535) is equal to previous stop departure_time 08:15:35 (1769584535) - times must increase between two sequential stops
- trip_id 2-121765929 stop_sequence 34 departure_time 08:15:35 (1769584535) is equal to previous stop arrival_time 08:15:35 (1769584535) - times must increase between two sequential stops
- trip_id 2-51118087 stop_sequence 32 arrival_time 08:09:35 (1769584175) is equal to previous stop arrival_time 08:09:35 (1769584175) - times must increase between two sequential stops
trip start_time does not match first GTFS arrival_time E023 10 errors
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Sample errors
- GTFS-rt trip_id 2-5671092818 start_time is 13:15:00 and GTFS initial arrival_time is 13:20:00 - times do not match
- GTFS-rt trip_id 2-5671027272 start_time is 11:22:00 and GTFS initial arrival_time is 11:32:00 - times do not match
- GTFS-rt trip_id 2-5671092439 start_time is 11:50:00 and GTFS initial arrival_time is 12:00:00 - times do not match
- GTFS-rt trip_id 2-5671026900 start_time is 12:20:00 and GTFS initial arrival_time is 12:35:00 - times do not match
- GTFS-rt trip_id 2-5671092232 start_time is 17:30:00 and GTFS initial arrival_time is 17:25:00 - times do not match
stop_time_update departure time is before arrival time E025 4 errors
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.
Sample errors
- trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC stop_sequence 10 departure_time 08:06:55 (1769584015) is less than the same stop arrival_time 08:07:20 (1769584040) - departure time must be equal to or greater than arrival time
- trip_id 2-319160383 stop_sequence 13 departure_time 08:06:48 (1769584008) is less than the same stop arrival_time 08:07:07 (1769584027) - departure time must be equal to or greater than arrival time
- trip_id 2-52756519 stop_sequence 3 departure_time 08:07:14 (1769584034) is less than the same stop arrival_time 08:07:25 (1769584045) - departure time must be equal to or greater than arrival time
- trip_id 22-2198142977 stop_sequence 3 departure_time 08:07:05 (1769584025) is less than the same stop arrival_time 08:07:26 (1769584046) - departure time must be equal to or greater than arrival time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 104 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 2-5671092227 stop_sequence 7 has stop_id 4359 but GTFS stop_sequence 7 has stop_id 6816 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 8 has stop_id 4360 but GTFS stop_sequence 8 has stop_id 4359 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 9 has stop_id 4419 but GTFS stop_sequence 9 has stop_id 4360 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 10 has stop_id 4347 but GTFS stop_sequence 10 has stop_id 4419 - stop_ids should be the same
- GTFS-rt trip_id 2-5671092227 stop_sequence 11 has stop_id 4350 but GTFS stop_sequence 11 has stop_id 4347 - stop_ids should be the same
Warnings
timestamp not populated W001 721 errors
Timestamps should be populated for all elements
Sample errors
- trip_id chouette:VehicleJourney:3df567e2-4557-4e9c-ac99-3b7cb8a00726:LOC does not have a timestamp
- trip_id 2-319160397 does not have a timestamp
- trip_id 22-486604801 does not have a timestamp
- trip_id 2-288161794 does not have a timestamp
- trip_id 2-73138204 does not have a timestamp
vehicle_id not populated W002 559 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 2-169279502 does not have a vehicle_id
- trip_id 2-168099873 does not have a vehicle_id
- trip_id 2-73203744 does not have a vehicle_id
- trip_id 2-34144415 does not have a vehicle_id
- trip_id 2-34144413 does not have a vehicle_id
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 14,450 | 26 times (90 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 11,488 | 26 times (90 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 568 | 24 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 423 | 24 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2,970 | 24 times (83 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 63,735 | 24 times (83 % 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. | 130 | 23 times (79 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 118 | 12 times (41 % 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 | 1,150 | 12 times (41 % 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.