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
❌52 erreurs, 11 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 15/02/2026 à 08h11 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
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 3757919-2025_H-Mult_Dim-Dimanche-60 stop_id SVCOL1 does not exist in GTFS data stops.txt
- trip_id 3757925-2025_H-Mult_Dim-Dimanche-60 stop_id SVCOL2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 44 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 3757919-2025_H-Mult_Dim-Dimanche-60 stop_sequence 23 arrival_time 09:28:40 (1771144120) is equal to previous stop arrival_time 09:28:40 (1771144120) - times must increase between two sequential stops
- trip_id 3757919-2025_H-Mult_Dim-Dimanche-60 stop_sequence 23 arrival_time 09:28:40 (1771144120) is equal to previous stop departure_time 09:28:40 (1771144120) - times must increase between two sequential stops
- trip_id 3757919-2025_H-Mult_Dim-Dimanche-60 stop_sequence 23 departure_time 09:28:40 (1771144120) is equal to previous stop departure_time 09:28:40 (1771144120) - times must increase between two sequential stops
- trip_id 3757919-2025_H-Mult_Dim-Dimanche-60 stop_sequence 23 departure_time 09:28:40 (1771144120) is equal to previous stop arrival_time 09:28:40 (1771144120) - times must increase between two sequential stops
- trip_id 3757919-2025_H-Mult_Dim-Dimanche-60 stop_sequence 29 arrival_time 09:35:40 (1771144540) is equal to previous stop arrival_time 09:35:40 (1771144540) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 1 erreur
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 3746658-2025_H-Mult_Sam-Samedi-60 stop_sequence 19 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 2 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 3757919-2025_H-Mult_Dim-Dimanche-60 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 3757925-2025_H-Mult_Dim-Dimanche-60 stop_sequence 24 has stop_id SVCOL2 but GTFS stop_sequence 24 has stop_id SVPBI2 - stop_ids should be the same
VehiclePosition and TripUpdate ID pairing mismatch E047 3 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 3748905-2025_H-Mult_Dim-Dimanche-60 and vehicle_id 63fc89146a6784155006f37c pairing in VehiclePositions does not match trip_id 3747771-2025_H-Mult_Sam-Samedi-60 and vehicle_id 63fc89146a6784155006f37c pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 3748895-2025_H-Mult_Dim-Dimanche-60 and vehicle_id 63fc89331e80e243150f9047 pairing in VehiclePositions does not match trip_id 3748254-2025_H-Mult_Sam-Samedi-60 and vehicle_id 63fc89331e80e243150f9047 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 3748939-2025_H-Mult_Dim-Dimanche-60 and vehicle_id 63fc89070689e241eae4e0c7 pairing in VehiclePositions does not match trip_id 3746658-2025_H-Mult_Sam-Samedi-60 and vehicle_id 63fc89070689e241eae4e0c7 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 11 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 3748858-2025_H-Mult_Dim-Dimanche-60 is in TripUpdates but not in VehiclePositions feed
- trip_id 3748206-2025_H-Mult_Sam-Samedi-60 is in TripUpdates but not in VehiclePositions feed
- trip_id 3746658-2025_H-Mult_Sam-Samedi-60 is in TripUpdates but not in VehiclePositions feed
- trip_id 3748887-2025_H-Mult_Dim-Dimanche-60 is in TripUpdates but not in VehiclePositions feed
- trip_id 3748254-2025_H-Mult_Sam-Samedi-60 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 | 13 | 5 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. | 709 | 5 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 | 60 | 5 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. | 14 | 5 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 | 323 | 5 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 | 43 | 4 fois (80 % 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. | 3 | 2 fois (40 % 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 | 4 | 2 fois (40 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 15/02/2026 à 23h33 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 15/02/2026 à 23h33 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771194783"
}
}