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
❌22 errors, 24 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-10-30 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 22 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 12000385 stop_sequence 27 arrival_time 08:14:12 (1793344452) is equal to previous stop arrival_time 08:14:12 (1793344452) - times must increase between two sequential stops
- trip_id 12000385 stop_sequence 27 arrival_time 08:14:12 (1793344452) is equal to previous stop departure_time 08:14:12 (1793344452) - times must increase between two sequential stops
- trip_id 12000385 stop_sequence 27 departure_time 08:14:12 (1793344452) is equal to previous stop departure_time 08:14:12 (1793344452) - times must increase between two sequential stops
- trip_id 12000385 stop_sequence 27 departure_time 08:14:12 (1793344452) is equal to previous stop arrival_time 08:14:12 (1793344452) - times must increase between two sequential stops
- trip_id 12000501 stop_sequence 20 arrival_time 08:22:11 (1793344931) is equal to previous stop arrival_time 08:22:11 (1793344931) - times must increase between two sequential stops
Warnings
vehicle_id not populated W002 12 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 12000010 does not have a vehicle_id
- trip_id 12000435 does not have a vehicle_id
- trip_id 12000297 does not have a vehicle_id
- trip_id 12000089 does not have a vehicle_id
- trip_id 12000543 does not have a vehicle_id
ID in one feed missing from the other W003 12 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 12000543 is in TripUpdates but not in VehiclePositions feed
- trip_id 12000103 is in TripUpdates but not in VehiclePositions feed
- trip_id 12000435 is in TripUpdates but not in VehiclePositions feed
- trip_id 12000010 is in TripUpdates but not in VehiclePositions feed
- trip_id 12000297 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1,478 | 29 times (97 % of validations) |
| 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 | 49 | 16 times (53 % 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. | 15 | 12 times (40 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 26 | 10 times (33 % 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. | 1 | 1 times (3 % 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 2026-10-30 at 21:44 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2026-10-30 at 21:44 Europe/Paris.
Detour
Between 2026-10-30 at 00:00 Europe/Paris and 2026-10-31 at 00:00 Europe/Paris
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-10-30 at 21:44 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"activePeriod": [
{
"end": "1793401200",
"start": "1793314800"
}
],
"descriptionText": {
"translation": [
{
"language": "fr",
"text": "En raison des travaux, la ligne 7 est déviée du 4 septembre au 31 décembre 2026."
}
]
},
"effect": "DETOUR",
"headerText": {
"translation": [
{
"language": "fr",
"text": "Déviation ligne 7 : Travaux"
}
]
},
"informedEntity": [
{
"routeId": "7"
},
{
"routeId": "7",
"stopId": "jargedi3"
},
{
"routeId": "7",
"stopId": "jarcoll"
},
{
"routeId": "7",
"stopId": "jarbera3"
},
{
"routeId": "7",
"stopId": "jartonk"
},
{
"routeId": "7",
"stopId": "jarbera2"
},
{
"routeId": "7",
"stopId": "jarcoll2"
},
{
"routeId": "7",
"stopId": "jargedi"
},
{
"routeId": "7",
"stopId": "jartonk4"
}
]
},
"id": "alert-detour-vienne-2-7"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1793393051"
}
}