Jeu de données ouvert gtfs-rt - Base de données multimodale de la position des véhicules des réseaux de transport public normands en temps réel pour Agrégat de réseaux urbains et interurbains de Normandie

Détails de la ressource

Nom du fichier : Base de données multimodale de la position des véhicules des réseaux de transport public normands en temps réel

Format : gtfs-rt

Télécharger

La base de données multimodale présente de manière agrégée la position des véhicules des réseaux de transport public normands en temps réel.

Cette ressource fait partie du jeu de données Agrégat de réseaux urbains et interurbains de Normandie.

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

❌142 erreurs, 106 avertissements

Les shapes présentes dans le GTFS ont été ignorées, certaines règles de validation n'ont pas été vérifiées.

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 23/01/2025 à 08h08 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 15 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 zenbus:Vehicle:4785451572396032:LOC trip_id ATOUMOD036:ServiceJourney:5812927287263232x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id zenbus:Vehicle:5972619036721152:LOC trip_id ATOUMOD036:ServiceJourney:4826533605670912x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 0200001002FF7E16 trip_id ATOUMOD005:ServiceJourney:103:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id zenbus:Vehicle:5780902635372544:LOC trip_id ATOUMOD036:ServiceJourney:5241004140527616x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id zenbus:Vehicle:4845661980721152:LOC trip_id ATOUMOD036:ServiceJourney:6432145456234496x0:LOC 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 14 erreurs

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

Exemples d'erreurs

vehicle_id zenbus:Vehicle:4785451572396032:LOC route_id ATOUMOD036:Line:4895131028160512:LOC does not exist in the GTFS data routes.txt
vehicle_id zenbus:Vehicle:5972619036721152:LOC route_id ATOUMOD036:Line:6482477221675008:LOC does not exist in the GTFS data routes.txt
vehicle_id 0200001002FF7E16 route_id ATOUMOD005:Line:500:LOC does not exist in the GTFS data routes.txt
vehicle_id zenbus:Vehicle:5780902635372544:LOC route_id ATOUMOD036:Line:6704313154928640:LOC does not exist in the GTFS data routes.txt
vehicle_id zenbus:Vehicle:4845661980721152:LOC route_id ATOUMOD036:Line:5515601163321344:LOC does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs

vehicle_id zenbus:Vehicle:5972619036721152:LOC stop_id FR:14654:ZE:5916523743936512:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:4845661980721152:LOC stop_id FR:14371:ZE:6688429493452800:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:5473118584832000:LOC stop_id FR:14193:ZE:4795773402218496:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:5186724806262784:LOC stop_id FR:14654:ZE:4819455851888640:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:4840051746799616:LOC stop_id FR:14478:ZE:5875409095753728:ATOUMOD036 does not exist in GTFS data stops.txt

trip direction_id does not match GTFS data E024 91 erreurs

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Exemples d'erreurs

GTFS-rt vehicle_id 61d417d498c0fb4378b18e65 trip_id ATOUMOD035:ServiceJourney:3664298x2024xHxMultxJxVxJeuxVenx02:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt vehicle_id zenbus:Vehicle:817050001:LOC trip_id ATOUMOD105:ServiceJourney:5110781483941888x1:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt vehicle_id 6773fc44aac40fd87f1346d9 trip_id ATOUMOD041:ServiceJourney:5:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt vehicle_id 61289ff756b38782f6019954 trip_id ATOUMOD035:ServiceJourney:3663601x2024xHxMultxJxVxJeuxVenx02:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt vehicle_id 667ecea392c99b62cc677055 trip_id ATOUMOD035:ServiceJourney:3662765x2024xHxMultxJxVxJeuxVenx02:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match

Vehicle position outside agency coverage area E028 3 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 428 at (27.14097,-3.404561) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
vehicle.id 3137 at (27.14097,-3.404561) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
vehicle.id 434 at (27.14097,-3.404561) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area

vehicle.id is not unique E052 11 erreurs

Each vehicle should have a unique ID

Exemples d'erreurs

entity ID VM:ATOUMOD105:ServiceJourney:5117712890068992x0:LOC has vehicle.id zenbus:Vehicle:769100145:LOC which is used by more than one vehicle in the feed
entity ID VM:ATOUMOD036:ServiceJourney:5253792405651456x1:LOC has vehicle.id zenbus:Vehicle:4957008051568640:LOC which is used by more than one vehicle in the feed
entity ID VM:ATOUMOD036:ServiceJourney:4767410897813504x0:LOC has vehicle.id zenbus:Vehicle:4790775234691072:LOC which is used by more than one vehicle in the feed
entity ID VM:ATOUMOD036:ServiceJourney:5721494932946944x0:LOC has vehicle.id zenbus:Vehicle:6616704076480512:LOC which is used by more than one vehicle in the feed
entity ID VM:ATOUMOD036:ServiceJourney:4644982938927104x2:LOC has vehicle.id zenbus:Vehicle:506240001:LOC which is used by more than one vehicle in the feed

