Détails de la ressource

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

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

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

❌45 erreurs

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 18/11/2026 à 08h07 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 12 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 48 trip_id 1003001 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 71 trip_id 30 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 157 trip_id 275 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 155 trip_id 46 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 49 trip_id 1004001 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 12 erreurs

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

Exemples d'erreurs
  • vehicle_id 48 route_id 1003 does not exist in the GTFS data routes.txt
  • vehicle_id 71 route_id 13 does not exist in the GTFS data routes.txt
  • vehicle_id 157 route_id 28 does not exist in the GTFS data routes.txt
  • vehicle_id 155 route_id 17 does not exist in the GTFS data routes.txt
  • vehicle_id 49 route_id 1004 does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs
  • vehicle_id 48 stop_id 10000 does not exist in GTFS data stops.txt
  • vehicle_id 71 stop_id E4119 does not exist in GTFS data stops.txt
  • vehicle_id 157 stop_id E4297 does not exist in GTFS data stops.txt
  • vehicle_id 155 stop_id E49 does not exist in GTFS data stops.txt
  • vehicle_id 49 stop_id 10000 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 71 at (48.56799,-3.343221) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 155 at (48.44212,-3.203206) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 156 at (48.47587,-3.145722) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 274 at (48.39805,-3.421127) 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.461205,-3.269606) 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 112 18 fois (60 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 112 18 fois (60 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 112 18 fois (60 % 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. 83 17 fois (57 % des validations)
W001 Timestamps should be populated for all elements 19 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)
E052 Each vehicle should have a unique ID 1 1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 18/11/2026 à 20h23 Europe/Paris.

vehicle_positions (1) 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 18/11/2026 à 20h23 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "203037", "vehicle": { "currentStopSequence": 29, "position": { "bearing": 198.0, "latitude": 48.583621978759766, "longitude": -3.1417129039764404, "speed": 15.0 }, "stopId": "LA_POTERIE", "timestamp": "1795029737", "trip": { "directionId": 1, "routeId": "A", "scheduleRelationship": "SCHEDULED", "startDate": "20261118", "startTime": "19:42:00", "tripId": "A_A_LMWJV_036" }, "vehicle": { "id": "5", "label": "605", "licensePlate": "ET-258-YG" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1795029805" } }