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

08/04/2025
100%
09/04/2025
100%
10/04/2025
100%
11/04/2025
100%
12/04/2025
100%
13/04/2025
100%
14/04/2025
100%
15/04/2025
100%
16/04/2025
100%
17/04/2025
100%
18/04/2025
100%
19/04/2025
100%
20/04/2025
100%
21/04/2025
100%
22/04/2025
100%
23/04/2025
100%
24/04/2025
100%
25/04/2025
100%
26/04/2025
100%
27/04/2025
100%
28/04/2025
100%
29/04/2025
100%
30/04/2025
100%
01/05/2025
100%
02/05/2025
100%
03/05/2025
100%
04/05/2025
100%
05/05/2025
100%
06/05/2025
100%
07/05/2025
100%
08/05/2025
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

2 136 erreurs, 858 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 07/05/2025 à 09h52 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

Not in POSIX time E001 1 erreur

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 4208 stop_sequence 18 departure_time 0 is not POSIX time

stop_times_updates not strictly sorted E002 2 erreurs

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

Exemples d'erreurs
  • trip_id 5851943 stop_sequence [0, 0] is not strictly sorted by increasing stop_sequence
  • trip_id 5851558 stop_sequence [17, 17] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 142 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 5853485 stop_sequence 27 arrival_time 09:50:24 (1746604224) is less than previous stop arrival_time 09:51:59 (1746604319) - times must increase between two sequential stops
  • trip_id 5853485 stop_sequence 27 arrival_time 09:50:24 (1746604224) is less than previous stop departure_time 09:51:59 (1746604319) - times must increase between two sequential stops
  • trip_id 5853485 stop_sequence 27 departure_time 09:50:24 (1746604224) is less than previous stop departure_time 09:51:59 (1746604319) - times must increase between two sequential stops
  • trip_id 5853485 stop_sequence 27 departure_time 09:50:24 (1746604224) is less than previous stop arrival_time 09:51:59 (1746604319) - times must increase between two sequential stops
  • trip_id 5853488 stop_sequence 24 arrival_time 10:37:21 (1746607041) is less than previous stop arrival_time 10:39:11 (1746607151) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 1 erreur

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 4208 stop_sequence 18 departure_time 01:00:00 (0) is less than the same stop arrival_time 09:50:27 (1746604227) - departure time must be equal to or greater than arrival time

Sequential stop_time_updates have the same stop_sequence E036 2 erreurs

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

Exemples d'erreurs
  • trip_id 5851943 has repeating stop_sequence 0 - stop_sequence must increase for each stop_time_update
  • trip_id 5851558 has repeating stop_sequence 17 - stop_sequence must increase for each stop_time_update

stop_time_update arrival/departure doesn't have delay or time E044 192 erreurs

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

Exemples d'erreurs
  • trip_id 5853485 stop_sequence 69 departure doesn't have delay or time
  • trip_id 5853191 stop_sequence 33 departure doesn't have delay or time
  • trip_id 5852274 stop_sequence 0 arrival doesn't have delay or time
  • trip_id 5852869 stop_sequence 0 arrival doesn't have delay or time
  • trip_id 5853488 stop_sequence 0 arrival doesn't have delay or time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 792 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 5853485 stop_sequence 23 has stop_id CLEMOINE but GTFS stop_sequence 23 has stop_id STEXUPER - stop_ids should be the same
  • GTFS-rt trip_id 5853485 stop_sequence 27 has stop_id SECUSOCI but GTFS stop_sequence 27 has stop_id STAUBI-E - stop_ids should be the same
  • GTFS-rt trip_id 5853485 stop_sequence 28 has stop_id MAIL-NAE but GTFS stop_sequence 28 has stop_id HARAS-E - stop_ids should be the same
  • GTFS-rt trip_id 5853485 stop_sequence 29 has stop_id FO-LOR-R but GTFS stop_sequence 29 has stop_id LESGAR-E - stop_ids should be the same
  • GTFS-rt trip_id 5853485 stop_sequence 30 has stop_id STAUBI-E but GTFS stop_sequence 30 has stop_id BREMON-E - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 4 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 5853918 contains stop_sequence 54 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 5851943 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 5853429 contains stop_sequence 67 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 5863377 contains stop_sequence 29 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 215 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 5853485 does not have a timestamp
  • trip_id 5853191 does not have a timestamp
  • trip_id 5852274 does not have a timestamp
  • trip_id 5852869 does not have a timestamp
  • trip_id 5853488 does not have a timestamp

