Resource details
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
Learn more
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 errors, 6 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-29 at 08:05 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 2 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_vfd-447 trip_id 1400001476 at (45.49704,4.9538045) 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-8303 trip_id 1400001168 at (45.57639,4.802054) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
vehicle_id not populated W002 3 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1400001150 does not have a vehicle_id
- trip_id 1400000036 does not have a vehicle_id
- trip_id 1400000691 does not have a vehicle_id
ID in one feed missing from the other W003 3 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 1400001150 is in TripUpdates but not in VehiclePositions feed
- trip_id 1400000036 is in TripUpdates but not in VehiclePositions feed
- trip_id 1400000691 is in TripUpdates but not in VehiclePositions feed
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 | 101 | 23 times (77 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 56 | 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. | 34 | 14 times (47 % of validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 3 | 2 times (7 % 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) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-29 at 21:41 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-29 at 21:41 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1769719290"
}
}