Resource details

File name: Horaires en temps réel des lignes urbaines et interurbaines sur le réseau Ales'y. (GTFS-RT)
Format: gtfs-rt

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

2025-12-23
100%
2025-12-24
100%
2025-12-25
100%
2025-12-26
100%
2025-12-27
100%
2025-12-28
100%
2025-12-29
100%
2025-12-30
100%
2025-12-31
100%
2026-01-01
100%
2026-01-02
100%
2026-01-03
100%
2026-01-04
100%
2026-01-05
100%
2026-01-06
100%
2026-01-07
98.3%
2026-01-08
100%
2026-01-09
100%
2026-01-10
100%
2026-01-11
100%
2026-01-12
100%
2026-01-13
100%
2026-01-14
100%
2026-01-15
100%
2026-01-16
100%
2026-01-17
100%
2026-01-18
100%
2026-01-19
100%
2026-01-20
100%
2026-01-21
100%
2026-01-22
100%
Learn more
We test this resource download availability every hour by making an HTTP 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

9 errors, 1,197 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-22 at 08:05 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_update times are not increasing E022 6 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 1288 stop_sequence 15 arrival_time 07:54:18 (1769064858) is equal to previous stop departure_time 07:54:18 (1769064858) - times must increase between two sequential stops
  • trip_id 1285 stop_sequence 8 arrival_time 07:56:02 (1769064962) is equal to previous stop departure_time 07:56:02 (1769064962) - times must increase between two sequential stops
  • trip_id 1279 stop_sequence 13 arrival_time 07:53:51 (1769064831) is less than previous stop arrival_time 08:21:59 (1769066519) - times must increase between two sequential stops
  • trip_id 1279 stop_sequence 13 arrival_time 07:53:51 (1769064831) is less than previous stop departure_time 08:29:59 (1769066999) - times must increase between two sequential stops
  • trip_id 1279 stop_sequence 13 departure_time 07:54:02 (1769064842) is less than previous stop departure_time 08:29:59 (1769066999) - 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 464 stop_sequence 19 departure_time 08:05:16 (1769065516) is less than the same stop arrival_time 08:05:17 (1769065517) - departure time must be equal to or greater than arrival time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 2 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors
  • GTFS-rt trip_id 1309 stop_sequence 7 has stop_id 2778 but GTFS stop_sequence 7 has stop_id 2680 - stop_ids should be the same
  • GTFS-rt trip_id 1308 stop_sequence 3 has stop_id 2778 but GTFS stop_sequence 3 has stop_id 2680 - stop_ids should be the same

Warnings

timestamp not populated W001 640 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 2024 does not have a timestamp
  • trip_id 723 does not have a timestamp
  • trip_id 4 does not have a timestamp
  • trip_id 1288 does not have a timestamp
  • trip_id 1054 does not have a timestamp

vehicle_id not populated W002 557 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1540 does not have a vehicle_id
  • trip_id 1539 does not have a vehicle_id
  • trip_id 1538 does not have a vehicle_id
  • trip_id 1537 does not have a vehicle_id
  • trip_id 1536 does not have a vehicle_id
Validate this GTFS-RT now

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 12,846 24 times (80 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 11,532 24 times (80 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 96 20 times (67 % 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. 39 17 times (57 % 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 6 5 times (17 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-23 at 00:43 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-23 at 00:43 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1769125412" } }