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

❌74 errors, 9 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-26 at 08:03 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 23 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 389 trip_id ext:12069 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
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 170 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

GTFS-rt route_id does not exist in GTFS data E004 23 errors

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

Sample errors

vehicle_id 389 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 244 route_id BSAScol61137 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 170 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

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

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

Sample errors

vehicle_id 389 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
vehicle_id 244 stop_id bre_vannes_2024_2025.18093 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 170 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 position outside agency coverage area E028 1 error

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.

Sample errors

vehicle.id 457 at (48.28842,-2.826334) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Vehicle position far from trip shape E029 4 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 298 trip_id 22-3172532227-AFF-6-__CJV__ at (47.627544,-2.830237) 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 284 trip_id 22-2466447361 at (47.694378,-2.561581) 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 353 trip_id 22-2432761857 at (47.694515,-2.560281) 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 318 trip_id 2-251920390 at (47.633278,-2.674238) 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 8 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 51 does not have a timestamp
vehicle_id 177 does not have a timestamp
vehicle_id 27 does not have a timestamp
vehicle_id 54 does not have a timestamp
vehicle_id 247 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 260 speed of 27.222221 m/s (60.89 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	630	22 times (73 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	393	22 times (73 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	393	22 times (73 % of validations)
W001	Timestamps should be populated for all elements	166	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.	107	20 times (67 % of validations)
E052	Each vehicle should have a unique ID	25	13 times (43 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	14	12 times (40 % 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	7 times (23 % 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-26 at 22:03 Europe/Paris.

vehicle_positions (1) 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-26 at 22:03 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "599876",
      "vehicle": {
        "currentStopSequence": 14,
        "position": {
          "bearing": 69.0,
          "latitude": 47.63439178466797,
          "longitude": -2.938728094100952,
          "speed": 1.9444444179534912
        },
        "stopId": "5915",
        "timestamp": "1764159514",
        "trip": {
          "directionId": 1,
          "routeId": "160",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20251126",
          "startTime": "12:30:00",
          "tripId": "22-2684420097"
        },
        "vehicle": {
          "id": "198",
          "label": "A61",
          "licensePlate": "FH-578-NR"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1764191037"
  }
}