Jeu de données ouvert gtfs-rt - Données en temps réel au format GTFS-RT (VehiclePosition) pour Réseau urbain et scolaire Guingamp-Paimpol Mobilité - CA Guingamp-Paimpol Agglomération de l'Armor à l'Argoat

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

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 21/11/2024 à 08h02 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 33 trip_id 1-923074561 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 51 trip_id 1-705363969 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 71 trip_id 1-604766209 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
vehicle_id 60 trip_id 1-689111041 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 33 route_id 55 does not exist in the GTFS data routes.txt
vehicle_id 51 route_id 42 does not exist in the GTFS data routes.txt
vehicle_id 71 route_id 36 does not exist in the GTFS data routes.txt
vehicle_id 65 route_id 27 does not exist in the GTFS data routes.txt
vehicle_id 60 route_id 41 does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs

vehicle_id 51 stop_id 17449 does not exist in GTFS data stops.txt
vehicle_id 71 stop_id 17139 does not exist in GTFS data stops.txt
vehicle_id 65 stop_id 17609 does not exist in GTFS data stops.txt
vehicle_id 60 stop_id 18201 does not exist in GTFS data stops.txt
vehicle_id 162 stop_id 17878 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 51 at (48.40961,-3.53637) 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.55852,-3.332605) 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.46141,-3.266376) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 60 at (48.465706,-3.426075) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 162 at (48.40977,-3.378779) 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 1 erreur

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 6 trip_id 25-67371017 at (48.548656,-3.179862) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

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	106	11 fois (37 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	106	11 fois (37 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	100	11 fois (37 % 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.	86	11 fois (37 % 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.	2	2 fois (7 % des validations)
E052	Each vehicle should have a unique ID	1	1 fois (3 % des validations)
W001	Timestamps should be populated for all elements	1	1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 21/11/2024 à 13h15 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 21/11/2024 à 13h15 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "entity": [
    {
      "id": "133932",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 25,
        "position": {
          "bearing": 88.0,
          "latitude": 48.57484436035156,
          "longitude": -3.143543004989624,
          "speed": 7.777777671813965
        },
        "stop_id": "10888",
        "timestamp": "1732191268",
        "trip": {
          "direction_id": 1,
          "route_id": "2",
          "start_date": "20241121",
          "start_time": "12:38:00",
          "trip_id": "25-33816598"
        },
        "vehicle": {
          "id": "5",
          "label": "D19005",
          "license_plate": "ET-258-YG"
        }
      }
    },
    {
      "id": "133933",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 19,
        "position": {
          "bearing": 20.0,
          "latitude": 48.56694030761719,
          "longitude": -3.1510419845581055,
          "speed": 10.277777671813965
        },
        "stop_id": "7550",
        "timestamp": "1732191305",
        "trip": {
          "direction_id": 1,
          "route_id": "4",
          "start_date": "20241121",
          "start_time": "12:42:00",
          "trip_id": "25-67633165"
        },
        "vehicle": {
          "id": "6",
          "label": "D19006",
          "license_plate": "ET-254-YG"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1732191322"
  }
}