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
❌74 errors, 6 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-09 at 08:10 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
- vehicle_id 183 trip_id chouette:VehicleJourney:9cc13582-74f4-4e03-9e7c-e24969614839:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 375 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 461 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
- vehicle_id 438 trip_id chouette:VehicleJourney:b0f613b9-a746-4109-b3ca-f25bf87e95a5:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 345 trip_id chouette:VehicleJourney:24da96cb-e04d-417c-97a3-a9fdf9cbe556: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
- vehicle_id 183 route_id MAURYScol60927 does not exist in the GTFS data routes.txt
- vehicle_id 375 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 461 route_id CAT56Ligne604 does not exist in the GTFS data routes.txt
- vehicle_id 438 route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
- vehicle_id 345 route_id CAT56Scol60380 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 22 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 183 stop_id bre_vannes_2024_2025.18829 does not exist in GTFS data stops.txt
- vehicle_id 375 stop_id STP-DEPART does not exist in GTFS data stops.txt
- vehicle_id 461 stop_id chouette:StopArea:2a0f57b9-f432-405d-bfd4-32246e61917a:LOC does not exist in GTFS data stops.txt
- vehicle_id 438 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
- vehicle_id 345 stop_id bre_vannes_2024_2025.28004 does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 1 error
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.
Sample errors
- vehicle.id 183 at (47.663136,-2.462446) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Vehicle position far from trip shape E029 6 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 214 trip_id 22-2499870721 at (47.696125,-2.627648) 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 129 trip_id 22-6174212097 at (47.701492,-2.809455) 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 297 trip_id 22-2113994753 at (47.576035,-2.626938) 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 265 trip_id 22-2650865666 at (47.659218,-2.868892) 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 241 trip_id 22-6157369345 at (47.715557,-2.682447) 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 is not unique E052 1 error
Each vehicle should have a unique ID
Sample errors
- entity ID 616366 has vehicle.id 97 which is used by more than one vehicle in the feed
Warnings
timestamp not populated W001 6 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 22 does not have a timestamp
- vehicle_id 373 does not have a timestamp
- vehicle_id 86 does not have a timestamp
- vehicle_id 469 does not have a timestamp
- vehicle_id 371 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 | 536 | 22 times (76 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 408 | 22 times (76 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 408 | 22 times (76 % 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 | 22 times (76 % of validations) |
| W001 | Timestamps should be populated for all elements | 144 | 22 times (76 % of validations) |
| E052 | Each vehicle should have a unique ID | 29 | 15 times (52 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 14 | 11 times (38 % 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. | 11 | 9 times (31 % 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 (3 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-10 at 01:10 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-10 at 01:10 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1765325424"
}
}