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-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
97%
2025-11-20
93.4%
2025-11-21
99.4%
2025-11-22
100%
2025-11-23
100%
2025-11-24
99.5%
2025-11-25
97.9%
2025-11-26
99.8%
2025-11-27
99.9%
2025-11-28
99.8%
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

❌89 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-28 at 08:00 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 26 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 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 179 trip_id chouette:VehicleJourney:cb277215-b8ef-4848-8f33-16880fd56527:LOC 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 366 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 163 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 26 errors

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

Sample errors
  • vehicle_id 251 route_id BSALigne611 does not exist in the GTFS data routes.txt
  • vehicle_id 179 route_id MAURYLigne609 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 366 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 163 route_id MOBICEO does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 251 stop_id chouette:StopArea:30e65cbd-d8bf-4436-9752-6d999f3da93e:LOC does not exist in GTFS data stops.txt
  • vehicle_id 179 stop_id chouette:StopArea:2ef8e4c3-a005-47c2-8794-d057a0c5b79e:LOC 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 366 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 163 stop_id STP-DEPART does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 2 errors

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 229 at (47.54981,-2.468091) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 457 at (48.180607,-2.762514) 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 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 285 trip_id 22-2298544129 at (47.790268,-2.594896) 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-2013331457 at (47.53483,-2.832271) 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 97 trip_id 22-3070296065 at (47.717625,-2.887939) 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 324 trip_id 22-1292304385 at (47.68649,-2.692743) 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 300 trip_id 22-3154378753 at (47.6403,-2.688154) 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 602952 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 89 does not have a timestamp
  • vehicle_id 247 does not have a timestamp
  • vehicle_id 177 does not have a timestamp
  • vehicle_id 85 does not have a timestamp
  • vehicle_id 86 does not have a timestamp

vehicle speed is unrealistic W004 2 errors

vehicle.position.speed has an unrealistic speed that may be incorrect

Sample errors
  • vehicle.id 460 speed of 26.38889 m/s (59.03 mph) is unrealistic
  • vehicle.id 461 speed of 26.38889 m/s (59.03 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 647 22 times (73 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 410 22 times (73 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 410 22 times (73 % of validations)
W001 Timestamps should be populated for all elements 161 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. 116 20 times (67 % of validations)
E052 Each vehicle should have a unique ID 27 14 times (47 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 16 13 times (43 % 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 9 times (30 % 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

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.