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
⚠️842 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-15 at 09:06 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
timestamp not populated W001 433 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 1397 does not have a timestamp
- trip_id 1275 does not have a timestamp
- trip_id 1405 does not have a timestamp
- trip_id 7 does not have a timestamp
- trip_id 1527 does not have a timestamp
vehicle_id not populated W002 409 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 1854 does not have a vehicle_id
- trip_id 1853 does not have a vehicle_id
- trip_id 1852 does not have a vehicle_id
- trip_id 1851 does not have a vehicle_id
- trip_id 1850 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 | 7 116 | 19 times (86 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 6 706 | 19 times (86 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 22 | 12 times (55 % 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. | 14 | 10 times (45 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 3 | 3 times (14 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 3 | 3 times (14 % of validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 50 | 3 times (14 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 6 | 2 times (9 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-16 at 00:30 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-09-16 at 00:30 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1757975420"
}
}