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
❌82 errors, 9 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-19 at 08:05 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 24 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 163 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 170 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 177 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 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
- vehicle_id 179 trip_id chouette:VehicleJourney:e9b0f44f-fc90-459e-a0ff-6016a552f524: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 24 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 163 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 170 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 177 route_id MAURYLigne609 does not exist in the GTFS data routes.txt
- vehicle_id 345 route_id CAT56Scol60380 does not exist in the GTFS data routes.txt
- vehicle_id 179 route_id MAURYLigne609 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 24 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 163 stop_id STP-DEPART does not exist in GTFS data stops.txt
- vehicle_id 170 stop_id STP-DEPART does not exist in GTFS data stops.txt
- vehicle_id 177 stop_id chouette:StopArea:3787ff95-aebf-4d5c-a4b7-9de7c34c7f06:LOC does not exist in GTFS data stops.txt
- vehicle_id 345 stop_id bre_vannes_2024_2025.14553 does not exist in GTFS data stops.txt
- vehicle_id 179 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC does not exist in GTFS data stops.txt
Vehicle position far from trip shape E029 8 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 336 trip_id 22-1359282177 at (47.710983,-2.779503) 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 318 trip_id 2-251920390 at (47.631863,-2.663432) 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 269 trip_id 22-2281897985 at (47.69735,-2.659518) 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.6563,-2.873651) 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.698933,-2.538509) 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 2 errors
Each vehicle should have a unique ID
Sample errors
- entity ID 663554 has vehicle.id 97 which is used by more than one vehicle in the feed
- entity ID 664438 has vehicle.id 359 which is used by more than one vehicle in the feed
Warnings
timestamp not populated W001 8 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 179 does not have a timestamp
- vehicle_id 55 does not have a timestamp
- vehicle_id 72 does not have a timestamp
- vehicle_id 119 does not have a timestamp
- vehicle_id 86 does not have a timestamp
vehicle speed is unrealistic W004 1 error
vehicle.position.speed has an unrealistic speed that may be incorrect
Sample errors
- vehicle.id 120 speed of 28.055555 m/s (62.76 mph) is unrealistic
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 | 373 | 21 times (78 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 333 | 21 times (78 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 332 | 21 times (78 % of validations) |
| W001 | Timestamps should be populated for all elements | 164 | 21 times (78 % 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. | 68 | 15 times (56 % of validations) |
| E052 | Each vehicle should have a unique ID | 11 | 9 times (33 % 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. | 7 | 6 times (22 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 4 | 4 times (15 % 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 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-21 at 21:55 Europe/Paris.
vehicle_positions (2) 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 2026-01-21 at 21:55 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "666858",
"vehicle": {
"currentStopSequence": 18,
"position": {
"bearing": 179.0,
"latitude": 47.69798278808594,
"longitude": -2.7747950553894043,
"speed": 5.833333492279053
},
"stopId": "5974",
"timestamp": "1768999807",
"trip": {
"directionId": 1,
"routeId": "140",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260121",
"startTime": "12:46:00",
"tripId": "22-2349137922"
},
"vehicle": {
"id": "212",
"label": "A62",
"licensePlate": "ER-894-PZ"
}
}
},
{
"id": "667766",
"vehicle": {
"currentStopSequence": 12,
"position": {
"bearing": 222.0,
"latitude": 47.8830680847168,
"longitude": -2.8327720165252686,
"speed": 5.0
},
"stopId": "bre_vannes_2024_2025.14599",
"timestamp": "1769017417",
"trip": {
"directionId": 0,
"routeId": "CAT56Scol60379",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260121",
"startTime": "17:30:00",
"tripId": "chouette:VehicleJourney:30ea24b1-4f43-4d1c-afca-c4b4c95bd630:LOC"
},
"vehicle": {
"id": "326",
"label": "37801",
"licensePlate": "FS 789 JB"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769028936"
}
}