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-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.9%
2025-11-29
100%
2025-11-30
100%
2025-12-01
96.5%
2025-12-02
99.8%
2025-12-03
99.8%
2025-12-04
98.5%
2025-12-05
97.9%
2025-12-06
100%
2025-12-07
99.5%
2025-12-08
99.2%
2025-12-09
98.7%
2025-12-10
98.8%
2025-12-11
96.7%
2025-12-12
99.5%
2025-12-13
99.2%
2025-12-14
99.4%
2025-12-15
98.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

❌88 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-15 at 08:14 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 24 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 183 trip_id chouette:VehicleJourney:9cc13582-74f4-4e03-9e7c-e24969614839:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 461 trip_id chouette:VehicleJourney:ab91280a-1f0b-4fda-b287-1dcf2e784b49:LOC 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 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 229 trip_id chouette:VehicleJourney:1267fcef-9e99-44f6-bfa8-33b9e7d96560:LOC 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 24 errors

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

Sample errors
  • vehicle_id 183 route_id MAURYScol60927 does not exist in the GTFS data routes.txt
  • vehicle_id 461 route_id CAT56Ligne604 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 358 route_id MorioLigne602 does not exist in the GTFS data routes.txt
  • vehicle_id 229 route_id AVBLigne608 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 183 stop_id bre_vannes_2024_2025.17559 does not exist in GTFS data stops.txt
  • vehicle_id 461 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96:LOC 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 358 stop_id chouette:StopArea:74e45eb3-ed17-47d1-b3fe-c7ea29f13232:LOC does not exist in GTFS data stops.txt
  • vehicle_id 229 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt

Vehicle position far from trip shape E029 12 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 306 trip_id 2-251854853 at (47.658504,-2.718938) 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 309 trip_id 22-3170959361-AFF-6-LM_____ at (47.70047,-2.769546) 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 208 trip_id 22-2315452417 at (47.72869,-2.59368) 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 356 trip_id 22-620822529 at (47.75693,-2.789473) 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 298 trip_id 22-3172532227-AFF-7-LM_____ at (47.62772,-2.829825) 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 4 errors

Each vehicle should have a unique ID

Sample errors
  • entity ID 623808 has vehicle.id 273 which is used by more than one vehicle in the feed
  • entity ID 623815 has vehicle.id 265 which is used by more than one vehicle in the feed
  • entity ID 623832 has vehicle.id 97 which is used by more than one vehicle in the feed
  • entity ID 623799 has vehicle.id 202 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 10 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 391 does not have a timestamp
  • vehicle_id 49 does not have a timestamp
  • vehicle_id 371 does not have a timestamp
  • vehicle_id 305 does not have a timestamp
  • vehicle_id 104 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 401 21 times (75 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 401 21 times (75 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 401 21 times (75 % of validations)
W001 Timestamps should be populated for all elements 138 21 times (75 % 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. 130 20 times (71 % of validations)
E052 Each vehicle should have a unique ID 32 15 times (54 % 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. 12 10 times (36 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 13 9 times (32 % 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.