gtfs-rt Transport open dataset - irigo-angers-gtfs-trip-updates for Réseau urbain Irigo

Resource details

File name: irigo-angers-gtfs-trip-updates

Format: gtfs-rt

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

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.

Validation details

❌248 errors, 132 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-20 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Sequential stop_time_update times are not increasing E022 18 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 5367428 stop_sequence 34 arrival_time 09:49:00 (1716191340) is less than previous stop arrival_time 09:50:57 (1716191457) - times must increase between two sequential stops
trip_id 5367428 stop_sequence 34 arrival_time 09:49:00 (1716191340) is less than previous stop departure_time 09:50:57 (1716191457) - times must increase between two sequential stops
trip_id 5367428 stop_sequence 34 departure_time 09:49:00 (1716191340) is less than previous stop departure_time 09:50:57 (1716191457) - times must increase between two sequential stops
trip_id 5367428 stop_sequence 34 departure_time 09:49:00 (1716191340) is less than previous stop arrival_time 09:50:57 (1716191457) - times must increase between two sequential stops
trip_id 5367428 stop_sequence 38 arrival_time 09:51:35 (1716191495) is less than previous stop arrival_time 09:51:45 (1716191505) - times must increase between two sequential stops

stop_time_update arrival/departure doesn't have delay or time E044 38 errors

stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing

Sample errors

trip_id 5367428 stop_sequence 0 arrival doesn't have delay or time
trip_id 5367430 stop_sequence 0 arrival doesn't have delay or time
trip_id 5367387 stop_sequence 37 departure doesn't have delay or time
trip_id 5367340 stop_sequence 0 arrival doesn't have delay or time
trip_id 5367541 stop_sequence 25 departure doesn't have delay or time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 192 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 5367428 stop_sequence 33 has stop_id CHDARR but GTFS stop_sequence 33 has stop_id REPUBLIQ - stop_ids should be the same
GTFS-rt trip_id 5367428 stop_sequence 34 has stop_id POISSONN but GTFS stop_sequence 34 has stop_id SAICRO-E - stop_ids should be the same
GTFS-rt trip_id 5367428 stop_sequence 35 has stop_id REPUBLIQ but GTFS stop_sequence 35 has stop_id OFFTOU-E - stop_ids should be the same
GTFS-rt trip_id 5367428 stop_sequence 36 has stop_id SAICRO-E but GTFS stop_sequence 36 has stop_id ACADEMIE - stop_ids should be the same
GTFS-rt trip_id 5367428 stop_sequence 37 has stop_id OFFTOU-E but GTFS stop_sequence 37 has stop_id GBREM-E - stop_ids should be the same

Warnings

timestamp not populated W001 33 errors

Timestamps should be populated for all elements

Sample errors

trip_id 5367428 does not have a timestamp
trip_id 5367430 does not have a timestamp
trip_id 5367387 does not have a timestamp
trip_id 5367340 does not have a timestamp
trip_id 5367541 does not have a timestamp

vehicle_id not populated W002 33 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 5367428 does not have a vehicle_id
trip_id 5367430 does not have a vehicle_id
trip_id 5367387 does not have a vehicle_id
trip_id 5367340 does not have a vehicle_id
trip_id 5367541 does not have a vehicle_id

schedule_relationship not populated W009 66 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 5367428 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id 5367428 does not have a schedule_relationship
trip_id 5367430 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id 5367430 does not have a schedule_relationship
trip_id 5367387 stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship

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
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	4 535	29 times (97 % of validations)
E044	stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing	3 737	29 times (97 % 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	26 037	29 times (97 % of validations)
W001	Timestamps should be populated for all elements	4 236	29 times (97 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	4 236	29 times (97 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	8 354	29 times (97 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	44	21 times (70 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	45	21 times (70 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	135	21 times (70 % 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.	7	7 times (23 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-21 at 01:25 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-05-21 at 01:25 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1716247528"
  }
}