Resource details

File name: Données en temps réel au format GTFS-RT (VehiclePosition)
Format: gtfs-rt

Le message VehiclePosition au format GTFS-RT est disponibles dans ce flux.

This resource file is part of the dataset Réseau urbain Distribus.

Download availability

2025-11-18
100%
2025-11-19
100%
2025-11-20
100%
2025-11-21
100%
2025-11-22
100%
2025-11-23
100%
2025-11-24
100%
2025-11-25
100%
2025-11-26
100%
2025-11-27
100%
2025-11-28
100%
2025-11-29
100%
2025-11-30
100%
2025-12-01
100%
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
100%
2025-12-16
100%
2025-12-17
100%
2025-12-18
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

⚠️5 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-18 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 4 does not have a vehicle_id
  • entity ID 5 does not have a vehicle_id
  • entity ID 6 does not have a vehicle_id
  • entity ID 7 does not have a vehicle_id
  • entity ID 9 does not have a vehicle_id
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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 68 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. 3 3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-18 at 17:22 Europe/Paris.

vehicle_positions (4) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-18 at 17:22 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "38", "vehicle": { "position": { "bearing": 0.0, "latitude": 48.48517608642578, "longitude": -2.5152130126953125 }, "timestamp": "1766074961", "trip": { "routeId": "42", "scheduleRelationship": "SCHEDULED", "tripId": "1-711720961" }, "vehicle": { "label": "37253" } } }, { "id": "39", "vehicle": { "position": { "bearing": 0.0, "latitude": 48.555118560791016, "longitude": -2.537846088409424 }, "timestamp": "1766074961", "trip": { "routeId": "42", "scheduleRelationship": "SCHEDULED", "tripId": "1-710868993" }, "vehicle": { "label": "37252" } } }, { "id": "50", "vehicle": { "position": { "bearing": 0.0, "latitude": 48.62885665893555, "longitude": -2.464261054992676 }, "timestamp": "1766074961", "trip": { "routeId": "43", "scheduleRelationship": "SCHEDULED", "tripId": "1-727187463" }, "vehicle": { "label": "37251" } } }, { "id": "51", "vehicle": { "position": { "bearing": 0.0, "latitude": 48.47187042236328, "longitude": -2.514988899230957 }, "timestamp": "1766074961", "trip": { "routeId": "15", "scheduleRelationship": "SCHEDULED", "tripId": "1-258736170" }, "vehicle": { "label": "75569" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1766074966" } }