gtfs-rt Transport open dataset - Position des véhicules en temps réel (GTFS-RT) for Réseau urbain Transp’Or

Resource details

File name: Position des véhicules en temps réel (GTFS-RT)

Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Transp’Or.

Download availability

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

❌9 errors, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-13 at 09:11 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 4 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 12 trip_id 191 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 10 trip_id 193 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 11 trip_id 193 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 23 trip_id 191 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 4 errors

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

Sample errors

vehicle_id 12 route_id TAD does not exist in the GTFS data routes.txt
vehicle_id 10 route_id TAD does not exist in the GTFS data routes.txt
vehicle_id 11 route_id TAD does not exist in the GTFS data routes.txt
vehicle_id 23 route_id TAD does not exist in the GTFS data routes.txt

vehicle.id is not unique E052 1 error

Each vehicle should have a unique ID

Sample errors

entity ID 452198 has vehicle.id 51 which is used by more than one vehicle in the feed

Warnings

timestamp not populated W001 2 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 55 does not have a timestamp
vehicle_id 153 does not have a timestamp

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
W001	Timestamps should be populated for all elements	49	28 times (90 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	61	27 times (87 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	61	27 times (87 % 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.	9	8 times (26 % of validations)
E052	Each vehicle should have a unique ID	2	2 times (6 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-13 at 22:24 Europe/Paris.

vehicle_positions (0) 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-06-13 at 22:24 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1749846270"
  }
}