Resource details
Horaires en temps réel des lignes urbaines et interurbaines sur le réseau Ales’y. (GTFS-RT)
This resource file is part of the dataset Réseau urbain Alesy.
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
❌3 errors, 782 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-07 at 09:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 2 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 1603 stop_sequence 12 arrival_time 09:00:40 (1751871640) is less than previous stop arrival_time 09:02:32 (1751871752) - times must increase between two sequential stops
- trip_id 1603 stop_sequence 12 arrival_time 09:00:40 (1751871640) is less than previous stop departure_time 09:02:41 (1751871761) - times must increase between two sequential stops
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 1984 stop_sequence 3 departure_time 09:02:27 (1751871747) is less than the same stop arrival_time 09:02:40 (1751871760) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 401 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 2030 does not have a timestamp
- trip_id 7 does not have a timestamp
- trip_id 1426 does not have a timestamp
- trip_id 1527 does not have a timestamp
- trip_id 303 does not have a timestamp
vehicle_id not populated W002 381 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 78 does not have a vehicle_id
- trip_id 74 does not have a vehicle_id
- trip_id 70 does not have a vehicle_id
- trip_id 66 does not have a vehicle_id
- trip_id 62 does not have a vehicle_id
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 3 396 | 8 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 3 195 | 8 times (100 % 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. | 9 | 6 times (75 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 5 | 3 times (38 % 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.