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

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.

Disponibilité au téléchargement

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

191 erreurs, 77 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 04/03/2026 à 08h07 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 61289ff756b38782f6019df0 trip_id 3763955-2025_H-Mult_Me-Mercredi-00-1110100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61289ff756b38782f601a12c trip_id 3758382-2025_H-Mult_Me-Mercredi-00-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 61289ff756b38782f6019f96 trip_id 3758115-2025_H-Mult_Me-Mercredi-00-1110100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3758175-2025_H-Mult_Me-Mercredi-00-1110100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 3763955-2025_H-Mult_Me-Mercredi-00-1110100 does not exist in the GTFS data and does not have schedule_relationship of ADDED

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

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

Exemples d'erreurs
  • trip_id 3757967-2025_H-Mult_Me-Mercredi-00-0010000 stop_id SVCOL1 does not exist in GTFS data stops.txt
  • trip_id 3757973-2025_H-Mult_Me-Mercredi-00-0010000 stop_id SVCOL2 does not exist in GTFS data stops.txt
  • trip_id 3757972-2025_H-Mult_Me-Mercredi-00-0010000 stop_id SVCOL2 does not exist in GTFS data stops.txt
  • trip_id 3757968-2025_H-Mult_Me-Mercredi-00-0010000 stop_id SVCOL1 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 166 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 3747841-2025_H-Mult_Me-Mercredi-00 stop_sequence 16 arrival_time 08:08:20 (1772608100) is equal to previous stop arrival_time 08:08:20 (1772608100) - times must increase between two sequential stops
  • trip_id 3747841-2025_H-Mult_Me-Mercredi-00 stop_sequence 16 arrival_time 08:08:20 (1772608100) is equal to previous stop departure_time 08:08:20 (1772608100) - times must increase between two sequential stops
  • trip_id 3747841-2025_H-Mult_Me-Mercredi-00 stop_sequence 16 departure_time 08:08:20 (1772608100) is equal to previous stop departure_time 08:08:20 (1772608100) - times must increase between two sequential stops
  • trip_id 3747841-2025_H-Mult_Me-Mercredi-00 stop_sequence 16 departure_time 08:08:20 (1772608100) is equal to previous stop arrival_time 08:08:20 (1772608100) - times must increase between two sequential stops
  • trip_id 3746161-2025_H-Mult_Me-Mercredi-00 stop_sequence 9 arrival_time 08:13:30 (1772608410) is equal to previous stop arrival_time 08:13:30 (1772608410) - times must increase between two sequential stops

stop_time_update doesn't have arrival or departure E043 6 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 3748506-2025_H-Mult_Me-Mercredi-00 stop_sequence 1 doesn't have arrival or departure
  • trip_id 3748506-2025_H-Mult_Me-Mercredi-00 stop_sequence 2 doesn't have arrival or departure
  • trip_id 3748506-2025_H-Mult_Me-Mercredi-00 stop_sequence 3 doesn't have arrival or departure
  • trip_id 3747835-2025_H-Mult_Me-Mercredi-00 stop_sequence 1 doesn't have arrival or departure
  • trip_id 3747835-2025_H-Mult_Me-Mercredi-00 stop_sequence 2 doesn't have arrival or departure

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 4 erreurs

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Exemples d'erreurs
  • GTFS-rt trip_id 3757967-2025_H-Mult_Me-Mercredi-00-0010000 stop_sequence 8 has stop_id SVCOL1 but GTFS stop_sequence 8 has stop_id SVPBI1 - stop_ids should be the same
  • GTFS-rt trip_id 3757973-2025_H-Mult_Me-Mercredi-00-0010000 stop_sequence 24 has stop_id SVCOL2 but GTFS stop_sequence 24 has stop_id SVPBI2 - stop_ids should be the same
  • GTFS-rt trip_id 3757972-2025_H-Mult_Me-Mercredi-00-0010000 stop_sequence 24 has stop_id SVCOL2 but GTFS stop_sequence 24 has stop_id SVPBI2 - stop_ids should be the same
  • GTFS-rt trip_id 3757968-2025_H-Mult_Me-Mercredi-00-0010000 stop_sequence 8 has stop_id SVCOL1 but GTFS stop_sequence 8 has stop_id SVPBI1 - stop_ids should be the same

VehiclePosition and TripUpdate ID pairing mismatch E047 1 erreur

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 3757973-2025_H-Mult_Me-Mercredi-00-0010000 and vehicle_id 61289ff756b38782f60195e4 pairing in VehiclePositions does not match trip_id 3758048-2025_H-Mult_Me-Mercredi-00-1111100 and vehicle_id 61289ff756b38782f60195e4 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 77 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 3748425-2025_H-Mult_Me-Mercredi-00 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3747501-2025_H-Mult_Me-Mercredi-00 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3745196-2025_H-Mult_Me-Mercredi-00 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3758056-2025_H-Mult_Me-Mercredi-00 is in TripUpdates but not in VehiclePositions feed
  • trip_id 3746205-2025_H-Mult_Me-Mercredi-00 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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 63 22 fois (100 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 3 478 22 fois (100 % des validations)
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 280 22 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 1 504 22 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 1 933 21 fois (95 % 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 360 21 fois (95 % 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. 51 12 fois (55 % des validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 8 3 fois (14 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 05/03/2026 à 00h15 Europe/Paris.

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

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

trip_updates vehicle_positions

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 05/03/2026 à 00h15 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1772666152" } }