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-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.8%
2025-12-16
99.4%
2025-12-17
99.5%
2025-12-18
98.6%
2025-12-19
98.2%
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

❌80 errors, 12 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-19 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 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 260 trip_id chouette:VehicleJourney:67309930-e07e-49b6-afc5-46c916cff303:LOC 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 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 434 trip_id chouette:VehicleJourney:54c6fce1-2edd-4c29-b936-efb19a9d04fb:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 359 trip_id chouette:VehicleJourney:2a8008ee-111a-41d6-a676-990a9d338f94: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 22 errors

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

Sample errors
  • vehicle_id 260 route_id CAT56Ligne604 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 177 route_id MAURYLigne609 does not exist in the GTFS data routes.txt
  • vehicle_id 434 route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
  • vehicle_id 359 route_id MorioLigne602 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 260 stop_id chouette:StopArea:2c9b2503-e6a4-4236-bce7-36c55c8613ca:LOC does not exist in GTFS data stops.txt
  • vehicle_id 358 stop_id chouette:StopArea:2b3ddbd2-6c81-48c1-ae43-0b35901be04d:LOC 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 434 stop_id chouette:StopArea:d2c53593-28a8-4ebb-bed3-91cee01b4496:LOC does not exist in GTFS data stops.txt
  • vehicle_id 359 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt

trip start_time does not match first GTFS arrival_time E023 3 errors

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

Sample errors
  • GTFS-rt vehicle_id 331 trip_id 2-288161794 start_time is 07:18:00 and GTFS initial arrival_time is 07:15:00 - times do not match
  • GTFS-rt vehicle_id 332 trip_id 2-288097130 start_time is 07:44:00 and GTFS initial arrival_time is 07:45:00 - times do not match
  • GTFS-rt vehicle_id 118 trip_id 2-285868035 start_time is 07:48:00 and GTFS initial arrival_time is 07:45:00 - times do not match

Vehicle position far from trip shape E029 10 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 320 trip_id 22-2130903041 at (47.60004,-2.663995) 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 353 trip_id 22-2432761857 at (47.701973,-2.544892) 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 276 trip_id 22-2499870721 at (47.691586,-2.579938) 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 314 trip_id 22-2835415041 at (47.584377,-2.643636) 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.717617,-2.887948) 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 630207 has vehicle.id 97 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 177 does not have a timestamp
  • vehicle_id 359 does not have a timestamp
  • vehicle_id 34 does not have a timestamp
  • vehicle_id 247 does not have a timestamp
  • vehicle_id 41 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 266 speed of 27.222221 m/s (60.89 mph) is unrealistic
  • vehicle.id 375 speed of 30.555555 m/s (68.35 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 490 24 times (86 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 490 24 times (86 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 490 24 times (86 % of validations)
W001 Timestamps should be populated for all elements 161 24 times (86 % 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. 150 23 times (82 % of validations)
E052 Each vehicle should have a unique ID 40 18 times (64 % 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. 16 13 times (46 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 18 13 times (46 % 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 3 1 times (4 % 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.