transport.data.gouv.fr transport.data.gouv.fr

Détails de la ressource

Nom du fichier : Données en temps réel au format GTFS-RT (VehiclePosition)
Format : gtfs-rt
Télécharger

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

Disponibilité au téléchargement

22/10/2024
94.2%
23/10/2024
94.9%
24/10/2024
93.9%
25/10/2024
95.4%
26/10/2024
98.6%
27/10/2024
96.2%
28/10/2024
93.4%
29/10/2024
81.3%
30/10/2024
94.9%
31/10/2024
88.1%
01/11/2024
94.5%
02/11/2024
98.6%
03/11/2024
95.8%
04/11/2024
87.4%
05/11/2024
95.9%
06/11/2024
94.6%
07/11/2024
89.7%
08/11/2024
93.7%
09/11/2024
96.7%
10/11/2024
95.7%
11/11/2024
97.8%
12/11/2024
86.3%
13/11/2024
90%
14/11/2024
94.6%
15/11/2024
93.3%
16/11/2024
97.6%
17/11/2024
94.5%
18/11/2024
91.4%
19/11/2024
90.6%
20/11/2024
93.1%
21/11/2024
95.7%
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

❌320 erreurs, 3 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 21/11/2024 à 08h16 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 123 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
  • vehicle_id 354 trip_id 2-153259933697 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 101 trip_id 2-153897664513 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 64 trip_id 2-319160324 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 272 trip_id 2-153075449857 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 238 trip_id ANVAN.60682 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 95 erreurs

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

Exemples d'erreurs
  • vehicle_id 354 route_id 9135 does not exist in the GTFS data routes.txt
  • vehicle_id 101 route_id 9173 does not exist in the GTFS data routes.txt
  • vehicle_id 272 route_id 9124 does not exist in the GTFS data routes.txt
  • vehicle_id 238 route_id bre_vannes_2024_2025.1612938084700 does not exist in the GTFS data routes.txt
  • vehicle_id 107 route_id 9021 does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs
  • vehicle_id 354 stop_id 732 does not exist in GTFS data stops.txt
  • vehicle_id 101 stop_id 1079 does not exist in GTFS data stops.txt
  • vehicle_id 272 stop_id 965 does not exist in GTFS data stops.txt
  • vehicle_id 238 stop_id bre_vannes_2024_2025.18649 does not exist in GTFS data stops.txt
  • vehicle_id 107 stop_id 2780 does not exist in GTFS data stops.txt

All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 E015 2 erreurs

All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt

Exemples d'erreurs
  • vehicle_id 113 stop_id 3369 does not have location_type=0 in GTFS stops.txt
  • vehicle_id 308 stop_id 3371 does not have location_type=0 in GTFS stops.txt

Vehicle position outside agency coverage area E028 4 erreurs

The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.

Exemples d'erreurs
  • vehicle.id 218 at (47.794586,-2.554899) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 364 at (47.784615,-2.693603) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 95 at (47.78063,-2.839512) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 252 at (47.893425,-2.837864) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Vehicle position far from trip shape E029 3 erreurs

The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.

Exemples d'erreurs
  • vehicle.id 334 trip_id 2-5586944020 at (47.6642,-2.754557) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 342 trip_id 2-286457862 at (47.525173,-2.765963) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 306 trip_id 2-251854853 at (47.653465,-2.734341) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Avertissements

timestamp not populated W001 3 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • vehicle_id 359 does not have a timestamp
  • vehicle_id 44 does not have a timestamp
  • vehicle_id 63 does not have a timestamp
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 123 1 fois (100 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 95 1 fois (100 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 93 1 fois (100 % des validations)
E015 All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt 2 1 fois (100 % des validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 4 1 fois (100 % des validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 3 1 fois (100 % des validations)
W001 Timestamps should be populated for all elements 3 1 fois (100 % des validations)

Contenu du flux GTFS-RT

Impossible de décoder le flux GTFS-RT

Le flux GTFS-RT doit être accessible en HTTP, sans authentification et utiliser le format Protobuf.