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
❌380 erreurs, 79 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 25/02/2026 à 08h12 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 165 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 61289ff756b38782f6019cc2 trip_id 3758503-2025_H-Mult_LaM-L-Ma-Me-60 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 61289ff756b38782f6019ed2 trip_id 3758836-2025_H-Mult_LaM-L-Ma-Me-60 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 667ecec3b43ef98706f523b7 trip_id 3745454-2025_H-Mult_LaM-L-Ma-Me-60 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 61289ff756b38782f60199ad trip_id 3748455-2025_H-Mult_LaM-L-Ma-Me-60 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 667ecea392c99b62cc677055 trip_id 3745391-2025_H-Mult_LaM-L-Ma-Me-60 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 3757973-2025_H-Mult_LaM-L-Ma-Me-60-0010000 stop_id SVCOL2 does not exist in GTFS data stops.txt
- trip_id 3757967-2025_H-Mult_LaM-L-Ma-Me-60-0010000 stop_id SVCOL1 does not exist in GTFS data stops.txt
- trip_id 3757968-2025_H-Mult_LaM-L-Ma-Me-60-0010000 stop_id SVCOL1 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 172 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 3759195-2025_H-Mult_LaM-L-Ma-Me-60 stop_sequence 3 arrival_time 08:12:10 (1772003530) is equal to previous stop arrival_time 08:12:10 (1772003530) - times must increase between two sequential stops
- trip_id 3759195-2025_H-Mult_LaM-L-Ma-Me-60 stop_sequence 3 arrival_time 08:12:10 (1772003530) is equal to previous stop departure_time 08:12:10 (1772003530) - times must increase between two sequential stops
- trip_id 3759195-2025_H-Mult_LaM-L-Ma-Me-60 stop_sequence 3 departure_time 08:12:10 (1772003530) is equal to previous stop departure_time 08:12:10 (1772003530) - times must increase between two sequential stops
- trip_id 3759195-2025_H-Mult_LaM-L-Ma-Me-60 stop_sequence 3 departure_time 08:12:10 (1772003530) is equal to previous stop arrival_time 08:12:10 (1772003530) - times must increase between two sequential stops
- trip_id 3758884-2025_H-Mult_LaM-L-Ma-Me-60 stop_sequence 15 arrival_time 08:13:50 (1772003630) is equal to previous stop arrival_time 08:13:50 (1772003630) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 2 erreurs
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.
Exemples d'erreurs
- trip_id 3758115-2025_H-Mult_LaM-L-Ma-Me-60-1110100 stop_sequence 17 departure_time 08:11:43 (1772003503) is less than the same stop arrival_time 08:11:55 (1772003515) - departure time must be equal to or greater than arrival time
- trip_id 3759207-2025_H-Mult_LaM-L-Ma-Me-60 stop_sequence 18 departure_time 08:06:10 (1772003170) is less than the same stop arrival_time 08:07:39 (1772003259) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 10 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 3774268-2025_H-Mult_LaM-L-Ma-Me-60-1111100 stop_sequence 1 doesn't have arrival or departure
- trip_id 3758175-2025_H-Mult_LaM-L-Ma-Me-60-1110100 stop_sequence 1 doesn't have arrival or departure
- trip_id 3758175-2025_H-Mult_LaM-L-Ma-Me-60-1110100 stop_sequence 2 doesn't have arrival or departure
- trip_id 3758175-2025_H-Mult_LaM-L-Ma-Me-60-1110100 stop_sequence 3 doesn't have arrival or departure
- trip_id 3758175-2025_H-Mult_LaM-L-Ma-Me-60-1110100 stop_sequence 4 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 28 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 3758530-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f60193ad pairing in VehiclePositions does not match trip_id 3758532-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f60193ad pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 3759046-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f6019954 pairing in VehiclePositions does not match trip_id 3759091-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f6019954 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 3747522-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f6019979 pairing in VehiclePositions does not match trip_id 3747501-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f6019979 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 3748455-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f60199ad pairing in VehiclePositions does not match trip_id 3748426-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f60199ad pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 3758517-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f60197af pairing in VehiclePositions does not match trip_id 3758502-2025_H-Mult_LaM-L-Ma-Me-60 and vehicle_id 61289ff756b38782f60197af 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 79 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 3748518-2025_H-Mult_LaM-L-Ma-Me-60 is in TripUpdates but not in VehiclePositions feed
- trip_id 3759041-2025_H-Mult_LaM-L-Ma-Me-60 is in TripUpdates but not in VehiclePositions feed
- trip_id 3758881-2025_H-Mult_LaM-L-Ma-Me-60 is in TripUpdates but not in VehiclePositions feed
- trip_id 3774268-2025_H-Mult_LaM-L-Ma-Me-60-1111100 is in TripUpdates but not in VehiclePositions feed
- trip_id 3748424-2025_H-Mult_LaM-L-Ma-Me-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 | 41 | 15 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. | 2 322 | 15 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. | 204 | 15 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 017 | 15 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 379 | 14 fois (93 % 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 | 241 | 14 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. | 48 | 10 fois (67 % 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 (13 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 26/02/2026 à 04h07 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 26/02/2026 à 04h07 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1772075230"
}
}