Détails de la ressource
Les mises à jour de trajet représentent des fluctuations dans les horaires
Cette ressource fait partie du jeu de données Réseau urbain Léo.
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
❌313 erreurs, 42 avertissements
De nombreuses erreurs de validation indiquent que les identifiants du GTFS-RT ne correspondent pas aux identifiants du GTFS.
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 23/04/2026 à 09h11 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 14 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 4-10083368961 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066722818 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10100015106 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10066788354 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4-10083368964 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 14 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id 601 does not exist in the GTFS data routes.txt
- route_id 600 does not exist in the GTFS data routes.txt
- route_id 602 does not exist in the GTFS data routes.txt
- route_id 600 does not exist in the GTFS data routes.txt
- route_id 601 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 201 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 4-10083368961 stop_id 2860 does not exist in GTFS data stops.txt
- trip_id 4-10083368961 stop_id 2861 does not exist in GTFS data stops.txt
- trip_id 4-10083368961 stop_id 2862 does not exist in GTFS data stops.txt
- trip_id 4-10083368961 stop_id 2863 does not exist in GTFS data stops.txt
- trip_id 4-10083368961 stop_id 3210 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 84 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 15420{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 38 arrival_time 09:15:33 (1776928533) is equal to previous stop arrival_time 09:15:33 (1776928533) - times must increase between two sequential stops
- trip_id 15420{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 38 arrival_time 09:15:33 (1776928533) is equal to previous stop departure_time 09:15:33 (1776928533) - times must increase between two sequential stops
- trip_id 15420{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 38 departure_time 09:15:33 (1776928533) is equal to previous stop departure_time 09:15:33 (1776928533) - times must increase between two sequential stops
- trip_id 15420{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 38 departure_time 09:15:33 (1776928533) is equal to previous stop arrival_time 09:15:33 (1776928533) - times must increase between two sequential stops
- trip_id 15440{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 24 arrival_time 09:14:56 (1776928496) is equal to previous stop arrival_time 09:14:56 (1776928496) - times must increase between two sequential stops
Avertissements
timestamp not populated W001 32 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 17973{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 17987{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 15420{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 17925{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
- trip_id 17770{04_2}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
vehicle_id not populated W002 10 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 4-10083368964 does not have a vehicle_id
- trip_id 4-10083368963 does not have a vehicle_id
- trip_id 4-10083237891 does not have a vehicle_id
- trip_id 4-10083368962 does not have a vehicle_id
- trip_id 4-10066788356 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 705 | 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. | 1 844 | 28 fois (93 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 295 | 25 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 295 | 25 fois (83 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 533 | 25 fois (83 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 218 | 25 fois (83 % 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. | 7 | 6 fois (20 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 24/04/2026 à 01h30 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 24/04/2026 à 01h30 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1776987042"
}
}