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
❌65 errors, 8 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-03 at 08:02 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 20 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 179 trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 168 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 358 trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 166 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 347 trip_id chouette:VehicleJourney:ab91280a-1f0b-4fda-b287-1dcf2e784b49: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 20 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 179 route_id MAURYLigne609 does not exist in the GTFS data routes.txt
- vehicle_id 168 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 358 route_id MorioLigne602 does not exist in the GTFS data routes.txt
- vehicle_id 166 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 347 route_id CAT56Ligne604 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 20 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 179 stop_id chouette:StopArea:a2aee715-f649-4118-aa2d-b6f7719a6aad:LOC does not exist in GTFS data stops.txt
- vehicle_id 168 stop_id STP-DEPART does not exist in GTFS data stops.txt
- vehicle_id 358 stop_id chouette:StopArea:2b3ddbd2-6c81-48c1-ae43-0b35901be04d:LOC does not exist in GTFS data stops.txt
- vehicle_id 166 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
- vehicle_id 347 stop_id chouette:StopArea:2a0f57b9-f432-405d-bfd4-32246e61917a:LOC does not exist in GTFS data stops.txt
Vehicle position far from trip shape E029 5 errors
The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.
Sample errors
- vehicle.id 318 trip_id 2-251920390 at (47.63752,-2.682929) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 110 trip_id 22-2013331457 at (47.53421,-2.832) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 285 trip_id 22-2466447361 at (47.685665,-2.571756) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 324 trip_id 22-1610678273 at (47.685883,-2.70709) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 353 trip_id 22-2432761857 at (47.694496,-2.560643) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
timestamp not populated W001 8 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 470 does not have a timestamp
- vehicle_id 247 does not have a timestamp
- vehicle_id 87 does not have a timestamp
- vehicle_id 27 does not have a timestamp
- vehicle_id 366 does not have a timestamp
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 600 | 21 times (75 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 388 | 21 times (75 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 388 | 21 times (75 % of validations) |
| W001 | Timestamps should be populated for all elements | 142 | 21 times (75 % of validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 118 | 20 times (71 % of validations) |
| E052 | Each vehicle should have a unique ID | 28 | 14 times (50 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 14 | 11 times (39 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 9 | 7 times (25 % 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 | 1 | 1 times (4 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-04 at 02:04 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-12-04 at 02:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764810241"
}
}