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

7 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-26 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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 vienne-95 trip_id 1400000330 at (45.52182,4.9221325) 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 vienne_vfd-447 trip_id 1400001476 at (45.5042,4.9498634) 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 vienne_faure-2840 trip_id 1400001065 at (45.5224,4.649555) 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 vienne_faure-983 trip_id 1400000949 at (45.58724,4.95975) 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 vienne_faure-7170 trip_id 1400000404 at (45.601654,4.770325) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

trip doesn't have any stop_time_updates E041 2 errors

Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update

Sample errors
  • trip_id 1400000330 doesn't have any stop_time_updates and isn't CANCELED
  • trip_id 1400000404 doesn't have any stop_time_updates and isn't CANCELED

Warnings

vehicle_id not populated W002 4 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1400001150 does not have a vehicle_id
  • trip_id 1400001566 does not have a vehicle_id
  • trip_id 1400000691 does not have a vehicle_id
  • trip_id 1400001177 does not have a vehicle_id

ID in one feed missing from the other W003 6 errors

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 1400000902 is in TripUpdates but not in VehiclePositions feed
  • vehicle_id vienne-71 is in TripUpdates but not in VehiclePositions feed
  • trip_id 1400001150 is in TripUpdates but not in VehiclePositions feed
  • trip_id 1400001566 is in TripUpdates but not in VehiclePositions feed
  • trip_id 1400000691 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 100 22 times (73 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 53 21 times (70 % 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. 29 13 times (43 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 39 1 times (3 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 10 1 times (3 % of validations)
E041 Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update 2 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-27 at 00:24 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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 2026-01-27 at 00:24 Europe/Paris. You can look at the GTFS-RT documentation.

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