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

12/01/2026
100%
13/01/2026
100%
14/01/2026
100%
15/01/2026
100%
16/01/2026
100%
17/01/2026
100%
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%
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 777 erreurs, 1 337 avertissements

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

Erreurs

Not in POSIX time E001 22 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 35401 stop_sequence 9 departure_time 0 is not POSIX time
  • trip_id 4003 stop_sequence 8 departure_time 0 is not POSIX time
  • trip_id 15010 stop_sequence 1 departure_time 0 is not POSIX time
  • trip_id 21004 stop_sequence 0 departure_time 0 is not POSIX time
  • trip_id 4203 stop_sequence 1 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 6237321 stop_sequence [17, 17, 17] is not strictly sorted by increasing stop_sequence
  • trip_id 6237340 stop_sequence [0, 0] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 172 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 6238919 stop_sequence 46 arrival_time 08:30:30 (1770708630) is less than previous stop arrival_time 08:30:36 (1770708636) - times must increase between two sequential stops
  • trip_id 6238919 stop_sequence 46 arrival_time 08:30:30 (1770708630) is less than previous stop departure_time 08:30:36 (1770708636) - times must increase between two sequential stops
  • trip_id 6238919 stop_sequence 46 departure_time 08:30:30 (1770708630) is less than previous stop departure_time 08:30:36 (1770708636) - times must increase between two sequential stops
  • trip_id 6238919 stop_sequence 46 departure_time 08:30:30 (1770708630) is less than previous stop arrival_time 08:30:36 (1770708636) - times must increase between two sequential stops
  • trip_id 4003 stop_sequence 8 departure_time 01:00:00 (0) is less than previous stop departure_time 08:08:43 (1770707323) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 25 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 6239036 stop_sequence 28 departure_time 08:18:00 (1770707880) is less than the same stop arrival_time 08:18:02 (1770707882) - departure time must be equal to or greater than arrival time
  • trip_id 35401 stop_sequence 9 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:08:25 (1770707305) - departure time must be equal to or greater than arrival time
  • trip_id 4003 stop_sequence 8 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:09:55 (1770707395) - departure time must be equal to or greater than arrival time
  • trip_id 15010 stop_sequence 1 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:08:57 (1770707337) - departure time must be equal to or greater than arrival time
  • trip_id 21004 stop_sequence 0 departure_time 01:00:00 (0) is less than the same stop arrival_time 08:09:59 (1770707399) - departure time must be equal to or greater than arrival time

Sequential stop_time_updates have the same stop_sequence E036 3 erreurs

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

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

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 526 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 3610 stop_sequence 8 has stop_id FARCYSJA but GTFS stop_sequence 8 has stop_id QUAIsubN - stop_ids should be the same
  • GTFS-rt trip_id 6240115 stop_sequence 19 has stop_id ESA but GTFS stop_sequence 19 has stop_id RABELAI - stop_ids should be the same
  • GTFS-rt trip_id 6240115 stop_sequence 20 has stop_id RABELAI but GTFS stop_sequence 20 has stop_id ALEROY - stop_ids should be the same
  • GTFS-rt trip_id 6240115 stop_sequence 21 has stop_id ALEROY but GTFS stop_sequence 21 has stop_id PAULBERT - stop_ids should be the same
  • GTFS-rt trip_id 6240115 stop_sequence 22 has stop_id PAULBERT but GTFS stop_sequence 22 has stop_id HARAS - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 27 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 14402 contains stop_sequence 7 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 6239130 contains stop_sequence 51 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 3806 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 3438 contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 3512 contains stop_sequence 21 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 335 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 6238688 does not have a timestamp
  • trip_id 6238265 does not have a timestamp
  • trip_id 6238574 does not have a timestamp
  • trip_id 6054497 does not have a timestamp
  • trip_id 6237278 does not have a timestamp

vehicle_id not populated W002 335 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 6238688 does not have a vehicle_id
  • trip_id 6238265 does not have a vehicle_id
  • trip_id 6238574 does not have a vehicle_id
  • trip_id 6054497 does not have a vehicle_id
  • trip_id 6237278 does not have a vehicle_id

schedule_relationship not populated W009 667 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id 6238688 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6238688 does not have a schedule_relationship
  • trip_id 6238265 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 6238265 does not have a schedule_relationship
  • trip_id 6238574 stop_sequence 40 (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. 5 018 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 941 29 fois (100 % des validations)
W001 Timestamps should be populated for all elements 7 820 29 fois (100 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 7 820 29 fois (100 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 15 604 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 523 28 fois (97 % des validations)
E001 All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) 314 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. 335 23 fois (79 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 41 14 fois (48 % des validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 48 14 fois (48 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 26 12 fois (41 % 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 11/02/2026 à 03h48 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 11/02/2026 à 03h48 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

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