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
❌103 erreurs, 113 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 23/04/2026 à 09h04 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 61289ff756b38782f6019ab1 trip_id 3758050-2025_H-Mult_J&V-Jeu-Ven-01-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 6321dae2705a3a871c21a933 trip_id 3757952-2025_H-Mult_J&V-Jeu-Ven-01-1101110 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-01-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-01-1111100 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3757952-2025_H-Mult_J&V-Jeu-Ven-01-1101110 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 3 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-01-1101110 stop_id SVCOL1 does not exist in GTFS data stops.txt
- trip_id 3757952-2025_H-Mult_J&V-Jeu-Ven-01-1101110 stop_id SVCOL2 does not exist in GTFS data stops.txt
- trip_id 3757936-2025_H-Mult_J&V-Jeu-Ven-01-1101110 stop_id SVCOL1 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 23 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_J&V-Jeu-Ven-01 stop_sequence 14 arrival_time 07:19:30 (1776921570) is less than previous stop arrival_time 07:20:18 (1776921618) - times must increase between two sequential stops
- trip_id 3758078-2025_H-Mult_J&V-Jeu-Ven-01 stop_sequence 14 arrival_time 07:19:30 (1776921570) is less than previous stop departure_time 07:20:47 (1776921647) - times must increase between two sequential stops
- trip_id 3758078-2025_H-Mult_J&V-Jeu-Ven-01 stop_sequence 14 departure_time 07:19:30 (1776921570) is less than previous stop departure_time 07:20:47 (1776921647) - times must increase between two sequential stops
- trip_id 3758078-2025_H-Mult_J&V-Jeu-Ven-01 stop_sequence 14 departure_time 07:19:30 (1776921570) is less than previous stop arrival_time 07:20:18 (1776921618) - times must increase between two sequential stops
- trip_id 3757937-2025_H-Mult_J&V-Jeu-Ven-01-1101110 stop_sequence 34 arrival_time 08:24:00 (1776925440) is less than previous stop arrival_time 08:26:31 (1776925591) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 69 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 3759195-2025_H-Mult_J&V-Jeu-Ven-01 stop_sequence 2 doesn't have arrival or departure
- trip_id 3759195-2025_H-Mult_J&V-Jeu-Ven-01 stop_sequence 3 doesn't have arrival or departure
- trip_id 3748427-2025_H-Mult_J&V-Jeu-Ven-01 stop_sequence 23 doesn't have arrival or departure
- trip_id 3748433-2025_H-Mult_J&V-Jeu-Ven-01 stop_sequence 23 doesn't have arrival or departure
- trip_id 3757937-2025_H-Mult_J&V-Jeu-Ven-01-1101110 stop_sequence 8 doesn't have arrival or departure
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 3758057-2025_H-Mult_J&V-Jeu-Ven-01 and vehicle_id 61289ff756b38782f6019f09 pairing in VehiclePositions does not match trip_id 3757936-2025_H-Mult_J&V-Jeu-Ven-01-1101110 and vehicle_id 61289ff756b38782f6019f09 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 113 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 3758820-2025_H-Mult_J&V-Jeu-Ven-01 is in TripUpdates but not in VehiclePositions feed
- trip_id 3745392-2025_H-Mult_J&V-Jeu-Ven-01 is in TripUpdates but not in VehiclePositions feed
- trip_id 3748507-2025_H-Mult_J&V-Jeu-Ven-01 is in TripUpdates but not in VehiclePositions feed
- trip_id 3758656-2025_H-Mult_J&V-Jeu-Ven-01 is in TripUpdates but not in VehiclePositions feed
- trip_id 3759039-2025_H-Mult_J&V-Jeu-Ven-01 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 |
|---|---|---|---|
| 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 763 | 29 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 46 | 28 fois (97 % 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 | 1 042 | 26 fois (90 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 290 | 25 fois (86 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 49 | 24 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 | 187 | 23 fois (79 % 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 | 14 | 10 fois (34 % 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
Entités
Entités présentes dans ce flux le 24/04/2026 à 01h30 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 24/04/2026 à 01h30 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1776987056"
}
}