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
❌1 error, 634 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-15 at 09:07 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 1527 stop_sequence 27 departure_time 09:07:05 (1760512025) is less than the same stop arrival_time 09:07:14 (1760512034) - departure time must be equal to or greater than arrival time
Warnings
timestamp not populated W001 326 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1405 does not have a timestamp
- trip_id 7 does not have a timestamp
- trip_id 1527 does not have a timestamp
- trip_id 8 does not have a timestamp
- trip_id 498 does not have a timestamp
vehicle_id not populated W002 308 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 336 does not have a vehicle_id
- trip_id 335 does not have a vehicle_id
- trip_id 334 does not have a vehicle_id
- trip_id 333 does not have a vehicle_id
- trip_id 332 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 | 10 445 | 26 times (87 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 9 840 | 26 times (87 % 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. | 37 | 20 times (67 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 24 | 10 times (33 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-10-16 at 01:14 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-10-16 at 01:14 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1760570060"
}
}