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

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.8%
2026-01-15
97.1%
2026-01-16
98.7%
2026-01-17
100%
2026-01-18
100%
2026-01-19
91.6%
2026-01-20
95%
2026-01-21
96.9%
2026-01-22
92.6%
2026-01-23
98.5%
2026-01-24
97.2%
2026-01-25
100%
2026-01-26
96.1%
2026-01-27
98.5%
2026-01-28
98.1%
2026-01-29
98%
2026-01-30
97.8%
2026-01-31
99.7%
2026-02-01
100%
2026-02-02
97.4%
2026-02-03
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

❌68 errors, 11 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-02 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 21 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 422 trip_id chouette:VehicleJourney:0d8b29c8-069d-42ea-a820-f221c793dc03: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 462 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 389 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 248 trip_id chouette:VehicleJourney:b63ae62c-dd08-4c0a-b966-8df89fe347b1: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 20 errors

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

Sample errors
  • vehicle_id 422 route_id AVBLigne608 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 462 route_id CAT56Ligne604 does not exist in the GTFS data routes.txt
  • vehicle_id 389 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 248 route_id BSALigne611 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 422 stop_id chouette:StopArea:7774202c-455f-4bc0-8826-f2c159907149:LOC does not exist in GTFS data stops.txt
  • vehicle_id 434 stop_id chouette:StopArea:c7278b07-f2fa-40a0-a19f-b93e0f1b1651:LOC does not exist in GTFS data stops.txt
  • vehicle_id 462 stop_id chouette:StopArea:2a0f57b9-f432-405d-bfd4-32246e61917a:LOC does not exist in GTFS data stops.txt
  • vehicle_id 389 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • vehicle_id 248 stop_id chouette:StopArea:f22729a5-ff01-4cb2-817c-129545525489:LOC 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 422 at (47.552544,-2.481204) 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 4 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 579 trip_id 2-5586944003 at (47.664066,-2.755306) 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.70111,-2.54313) 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 218 trip_id 22-2852192257 at (47.777023,-2.646332) 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.717625,-2.887898) 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 2 errors

Each vehicle should have a unique ID

Sample errors
  • entity ID 681751 has vehicle.id 108 which is used by more than one vehicle in the feed
  • entity ID 681747 has vehicle.id 97 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 72 does not have a timestamp
  • vehicle_id 81 does not have a timestamp
  • vehicle_id 32 does not have a timestamp
  • vehicle_id 55 does not have a timestamp
  • vehicle_id 95 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 434 speed of 26.11111 m/s (58.41 mph) is unrealistic
  • vehicle.id 435 speed of 27.5 m/s (61.52 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 400 21 times (81 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 361 21 times (81 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 361 21 times (81 % of validations)
W001 Timestamps should be populated for all elements 136 21 times (81 % 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. 103 19 times (73 % of validations)
E052 Each vehicle should have a unique ID 24 16 times (62 % 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. 10 9 times (35 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 8 5 times (19 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-03 at 01:16 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 2026-02-03 at 01:16 Europe/Paris. You can look at the GTFS-RT documentation.

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