Resource details
This resource file is part of the dataset Réseau urbain Distribus.
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
❌1 error, 130 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-12 at 09:15 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_time_update departure time is before arrival time E025 1 error
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.
Sample errors
- trip_id 401-0828 stop_sequence 19 departure_time 09:00:08 (1757660408) is less than the same stop arrival_time 09:02:08 (1757660528) - departure time must be equal to or greater than arrival time
Warnings
vehicle_id not populated W002 43 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1101-0850 does not have a vehicle_id
- trip_id 1103-0905 does not have a vehicle_id
- trip_id 1103-0920 does not have a vehicle_id
- trip_id 1103-0850 does not have a vehicle_id
- trip_id 1101-0905 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 4 min 14 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 86 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 1101-0850 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1101-0850 does not have a schedule_relationship
- trip_id 1103-0905 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 1103-0905 does not have a schedule_relationship
- trip_id 1103-0920 stop_sequence 1 (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 | 589 | 24 times (86 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 147 | 23 times (82 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 17 | 17 times (61 % 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. | 13 | 11 times (39 % of validations) |
GTFS-RT feed content
Could not decode the GTFS-RT feed.
The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.