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

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

❌26 erreurs, 2 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 12/11/2026 à 08h22 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 7 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 223 trip_id 55 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 49 trip_id 1003001 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 71 trip_id 13 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 157 trip_id 103 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 274 trip_id 9 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 7 erreurs

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

Exemples d'erreurs
  • vehicle_id 223 route_id 20 does not exist in the GTFS data routes.txt
  • vehicle_id 49 route_id 1003 does not exist in the GTFS data routes.txt
  • vehicle_id 71 route_id 5 does not exist in the GTFS data routes.txt
  • vehicle_id 157 route_id 35 does not exist in the GTFS data routes.txt
  • vehicle_id 274 route_id 3 does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs
  • vehicle_id 223 stop_id E435 does not exist in GTFS data stops.txt
  • vehicle_id 49 stop_id 10000 does not exist in GTFS data stops.txt
  • vehicle_id 71 stop_id E4118 does not exist in GTFS data stops.txt
  • vehicle_id 157 stop_id E4309 does not exist in GTFS data stops.txt
  • vehicle_id 274 stop_id E424 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 5 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 223 at (48.40601,-3.430176) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 71 at (48.537178,-3.35802) 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.405273,-3.427149) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 51 at (48.405823,-3.429976) 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.474792,-3.304851) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Avertissements

timestamp not populated W001 2 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • vehicle_id 2 does not have a timestamp
  • vehicle_id 4 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 92 18 fois (60 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 92 18 fois (60 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 92 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. 57 17 fois (57 % des validations)
W001 Timestamps should be populated for all elements 24 15 fois (50 % des validations)
E052 Each vehicle should have a unique ID 2 2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

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

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

{ "entity": [ { "id": "202206", "vehicle": { "currentStopSequence": 28, "position": { "bearing": 231.0, "latitude": 48.568538665771484, "longitude": -3.152925968170166, "speed": 2.5 }, "stopId": "CASTEL_PIC", "timestamp": "1794511166", "trip": { "directionId": 0, "routeId": "B", "scheduleRelationship": "SCHEDULED", "startDate": "20261112", "startTime": "19:42:00", "tripId": "B_B_LMWJV_018" }, "vehicle": { "id": "4", "label": "604", "licensePlate": "ET-262-YG" } } }, { "id": "202188", "vehicle": { "currentStopSequence": 29, "position": { "bearing": 149.0, "latitude": 48.55935287475586, "longitude": -3.125462055206299, "speed": 7.777777671813965 }, "stopId": "LA_POTERIE", "timestamp": "1794511204", "trip": { "directionId": 1, "routeId": "A", "scheduleRelationship": "SCHEDULED", "startDate": "20261112", "startTime": "19:42:00", "tripId": "A_A_LMWJV_036" }, "vehicle": { "id": "264", "label": "614", "licensePlate": "FZ 087 VG" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1794511263" } }