Resource details

File name: Réseau CVLmobilité - information temps réel ligne A (vehicle positions)
Format: gtfs-rt

This resource file is part of the dataset Réseau CVL Mobilité.

Download availability

2025-06-04
100%
2025-06-05
100%
2025-06-06
100%
2025-06-07
100%
2025-06-08
100%
2025-06-09
100%
2025-06-10
100%
2025-06-11
100%
2025-06-12
100%
2025-06-13
100%
2025-06-14
100%
2025-06-15
100%
2025-06-16
100%
2025-06-17
100%
2025-06-18
100%
2025-06-19
100%
2025-06-20
100%
2025-06-21
100%
2025-06-22
100%
2025-06-23
100%
2025-06-24
100%
2025-06-25
100%
2025-06-26
100%
2025-06-27
100%
2025-06-28
100%
2025-06-29
100%
2025-06-30
100%
2025-07-01
100%
2025-07-02
100%
2025-07-03
100%
2025-07-04
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

12 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-03 at 09: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 3 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 42 trip_id MeJ_1.1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61 trip_id MeJ_2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 43 trip_id MeJ_3 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 3 errors

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

Sample errors
  • vehicle_id 42 route_id LMaV does not exist in the GTFS data routes.txt
  • vehicle_id 61 route_id LMaV does not exist in the GTFS data routes.txt
  • vehicle_id 43 route_id LMaV does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 42 stop_id ZONE does not exist in GTFS data stops.txt
  • vehicle_id 61 stop_id ZONE does not exist in GTFS data stops.txt
  • vehicle_id 43 stop_id ZONE does not exist in GTFS data stops.txt

trip direction_id does not match GTFS data E024 3 errors

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Sample errors
  • GTFS-rt vehicle_id 5 trip_id SIT01_R6 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
  • GTFS-rt vehicle_id 6 trip_id SIT01_A5 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
  • GTFS-rt vehicle_id 10 trip_id SIT01_A6 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
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 47 13 times (87 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 47 13 times (87 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 47 13 times (87 % of validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 40 13 times (87 % 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. 3 3 times (20 % of validations)
W001 Timestamps should be populated for all elements 3 3 times (20 % 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. 2 2 times (13 % of validations)
E052 Each vehicle should have a unique ID 1 1 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-07-04 at 04:47 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-07-04 at 04:47 Europe/Paris. You can look at the GTFS-RT documentation.

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