gtfs-rt Transport open dataset - cars Région Isère (38) - Offre temps-réel au format GTFS-RT (PB) for Réseau interurbain - Isère (38)

Resource details

File name: cars Région Isère (38) - Offre temps-réel au format GTFS-RT (PB)

Format: gtfs-rt

Données temps-réel du réseau cars Région Isère (38) suivant la structure GTFS-RT au format Protocol Buffers.

This resource file is part of the dataset Réseau interurbain - Isère (38).

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

⚠️801 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-08 at 08:10 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 267 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id ABR0100|1 does not have a vehicle_id
trip_id ABR0700|1 does not have a vehicle_id
trip_id BDO0506|1 does not have a vehicle_id
trip_id CRE0100|1 does not have a vehicle_id
trip_id CRE0704|1 does not have a vehicle_id

schedule_relationship not populated W009 534 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id ABR0100|1 stop_sequence 5 (and potentially more for this trip) does not have a schedule_relationship
trip_id ABR0100|1 does not have a schedule_relationship
trip_id ABR0700|1 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
trip_id ABR0700|1 does not have a schedule_relationship
trip_id BDO0506|1 stop_sequence 4 (and potentially more for this trip) 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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3,622	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	7,244	30 times (100 % 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 2026-01-09 at 02:43 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-09 at 02:43 Europe/Paris. You can look at the GTFS-RT documentation.


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