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

❌13 errors, 5 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-29 at 08:02 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 4 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 367 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 366 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 164 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 4 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 367 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 366 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 164 route_id MOBICEO does not exist in the GTFS data routes.txt

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

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

Sample errors

vehicle_id 165 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 367 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
vehicle_id 366 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 164 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 306 trip_id 2-251920390 at (47.633026,-2.673505) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Warnings

timestamp not populated W001 5 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 79 does not have a timestamp
vehicle_id 81 does not have a timestamp
vehicle_id 334 does not have a timestamp
vehicle_id 63 does not have a timestamp
vehicle_id 51 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	635	22 times (73 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	398	22 times (73 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	398	22 times (73 % of validations)
W001	Timestamps should be populated for all elements	159	22 times (73 % 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.	117	21 times (70 % of validations)
E052	Each vehicle should have a unique ID	27	14 times (47 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	16	13 times (43 % 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.	10	8 times (27 % 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-30 at 00:35 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-30 at 00:35 Europe/Paris. You can look at the GTFS-RT documentation.


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