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-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.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
95.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

❌55 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-05 at 08:06 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 18 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 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 419 trip_id chouette:VehicleJourney:53fde64b-2101-4fa3-a9b4-662bc437d21e:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 165 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 177 trip_id chouette:VehicleJourney:e9b0f44f-fc90-459e-a0ff-6016a552f524: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

GTFS-rt route_id does not exist in GTFS data E004 18 errors

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

Sample errors
  • vehicle_id 358 route_id MorioLigne602 does not exist in the GTFS data routes.txt
  • vehicle_id 419 route_id AurayVayagesLigne606 does not exist in the GTFS data routes.txt
  • vehicle_id 165 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 177 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

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

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

Sample errors
  • vehicle_id 358 stop_id chouette:StopArea:2b3ddbd2-6c81-48c1-ae43-0b35901be04d:LOC does not exist in GTFS data stops.txt
  • vehicle_id 419 stop_id chouette:StopArea:bdb39b3e-2a06-4a3c-a6d2-dac0953fc1f5:LOC does not exist in GTFS data stops.txt
  • vehicle_id 165 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • vehicle_id 177 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96: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 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 306 trip_id 2-251920390 at (47.629963,-2.65699) 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 6 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 177 does not have a timestamp
  • vehicle_id 470 does not have a timestamp
  • vehicle_id 31 does not have a timestamp
  • vehicle_id 63 does not have a timestamp
  • vehicle_id 86 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 452 23 times (77 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 412 23 times (77 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 411 23 times (77 % of validations)
W001 Timestamps should be populated for all elements 181 23 times (77 % 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. 96 16 times (53 % of validations)
E052 Each vehicle should have a unique ID 23 10 times (33 % 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. 9 8 times (27 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 10 8 times (27 % 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

Could not decode the GTFS-RT feed.

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