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

Resource details

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

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

❌2 966 errors, 1 281 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-05 at 08:01 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 25 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors

trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:aaa13cdd-af52-4aae-9f1a-224f4c8404f6:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:b4c75824-d6d6-40be-a33b-9b0675a2b79d:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527: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 21 errors

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

Sample errors

route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
route_id BSAScol61133 does not exist in the GTFS data routes.txt
route_id MorioLigne602 does not exist in the GTFS data routes.txt
route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
route_id MAURYLigne609 does not exist in the GTFS data routes.txt

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

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

Sample errors

trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:413a86f6-9498-468f-a2e8-77f5c0a9642b:LOC does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:c7278b07-f2fa-40a0-a19f-b93e0f1b1651:LOC does not exist in GTFS data stops.txt
trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC stop_id chouette:StopArea:d2c53593-28a8-4ebb-bed3-91cee01b4496:LOC does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 2 757 errors

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors

trip_id 2-33620094-M2B-LMCJV__ stop_sequence 12 arrival_time 06:43:14 (1764913394) is equal to previous stop arrival_time 06:43:14 (1764913394) - times must increase between two sequential stops
trip_id 2-33620094-M2B-LMCJV__ stop_sequence 12 arrival_time 06:43:14 (1764913394) is equal to previous stop departure_time 06:43:14 (1764913394) - times must increase between two sequential stops
trip_id 2-33620094-M2B-LMCJV__ stop_sequence 12 departure_time 06:43:14 (1764913394) is equal to previous stop departure_time 06:43:14 (1764913394) - times must increase between two sequential stops
trip_id 2-33620094-M2B-LMCJV__ stop_sequence 12 departure_time 06:43:14 (1764913394) is equal to previous stop arrival_time 06:43:14 (1764913394) - times must increase between two sequential stops
trip_id 2-33620094-M2B-LMCJV__ stop_sequence 15 arrival_time 06:45:14 (1764913514) is equal to previous stop arrival_time 06:45:14 (1764913514) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 4 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 22-1292304385 stop_sequence 2 has stop_id 6642 but GTFS stop_sequence 2 has stop_id 6653 - stop_ids should be the same
GTFS-rt trip_id 22-1292304385 stop_sequence 3 has stop_id 6653 but GTFS stop_sequence 3 has stop_id 6642 - stop_ids should be the same
GTFS-rt trip_id 22-1292304385 stop_sequence 2 has stop_id 6642 but GTFS stop_sequence 2 has stop_id 6653 - stop_ids should be the same
GTFS-rt trip_id 22-1292304385 stop_sequence 3 has stop_id 6653 but GTFS stop_sequence 3 has stop_id 6642 - stop_ids should be the same

Warnings

timestamp not populated W001 719 errors

Timestamps should be populated for all elements

Sample errors

trip_id chouette:VehicleJourney:6629bdb4-a14f-4c4d-96e9-5ccc0b9409c7:LOC does not have a timestamp
trip_id 2-33620094-M2B-LMCJV__ does not have a timestamp
trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374:LOC does not have a timestamp
trip_id 22-822149121 does not have a timestamp
trip_id 2-73203743-V426B-LMCJV__ does not have a timestamp

vehicle_id not populated W002 562 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 2-17236055 does not have a vehicle_id
trip_id 2-19202121 does not have a vehicle_id
trip_id 2-17236054 does not have a vehicle_id
trip_id 2-19202120 does not have a vehicle_id
trip_id 2-17236053 does not have a vehicle_id

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
W001	Timestamps should be populated for all elements	14 974	27 times (87 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	11 651	26 times (84 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	2 022	24 times (77 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	459	24 times (77 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	3 159	24 times (77 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	62 022	24 times (77 % of validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	135	23 times (74 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	164	11 times (35 % 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)
E041	Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-06 at 00:06 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-06 at 00:06 Europe/Paris. You can look at the GTFS-RT documentation.


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