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-10-20
97.6%
2025-10-21
99.7%
2025-10-22
99.4%
2025-10-23
99.7%
2025-10-24
100%
2025-10-25
99.6%
2025-10-26
100%
2025-10-27
99.1%
2025-10-28
99.5%
2025-10-29
97.4%
2025-10-30
98.9%
2025-10-31
98.2%
2025-11-01
100%
2025-11-02
100%
2025-11-03
97.7%
2025-11-04
98.9%
2025-11-05
99%
2025-11-06
96.8%
2025-11-07
96.4%
2025-11-08
100%
2025-11-09
100%
2025-11-10
99.4%
2025-11-11
100%
2025-11-12
98.6%
2025-11-13
99.5%
2025-11-14
99.1%
2025-11-15
99.4%
2025-11-16
100%
2025-11-17
96.8%
2025-11-18
98.6%
2025-11-19
96.6%
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

❌76 errors, 5 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-18 at 08:02 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 22 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 247 trip_id chouette:VehicleJourney:1ab68529-c117-4693-a98a-4a4de751be95:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 243 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 169 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 358 trip_id chouette:VehicleJourney:110285b0-a061-467e-a681-25e4aaf45af4:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 366 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 22 errors

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

Sample errors
  • vehicle_id 247 route_id BSALigne611 does not exist in the GTFS data routes.txt
  • vehicle_id 243 route_id BSALigne611 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 358 route_id MorioLigne602 does not exist in the GTFS data routes.txt
  • vehicle_id 366 route_id MOBICEO does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 247 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC does not exist in GTFS data stops.txt
  • vehicle_id 243 stop_id chouette:StopArea:30e65cbd-d8bf-4436-9752-6d999f3da93e:LOC 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 358 stop_id chouette:StopArea:80b96852-8a75-4549-abbc-56e32fb43823:LOC does not exist in GTFS data stops.txt
  • vehicle_id 366 stop_id STP-DEPART does not exist in GTFS data stops.txt

Vehicle position far from trip shape E029 8 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 250 trip_id 22-6157369345 at (47.737118,-2.684049) 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 337 trip_id 22-1292304385 at (47.71413,-2.755118) 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 354 trip_id 22-2634088449 at (47.639545,-2.867883) 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 334 trip_id 22-2818768897 at (47.57138,-2.601008) 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 275 trip_id 22-2466447361 at (47.68514,-2.571647) 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 2 errors

Each vehicle should have a unique ID

Sample errors
  • entity ID 590314 has vehicle.id 357 which is used by more than one vehicle in the feed
  • entity ID 589061 has vehicle.id 97 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 295 does not have a timestamp
  • vehicle_id 177 does not have a timestamp
  • vehicle_id 72 does not have a timestamp
  • vehicle_id 27 does not have a timestamp
  • vehicle_id 97 does not have a timestamp
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 613 23 times (74 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 376 23 times (74 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 375 23 times (74 % of validations)
W001 Timestamps should be populated for all elements 178 23 times (74 % 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. 100 20 times (65 % of validations)
E052 Each vehicle should have a unique ID 18 10 times (32 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 10 9 times (29 % 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-19 at 22:24 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 2025-11-19 at 22:24 Europe/Paris. You can look at the GTFS-RT documentation.

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