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-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
98.1%
2026-01-06
99.6%
2026-01-07
97.6%
2026-01-08
97.4%
2026-01-09
96%
2026-01-10
99.5%
2026-01-11
100%
2026-01-12
95.5%
2026-01-13
99.5%
2026-01-14
93.7%
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

❌79 errors, 9 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-14 at 08:01 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 244 trip_id chouette:VehicleJourney:753818a8-6b11-410c-9da2-c2643f4df3eb:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • 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 169 trip_id ext:12071 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 165 trip_id ext:12071 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 24 errors

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

Sample errors
  • vehicle_id 244 route_id BSAScol61137 does not exist in the GTFS data routes.txt
  • vehicle_id 183 route_id MAURYScol60927 does not exist in the GTFS data routes.txt
  • vehicle_id 169 route_id MATINEO does not exist in the GTFS data routes.txt
  • vehicle_id 165 route_id MATINEO 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 24 errors

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

Sample errors
  • vehicle_id 244 stop_id bre_vannes_2024_2025.18039 does not exist in GTFS data stops.txt
  • vehicle_id 183 stop_id bre_vannes_2024_2025.18829 does not exist in GTFS data stops.txt
  • vehicle_id 169 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 165 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 1 error

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 232 at (47.55212,-2.480624) 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 5 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 110 trip_id 22-2013331457 at (47.535656,-2.832902) 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-2298544129 at (47.7911,-2.59524) 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-6-__CJV__ at (47.62756,-2.830144) 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 116 trip_id 22-1946288129 at (47.489944,-2.793409) 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 118 trip_id 2-288161794 at (47.65796,-2.74677) 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 658599 has vehicle.id 635 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 9 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 59 does not have a timestamp
  • vehicle_id 63 does not have a timestamp
  • vehicle_id 61 does not have a timestamp
  • vehicle_id 87 does not have a timestamp
  • vehicle_id 179 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 438 24 times (80 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 398 24 times (80 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 397 24 times (80 % of validations)
W001 Timestamps should be populated for all elements 186 24 times (80 % 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. 80 17 times (57 % of validations)
E052 Each vehicle should have a unique ID 19 11 times (37 % 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 7 times (23 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 7 6 times (20 % 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.