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 urbain CVL Mobilité.

Download availability

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

6 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-13 at 09:09 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 1 error

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 1 trip_id S_2 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 1 error

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

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

GTFS-rt stop_id does not exist in GTFS data E011 1 error

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

Sample errors
  • vehicle_id 1 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 10 trip_id SIT01_Sa_A6 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_Sa_A5 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
  • GTFS-rt vehicle_id 5 trip_id SIT01_Sa_R6 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 88 26 times (84 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 88 26 times (84 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 88 26 times (84 % of validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 71 26 times (84 % of validations)
W001 Timestamps should be populated for all elements 11 11 times (35 % 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. 7 7 times (23 % 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. 2 2 times (6 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-09-13 at 13:41 Europe/Paris.

vehicle_positions (3) 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-09-13 at 13:41 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "15194", "vehicle": { "currentStopSequence": 17, "position": { "latitude": 47.169456481933594, "longitude": 0.21617500483989716, "speed": 0.0 }, "stopId": "RSM01", "timestamp": "1757763670", "trip": { "directionId": 0, "routeId": "A", "scheduleRelationship": "SCHEDULED", "startDate": "20250913", "startTime": "13:08:00", "tripId": "SIT01_Sa_R12" }, "vehicle": { "id": "9", "label": "GW 248 FX", "licensePlate": "GW 248 FX" } } }, { "id": "15176", "vehicle": { "currentStopSequence": 18, "position": { "latitude": 47.1671257019043, "longitude": 0.23364700376987457, "speed": 0.0 }, "stopId": "SRA02", "timestamp": "1757763643", "trip": { "directionId": 0, "routeId": "A", "scheduleRelationship": "SCHEDULED", "startDate": "20250913", "startTime": "13:02:00", "tripId": "SIT01_Sa_A11" }, "vehicle": { "id": "7", "label": "GX 706 JM", "licensePlate": "GX 706 JM" } } }, { "id": "15173", "vehicle": { "currentStopSequence": 1, "position": { "bearing": 28.0, "latitude": 47.216861724853516, "longitude": 0.18891100585460663, "speed": 21.11111068725586 }, "stopId": "ZONE", "timestamp": "1757761826", "trip": { "directionId": 0, "routeId": "LMaV", "scheduleRelationship": "SCHEDULED", "startDate": "20250913", "startTime": "08:10:00", "tripId": "S_2" }, "vehicle": { "id": "1", "label": "GX 763 DF", "licensePlate": "GX 763 DF" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1757763688" } }