Resource details
This resource file is part of the dataset Réseau urbain Pays des Ecrins.
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
❌5 errors, 1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-08 at 08:03 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 1 error
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id ABC VALL 07h41 stop_sequence 2 arrival_time 07:44:01 (1767854641) is equal to previous stop departure_time 07:44:01 (1767854641) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 4 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id A aller 07H45 HS+BS stop_sequence 0 doesn't have arrival or departure
- trip_id A aller 07H45 HS+BS stop_sequence 1 doesn't have arrival or departure
- trip_id A aller 07H45 HS+BS stop_sequence 2 doesn't have arrival or departure
- trip_id A aller 07H45 HS+BS stop_sequence 4 doesn't have arrival or departure
Warnings
ID in one feed missing from the other W003 1 error
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id L2 La Gare Pra Reboul is in TripUpdates but not in VehiclePositions feed
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 |
|---|---|---|---|
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 35 | 21 times (72 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 10 | 9 times (31 % of validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 8 | 3 times (10 % of validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 1 | 1 times (3 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 1 | 1 times (3 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-10 at 04:26 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-10 at 04:26 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768015591"
}
}