gtfs-rt Transport open dataset - Données en temps réel de la position des véhicules du réseau Transurbain for Réseau urbain Transurbain

Resource details

File name: Données en temps réel de la position des véhicules du réseau Transurbain

Format: gtfs-rt

GTFS-RT (protobuff) de la position des véhicules.

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

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

❌20 errors, 20 warnings

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

Errors

GTFS-rt stop_id does not exist in GTFS data E011 20 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

vehicle_id 17 stop_id RON02 does not exist in GTFS data stops.txt
vehicle_id 44 stop_id BRI02 does not exist in GTFS data stops.txt
vehicle_id 45 stop_id VOL02 does not exist in GTFS data stops.txt
vehicle_id 29 stop_id BOR02 does not exist in GTFS data stops.txt
vehicle_id 31 stop_id BRI01 does not exist in GTFS data stops.txt

Warnings

schedule_relationship not populated W009 20 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id ATOUMOD004:ServiceJourney:491394:LOC does not have a schedule_relationship
trip_id ATOUMOD004:ServiceJourney:489886:LOC does not have a schedule_relationship
trip_id ATOUMOD004:ServiceJourney:489883:LOC does not have a schedule_relationship
trip_id ATOUMOD004:ServiceJourney:491067:LOC does not have a schedule_relationship
trip_id ATOUMOD004:ServiceJourney:489862:LOC does not have a schedule_relationship

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
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	395	18 times (62 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	395	18 times (62 % 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.	18	13 times (45 % of validations)
E050	All timestamps must be less than the current time	3	3 times (10 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	3	3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-08 at 07:38 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-08 at 07:38 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1749361139"
  }
}