Jeu de données ouvert gtfs-rt - Extension GTFS-RT : Mises à jour de trajet pour Réseau urbain Léo

Détails de la ressource

Nom du fichier : Extension GTFS-RT : Mises à jour de trajet

Format : gtfs-rt

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

Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type 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

❌258 erreurs, 44 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 18/12/2025 à 08h12 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 16 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 14733{A32_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 15374{B31_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 15375{B32_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 15372{B30_1}-24I_PSC_LMCJVSDF_03_LMJV does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 15376{B33_1}-24I_PSC_LMCJVSDF_03_LMJV 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 16 erreurs

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Exemples d'erreurs

route_id A32_1 does not exist in the GTFS data routes.txt
route_id B31_1 does not exist in the GTFS data routes.txt
route_id B32_1 does not exist in the GTFS data routes.txt
route_id B30_1 does not exist in the GTFS data routes.txt
route_id B33_1 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 149 erreurs

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Exemples d'erreurs

trip_id 14733{A32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHABPSM1 does not exist in GTFS data stops.txt
trip_id 14733{A32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHAVCHA1 does not exist in GTFS data stops.txt
trip_id 14733{A32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHABR131 does not exist in GTFS data stops.txt
trip_id 14733{A32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHABVBL1 does not exist in GTFS data stops.txt
trip_id 14733{A32_1}-24I_PSC_LMCJVSDF_03_LMJV stop_id CHALVAL1 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 74 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 15539{02_2}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 7 arrival_time 06:59:07 (1766037547) is less than previous stop arrival_time 07:45:41 (1766040341) - times must increase between two sequential stops
trip_id 15539{02_2}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 7 arrival_time 06:59:07 (1766037547) is less than previous stop departure_time 07:45:49 (1766040349) - times must increase between two sequential stops
trip_id 15539{02_2}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 7 departure_time 07:00:59 (1766037659) is less than previous stop departure_time 07:45:49 (1766040349) - times must increase between two sequential stops
trip_id 15539{02_2}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 7 departure_time 07:00:59 (1766037659) is less than previous stop arrival_time 07:45:41 (1766040341) - times must increase between two sequential stops
trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV stop_sequence 41 arrival_time 08:16:15 (1766042175) is equal to previous stop arrival_time 08:16:15 (1766042175) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 3 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 4-10083172355 stop_sequence 6 departure_time 07:19:26 (1766038766) is less than the same stop arrival_time 08:11:24 (1766041884) - departure time must be equal to or greater than arrival time
trip_id 4-10083172355 stop_sequence 7 departure_time 07:24:26 (1766039066) is less than the same stop arrival_time 08:11:25 (1766041885) - departure time must be equal to or greater than arrival time
trip_id 4-10083172355 stop_sequence 8 departure_time 07:29:26 (1766039366) is less than the same stop arrival_time 08:11:26 (1766041886) - departure time must be equal to or greater than arrival time

Avertissements

timestamp not populated W001 37 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id 15539{02_2}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 15438{03_4}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 17986{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 17924{01_3}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp
trip_id 17788{04_2}-25U_PSC_LMCJVSDF_01_LMWJV does not have a timestamp

vehicle_id not populated W002 7 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 4-10066657284 does not have a vehicle_id
trip_id 4-10066657283 does not have a vehicle_id
trip_id 4-10066788356 does not have a vehicle_id
trip_id 4-10066788355 does not have a vehicle_id
trip_id 4-10066460675 does not have a vehicle_id

Valider ce GTFS-RT maintenant

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	377	26 fois (87 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	377	26 fois (87 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	3 807	26 fois (87 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1 707	26 fois (87 % des validations)
W001	Timestamps should be populated for all elements	862	26 fois (87 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	236	26 fois (87 % 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.	17	9 fois (30 % des validations)
E023	For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip	1	1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 19/12/2025 à 04h52 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 19/12/2025 à 04h52 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1766116364"
  }
}