Détails de la ressource

Nom du fichier : GTFS-RT TripUpdate Marinéo Boulogne - horaires des prochains passages à l'arrêt
Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau urbain Marinéo.

Disponibilité au téléchargement

19/03/2025
100%
20/03/2025
100%
21/03/2025
100%
22/03/2025
100%
23/03/2025
100%
24/03/2025
100%
25/03/2025
100%
26/03/2025
100%
27/03/2025
100%
28/03/2025
100%
29/03/2025
100%
30/03/2025
100%
31/03/2025
100%
01/04/2025
100%
02/04/2025
100%
03/04/2025
100%
04/04/2025
100%
05/04/2025
100%
06/04/2025
100%
07/04/2025
100%
08/04/2025
100%
09/04/2025
100%
10/04/2025
100%
11/04/2025
100%
12/04/2025
100%
13/04/2025
100%
14/04/2025
100%
15/04/2025
100%
16/04/2025
100%
17/04/2025
100%
18/04/2025
100%
En savoir plus
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

136 erreurs, 34 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 17/04/2025 à 09h13 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 11 erreurs

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Exemples d'erreurs
  • trip_id 20550863 stop_sequence for stop_ids [lpopagn, lpoalpr, smblamb2, smbpeu1, smbpoly, smbdesv2, smbgir2, smbecol3, bsmhopi3, bsmhre, smbecol, bsmrho, bsmbran2, bsmhenn, bsmsncf2, bsmdute, bsmcca2, bsmpft1, bsmepe, bsmpca, bsmmba, lepcime, lpohen, lpopfa, lpogou, lpolive, lpopagn, lpoloti, lpoegli, lpoalpr, outsall2, outmass2, outserv2] is not strictly sorted by increasing stop_sequence
  • trip_id 20550860 stop_sequence for stop_ids [lpopagn, lpoalpr, smbpoly, smbdesv2, smbgir2, smbecol3, bsmhopi3, bsmhre, smbecol, bsmrho, bsmbran2, bsmhenn, bsmsncf2, bsmdute, bsmcca2, bsmpft1, bsmepe, bsmpca, bsmmba, lepcime, lpohen, lpopfa, lpogou, lpolive, lpopagn, lpoloti, lpoegli, lpoalpr, outsall2, outmass2, outserv2] is not strictly sorted by increasing stop_sequence
  • trip_id 20550858 stop_sequence for stop_ids [lpopagn, lpoalpr, baicas1, baiaub1, baihetr, baique1, baibert2, baipat2, baiboud2, smblamb2, smbpeu1, smbpoly, smbdesv2, smbgir2, smbecol3, bsmhopi3, bsmhre, smbecol, bsmrho, bsmbran2, bsmhenn, bsmsncf2, bsmdute, bsmcca2, bsmpft1, bsmepe, bsmpca, bsmmba, lepcime, lpohen, lpopfa, lpogou, lpolive, lpopagn, lpoloti, lpoegli, lpoalpr, outsall2, outmass2, outserv2] is not strictly sorted by increasing stop_sequence
  • trip_id 20550871 stop_sequence for stop_ids [lpopagn, lpoalpr, smbpoly, smbdesv2, smbgir2, smbecol3, bsmhopi3, bsmhre, smbecol, bsmrho, bsmbran2, bsmhenn, bsmsncf2, bsmdute, bsmcca2, bsmpft1, bsmepe, bsmpca, bsmmba, lepcime, lpohen, lpopfa, lpogou, lpolive, lpopagn, lpoloti, lpoegli, lpoalpr, outsall2, outmass2, outserv2] is not strictly sorted by increasing stop_sequence
  • trip_id 20550869 stop_sequence for stop_ids [lpopagn, lpoalpr, smblamb2, smbpeu1, smbpoly, smbdesv2, smbgir2, smbecol3, bsmhopi3, bsmhre, smbecol, bsmrho, bsmbran2, bsmhenn, bsmsncf2, bsmdute, bsmcca2, bsmpft1, bsmepe, bsmpca, bsmmba, lepcime, lpohen, lpopfa, lpogou, lpolive, lpopagn, lpoloti, lpoegli, lpoalpr, outsall2, outmass2, outserv2] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 1 erreur

If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence

Exemples d'erreurs
  • trip_id 20472992 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided

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

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

Exemples d'erreurs
  • trip_id 20550865 stop_id outaisn2 does not exist in GTFS data stops.txt
  • trip_id 20550865 stop_id outaisn does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 118 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 20550854 stop_id wimmair departure_time 08:07:00 (1744870020) is less than previous stop departure_time 08:11:39 (1744870299) - times must increase between two sequential stops
  • trip_id 20550854 stop_id wimmair departure_time 08:07:00 (1744870020) is less than previous stop arrival_time 08:10:19 (1744870219) - times must increase between two sequential stops
  • trip_id 20550854 stop_id wimnapo2 arrival_time 08:08:32 (1744870112) is less than previous stop arrival_time 08:10:19 (1744870219) - times must increase between two sequential stops
  • trip_id 20550854 stop_id wimnapo2 departure_time 08:08:32 (1744870112) is less than previous stop arrival_time 08:10:19 (1744870219) - times must increase between two sequential stops
  • trip_id 20550862 stop_id wimmair departure_time 09:03:00 (1744873380) is less than previous stop departure_time 09:10:13 (1744873813) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 4 erreurs

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs
  • trip_id 20550861 has repeating stop_id wimsncf - sequential stop_ids should be different
  • trip_id 20550868 has repeating stop_id wimmair2 - sequential stop_ids should be different
  • trip_id 20550867 has repeating stop_id wimsncf - sequential stop_ids should be different
  • trip_id 20550872 has repeating stop_id wimsncf - sequential stop_ids should be different

Avertissements

vehicle_id not populated W002 34 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 20756806 does not have a vehicle_id
  • trip_id 20756814 does not have a vehicle_id
  • trip_id 20756839 does not have a vehicle_id
  • trip_id 20756842 does not have a vehicle_id
  • trip_id 20756841 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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 2 150 30 fois (100 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 166 30 fois (100 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 009 30 fois (100 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 80 26 fois (87 % des validations)
E009 If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence 51 22 fois (73 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 88 22 fois (73 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 5 5 fois (17 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 5 5 fois (17 % 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. 3 3 fois (10 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 18/04/2025 à 04h04 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (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 18/04/2025 à 04h04 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "20756823", "trip_update": { "stop_time_update": [ { "departure": { "time": "1744945200", "uncertainty": 120 }, "stop_id": "bsmcca7" } ], "timestamp": "1744941859", "trip": { "direction_id": 1, "route_id": "B2", "schedule_relationship": "SCHEDULED", "trip_id": "20756823" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1744941859" } }