Resource details
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
This resource file is part of the dataset Réseau urbain Cap Cotentin.
Related resources
Horaires théoriques des lignes régulières et secondaires du réseau Cap Cotentin
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
❌30 errors, 16 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-31 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 2 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- 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 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- 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 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- 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 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- 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
Warnings
ID in one feed missing from the other W003 16 errors
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
Sample errors
- 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
Previous validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 15 | 2 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 187 | 2 times (100 % of 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 | 94 | 2 times (100 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 3 | 2 times (100 % of 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 | 127 | 2 times (100 % of 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. | 28 | 1 times (50 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-29 at 04:29 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-29 at 04:29 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1759112940"
}
}