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

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

12 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-07 at 09:13 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 6 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 34749_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 34730_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 35381_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 34678_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 34704_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 6 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 2 does not exist in the GTFS data routes.txt
  • vehicle_id route_id 7 does not exist in the GTFS data routes.txt
  • vehicle_id route_id 1 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 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 20 does not have a vehicle_id
  • entity ID 22 does not have a vehicle_id
  • entity ID 23 does not have a vehicle_id
  • entity ID 24 does not have a vehicle_id
  • entity ID 25 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 86 15 times (83 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 86 15 times (83 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 86 15 times (83 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 2 2 times (11 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-19 at 15:27 Europe/Paris.

vehicle_positions (5) 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-04-19 at 15:27 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "238", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.90596008300781, "longitude": 3.0591909885406494 }, "timestamp": "1745063118", "trip": { "route_id": "2", "schedule_relationship": "SCHEDULED", "trip_id": "34786_0" }, "vehicle": { "label": "182051" } } }, { "id": "241", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.911102294921875, "longitude": 3.055996894836426 }, "timestamp": "1745065006", "trip": { "route_id": "2", "schedule_relationship": "SCHEDULED", "trip_id": "34773_0" }, "vehicle": { "label": "227032" } } }, { "id": "244", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.886695861816406, "longitude": 3.0641028881073 }, "timestamp": "1745069271", "trip": { "route_id": "1", "schedule_relationship": "SCHEDULED", "trip_id": "34654_0" }, "vehicle": { "label": "182062" } } }, { "id": "246", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.89326477050781, "longitude": 3.1177849769592285 }, "timestamp": "1745069271", "trip": { "route_id": "6", "schedule_relationship": "SCHEDULED", "trip_id": "35360_0" }, "vehicle": { "label": "247041" } } }, { "id": "247", "vehicle": { "position": { "bearing": 0.0, "latitude": 45.89788818359375, "longitude": 3.2265329360961914 }, "timestamp": "1745069271", "trip": { "route_id": "3", "schedule_relationship": "SCHEDULED", "trip_id": "35329_0" }, "vehicle": { "label": "197062" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1745069274" } }