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
❌30 erreurs, 16 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 31/08/2025 à 09h11 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 2 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
- trip_id 3730855-2025_E-Mult_Sam-Samedi-00-0001110 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 3730930-2025_E-Mult_Sam-Samedi-00-0001110 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 24 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 3741634-2025_E-Mult_Dim-Dimanche-00 stop_sequence 37 arrival_time 09:19:00 (1756624740) is equal to previous stop arrival_time 09:19:00 (1756624740) - times must increase between two sequential stops
- trip_id 3741634-2025_E-Mult_Dim-Dimanche-00 stop_sequence 37 arrival_time 09:19:00 (1756624740) is equal to previous stop departure_time 09:19:00 (1756624740) - times must increase between two sequential stops
- trip_id 3741634-2025_E-Mult_Dim-Dimanche-00 stop_sequence 37 departure_time 09:19:00 (1756624740) is equal to previous stop departure_time 09:19:00 (1756624740) - times must increase between two sequential stops
- trip_id 3741634-2025_E-Mult_Dim-Dimanche-00 stop_sequence 37 departure_time 09:19:00 (1756624740) is equal to previous stop arrival_time 09:19:00 (1756624740) - times must increase between two sequential stops
- trip_id 3741634-2025_E-Mult_Dim-Dimanche-00 stop_sequence 40 arrival_time 09:21:00 (1756624860) is equal to previous stop arrival_time 09:21:00 (1756624860) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 3 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 3730930-2025_E-Mult_Sam-Samedi-00-0001110 stop_sequence 34 doesn't have arrival or departure
- trip_id 3741618-2025_E-Mult_Dim-Dimanche-00 stop_sequence 34 doesn't have arrival or departure
- trip_id 3741633-2025_E-Mult_Dim-Dimanche-00 stop_sequence 16 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 3741601-2025_E-Mult_Dim-Dimanche-00 and vehicle_id 63fc89331e80e243150f9047 pairing in VehiclePositions does not match trip_id 3730855-2025_E-Mult_Sam-Samedi-00-0001110 and vehicle_id 63fc89331e80e243150f9047 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 16 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 3741600-2025_E-Mult_Dim-Dimanche-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3741335-2025_E-Mult_Dim-Dimanche-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3741633-2025_E-Mult_Dim-Dimanche-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3750386-2025_E-Mult_Dim-Dimanche-00 is in TripUpdates but not in VehiclePositions feed
- trip_id 3741618-2025_E-Mult_Dim-Dimanche-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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 079 | 14 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. | 1 553 | 14 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 | 494 | 14 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 308 | 14 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. | 162 | 13 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. | 34 | 5 fois (36 % 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 (7 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 17/09/2025 à 02h01 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 17/09/2025 à 02h01 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1758067292"
}
}