Resource details

File name: Position des véhicules au format GTFS-RT
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain RLV Mobilités.

Download availability

2026-02-19
100%
2026-02-20
100%
2026-02-21
100%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
100%
2026-03-02
100%
2026-03-03
100%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
100%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
100%
2026-03-16
100%
2026-03-17
100%
2026-03-18
100%
2026-03-19
100%
2026-03-20
100%
2026-03-21
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

4 errors, 2 warnings

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 2 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • vehicle_id trip_id 36297_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 34703_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 2 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • vehicle_id route_id 2 does not exist in the GTFS data routes.txt
  • vehicle_id route_id 1 does not exist in the GTFS data routes.txt

Warnings

vehicle_id not populated W002 2 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 14 does not have a vehicle_id
  • entity ID 15 does not have a vehicle_id
Validate this GTFS-RT now

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-21 at 14:52 Europe/Paris.

vehicle_positions (3) 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 2026-03-21 at 14:52 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "249", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.89485549926758, "longitude": 3.1246070861816406 }, "timestamp": "1774101164", "trip": { "routeId": "3", "scheduleRelationship": "SCHEDULED", "tripId": "36386_0" }, "vehicle": { "label": "7040" } } }, { "id": "250", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.89027786254883, "longitude": 3.1177220344543457 }, "timestamp": "1774101164", "trip": { "routeId": "7", "scheduleRelationship": "SCHEDULED", "tripId": "36510_0" }, "vehicle": { "label": "7039" } } }, { "id": "251", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.88248825073242, "longitude": 3.107311964035034 }, "timestamp": "1774101164", "trip": { "routeId": "2", "scheduleRelationship": "SCHEDULED", "tripId": "36341_0" }, "vehicle": { "label": "7041" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1774101167" } }