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.

Rapport de validation

❌1 619 erreurs, 610 avertissements

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

Erreurs

Sequential stop_time_update times are not increasing E022 146 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 5691829 stop_sequence 31 arrival_time 09:12:14 (1721977934) is less than previous stop arrival_time 09:12:19 (1721977939) - times must increase between two sequential stops
trip_id 5691829 stop_sequence 31 arrival_time 09:12:14 (1721977934) is less than previous stop departure_time 09:12:19 (1721977939) - times must increase between two sequential stops
trip_id 5691829 stop_sequence 31 departure_time 09:12:14 (1721977934) is less than previous stop departure_time 09:12:19 (1721977939) - times must increase between two sequential stops
trip_id 5691829 stop_sequence 31 departure_time 09:12:14 (1721977934) is less than previous stop arrival_time 09:12:19 (1721977939) - times must increase between two sequential stops
trip_id 5691029 stop_sequence 60 arrival_time 10:02:12 (1721980932) is less than previous stop arrival_time 10:02:14 (1721980934) - 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 5691679 stop_sequence 43 departure_time 09:44:00 (1721979840) is less than the same stop arrival_time 09:44:01 (1721979841) - departure time must be equal to or greater than arrival time

stop_time_update arrival/departure doesn't have delay or time E044 149 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 5691712 stop_sequence 0 arrival doesn't have delay or time
trip_id 5692163 stop_sequence 0 arrival doesn't have delay or time
trip_id 5692163 stop_sequence 35 departure doesn't have delay or time
trip_id 5693477 stop_sequence 0 arrival doesn't have delay or time
trip_id 5692144 stop_sequence 37 departure doesn't have delay or time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 319 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 2455 stop_sequence 5 has stop_id BRAI8M-E but GTFS stop_sequence 5 has stop_id BRAICO-E - stop_ids should be the same
GTFS-rt trip_id 2455 stop_sequence 6 has stop_id BRAICO-E but GTFS stop_sequence 6 has stop_id ANDAMA-E - stop_ids should be the same
GTFS-rt trip_id 2455 stop_sequence 7 has stop_id ANDAMA-E but GTFS stop_sequence 7 has stop_id RESTLA-E - stop_ids should be the same
GTFS-rt trip_id 2455 stop_sequence 8 has stop_id RESTLA-E but GTFS stop_sequence 8 has stop_id ANDALA-E - stop_ids should be the same
GTFS-rt trip_id 2455 stop_sequence 9 has stop_id ANDALA-E but GTFS stop_sequence 9 has stop_id JDELAV-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 5693344 contains stop_sequence 22 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 5691445 contains stop_sequence 79 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 5691447 contains stop_sequence 82 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 5693345 contains stop_sequence 22 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 153 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id 5691712 does not have a timestamp
trip_id 5692163 does not have a timestamp
trip_id 5693477 does not have a timestamp
trip_id 5692144 does not have a timestamp
trip_id 5693468 does not have a timestamp

vehicle_id not populated W002 153 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 5691712 does not have a vehicle_id
trip_id 5692163 does not have a vehicle_id
trip_id 5693477 does not have a vehicle_id
trip_id 5692144 does not have a vehicle_id
trip_id 5693468 does not have a vehicle_id

schedule_relationship not populated W009 304 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id 5691712 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id 5691712 does not have a schedule_relationship
trip_id 5692163 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
trip_id 5692163 does not have a schedule_relationship
trip_id 5693477 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.	5 356	27 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	3 994	27 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 055	27 fois (100 % des validations)
W001	Timestamps should be populated for all elements	4 212	27 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	4 212	27 fois (100 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	8 315	27 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	140	24 fois (89 % 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.	25	16 fois (59 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	44	14 fois (52 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	45	14 fois (52 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	139	13 fois (48 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	65	9 fois (33 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	328	9 fois (33 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	4	2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 27/07/2024 à 03h22 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 27/07/2024 à 03h22 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


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