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
❌100 erreurs, 156 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 21/12/2025 à 08h03 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 6 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 6189670 stop_sequence 1 arrival_time 08:41:00 (1766302860) is equal to previous stop departure_time 08:41:00 (1766302860) - times must increase between two sequential stops
- trip_id 6189670 stop_sequence 1 departure_time 08:41:00 (1766302860) is equal to previous stop departure_time 08:41:00 (1766302860) - times must increase between two sequential stops
- trip_id 6189573 stop_sequence 28 arrival_time 08:01:20 (1766300480) is less than previous stop arrival_time 08:02:48 (1766300568) - times must increase between two sequential stops
- trip_id 6189573 stop_sequence 28 arrival_time 08:01:20 (1766300480) is less than previous stop departure_time 08:02:48 (1766300568) - times must increase between two sequential stops
- trip_id 6189573 stop_sequence 28 departure_time 08:01:20 (1766300480) is less than previous stop departure_time 08:02:48 (1766300568) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 94 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 6189793 stop_sequence 8 has stop_id 1VERN but GTFS stop_sequence 8 has stop_id 1HSAU - stop_ids should be the same
- GTFS-rt trip_id 6189793 stop_sequence 9 has stop_id 1HSAU but GTFS stop_sequence 9 has stop_id 1JMOU - stop_ids should be the same
- GTFS-rt trip_id 6189793 stop_sequence 10 has stop_id 1JMOU but GTFS stop_sequence 10 has stop_id 1CAPU - stop_ids should be the same
- GTFS-rt trip_id 6189793 stop_sequence 11 has stop_id 1CAPU but GTFS stop_sequence 11 has stop_id 1HOPA - stop_ids should be the same
- GTFS-rt trip_id 6189793 stop_sequence 12 has stop_id 1HOPA but GTFS stop_sequence 12 has stop_id 1BMAI - stop_ids should be the same
Avertissements
timestamp not populated W001 39 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 6189695 does not have a timestamp
- trip_id 6189669 does not have a timestamp
- trip_id 6189755 does not have a timestamp
- trip_id 6261753 does not have a timestamp
- trip_id 6189931 does not have a timestamp
vehicle_id not populated W002 39 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 6189695 does not have a vehicle_id
- trip_id 6189669 does not have a vehicle_id
- trip_id 6189755 does not have a vehicle_id
- trip_id 6261753 does not have a vehicle_id
- trip_id 6189931 does not have a vehicle_id
schedule_relationship not populated W009 78 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 6189695 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6189695 does not have a schedule_relationship
- trip_id 6189669 stop_sequence 20 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 6189669 does not have a schedule_relationship
- trip_id 6189755 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 114 | 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 | 39 800 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 7 685 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 7 685 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 15 333 | 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 | 422 | 24 fois (80 % 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. | 284 | 22 fois (73 % des validations) |
| E001 | All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) | 267 | 21 fois (70 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 24 | 11 fois (37 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 29 | 11 fois (37 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 22/12/2025 à 00h04 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 22/12/2025 à 00h04 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1766358290"
}
}