Jeu de données ouvert gtfs-rt - irigo-angers-gtfs-trip-updates pour Réseau urbain Irigo

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

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 107 erreurs, 949 avertissements

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

Erreurs

Sequential stop_time_update times are not increasing E022 196 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 5863378 stop_sequence 22 arrival_time 09:04:57 (1743663897) is less than previous stop arrival_time 09:10:10 (1743664210) - times must increase between two sequential stops
trip_id 5863378 stop_sequence 22 arrival_time 09:04:57 (1743663897) is less than previous stop departure_time 09:10:10 (1743664210) - times must increase between two sequential stops
trip_id 5863378 stop_sequence 22 departure_time 09:04:57 (1743663897) is less than previous stop departure_time 09:10:10 (1743664210) - times must increase between two sequential stops
trip_id 5863378 stop_sequence 22 departure_time 09:04:57 (1743663897) is less than previous stop arrival_time 09:10:10 (1743664210) - times must increase between two sequential stops
trip_id 5852417 stop_sequence 17 arrival_time 09:44:37 (1743666277) is less than previous stop arrival_time 09:45:00 (1743666300) - 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 5854055 stop_sequence 31 departure_time 09:30:00 (1743665400) is less than the same stop arrival_time 09:30:01 (1743665401) - departure time must be equal to or greater than arrival time

stop_time_update arrival/departure doesn't have delay or time E044 205 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 5851472 stop_sequence 26 departure doesn't have delay or time
trip_id 5863378 stop_sequence 31 departure doesn't have delay or time
trip_id 5851568 stop_sequence 0 arrival doesn't have delay or time
trip_id 5851568 stop_sequence 17 departure doesn't have delay or time
trip_id 5853996 stop_sequence 48 departure doesn't have delay or time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 700 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 5851472 stop_sequence 16 has stop_id 2JMOU but GTFS stop_sequence 16 has stop_id 2HSAU - stop_ids should be the same
GTFS-rt trip_id 5851472 stop_sequence 17 has stop_id 2HSAU but GTFS stop_sequence 17 has stop_id 2VERN - stop_ids should be the same
GTFS-rt trip_id 5851472 stop_sequence 18 has stop_id 2VERN but GTFS stop_sequence 18 has stop_id 2BOTA - stop_ids should be the same
GTFS-rt trip_id 5851472 stop_sequence 20 has stop_id 2BOTA but GTFS stop_sequence 20 has stop_id 2BROY - stop_ids should be the same
GTFS-rt trip_id 5851472 stop_sequence 21 has stop_id 2PMAY but GTFS stop_sequence 21 has stop_id 2ACAS - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 5 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 5853939 contains stop_sequence 58 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 5852393 contains stop_sequence 53 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 4103 contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 5852110 contains stop_sequence 80 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 5853428 contains stop_sequence 67 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 238 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id 5851472 does not have a timestamp
trip_id 5863378 does not have a timestamp
trip_id 5851568 does not have a timestamp
trip_id 5853996 does not have a timestamp
trip_id 5852417 does not have a timestamp

vehicle_id not populated W002 238 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 5851472 does not have a vehicle_id
trip_id 5863378 does not have a vehicle_id
trip_id 5851568 does not have a vehicle_id
trip_id 5853996 does not have a vehicle_id
trip_id 5852417 does not have a vehicle_id

schedule_relationship not populated W009 473 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id 5851472 stop_sequence 16 (and potentially more for this trip) does not have a schedule_relationship
trip_id 5851472 does not have a schedule_relationship
trip_id 5863378 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
trip_id 5863378 does not have a schedule_relationship
trip_id 5851568 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.	7 170	30 fois (100 % des validations)
E044	stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing	5 688	30 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	52 999	30 fois (100 % des validations)
W001	Timestamps should be populated for all elements	7 647	30 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	7 647	30 fois (100 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	15 149	30 fois (100 % 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.	283	26 fois (87 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	237	26 fois (87 % des validations)
E001	All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC)	259	24 fois (80 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	39	18 fois (60 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	14	6 fois (20 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	15	6 fois (20 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	1	1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 04/04/2025 à 00h53 Europe/Paris.

trip_updates (1) 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 04/04/2025 à 00h53 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "entity": [
    {
      "id": "trip:5853928",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "time": "1743720729"
            },
            "departure": {
              "time": "1743720729"
            },
            "schedule_relationship": "SKIPPED",
            "stop_id": "SOLAND",
            "stop_sequence": 52
          }
        ],
        "trip": {
          "route_id": "03",
          "trip_id": "5853928"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1743720824"
  }
}