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

❌106 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-16 at 18:05 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 32 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 167 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
vehicle_id 379 trip_id ext:10866 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 389 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 32 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 167 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
vehicle_id 379 route_id DFL does not exist in the GTFS data routes.txt
vehicle_id 389 route_id MOBICEO does not exist in the GTFS data routes.txt

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

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

Sample errors

vehicle_id 165 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
vehicle_id 167 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
vehicle_id 164 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
vehicle_id 379 stop_id STP-TESTSENE does not exist in GTFS data stops.txt
vehicle_id 389 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 379 at (0.0,0.0) 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 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 267 trip_id 2-218431566 at (47.697433,-2.771559) 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-251920392 at (47.634884,-2.679565) 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 202 trip_id 22-2734751746 at (47.69671,-2.794799) 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 313 trip_id 22-1359413249 at (47.68082,-2.76992) 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 110 trip_id 22-2013462530 at (47.57452,-2.708197) 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 3 errors

Each vehicle should have a unique ID

Sample errors

entity ID 626728 has vehicle.id 358 which is used by more than one vehicle in the feed
entity ID 626286 has vehicle.id 241 which is used by more than one vehicle in the feed
entity ID 626179 has vehicle.id 311 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 5 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 206 does not have a timestamp
vehicle_id 83 does not have a timestamp
vehicle_id 282 does not have a timestamp
vehicle_id 37 does not have a timestamp
vehicle_id 391 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 163 speed of 29.166666 m/s (65.24 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	491	24 times (80 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	491	24 times (80 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	491	24 times (80 % of validations)
W001	Timestamps should be populated for all elements	156	24 times (80 % 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.	149	23 times (77 % of validations)
E052	Each vehicle should have a unique ID	41	18 times (60 % 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.	14	12 times (40 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	15	11 times (37 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-16 at 21:49 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-12-16 at 21:49 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "626721",
      "vehicle": {
        "currentStopSequence": 4,
        "position": {
          "bearing": 0.0,
          "speed": 0.0
        },
        "stopId": "STP-TESTSENE",
        "timestamp": "1765897116",
        "trip": {
          "directionId": 0,
          "routeId": "DFL",
          "scheduleRelationship": "UNSCHEDULED",
          "startDate": "20251216",
          "startTime": "10:00:00",
          "tripId": "ext:10866"
        },
        "vehicle": {
          "id": "379",
          "label": "TEST TGMVA - AXIO4",
          "licensePlate": "00-TEST-00"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1765918142"
  }
}