gtfs-rt Transport open dataset - Données en temps réel au format GTFS-RT (VehiclePosition) for Réseau urbain Kicéo - CA Golfe du Morbihan

Resource details

File name: Données en temps réel au format GTFS-RT (VehiclePosition)

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Kicéo.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌23 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-10 at 08:11 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 7 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 165 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 178 trip_id chouette:VehicleJourney:b06d0e1d-00b1-4f2f-bcd9-10ed2d719f04:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 247 trip_id chouette:VehicleJourney:b705ed83-6c28-4cc1-b505-5597ff7f05fa:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 357 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 163 trip_id ext: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 7 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

vehicle_id 165 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 178 route_id MAURYLigne609 does not exist in the GTFS data routes.txt
vehicle_id 247 route_id BSALigne611 does not exist in the GTFS data routes.txt
vehicle_id 357 route_id MorioLigne602 does not exist in the GTFS data routes.txt
vehicle_id 163 route_id MOBICEO does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 7 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

vehicle_id 165 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
vehicle_id 178 stop_id chouette:StopArea:5b4834b3-bdf7-402b-b6b3-d6e1db89d36f:LOC does not exist in GTFS data stops.txt
vehicle_id 247 stop_id chouette:StopArea:30e65cbd-d8bf-4436-9752-6d999f3da93e:LOC does not exist in GTFS data stops.txt
vehicle_id 357 stop_id chouette:StopArea:74e45eb3-ed17-47d1-b3fe-c7ea29f13232:LOC does not exist in GTFS data stops.txt
vehicle_id 163 stop_id STP-DEPART does not exist in GTFS data stops.txt

Vehicle position far from trip shape E029 1 error

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 57 trip_id 2-117571588 at (47.62396,-2.730459) 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 653938 has vehicle.id 357 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 48 does not have a timestamp
vehicle_id 81 does not have a timestamp
vehicle_id 71 does not have a timestamp
vehicle_id 85 does not have a timestamp
vehicle_id 83 does not have a timestamp

Validate this GTFS-RT now

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	430	24 times (80 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	390	24 times (80 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	389	24 times (80 % of validations)
W001	Timestamps should be populated for all elements	189	24 times (80 % 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.	80	16 times (53 % of validations)
E052	Each vehicle should have a unique ID	22	10 times (33 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	8	7 times (23 % 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 (20 % 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	9	3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-10 at 23:54 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-10 at 23:54 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1768085671"
  }
}