transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: Données en temps réel au format GTFS-RT (VehiclePosition)
Format: gtfs-rt
Download

This resource file is part of the dataset Réseau urbain Kicéo.

Download availability

2025-12-11
96.7%
2025-12-12
99.5%
2025-12-13
99.2%
2025-12-14
99.4%
2025-12-15
98.8%
2025-12-16
99.4%
2025-12-17
99.5%
2025-12-18
98.6%
2025-12-19
97.4%
2025-12-20
99.3%
2025-12-21
100%
2025-12-22
94.6%
2025-12-23
95.1%
2025-12-24
95.3%
2025-12-25
99.3%
2025-12-26
98.6%
2025-12-27
100%
2025-12-28
99.8%
2025-12-29
97.8%
2025-12-30
98.5%
2025-12-31
99.5%
2026-01-01
100%
2026-01-02
95.3%
2026-01-03
100%
2026-01-04
99.5%
2026-01-05
98.1%
2026-01-06
99.6%
2026-01-07
97.6%
2026-01-08
97.4%
2026-01-09
96%
2026-01-10
100%
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 2026-01-09 at 08:13 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 635 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 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 209 trip_id chouette:VehicleJourney:00e0ba0d-92fc-42cc-bd6f-ee28f7cd9e1c: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 166 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 635 route_id BSALigne611 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 209 route_id AurayVayagesLigne606 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 166 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 635 stop_id chouette:StopArea:30e65cbd-d8bf-4436-9752-6d999f3da93e:LOC does not exist in GTFS data stops.txt
  • vehicle_id 244 stop_id bre_vannes_2024_2025.17695 does not exist in GTFS data stops.txt
  • vehicle_id 209 stop_id chouette:StopArea:bdb39b3e-2a06-4a3c-a6d2-dac0953fc1f5:LOC does not exist in GTFS data stops.txt
  • vehicle_id 170 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 166 stop_id STP-DEPART does not exist in GTFS data stops.txt

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.62761,-2.830194) 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 107 trip_id 22-151060481 at (47.709347,-2.81607) 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-2499870721 at (47.723164,-2.591669) 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 281 trip_id 22-2516713473 at (47.655067,-2.873593) 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 1 error

Each vehicle should have a unique ID

Sample errors
  • entity ID 651806 has vehicle.id 97 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 8 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 56 does not have a timestamp
  • vehicle_id 72 does not have a timestamp
  • vehicle_id 64 does not have a timestamp
  • vehicle_id 48 does not have a timestamp
  • vehicle_id 356 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 169 speed of 28.333334 m/s (63.38 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 447 24 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 407 24 times (80 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 406 24 times (80 % of validations)
W001 Timestamps should be populated for all elements 187 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. 86 16 times (53 % of validations)
E052 Each vehicle should have a unique ID 23 10 times (33 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 10 8 times (27 % 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 6 times (20 % 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 9 3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-10 at 03:14 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 2026-01-10 at 03:14 Europe/Paris. You can look at the GTFS-RT documentation.

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