Détails de la ressource
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
En savoir plus
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
❌99 erreurs, 148 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 28/09/2025 à 09h02 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 2 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 6189671 stop_sequence 1 arrival_time 09:46:00 (1759045560) is equal to previous stop departure_time 09:46:00 (1759045560) - times must increase between two sequential stops
- trip_id 6189671 stop_sequence 1 departure_time 09:46:00 (1759045560) is equal to previous stop departure_time 09:46:00 (1759045560) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 97 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 6189763 stop_sequence 19 has stop_id 2BOTA but GTFS stop_sequence 19 has stop_id 2PMAY - stop_ids should be the same
- GTFS-rt trip_id 6189763 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 6189763 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 6189763 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 6189763 stop_sequence 23 has stop_id 2STGI but GTFS stop_sequence 23 has stop_id 2BASC - stop_ids should be the same
Avertissements
timestamp not populated W001 37 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 6189676 does not have a timestamp
- trip_id 6189756 does not have a timestamp
- trip_id 6189764 does not have a timestamp
- trip_id 6224896 does not have a timestamp
- trip_id 6189638 does not have a timestamp
vehicle_id not populated W002 37 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 6189676 does not have a vehicle_id
- trip_id 6189756 does not have a vehicle_id
- trip_id 6189764 does not have a vehicle_id
- trip_id 6224896 does not have a vehicle_id
- trip_id 6189638 does not have a vehicle_id
schedule_relationship not populated W009 74 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 6189676 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6189676 does not have a schedule_relationship
- trip_id 6189756 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6189756 does not have a schedule_relationship
- trip_id 6189764 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
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 404 | 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 | 32 206 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 5 800 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 5 800 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 11 547 | 30 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 | 179 | 28 fois (93 % 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. | 96 | 24 fois (80 % des validations) |
| E044 | stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing | 4 633 | 24 fois (80 % des validations) |
| E001 | All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) | 66 | 21 fois (70 % des validations) |
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 924 | 10 fois (33 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 9 | 4 fois (13 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 9 | 4 fois (13 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 4 | 2 fois (7 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 29/09/2025 à 01h56 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 29/09/2025 à 01h56 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1759103811"
}
}