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
❌204 erreurs, 78 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 12/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 8 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 61289ff756b38782f601a12c trip_id 3758382-2025_H-Mult_J&V-Jeu-Ven-00-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 6321dae2705a3a871c21a933 trip_id 3757937-2025_H-Mult_J&V-Jeu-Ven-00-1101110 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3758247-2025_H-Mult_J&V-Jeu-Ven-00-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3757937-2025_H-Mult_J&V-Jeu-Ven-00-1101110 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3758405-2025_H-Mult_J&V-Jeu-Ven-00-1111100 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 2 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 3757937-2025_H-Mult_J&V-Jeu-Ven-00-1101110 stop_id SVCOL1 does not exist in GTFS data stops.txt
- trip_id 3757936-2025_H-Mult_J&V-Jeu-Ven-00-1101110 stop_id SVCOL1 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 162 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_J&V-Jeu-Ven-00 stop_sequence 13 arrival_time 08:07:10 (1773299230) is equal to previous stop arrival_time 08:07:10 (1773299230) - times must increase between two sequential stops
- trip_id 3747841-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 13 arrival_time 08:07:10 (1773299230) is equal to previous stop departure_time 08:07:10 (1773299230) - times must increase between two sequential stops
- trip_id 3747841-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 13 departure_time 08:07:10 (1773299230) is equal to previous stop departure_time 08:07:10 (1773299230) - times must increase between two sequential stops
- trip_id 3747841-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 13 departure_time 08:07:10 (1773299230) is equal to previous stop arrival_time 08:07:10 (1773299230) - times must increase between two sequential stops
- trip_id 3747841-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 16 arrival_time 08:09:10 (1773299350) is equal to previous stop arrival_time 08:09:10 (1773299350) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 30 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 3745651-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 1 doesn't have arrival or departure
- trip_id 3745651-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 2 doesn't have arrival or departure
- trip_id 3745651-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 3 doesn't have arrival or departure
- trip_id 3745651-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 4 doesn't have arrival or departure
- trip_id 3745651-2025_H-Mult_J&V-Jeu-Ven-00 stop_sequence 5 doesn't have arrival or departure
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
- vehicle_id 61289ff756b38782f601a19e and trip_id 3745719-2025_H-Mult_J&V-Jeu-Ven-00 pairing in TripUpdates does not match vehicle_id 61289ff756b38782f601986f and trip_id 3745719-2025_H-Mult_J&V-Jeu-Ven-00 pairing in VehiclePositions feed - ID pairing between feeds should match
- trip_id 3758057-2025_H-Mult_J&V-Jeu-Ven-00 and vehicle_id 61289ff756b38782f60195e4 pairing in VehiclePositions does not match trip_id 3757936-2025_H-Mult_J&V-Jeu-Ven-00-1101110 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 78 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 3746135-2025_H-Mult_J&V-Jeu-Ven-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3748507-2025_H-Mult_J&V-Jeu-Ven-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3745650-2025_H-Mult_J&V-Jeu-Ven-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3758448-2025_H-Mult_J&V-Jeu-Ven-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3758404-2025_H-Mult_J&V-Jeu-Ven-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 | 87 | 30 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. | 4 724 | 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 047 | 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 | 490 | 29 fois (97 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 2 021 | 28 fois (93 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 295 | 28 fois (93 % 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. | 54 | 14 fois (47 % 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 | 13 | 5 fois (17 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 13/03/2026 à 03h01 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_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 13/03/2026 à 03h01 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1773367266"
}
}