Resource details
File name:
Desserte des stations de ski iséroises Transaltitude - Temps réel
Format: gtfs-rt
This resource file is part of the dataset Navettes saisonnières Transaltitude - Isère.
Download availability
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
100%
2026-03-16
100%
2026-03-17
100%
2026-03-18
100%
2026-03-19
100%
2026-03-20
100%
2026-03-21
100%
2026-03-22
100%
2026-03-23
100%
2026-03-24
100%
2026-03-25
100%
2026-03-26
100%
2026-03-27
100%
2026-03-28
100%
2026-03-29
100%
2026-03-30
100%
2026-03-31
100%
2026-04-01
100%
2026-04-02
100%
2026-04-03
100%
2026-04-04
100%
2026-04-05
100%
2026-04-06
100%
2026-04-07
100%
2026-04-08
100%
2026-04-09
100%
2026-04-10
100%
2026-04-11
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-10 at 09:08 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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 | 24 | 7 times (70 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 48 | 7 times (70 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-11 at 07:52 Europe/Paris.
trip_updates (3) vehicle_positions (0) service_alerts (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 2026-04-11 at 07:52 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "SM:TRANSALTITUDE:ServiceJourney:1094846x1158459:LOC",
"tripUpdate": {
"stopTimeUpdate": [
{
"departure": {
"delay": -64,
"time": "1775890256"
},
"stopId": "FR:38253:ZE:33268:TRANSALTITUDE",
"stopSequence": 2
},
{
"departure": {
"delay": -64,
"time": "1775890376"
},
"stopId": "FR:38253:ZE:33257:TRANSALTITUDE",
"stopSequence": 3
},
{
"departure": {
"delay": -64,
"time": "1775890556"
},
"stopId": "FR:38253:ZE:33254:TRANSALTITUDE",
"stopSequence": 4
},
{
"arrival": {
"delay": -64,
"time": "1775890736"
},
"stopId": "FR:38253:ZE:33253:TRANSALTITUDE",
"stopSequence": 5
}
],
"timestamp": "1775886608",
"trip": {
"routeId": "TRANSALTITUDE:Line:1006254:LOC",
"tripId": "TRANSALTITUDE:ServiceJourney:1094846x1158459:LOC"
}
}
},
{
"id": "SM:TRANSALTITUDE:ServiceJourney:1094830x1158410:LOC",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1775890800"
},
"stopId": "FR:38185:ZE:33295:TRANSALTITUDE",
"stopSequence": 7
}
],
"timestamp": "1775886644",
"trip": {
"directionId": 1,
"routeId": "TRANSALTITUDE:Line:1006294:LOC",
"tripId": "TRANSALTITUDE:ServiceJourney:1094830x1158410:LOC"
}
}
},
{
"id": "SM:TRANSALTITUDE:ServiceJourney:1094847x1158460:LOC",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"delay": 784,
"time": "1775891584"
},
"stopId": "FR:38185:ZE:33295:TRANSALTITUDE",
"stopSequence": 5
}
],
"timestamp": "1775886128",
"trip": {
"directionId": 1,
"routeId": "TRANSALTITUDE:Line:1006254:LOC",
"tripId": "TRANSALTITUDE:ServiceJourney:1094847x1158460:LOC"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1775886752"
}
}