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

✅No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-23 at 08:06 Europe/Paris using the MobilityData GTFS-RT validator.

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	585	20 times (69 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	348	20 times (69 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	348	20 times (69 % of validations)
W001	Timestamps should be populated for all elements	153	20 times (69 % 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.	96	18 times (62 % of validations)
E052	Each vehicle should have a unique ID	22	12 times (41 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	12	10 times (34 % 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.	6	6 times (21 % 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-11-25 at 01:18 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-11-25 at 01:18 Europe/Paris. You can look at the GTFS-RT documentation.


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