Resource details

File name: Données en temps réel au format GTFS-RT (VehiclePosition)
Format: gtfs-rt

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

78 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-03 at 08:02 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 165 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 375 trip_id ext:12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 357 trip_id chouette:VehicleJourney:aaa13cdd-af52-4aae-9f1a-224f4c8404f6:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 435 trip_id chouette:VehicleJourney:b4c75824-d6d6-40be-a33b-9b0675a2b79d:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 467 trip_id chouette:VehicleJourney:b433ad51-e1e1-48fb-a24c-fe24e15b1374: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 165 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 375 route_id MOBICEO does not exist in the GTFS data routes.txt
  • vehicle_id 357 route_id MorioLigne602 does not exist in the GTFS data routes.txt
  • vehicle_id 435 route_id CAT56Ligne603 does not exist in the GTFS data routes.txt
  • vehicle_id 467 route_id BSAScol61133 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 165 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • vehicle_id 375 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • vehicle_id 357 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
  • vehicle_id 435 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135:LOC does not exist in GTFS data stops.txt
  • vehicle_id 467 stop_id chouette:StopArea:f2903fd2-a299-4b09-a2a3-308b185e1135: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.55183,-2.478995) 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 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.59499,-2.652705) 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 290 trip_id 22-2634088449 at (47.63945,-2.867819) 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 274 trip_id 22-2298544129 at (47.792656,-2.595654) 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-7-LM_____ at (47.627594,-2.830186) 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.490685,-2.79418) 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 683429 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 311 does not have a timestamp
  • vehicle_id 275 does not have a timestamp
  • vehicle_id 89 does not have a timestamp
  • vehicle_id 69 does not have a timestamp
  • vehicle_id 72 does not have a timestamp

vehicle speed is unrealistic W004 1 error

vehicle.position.speed has an unrealistic speed that may be incorrect

Sample errors
  • vehicle.id 459 speed of 27.777779 m/s (62.14 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 422 22 times (85 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 383 22 times (85 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 383 22 times (85 % of validations)
W001 Timestamps should be populated for all elements 145 22 times (85 % 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. 113 20 times (77 % of validations)
E052 Each vehicle should have a unique ID 25 17 times (65 % 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. 11 10 times (38 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 9 6 times (23 % 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.