Resource details

File name: L'va - GTFS-RT TripUpdate
Format: gtfs-rt

Données temps-réel du réseau L’va suivant la structure GTFS-RT au format Protocol Buffers.

This resource file is part of the dataset Réseau urbain L'va.

Download availability

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

⚠️2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-19 at 08:17 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 800001245 does not have a vehicle_id

ID in one feed missing from the other W003 1 error

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id 800001245 is in TripUpdates but not in VehiclePositions feed
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
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 78 26 times (87 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 49 20 times (67 % 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. 36 17 times (57 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 34 3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-20 at 06:23 Europe/Paris.

trip_updates (2) vehicle_positions (1) service_alerts (0)

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-20 at 06:23 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "trip-1000000117", "tripUpdate": { "delay": 40, "stopTimeUpdate": [ { "arrival": { "delay": 38, "time": "1766208158" }, "departure": { "delay": 38 }, "stopId": "viemaur2", "stopSequence": 26 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viejeud", "stopSequence": 27 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "vietuil", "stopSequence": 28 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "vieport", "stopSequence": 29 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "vieteur", "stopSequence": 30 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "vierey", "stopSequence": 31 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "vieprin", "stopSequence": 32 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viegest", "stopSequence": 33 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viecite", "stopSequence": 34 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viecuri", "stopSequence": 35 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viecent", "stopSequence": 36 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viesavo", "stopSequence": 37 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viebern", "stopSequence": 38 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "viezies", "stopSequence": 39 }, { "arrival": { "delay": 40 }, "departure": { "delay": 40 }, "stopId": "vieccom", "stopSequence": 40 } ], "timestamp": "1766208162", "trip": { "directionId": 0, "routeId": "1", "scheduleRelationship": "SCHEDULED", "startTime": "05:54:00", "tripId": "1000000117" }, "vehicle": { "id": "vienne-92", "label": "92", "licensePlate": "" } } }, { "id": "trip-1000000194", "tripUpdate": { "delay": 0, "stopTimeUpdate": [ { "scheduleRelationship": "NO_DATA", "stopId": "vieurge", "stopSequence": 1 } ], "timestamp": "1766208180", "trip": { "directionId": 1, "routeId": "2", "scheduleRelationship": "SCHEDULED", "startTime": "06:23:00", "tripId": "1000000194" } } }, { "id": "vehicle-vienne-92", "vehicle": { "currentStatus": "STOPPED_AT", "currentStopSequence": 26, "position": { "bearing": 39.0, "latitude": 45.524017333984375, "longitude": 4.87078332901001, "speed": 6.94444465637207 }, "stopId": "viemaur2", "timestamp": "1766208160", "trip": { "directionId": 0, "routeId": "1", "scheduleRelationship": "SCHEDULED", "tripId": "1000000117" }, "vehicle": { "id": "vienne-92", "label": "92", "licensePlate": "" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1766208191" } }