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

2025-10-29
97.4%
2025-10-30
98.9%
2025-10-31
98.2%
2025-11-01
100%
2025-11-02
100%
2025-11-03
97.7%
2025-11-04
98.9%
2025-11-05
99%
2025-11-06
96.8%
2025-11-07
96.4%
2025-11-08
100%
2025-11-09
100%
2025-11-10
99.4%
2025-11-11
100%
2025-11-12
98.6%
2025-11-13
99.5%
2025-11-14
99.1%
2025-11-15
99.4%
2025-11-16
100%
2025-11-17
96.8%
2025-11-18
98.6%
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
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

82 errors, 8 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-27 at 08:00 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 461 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 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
  • 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 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 366 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 461 route_id CAT56Ligne604 does not exist in the GTFS data routes.txt
  • vehicle_id 467 route_id BSAScol61133 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 177 route_id MAURYLigne609 does not exist in the GTFS data routes.txt
  • vehicle_id 366 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 461 stop_id chouette:StopArea:2a0f57b9-f432-405d-bfd4-32246e61917a: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_id 357 stop_id chouette:StopArea:a0ec9a8a-7d92-4e55-89db-06e354cdfa96: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 366 stop_id STP-DEPART does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 2 errors

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.54941,-2.473174) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 457 at (48.170677,-2.755043) 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 324 trip_id 22-1292304385 at (47.68774,-2.692826) 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 320 trip_id 22-2130903041 at (47.59489,-2.652278) 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 71 trip_id 2-74121237 at (47.67977,-2.771367) 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.887936) 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.627438,-2.83034) 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 3 errors

Each vehicle should have a unique ID

Sample errors
  • entity ID 601331 has vehicle.id 97 which is used by more than one vehicle in the feed
  • entity ID 602652 has vehicle.id 357 which is used by more than one vehicle in the feed
  • entity ID 601349 has vehicle.id 334 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 6 errors

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 49 does not have a timestamp
  • vehicle_id 390 does not have a timestamp
  • vehicle_id 334 does not have a timestamp
  • vehicle_id 27 does not have a timestamp
  • vehicle_id 86 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 460 speed of 26.11111 m/s (58.41 mph) is unrealistic
  • vehicle.id 451 speed of 27.222221 m/s (60.89 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 636 22 times (73 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 399 22 times (73 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 399 22 times (73 % of validations)
W001 Timestamps should be populated for all elements 163 22 times (73 % 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. 110 20 times (67 % of validations)
E052 Each vehicle should have a unique ID 26 13 times (43 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 14 12 times (40 % 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 8 times (27 % 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 1 1 times (3 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 6 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-28 at 01:24 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-11-28 at 01:24 Europe/Paris. You can look at the GTFS-RT documentation.

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