Resource details
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
Learn more
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
⚠️106 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-29 at 09:08 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
vehicle_id not populated W002 35 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id BJA0605|1 does not have a vehicle_id
- trip_id MEN0601|2 does not have a vehicle_id
- trip_id T1006|1 does not have a vehicle_id
- trip_id T2000|6 does not have a vehicle_id
- trip_id T3001|1 does not have a vehicle_id
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 1 min 9 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 70 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id BJA0605|1 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id BJA0605|1 does not have a schedule_relationship
- trip_id MEN0601|2 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id MEN0601|2 does not have a schedule_relationship
- trip_id T1006|1 stop_sequence 11 (and potentially more for this trip) does not have a schedule_relationship
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 | 900 | 30 times (100 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 800 | 30 times (100 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-30 at 02:37 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-30 at 02:37 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1759192642"
}
}