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

❌61 errors, 12 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-29 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 31 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 52 trip_id 2-319160397-V627A-LMCJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 20 trip_id 2-201523238-V129A-L_C_V__ 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 71 trip_id 2-85983266-M575A-LMC____ does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 76 trip_id 2-73203738-V426A-LMCJV__ 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 13 errors

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

Sample errors

vehicle_id 170 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 166 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 169 route_id MOBICEO does not exist in the GTFS data routes.txt
vehicle_id 248 route_id BSALigne611 does not exist in the GTFS data routes.txt
vehicle_id 247 route_id BSALigne611 does not exist in the GTFS data routes.txt

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

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

Sample errors

vehicle_id 170 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 166 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 169 stop_id STP-DEPART does not exist in GTFS data stops.txt
vehicle_id 248 stop_id chouette:StopArea:f22729a5-ff01-4cb2-817c-129545525489:LOC does not exist in GTFS data stops.txt
vehicle_id 247 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC does not exist in GTFS data stops.txt

trip start_time does not match first GTFS arrival_time E023 3 errors

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

Sample errors

GTFS-rt vehicle_id 120 trip_id 2-285868035 start_time is 07:48:00 and GTFS initial arrival_time is 07:45:00 - times do not match
GTFS-rt vehicle_id 332 trip_id 2-288161794 start_time is 07:18:00 and GTFS initial arrival_time is 07:15:00 - times do not match
GTFS-rt vehicle_id 342 trip_id 2-288097130 start_time is 07:44:00 and GTFS initial arrival_time is 07:45:00 - times do not match

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 38 trip_id 2-73138204 at (47.699123,-2.768859) 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 11 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 57 does not have a timestamp
vehicle_id 390 does not have a timestamp
vehicle_id 83 does not have a timestamp
vehicle_id 86 does not have a timestamp
vehicle_id 59 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 451 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	453	23 times (79 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	429	23 times (79 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	429	23 times (79 % of validations)
W001	Timestamps should be populated for all elements	166	23 times (79 % 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.	120	18 times (62 % of validations)
E052	Each vehicle should have a unique ID	29	13 times (45 % 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.	11	10 times (34 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	11	9 times (31 % 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	6	2 times (7 % of validations)

GTFS-RT feed content

Entities

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


{
  "entity": [
    {
      "id": "639516",
      "vehicle": {
        "currentStopSequence": 35,
        "position": {
          "bearing": 240.0,
          "latitude": 47.682437896728516,
          "longitude": -2.7759830951690674,
          "speed": 10.277777671813965
        },
        "stopId": "552",
        "timestamp": "1767037151",
        "trip": {
          "directionId": 1,
          "routeId": "1",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20251229",
          "startTime": "20:05:00",
          "tripId": "2-19136580"
        },
        "vehicle": {
          "id": "33",
          "label": "75402",
          "licensePlate": "GH 197 SN"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1767037175"
  }
}