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
❌4 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-02 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 4 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 800000463 stop_sequence 14 arrival_time 08:07:35 (1764659255) is less than previous stop arrival_time 08:07:50 (1764659270) - times must increase between two sequential stops
- trip_id 800000463 stop_sequence 14 arrival_time 08:07:35 (1764659255) is less than previous stop departure_time 08:10:21 (1764659421) - times must increase between two sequential stops
- trip_id 800000463 stop_sequence 14 departure_time 08:07:36 (1764659256) is less than previous stop departure_time 08:10:21 (1764659421) - times must increase between two sequential stops
- trip_id 800000463 stop_sequence 14 departure_time 08:07:36 (1764659256) is less than previous stop arrival_time 08:07:50 (1764659270) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 1 error
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 800000724 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 800000724 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 | 85 | 24 times (80 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 60 | 22 times (73 % 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. | 35 | 18 times (60 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 36 | 4 times (13 % of validations) |
| E041 | Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-12-02 at 23:39 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 2025-12-02 at 23:39 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764715148"
}
}