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 472 errors, 432 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-03-31 at 17:30 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 92 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 TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TRIPID-12069 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 92 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id MOBICEO does not exist in the GTFS data routes.txt
- route_id MOBICEO does not exist in the GTFS data routes.txt
- route_id MOBICEO does not exist in the GTFS data routes.txt
- route_id MOBICEO does not exist in the GTFS data routes.txt
- route_id MOBICEO does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 1 261 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id TRIPID-12069 stop_id STP-DEPART does not exist in GTFS data stops.txt
- trip_id TRIPID-12069 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
- trip_id TRIPID-12069 stop_id STP-DEPART does not exist in GTFS data stops.txt
- trip_id TRIPID-12069 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
- trip_id TRIPID-12069 stop_id STP-DEPART does not exist in GTFS data stops.txt
All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 E015 30 errors
All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt
Sample errors
- trip_id 2-152991563777 stop_id 1727 does not have location_type=0 in GTFS stops.txt
- trip_id 2-152991563777 stop_id 1729 does not have location_type=0 in GTFS stops.txt
- trip_id 2-152505024513 stop_id 3369 does not have location_type=0 in GTFS stops.txt
- trip_id 2-153780158466 stop_id 1758 does not have location_type=0 in GTFS stops.txt
- trip_id 2-152907677698 stop_id 1724 does not have location_type=0 in GTFS stops.txt
Sequential stop_time_update times are not increasing E022 1 995 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-152958074881 stop_sequence 8 arrival_time 17:14:53 (1743434093) is less than previous stop arrival_time 17:16:01 (1743434161) - times must increase between two sequential stops
- trip_id 2-152958074881 stop_sequence 8 arrival_time 17:14:53 (1743434093) is less than previous stop departure_time 17:16:05 (1743434165) - times must increase between two sequential stops
- trip_id 2-152958074881 stop_sequence 8 departure_time 17:15:38 (1743434138) is less than previous stop departure_time 17:16:05 (1743434165) - times must increase between two sequential stops
- trip_id 2-152958074881 stop_sequence 8 departure_time 17:15:38 (1743434138) is less than previous stop arrival_time 17:16:01 (1743434161) - times must increase between two sequential stops
- trip_id 2-152035262465 stop_sequence 20 arrival_time 17:49:08 (1743436148) is equal to previous stop arrival_time 17:49:08 (1743436148) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 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 2-153343819778 stop_sequence 9 departure_time 17:29:17 (1743434957) is less than the same stop arrival_time 17:30:02 (1743435002) - departure time must be equal to or greater than arrival time
- trip_id 2-153276776450 stop_sequence 3 departure_time 17:28:09 (1743434889) is less than the same stop arrival_time 17:29:25 (1743434965) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 296 errors
Timestamps should be populated for all elements
Sample errors
- trip_id TRIPID-12069 does not have a timestamp
- trip_id TRIPID-12069 does not have a timestamp
- trip_id TRIPID-12069 does not have a timestamp
- trip_id TRIPID-12069 does not have a timestamp
- trip_id TRIPID-12069 does not have a timestamp
vehicle_id not populated W002 136 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 2-319160362 does not have a vehicle_id
- trip_id 2-336134271 does not have a vehicle_id
- trip_id 2-19139827 does not have a vehicle_id
- trip_id 2-17044653 does not have a vehicle_id
- trip_id 2-19211856 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 97 801 | 26 times (90 % of validations) |
| W001 | Timestamps should be populated for all elements | 14 617 | 26 times (90 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 11 302 | 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 | 3 182 | 24 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 2 951 | 24 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 39 301 | 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. | 160 | 24 times (83 % of validations) |
| E015 | All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt | 1 415 | 19 times (66 % of validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 7 | 2 times (7 % 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 | 6 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-01 at 01:47 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-04-01 at 01:47 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743464850"
}
}