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

❌68 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-04 at 08:09 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 168 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 169 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 251 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 166 trip_id ext:12071 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 244 trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb: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 168 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 169 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 251 route_id BSALigne611 does not exist in the GTFS data routes.txt
vehicle_id 166 route_id MATINEO does not exist in the GTFS data routes.txt
vehicle_id 244 route_id BSAScol61137 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 168 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 169 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 251 stop_id chouette:StopArea:30e65cbd-d8bf-4436-9752-6d999f3da93e:LOC does not exist in GTFS data stops.txt
vehicle_id 166 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 244 stop_id bre_vannes_2024_2025.18087 does not exist in GTFS data stops.txt

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 283 trip_id 22-1460142081 at (47.697495,-2.659186) 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 298 trip_id 22-3172532227-AFF-6-__CJV__ at (47.627197,-2.830469) 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.65682,-2.873943) 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 215 trip_id 22-2751528961 at (47.658302,-2.869182) 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 278 trip_id 22-2499870721 at (47.692207,-2.591949) 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 610394 has vehicle.id 97 which is used by more than one vehicle in the feed
entity ID 610412 has vehicle.id 334 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 9 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 118 does not have a timestamp
vehicle_id 381 does not have a timestamp
vehicle_id 49 does not have a timestamp
vehicle_id 86 does not have a timestamp
vehicle_id 373 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 213 speed of 27.777779 m/s (62.14 mph) is unrealistic

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	620	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)
W001	Timestamps should be populated for all elements	151	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.	124	21 times (72 % of validations)
E052	Each vehicle should have a unique ID	30	15 times (52 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	15	12 times (41 % 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 (24 % 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-05 at 05:00 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 2025-12-05 at 05:00 Europe/Paris. You can look at the GTFS-RT documentation.


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