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 de l'Isère (38).

Download availability

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

⚠️45 warnings

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

Warnings

vehicle_id not populated W002 15 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id T3600|19 does not have a vehicle_id
  • trip_id T6500|3 does not have a vehicle_id
  • trip_id T6601|11 does not have a vehicle_id
  • trip_id T8301|7 does not have a vehicle_id
  • trip_id T9204|1 does not have a vehicle_id

schedule_relationship not populated W009 30 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id T3600|19 stop_sequence 10 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id T3600|19 does not have a schedule_relationship
  • trip_id T6500|3 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id T6500|3 does not have a schedule_relationship
  • trip_id T6601|11 stop_sequence 16 (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 834 29 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1 668 29 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-08 at 20:37 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (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 2025-06-08 at 20:37 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:T5016|2", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1749408291" }, "stopId": "14844", "stopSequence": 29 }, { "departure": { "time": "1749408951" }, "stopId": "13404", "stopSequence": 30 }, { "departure": { "time": "1749409251" }, "stopId": "12789", "stopSequence": 31 }, { "departure": { "time": "1749409311" }, "stopId": "12821", "stopSequence": 32 }, { "departure": { "time": "1749409431" }, "stopId": "20562", "stopSequence": 33 }, { "departure": { "time": "1749409611" }, "stopId": "12828", "stopSequence": 34 } ], "timestamp": "1749393000", "trip": { "routeId": "T50", "tripId": "T5016|2" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1749407832" } }