vehicle_id not populated W002 215 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 5853485 does not have a vehicle_id
  • trip_id 5853191 does not have a vehicle_id
  • trip_id 5852274 does not have a vehicle_id
  • trip_id 5852869 does not have a vehicle_id
  • trip_id 5853488 does not have a vehicle_id

schedule_relationship not populated W009 428 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id 5853485 stop_sequence 23 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5853485 does not have a schedule_relationship
  • trip_id 5853191 stop_sequence 15 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5853191 does not have a schedule_relationship
  • trip_id 5852274 stop_sequence 0 (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 475 29 fois (97 % des validations)
E044 stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing 4 606 29 fois (97 % 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 43 830 29 fois (97 % des validations)
W001 Timestamps should be populated for all elements 5 201 29 fois (97 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 5 201 29 fois (97 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 10 350 29 fois (97 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 164 26 fois (87 % 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. 60 17 fois (57 % des validations)
E001 All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) 47 16 fois (53 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 25 12 fois (40 % des validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 27 12 fois (40 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 2 1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 08/05/2025 à 06h21 Europe/Paris.

trip_updates (4) vehicle_positions (0) service_alerts (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 08/05/2025 à 06h21 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "trip:5791721", "trip_update": { "stop_time_update": [ { "arrival": {}, "departure": { "time": "1746681380" }, "stop_id": "1VERN", "stop_sequence": 0 }, { "arrival": { "time": "1746681470" }, "departure": { "time": "1746681470" }, "stop_id": "1HSAU", "stop_sequence": 1 }, { "arrival": { "time": "1746681590" }, "departure": { "time": "1746681590" }, "stop_id": "1JMOU", "stop_sequence": 2 }, { "arrival": { "time": "1746681670" }, "departure": { "time": "1746681670" }, "stop_id": "1CAPU", "stop_sequence": 3 } ], "trip": { "route_id": "A", "trip_id": "5791721" } } }, { "id": "trip:5791763", "trip_update": { "stop_time_update": [ { "arrival": {}, "departure": { "time": "1746681600" }, "stop_id": "2AARD", "stop_sequence": 0 }, { "arrival": { "time": "1746681690" }, "departure": { "time": "1746681690" }, "stop_id": "1BASC", "stop_sequence": 1 } ], "trip": { "route_id": "A", "trip_id": "5791763" } } }, { "id": "trip:5791724", "trip_update": { "stop_time_update": [ { "arrival": {}, "departure": { "time": "1746681420" }, "stop_id": "2MOLIE", "stop_sequence": 0 }, { "arrival": { "time": "1746681570" }, "departure": { "time": "1746681570" }, "stop_id": "2DOUT", "stop_sequence": 1 } ], "trip": { "route_id": "B", "trip_id": "5791724" } } }, { "id": "trip:5791723", "trip_update": { "stop_time_update": [ { "arrival": {}, "departure": { "time": "1746681120" }, "stop_id": "1STSE", "stop_sequence": 0 }, { "arrival": { "time": "1746681240" }, "departure": { "time": "1746681240" }, "stop_id": "1CECO", "stop_sequence": 1 }, { "arrival": { "time": "1746681380" }, "departure": { "time": "1746681380" }, "stop_id": "1CONS", "stop_sequence": 2 }, { "arrival": { "time": "1746681499" }, "departure": { "time": "1746681499" }, "stop_id": "1MTAI", "stop_sequence": 3 } ], "trip": { "route_id": "B", "trip_id": "5791723" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1746678096" } }