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
❌2 313 erreurs, 939 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 28/05/2025 à 09h07 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Not in POSIX time E001 2 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 15014 stop_sequence 6 departure_time 0 is not POSIX time
- trip_id 3522 stop_sequence 6 departure_time 0 is not POSIX time
Sequential stop_time_update times are not increasing E022 192 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 5843333 stop_sequence 13 arrival_time 09:50:00 (1748418600) is less than previous stop arrival_time 09:52:27 (1748418747) - times must increase between two sequential stops
- trip_id 5843333 stop_sequence 13 arrival_time 09:50:00 (1748418600) is less than previous stop departure_time 09:52:27 (1748418747) - times must increase between two sequential stops
- trip_id 5843333 stop_sequence 13 departure_time 09:50:00 (1748418600) is less than previous stop departure_time 09:52:27 (1748418747) - times must increase between two sequential stops
- trip_id 5843333 stop_sequence 13 departure_time 09:50:00 (1748418600) is less than previous stop arrival_time 09:52:27 (1748418747) - times must increase between two sequential stops
- trip_id 5852568 stop_sequence 8 arrival_time 09:06:31 (1748415991) is less than previous stop arrival_time 09:08:09 (1748416089) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 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 15014 stop_sequence 6 departure_time 01:00:00 (0) is less than the same stop arrival_time 09:06:51 (1748416011) - departure time must be equal to or greater than arrival time
- trip_id 3522 stop_sequence 6 departure_time 01:00:00 (0) is less than the same stop arrival_time 09:06:15 (1748415975) - 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 5852303 stop_sequence 0 arrival doesn't have delay or time
- trip_id 5851472 stop_sequence 26 departure doesn't have delay or time
- trip_id 5853487 stop_sequence 0 arrival doesn't have delay or time
- trip_id 5853652 stop_sequence 35 departure doesn't have delay or time
- trip_id 5851516 stop_sequence 17 departure doesn't have delay or time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 908 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 5851858 stop_sequence 1 has stop_id 2ANRO but GTFS stop_sequence 1 has stop_id 2JVIL - stop_ids should be the same
- GTFS-rt trip_id 5851858 stop_sequence 2 has stop_id 2JVIL but GTFS stop_sequence 2 has stop_id 2JE23 - stop_ids should be the same
- GTFS-rt trip_id 5851858 stop_sequence 3 has stop_id 2JE23 but GTFS stop_sequence 3 has stop_id 2BAMA - stop_ids should be the same
- GTFS-rt trip_id 5851858 stop_sequence 4 has stop_id 2BAMA but GTFS stop_sequence 4 has stop_id 2STRA - stop_ids should be the same
- GTFS-rt trip_id 5851858 stop_sequence 5 has stop_id 2STRA but GTFS stop_sequence 5 has stop_id 2LAFA - 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 4103 contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 5852447 contains stop_sequence 51 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 5853480 contains stop_sequence 68 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 5852393 contains stop_sequence 55 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 235 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 5851858 does not have a timestamp
- trip_id 5852303 does not have a timestamp
- trip_id 15014 does not have a timestamp
- trip_id 5851472 does not have a timestamp
- trip_id 5853487 does not have a timestamp
vehicle_id not populated W002 235 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 5851858 does not have a vehicle_id
- trip_id 5852303 does not have a vehicle_id
- trip_id 15014 does not have a vehicle_id
- trip_id 5851472 does not have a vehicle_id
- trip_id 5853487 does not have a vehicle_id
schedule_relationship not populated W009 469 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 5851858 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 5851858 does not have a schedule_relationship
- trip_id 5852303 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 5852303 does not have a schedule_relationship
- trip_id 15014 stop_sequence 6 (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 240 | 29 fois (97 % des validations) |
| E044 | stop_time_update.arrival and stop_time_update.departure must have either delay or time - both fields cannot be missing | 4 733 | 29 fois (97 % 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 | 45 157 | 29 fois (97 % des validations) |
| W001 | Timestamps should be populated for all elements | 5 450 | 29 fois (97 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 5 450 | 29 fois (97 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 10 845 | 29 fois (97 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 184 | 27 fois (90 % 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. | 76 | 20 fois (67 % des validations) |
| E001 | All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) | 55 | 19 fois (63 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 17 | 9 fois (30 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 18 | 9 fois (30 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 2 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 29/05/2025 à 01h42 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/05/2025 à 01h42 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1748475731"
}
}