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-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%
2025-12-21
100%
2025-12-22
100%
2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
2025-12-29
100%
2025-12-30
100%
2025-12-31
100%
2026-01-01
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-01 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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 | 75 | 23 times (77 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 38 | 17 times (57 % 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. | 17 | 10 times (33 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 4 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-01 at 19:56 Europe/Paris.
vehicle_positions (1) trip_updates (1) service_alerts (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-01 at 19:56 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "trip-1100000007",
"tripUpdate": {
"delay": 869,
"stopTimeUpdate": [
{
"arrival": {
"delay": 869,
"time": "1767293775"
},
"departure": {
"delay": 869,
"time": "1767293789"
},
"stopId": "vierava2",
"stopSequence": 16
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "viechar2",
"stopSequence": 17
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "vieceva2",
"stopSequence": 18
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponvega2",
"stopSequence": 19
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponforg2",
"stopSequence": 20
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponbleu2",
"stopSequence": 21
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "poncent2",
"stopSequence": 22
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponmesa2",
"stopSequence": 23
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "pongent2",
"stopSequence": 24
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponplan2",
"stopSequence": 25
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponbras2",
"stopSequence": 26
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "poncour2",
"stopSequence": 27
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponzmon2",
"stopSequence": 28
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponfrer2",
"stopSequence": 29
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "ponabb2",
"stopSequence": 30
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "vierond2",
"stopSequence": 31
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "viecedr2",
"stopSequence": 32
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "viehorl2",
"stopSequence": 33
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "vieferm2",
"stopSequence": 34
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "viehame2",
"stopSequence": 35
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "viemali2",
"stopSequence": 36
},
{
"arrival": {
"delay": 869
},
"departure": {
"delay": 869
},
"stopId": "viesmal2",
"stopSequence": 37
}
],
"timestamp": "1767293792",
"trip": {
"directionId": 1,
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"startTime": "19:22:00",
"tripId": "1100000007"
},
"vehicle": {
"id": "vienne-93",
"label": "93",
"licensePlate": ""
}
}
},
{
"id": "vehicle-vienne-93",
"vehicle": {
"currentStopSequence": 17,
"position": {
"bearing": 59.0,
"latitude": 45.52455520629883,
"longitude": 4.892553806304932,
"speed": 12.5
},
"stopId": "viechar2",
"timestamp": "1767293789",
"trip": {
"directionId": 1,
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"tripId": "1100000007"
},
"vehicle": {
"id": "vienne-93",
"label": "93",
"licensePlate": ""
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1767293799"
}
}