Détails de la ressource

Nom du fichier : irigo-angers-gtfs-trip-updates
Format : gtfs-rt

Prochains passages aux arrêts du réseau bus-tram Irigo

Cette ressource fait partie du jeu de données Réseau urbain Irigo.

Disponibilité au téléchargement

18/01/2026
100%
19/01/2026
100%
20/01/2026
100%
21/01/2026
100%
22/01/2026
100%
23/01/2026
100%
24/01/2026
100%
25/01/2026
100%
26/01/2026
100%
27/01/2026
100%
28/01/2026
100%
29/01/2026
100%
30/01/2026
100%
31/01/2026
100%
01/02/2026
100%
02/02/2026
100%
03/02/2026
100%
04/02/2026
100%
05/02/2026
100%
06/02/2026
100%
07/02/2026
100%
08/02/2026
100%
09/02/2026
100%
10/02/2026
100%
11/02/2026
100%
12/02/2026
100%
13/02/2026
100%
14/02/2026
100%
15/02/2026
100%
16/02/2026
100%
17/02/2026
100%
En savoir plus
Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type HEAD dont le temps de réponse doit être inférieur à 5 secondes. Si nous détectons une indisponibilité, nous effectuons un nouveau test toutes les 10 minutes, jusqu'à ce que la ressource soit à nouveau disponible.

Pour les flux SIRI et SIRI Lite, nous effectuons une requête HTTP de type GET : nous considérons une réponse avec un code 401 ou 405 comme étant disponible. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.

Rapport de validation

1 396 erreurs, 988 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 16/02/2026 à 08h09 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

Not in POSIX time E001 5 erreurs

All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC)

Exemples d'erreurs
  • trip_id 3752 stop_sequence 1 departure_time 0 is not POSIX time
  • trip_id 4251 stop_sequence 6 departure_time 0 is not POSIX time
  • trip_id 3456 stop_sequence 23 departure_time 0 is not POSIX time
  • trip_id 3751 stop_sequence 18 departure_time 0 is not POSIX time
  • trip_id 3254 stop_sequence 2 departure_time 0 is not POSIX time

stop_times_updates not strictly sorted E002 8 erreurs

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Exemples d'erreurs
  • trip_id 6260062 stop_sequence [0, 0] is not strictly sorted by increasing stop_sequence
  • trip_id 6260061 stop_sequence [0, 0] is not strictly sorted by increasing stop_sequence
  • trip_id 6258520 stop_sequence [0, 1, 2, 3, 4, 5, 5] is not strictly sorted by increasing stop_sequence
  • trip_id 6258950 stop_sequence [0, 0] is not strictly sorted by increasing stop_sequence
  • trip_id 6258962 stop_sequence [17, 18, 18] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 290 erreurs

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Exemples d'erreurs
  • trip_id 6260053 stop_sequence 51 arrival_time 08:10:00 (1771225800) is less than previous stop arrival_time 08:10:23 (1771225823) - times must increase between two sequential stops
  • trip_id 6257572 stop_sequence 17 arrival_time 08:37:00 (1771227420) is less than previous stop arrival_time 08:38:15 (1771227495) - times must increase between two sequential stops
  • trip_id 6257572 stop_sequence 17 arrival_time 08:37:00 (1771227420) is less than previous stop departure_time 08:38:15 (1771227495) - times must increase between two sequential stops
  • trip_id 6257572 stop_sequence 17 departure_time 08:37:00 (1771227420) is less than previous stop departure_time 08:38:15 (1771227495) - times must increase between two sequential stops
  • trip_id 6257572 stop_sequence 17 departure_time 08:37:00 (1771227420) is less than previous stop arrival_time 08:38:15 (1771227495) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 5 erreurs

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.

Exemples d'erreurs
  • trip_id 3752 stop_sequence 1 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:08:03 (1771225683) - departure time must be equal to or greater than arrival time
  • trip_id 4251 stop_sequence 6 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:08:04 (1771225684) - departure time must be equal to or greater than arrival time
  • trip_id 3456 stop_sequence 23 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:06:55 (1771225615) - departure time must be equal to or greater than arrival time
  • trip_id 3751 stop_sequence 18 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:07:34 (1771225654) - departure time must be equal to or greater than arrival time
  • trip_id 3254 stop_sequence 2 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:07:56 (1771225676) - departure time must be equal to or greater than arrival time

Sequential stop_time_updates have the same stop_sequence E036 8 erreurs

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Exemples d'erreurs
  • trip_id 6260062 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
  • trip_id 6260061 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
  • trip_id 6258520 has repeating stop_sequence 5 - stop_sequence must increase for each stop_time_update
  • trip_id 6258950 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
  • trip_id 6258962 has repeating stop_sequence 18 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 7 erreurs

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs
  • trip_id 6052659 has repeating stop_id AQUAVITA at stop_sequence 14 - sequential stop_ids should be different
  • trip_id 6052659 has repeating stop_id AQUAVITA at stop_sequence 15 - sequential stop_ids should be different
  • trip_id 6258520 has repeating stop_id DOMVATER at stop_sequence 5 - sequential stop_ids should be different
  • trip_id 6052646 has repeating stop_id AQUASUB at stop_sequence 27 - sequential stop_ids should be different
  • trip_id 6052658 has repeating stop_id AQUAVITA at stop_sequence 14 - sequential stop_ids should be different

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 061 erreurs

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

Exemples d'erreurs
  • GTFS-rt trip_id 6258979 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 6258979 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 6258979 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 6258979 stop_sequence 23 has stop_id 2STGI but GTFS stop_sequence 23 has stop_id 2BASC - stop_ids should be the same
  • GTFS-rt trip_id 6258979 stop_sequence 24 has stop_id 2BASC but GTFS stop_sequence 24 has stop_id 1AARD - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 12 erreurs

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Exemples d'erreurs
  • GTFS-rt trip_id 6260062 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 6260061 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 6258520 contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 6258950 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 6052646 contains stop_sequence 27 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 248 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 6258291 does not have a timestamp
  • trip_id 6258973 does not have a timestamp
  • trip_id 6258979 does not have a timestamp
  • trip_id 3556 does not have a timestamp
  • trip_id 6258942 does not have a timestamp

vehicle_id not populated W002 248 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 6258291 does not have a vehicle_id
  • trip_id 6258973 does not have a vehicle_id
  • trip_id 6258979 does not have a vehicle_id
  • trip_id 3556 does not have a vehicle_id
  • trip_id 6258942 does not have a vehicle_id

schedule_relationship not populated W009 492 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id 6258291 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6258291 does not have a schedule_relationship
  • trip_id 6258973 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6258973 does not have a schedule_relationship
  • trip_id 6258979 stop_sequence 20 (and potentially more for this trip) does not have a schedule_relationship
Valider ce GTFS-RT maintenant

Validations précédentes

Voici un récapitulatif des différents types d'erreurs constatés au cours des 30 derniers jours.

Identifiant d'erreur Description Nombre d'erreurs Nombre d'occurences
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 4 931 29 fois (100 % des 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 34 000 29 fois (100 % des validations)
W001 Timestamps should be populated for all elements 7 450 29 fois (100 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 7 450 29 fois (100 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 14 864 29 fois (100 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 459 26 fois (90 % des validations)
E001 All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) 283 23 fois (79 % des 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. 304 23 fois (79 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 43 13 fois (45 % des validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 49 13 fois (45 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 27 8 fois (28 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 1 1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 17/02/2026 à 03h18 Europe/Paris.

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

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 17/02/2026 à 03h18 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

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