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
❌46 errors, 5 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-03-31 at 09:13 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 14 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 168 trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 232 trip_id 0807 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 229 trip_id 0804 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 244 trip_id ANVAN.19421 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 347 trip_id 404 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 14 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 168 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 232 route_id SAEIV.26 does not exist in the GTFS data routes.txt
- vehicle_id 229 route_id SAEIV.26 does not exist in the GTFS data routes.txt
- vehicle_id 244 route_id bre_vannes_2024_2025.1612195510832 does not exist in the GTFS data routes.txt
- vehicle_id 347 route_id SAEIVTEO.47 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 14 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 168 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
- vehicle_id 232 stop_id SAEIV.50 does not exist in GTFS data stops.txt
- vehicle_id 229 stop_id SP199031 does not exist in GTFS data stops.txt
- vehicle_id 244 stop_id bre_vannes_2024_2025.19437 does not exist in GTFS data stops.txt
- vehicle_id 347 stop_id SP291499 does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 4 errors
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 347 at (47.766853,-2.494977) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 307 at (47.926983,-2.384854) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 248 at (47.846592,-2.700413) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 179 at (47.693123,-2.394372) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Warnings
timestamp not populated W001 5 errors
Timestamps should be populated for all elements
Sample errors
- vehicle_id 50 does not have a timestamp
- vehicle_id 42 does not have a timestamp
- vehicle_id 21 does not have a timestamp
- vehicle_id 63 does not have a timestamp
- vehicle_id 25 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 | 1 215 | 20 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 168 | 20 times (83 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 127 | 20 times (83 % of validations) |
| W001 | Timestamps should be populated for all elements | 156 | 20 times (83 % 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. | 95 | 19 times (79 % of validations) |
| E015 | All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt | 34 | 13 times (54 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 13 | 10 times (42 % 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. | 11 | 7 times (29 % of validations) |
| E052 | Each vehicle should have a unique ID | 4 | 4 times (17 % 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 | 5 | 1 times (4 % 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.
vehicle_positionsDecoded 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": "1743464849"
}
}