gtfs-rt Transport open dataset - Position des véhicules au format GTFS-RT for Réseau urbain Zest

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 Zest.

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

❌18 errors, 18 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-11 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 18 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 3926 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 3575 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 3816 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 3730 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 3907 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 18 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

entity ID 44 does not have a vehicle_id
entity ID 54 does not have a vehicle_id
entity ID 56 does not have a vehicle_id
entity ID 58 does not have a vehicle_id
entity ID 59 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	624	30 times (100 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	350	16 times (53 % 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

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.