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-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
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
100%
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

❌13 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-27 at 08:13 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 4 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 179 trip_id chouette:VehicleJourney:b06d0e1d-00b1-4f2f-bcd9-10ed2d719f04:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 169 trip_id ext:12069 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 367 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 4 errors

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

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

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

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

Sample errors
  • vehicle_id 179 stop_id chouette:StopArea:e462c1b3-6666-448e-b8ae-da455c43c7bf:LOC does not exist in GTFS data stops.txt
  • vehicle_id 169 stop_id STP-DEPART 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 367 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 73 trip_id 2-135987207 at (47.673626,-2.758501) 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 83 does not have a timestamp
  • vehicle_id 585 does not have a timestamp
  • vehicle_id 53 does not have a timestamp
  • vehicle_id 71 does not have a timestamp
  • vehicle_id 60 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 24 times (83 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 446 24 times (83 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 446 24 times (83 % of validations)
W001 Timestamps should be populated for all elements 168 24 times (83 % 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. 128 19 times (66 % of validations)
E052 Each vehicle should have a unique ID 30 14 times (48 % 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. 13 11 times (38 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 12 9 times (31 % 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 (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-28 at 01:57 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-28 at 01:57 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1766883450" } }