transport.data.gouv.fr transport.data.gouv.fr

Détails de la ressource

Nom du fichier : Horaires en temps réel des lignes régulières du réseau Cap Cotentin
Format : gtfs-rt
Télécharger

Horaires en temps réel des lignes urbaines et intercommunales du réseau de mobilité Cap Cotentin de la Communauté d’agglomération du Cotentin

Horaires en temps réel du réseau Cap Cotentin au format GTFS-RT comprenant :

  • Les lignes urbaines 1 à 6
  • Les lignes intercommunales A à G

Cette ressource fait partie du jeu de données Réseau urbain Cap Cotentin.

Horaires théoriques des lignes régulières et secondaires du réseau Cap Cotentin

Fichier GTFS associé

Disponibilité au téléchargement

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

❌408 erreurs, 74 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 18/02/2025 à 08h11 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 160 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 61289ff756b38782f6019979 trip_id 3723910-2024_H-Mult_LaM-L-Ma-Me-02 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 667ecec3b43ef98706f523b7 trip_id 3694497-2024_H-Mult_LaM-L-Ma-Me-02 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 6687ead37478ea9c00da355d trip_id 3694559-2024_H-Mult_LaM-L-Ma-Me-02 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61289ff756b38782f6019ce5 trip_id 3698118-2024_H-Mult_LaM-L-Ma-Me-02 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61289ff756b38782f601a1d5 trip_id 3726999-2024_H-Mult_LaM-L-Ma-Me-02 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Sequential stop_time_update times are not increasing E022 179 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 3719715-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 20 arrival_time 08:07:41 (1739862461) is less than previous stop departure_time 08:09:00 (1739862540) - times must increase between two sequential stops
  • trip_id 3692456-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 18 arrival_time 08:43:00 (1739864580) is equal to previous stop arrival_time 08:43:00 (1739864580) - times must increase between two sequential stops
  • trip_id 3692456-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 18 arrival_time 08:43:00 (1739864580) is equal to previous stop departure_time 08:43:00 (1739864580) - times must increase between two sequential stops
  • trip_id 3692456-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 18 departure_time 08:43:00 (1739864580) is equal to previous stop departure_time 08:43:00 (1739864580) - times must increase between two sequential stops
  • trip_id 3692456-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 18 departure_time 08:43:00 (1739864580) is equal to previous stop arrival_time 08:43:00 (1739864580) - times must increase between two sequential stops

stop_time_update doesn't have arrival or departure E043 51 erreurs

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Exemples d'erreurs
  • trip_id 3719715-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 3 doesn't have arrival or departure
  • trip_id 3719715-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 14 doesn't have arrival or departure
  • trip_id 3723175-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 15 doesn't have arrival or departure
  • trip_id 3723909-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 15 doesn't have arrival or departure
  • trip_id 3723909-2024_H-Mult_LaM-L-Ma-Me-02 stop_sequence 17 doesn't have arrival or departure

VehiclePosition and TripUpdate ID pairing mismatch E047 18 erreurs

If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.

Exemples d'erreurs
  • trip_id 3698166-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 63fc89146a6784155006f37c pairing in VehiclePositions does not match trip_id 3698113-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 63fc89146a6784155006f37c pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
  • trip_id 3723165-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 61289ff756b38782f6019dc5 pairing in VehiclePositions does not match trip_id 3723163-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 61289ff756b38782f6019dc5 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
  • trip_id 3697996-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 61289ff756b38782f6019954 pairing in VehiclePositions does not match trip_id 3697932-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 61289ff756b38782f6019954 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
  • trip_id 3697995-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 61d417c61ab3d1c49040c8b4 pairing in VehiclePositions does not match trip_id 3697931-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 61d417c61ab3d1c49040c8b4 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
  • trip_id 3694497-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 667ecec3b43ef98706f523b7 pairing in VehiclePositions does not match trip_id 3694495-2024_H-Mult_LaM-L-Ma-Me-02 and vehicle_id 667ecec3b43ef98706f523b7 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match

Avertissements

ID in one feed missing from the other W003 74 erreurs

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Exemples d'erreurs
  • trip_id 3697990-2024_H-Mult_LaM-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3692454-2024_H-Mult_LaM-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3726522-2024_H-Mult_LaM-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3697932-2024_H-Mult_LaM-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3698115-2024_H-Mult_LaM-L-Ma-Me-02 is in TripUpdates but not in VehiclePositions feed
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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1 264 9 fois (100 % des validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 880 9 fois (100 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 822 8 fois (89 % des validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 6 145 8 fois (89 % des validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 123 7 fois (78 % 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. 4 3 fois (33 % des validations)

Contenu du flux GTFS-RT

Impossible de décoder le flux GTFS-RT

Le flux GTFS-RT doit être accessible en HTTP, sans authentification et utiliser le format Protobuf.