Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Izilo.
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
❌275 erreurs, 234 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
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 150 erreurs
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Exemples d'erreurs
- trip_id 4351628 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4329045 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4329035 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4351614 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4444552 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 120 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 4329626 stop_sequence 1 departure_time 09:48:00 (1743666480) is less than previous stop departure_time 09:54:39 (1743666879) - times must increase between two sequential stops
- trip_id 4329626 stop_sequence 1 departure_time 09:48:00 (1743666480) is less than previous stop arrival_time 09:54:39 (1743666879) - times must increase between two sequential stops
- trip_id 4329626 stop_sequence 2 arrival_time 09:48:53 (1743666533) is less than previous stop arrival_time 09:54:39 (1743666879) - times must increase between two sequential stops
- trip_id 4329626 stop_sequence 2 departure_time 09:48:53 (1743666533) is less than previous stop arrival_time 09:54:39 (1743666879) - times must increase between two sequential stops
- trip_id 4444411 stop_sequence 12 arrival_time 09:08:33 (1743664113) is less than previous stop arrival_time 09:10:49 (1743664249) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 5 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 4497305 has repeating stop_id ALLE - sequential stop_ids should be different
- trip_id 4497355 has repeating stop_id ALLE - sequential stop_ids should be different
- trip_id 4497358 has repeating stop_id ALLE - sequential stop_ids should be different
- trip_id 4497357 has repeating stop_id ALLE - sequential stop_ids should be different
- trip_id 4497356 has repeating stop_id ALLE - sequential stop_ids should be different
Avertissements
timestamp not populated W001 150 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 4351628 does not have a timestamp
- trip_id 4329045 does not have a timestamp
- trip_id 4329035 does not have a timestamp
- trip_id 4351614 does not have a timestamp
- trip_id 4444552 does not have a timestamp
vehicle_id not populated W002 84 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 4351628 does not have a vehicle_id
- trip_id 4329045 does not have a vehicle_id
- trip_id 4351614 does not have a vehicle_id
- trip_id 4444552 does not have a vehicle_id
- trip_id 4351602 does not have a vehicle_id
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 5 493 | 30 fois (100 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 4 233 | 30 fois (100 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 87 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 5 495 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 3 266 | 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. | 2 | 2 fois (7 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 60 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 04/04/2025 à 01h24 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 04/04/2025 à 01h24 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743722675"
}
}