Détails de la ressource
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.
Ressources associées
Horaires théoriques des lignes régulières et secondaires du réseau Cap Cotentin
Disponibilité au téléchargement
En savoir plus
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
❌82 erreurs, 118 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 15/04/2026 à 09h07 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 7 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 3758176-2025_H-Mult_LaM-L-Ma-Me-00-1110101 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 61289ff756b38782f6019ab1 trip_id 3758050-2025_H-Mult_LaM-L-Ma-Me-00-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3758050-2025_H-Mult_LaM-L-Ma-Me-00-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3758176-2025_H-Mult_LaM-L-Ma-Me-00-1110101 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3763955-2025_H-Mult_LaM-L-Ma-Me-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 1 erreur
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 3757967-2025_H-Mult_LaM-L-Ma-Me-00-0010000 stop_id SVCOL1 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 12 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 3758078-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 11 arrival_time 07:14:40 (1776230080) is less than previous stop arrival_time 07:17:18 (1776230238) - times must increase between two sequential stops
- trip_id 3758078-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 11 arrival_time 07:14:40 (1776230080) is less than previous stop departure_time 07:17:53 (1776230273) - times must increase between two sequential stops
- trip_id 3758078-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 11 departure_time 07:14:40 (1776230080) is less than previous stop departure_time 07:17:53 (1776230273) - times must increase between two sequential stops
- trip_id 3758078-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 11 departure_time 07:14:40 (1776230080) is less than previous stop arrival_time 07:17:18 (1776230238) - times must increase between two sequential stops
- trip_id 3757967-2025_H-Mult_LaM-L-Ma-Me-00-0010000 stop_sequence 34 arrival_time 07:22:50 (1776230570) is less than previous stop arrival_time 07:31:16 (1776231076) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 59 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 3759049-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 10 doesn't have arrival or departure
- trip_id 3759049-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 11 doesn't have arrival or departure
- trip_id 3759049-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 12 doesn't have arrival or departure
- trip_id 3759039-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 10 doesn't have arrival or departure
- trip_id 3759039-2025_H-Mult_LaM-L-Ma-Me-00 stop_sequence 11 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 erreur
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_LaM-L-Ma-Me-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 2 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 3758176-2025_H-Mult_LaM-L-Ma-Me-00-1110101 and vehicle_id 61289ff756b38782f6019df0 pairing in VehiclePositions does not match trip_id 3758175-2025_H-Mult_LaM-L-Ma-Me-00-1110100 and vehicle_id 61289ff756b38782f6019df0 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 3758050-2025_H-Mult_LaM-L-Ma-Me-00-1111100 and vehicle_id 61289ff756b38782f6019ab1 pairing in VehiclePositions does not match trip_id 3758087-2025_H-Mult_LaM-L-Ma-Me-00 and vehicle_id 61289ff756b38782f6019ab1 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 118 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 3745391-2025_H-Mult_LaM-L-Ma-Me-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3758087-2025_H-Mult_LaM-L-Ma-Me-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3758503-2025_H-Mult_LaM-L-Ma-Me-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3758655-2025_H-Mult_LaM-L-Ma-Me-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3748506-2025_H-Mult_LaM-L-Ma-Me-00 is in TripUpdates but not in VehiclePositions feed
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 | 30 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 | 2 632 | 30 fois (100 % 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 | 659 | 27 fois (90 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 64 | 27 fois (90 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 257 | 25 fois (83 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 226 | 25 fois (83 % 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 | 17 | 10 fois (33 % 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. | 1 | 1 fois (3 % 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.