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

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

  • VehiclePosition

Cette ressource fait partie du jeu de données Réseau urbain et scolaire Guingamp-Paimpol Mobilité.

Disponibilité au téléchargement

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

❌39 erreurs

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 11/03/2025 à 08h11 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 10 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 150 trip_id 1-721747969 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 153 trip_id 1-621543425 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 161 trip_id 1-755367937 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 22 trip_id 1-638189569 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 65 trip_id 1-453312513 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 10 erreurs

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

Exemples d'erreurs
  • vehicle_id 150 route_id 43 does not exist in the GTFS data routes.txt
  • vehicle_id 153 route_id 37 does not exist in the GTFS data routes.txt
  • vehicle_id 161 route_id 45 does not exist in the GTFS data routes.txt
  • vehicle_id 22 route_id 38 does not exist in the GTFS data routes.txt
  • vehicle_id 65 route_id 27 does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs
  • vehicle_id 150 stop_id 17205 does not exist in GTFS data stops.txt
  • vehicle_id 153 stop_id 17223 does not exist in GTFS data stops.txt
  • vehicle_id 161 stop_id 17205 does not exist in GTFS data stops.txt
  • vehicle_id 22 stop_id 17457 does not exist in GTFS data stops.txt
  • vehicle_id 65 stop_id 17453 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 9 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 150 at (48.403915,-3.423621) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 153 at (48.573742,-3.353342) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 161 at (48.36683,-3.44045) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 22 at (48.46435,-3.242812) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 65 at (48.463715,-3.268734) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
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 109 12 fois (40 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 109 12 fois (40 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 106 12 fois (40 % 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. 93 12 fois (40 % 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. 1 1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 11/03/2025 à 10h00 Europe/Paris.

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

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

vehicle_positions

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 11/03/2025 à 10h00 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "143754", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 9, "position": { "latitude": 48.56218338012695, "longitude": -3.163641929626465 }, "stop_id": "6049", "timestamp": "1741683610", "trip": { "direction_id": 1, "route_id": "2", "start_date": "20250311", "start_time": "09:48:00", "trip_id": "15-33816578" }, "vehicle": { "id": "4", "label": "D19004", "license_plate": "ET-262-YG" } } }, { "id": "143824", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 3, "position": { "bearing": 51.0, "latitude": 48.77720260620117, "longitude": -3.046504020690918 }, "stop_id": "7558", "timestamp": "1741683576", "trip": { "route_id": "59", "start_date": "20250311", "start_time": "09:54:00", "trip_id": "15-990707715" }, "vehicle": { "id": "58", "label": "D19015", "license_plate": "GE-394-YD" } } }, { "id": "143755", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 6, "position": { "bearing": 173.0, "latitude": 48.54926300048828, "longitude": -3.160473108291626, "speed": 10.277777671813965 }, "stop_id": "16223", "timestamp": "1741683595", "trip": { "direction_id": 1, "route_id": "4", "start_date": "20250311", "start_time": "09:52:00", "trip_id": "15-67633153" }, "vehicle": { "id": "6", "label": "D19006", "license_plate": "ET-254-YG" } } }, { "id": "143753", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 14, "position": { "bearing": 271.0, "latitude": 48.568599700927734, "longitude": -3.1452829837799072, "speed": 4.44444465637207 }, "stop_id": "17082", "timestamp": "1741683544", "trip": { "direction_id": 1, "route_id": "1", "start_date": "20250311", "start_time": "09:45:00", "trip_id": "15-17039362" }, "vehicle": { "id": "5", "label": "D19005", "license_plate": "ET-258-YG" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1741683622" } }