Resource details
Prochains passages aux arrêts du réseau bus-tram Irigo
This resource file is part of the dataset Réseau urbain Irigo.
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
❌99 errors, 148 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-28 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 6189671 stop_sequence 1 arrival_time 09:46:00 (1759045560) is equal to previous stop departure_time 09:46:00 (1759045560) - times must increase between two sequential stops
- trip_id 6189671 stop_sequence 1 departure_time 09:46:00 (1759045560) is equal to previous stop departure_time 09:46:00 (1759045560) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 97 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 6189763 stop_sequence 19 has stop_id 2BOTA but GTFS stop_sequence 19 has stop_id 2PMAY - stop_ids should be the same
- GTFS-rt trip_id 6189763 stop_sequence 20 has stop_id 2PMAY but GTFS stop_sequence 20 has stop_id 2BROY - stop_ids should be the same
- GTFS-rt trip_id 6189763 stop_sequence 21 has stop_id 2BROY but GTFS stop_sequence 21 has stop_id 2ACAS - stop_ids should be the same
- GTFS-rt trip_id 6189763 stop_sequence 22 has stop_id 2ACAS but GTFS stop_sequence 22 has stop_id 2STGI - stop_ids should be the same
- GTFS-rt trip_id 6189763 stop_sequence 23 has stop_id 2STGI but GTFS stop_sequence 23 has stop_id 2BASC - stop_ids should be the same
Warnings
timestamp not populated W001 37 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 6189676 does not have a timestamp
- trip_id 6189756 does not have a timestamp
- trip_id 6189764 does not have a timestamp
- trip_id 6224896 does not have a timestamp
- trip_id 6189638 does not have a timestamp
vehicle_id not populated W002 37 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 6189676 does not have a vehicle_id
- trip_id 6189756 does not have a vehicle_id
- trip_id 6189764 does not have a vehicle_id
- trip_id 6224896 does not have a vehicle_id
- trip_id 6189638 does not have a vehicle_id
schedule_relationship not populated W009 74 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 6189676 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6189676 does not have a schedule_relationship
- trip_id 6189756 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6189756 does not have a schedule_relationship
- trip_id 6189764 stop_sequence 0 (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 |
---|---|---|---|
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 4 404 | 30 times (100 % 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 | 32 206 | 30 times (100 % of validations) |
W001 | Timestamps should be populated for all elements | 5 800 | 30 times (100 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 5 800 | 30 times (100 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 11 547 | 30 times (100 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 179 | 28 times (93 % 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. | 96 | 24 times (80 % of validations) |
E044 | stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing | 4 633 | 24 times (80 % of validations) |
E001 | All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) | 66 | 21 times (70 % of validations) |
E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 924 | 10 times (33 % of validations) |
E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 9 | 4 times (13 % of validations) |
E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 9 | 4 times (13 % of validations) |
E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 4 | 2 times (7 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-29 at 04:04 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-29 at 04:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1759111447"
}
}