Jeu de données ouvert gtfs-rt - Réseau CVLmobilité - information temps réel ligne A (trip updates) pour Réseau urbain CVL Mobilité

Détails de la ressource

Nom du fichier : Réseau CVLmobilité - information temps réel ligne A (trip updates)

Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau urbain CVL 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

❌34 erreurs, 10 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 15/12/2025 à 08h14 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 5 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

trip_id L_2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id L_1 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id L_3 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id L_8 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id L_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 5 erreurs

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

Exemples d'erreurs

route_id LMaV does not exist in the GTFS data routes.txt
route_id LMaV does not exist in the GTFS data routes.txt
route_id LMaV does not exist in the GTFS data routes.txt
route_id LMaV does not exist in the GTFS data routes.txt
route_id LMaV does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs

trip_id L_2 stop_id DEPOT_ARCHAMBAULT_LAROCHE does not exist in GTFS data stops.txt
trip_id L_2 stop_id ZONE does not exist in GTFS data stops.txt
trip_id L_2 stop_id DEPOT_ARCHAMBAULT_LAROCHE does not exist in GTFS data stops.txt
trip_id L_1 stop_id DEPOT_ARCHAMBAULT_LAROCHE does not exist in GTFS data stops.txt
trip_id L_1 stop_id ZONE does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 4 erreurs

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Exemples d'erreurs

trip_id L_1 stop_sequence 2 arrival_time 06:01:02 (1765774862) is less than previous stop arrival_time 08:13:12 (1765782792) - times must increase between two sequential stops
trip_id L_1 stop_sequence 2 arrival_time 06:01:02 (1765774862) is less than previous stop departure_time 08:13:12 (1765782792) - times must increase between two sequential stops
trip_id L_3 stop_sequence 2 arrival_time 06:12:32 (1765775552) is less than previous stop arrival_time 08:13:45 (1765782825) - times must increase between two sequential stops
trip_id L_3 stop_sequence 2 arrival_time 06:12:32 (1765775552) is less than previous stop departure_time 08:13:45 (1765782825) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 5 erreurs

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

Exemples d'erreurs

GTFS-rt trip_id SIT01_A4 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
GTFS-rt trip_id SIT01_R4 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
GTFS-rt trip_id SIT01_A5 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
GTFS-rt trip_id SIT01_R5 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match
GTFS-rt trip_id SIT01_R6 trip.direction_id is 0 but GTFS trip.direction_id is null - direction_id does not match

Avertissements

timestamp not populated W001 10 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id L_2 does not have a timestamp
trip_id L_1 does not have a timestamp
trip_id L_3 does not have a timestamp
trip_id L_8 does not have a timestamp
trip_id L_9 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
E024	GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt	134	25 fois (83 % des validations)
W001	Timestamps should be populated for all elements	242	25 fois (83 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	108	24 fois (80 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	108	24 fois (80 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	324	24 fois (80 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	96	21 fois (70 % des validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	2	2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 15/12/2025 à 21h33 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (0)

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

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 15/12/2025 à 21h33 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "entity": [
    {
      "id": "18906",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "departure": {
              "delay": -3503,
              "time": "1765806097"
            },
            "stopId": "DEPOT_ARCHAMBAULT_LAROCHE",
            "stopSequence": 0
          },
          {
            "arrival": {
              "delay": 9217,
              "time": "1765830817"
            },
            "departure": {
              "delay": 9217,
              "time": "1765830817"
            },
            "stopId": "ZONE",
            "stopSequence": 1
          },
          {
            "arrival": {
              "delay": -7314,
              "time": "1765828086"
            },
            "stopId": "DEPOT_ARCHAMBAULT_LAROCHE",
            "stopSequence": 2
          }
        ],
        "trip": {
          "directionId": 0,
          "routeId": "LMaV",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20251215",
          "startTime": "15:40:00",
          "tripId": "L_5"
        },
        "vehicle": {
          "id": "60",
          "label": "GX 015 MH",
          "licensePlate": "GX 015 MH"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1765830818"
  }
}