Avertissements

schedule_relationship not populated W009 106 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id ATOUMOD035:ServiceJourney:3664298x2024xHxMultxJxVxJeuxVenx02:LOC does not have a schedule_relationship
trip_id ATOUMOD105:ServiceJourney:5110781483941888x1:LOC does not have a schedule_relationship
trip_id ATOUMOD041:ServiceJourney:5:LOC does not have a schedule_relationship
trip_id ATOUMOD035:ServiceJourney:3663601x2024xHxMultxJxVxJeuxVenx02:LOC does not have a schedule_relationship
trip_id ATOUMOD035:ServiceJourney:3662765x2024xHxMultxJxVxJeuxVenx02:LOC does not have a schedule_relationship

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
E024	GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt	2 270	31 fois (100 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	2 455	31 fois (100 % des validations)
E052	Each vehicle should have a unique ID	236	27 fois (87 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	181	19 fois (61 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	247	19 fois (61 % 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.	347	19 fois (61 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	58	13 fois (42 % des validations)
E035	The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt	6	2 fois (6 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 24/01/2025 à 03h54 Europe/Paris.

vehicle_positions (6) 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 24/01/2025 à 03h54 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "entity": [
    {
      "id": "VM:ATOUMOD036:ServiceJourney:4959755505238016x1:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 44,
        "position": {
          "latitude": 48.9901008605957,
          "longitude": 0.2619140148162842
        },
        "stop_id": "FR:14371:ZE:6100193725382656:ATOUMOD036",
        "timestamp": "1737655249",
        "trip": {
          "direction_id": 1,
          "route_id": "ATOUMOD036:Line:4743889022877696:LOC",
          "trip_id": "ATOUMOD036:ServiceJourney:4959755505238016x1:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:5153612286132224:LOC"
        }
      }
    },
    {
      "id": "VM:ATOUMOD036:ServiceJourney:5315089038049280x2:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 30,
        "position": {
          "latitude": 48.92647171020508,
          "longitude": 0.19978399574756622
        },
        "stop_id": "FR:61508:ZE:5120149944270848:ATOUMOD036",
        "timestamp": "1737651494",
        "trip": {
          "direction_id": 1,
          "route_id": "ATOUMOD036:Line:4841323284660224:LOC",
          "trip_id": "ATOUMOD036:ServiceJourney:5315089038049280x2:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:5161589382578176:LOC"
        }
      }
    },
    {
      "id": "VM:ATOUMOD036:ServiceJourney:5315089038049280x3:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 30,
        "position": {
          "latitude": 48.92884826660156,
          "longitude": 0.20032000541687012
        },
        "stop_id": "FR:61508:ZE:5120149944270848:ATOUMOD036",
        "timestamp": "1737652687",
        "trip": {
          "direction_id": 1,
          "route_id": "ATOUMOD036:Line:4841323284660224:LOC",
          "trip_id": "ATOUMOD036:ServiceJourney:5315089038049280x3:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:5200081617682432:LOC"
        }
      }
    },
    {
      "id": "VM:ATOUMOD105:ServiceJourney:5173281244053504x24:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 16,
        "position": {
          "latitude": 48.83766174316406,
          "longitude": -1.5466309785842896
        },
        "stop_id": "FR:50647:ZE:740100001:ATOUMOD105",
        "timestamp": "1737657200",
        "trip": {
          "direction_id": 1,
          "route_id": "ATOUMOD105:Line:350210009:LOC",
          "trip_id": "ATOUMOD105:ServiceJourney:5173281244053504x24:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:817050001:LOC"
        }
      }
    },
    {
      "id": "VM:ATOUMOD105:ServiceJourney:5192777811886080x20:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 35,
        "position": {
          "latitude": 48.8394889831543,
          "longitude": -1.5596100091934204
        },
        "stop_id": "FR:50647:ZE:5176510791024640:ATOUMOD105",
        "timestamp": "1737657581",
        "trip": {
          "direction_id": 2,
          "route_id": "ATOUMOD105:Line:348940035:LOC",
          "trip_id": "ATOUMOD105:ServiceJourney:5192777811886080x20:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:758770006:LOC"
        }
      }
    },
    {
      "id": "VM:ATOUMOD036:ServiceJourney:5315089038049280x4:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 30,
        "position": {
          "latitude": 48.931640625,
          "longitude": 0.19543300569057465
        },
        "stop_id": "FR:61508:ZE:5120149944270848:ATOUMOD036",
        "timestamp": "1737687238",
        "trip": {
          "direction_id": 1,
          "route_id": "ATOUMOD036:Line:4841323284660224:LOC",
          "trip_id": "ATOUMOD036:ServiceJourney:5315089038049280x4:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:5085860519215104:LOC"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1737687263"
  }
}