Resource details
This resource file is part of the dataset Réseau urbain Cmonbus.
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
❌58 errors, 197 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-15 at 16:17 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 15 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 3 GARE--DUMAS 7H42 stop_sequence 5 departure_time 07:55:30 (1757915730) is less than previous stop departure_time 07:56:50 (1757915810) - times must increase between two sequential stops
- trip_id A---) Parc Luberon stop_sequence 10 arrival_time 07:43:33 (1757915013) is less than previous stop arrival_time 07:52:27 (1757915547) - times must increase between two sequential stops
- trip_id A---) Parc Luberon stop_sequence 10 arrival_time 07:43:33 (1757915013) is less than previous stop departure_time 07:52:42 (1757915562) - times must increase between two sequential stops
- trip_id A---) Parc Luberon stop_sequence 10 departure_time 07:43:53 (1757915033) is less than previous stop departure_time 07:52:42 (1757915562) - times must increase between two sequential stops
- trip_id A---) Parc Luberon stop_sequence 10 departure_time 07:43:53 (1757915033) is less than previous stop arrival_time 07:52:27 (1757915547) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 3 errors
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.
Sample errors
- trip_id 3 GARE--DUMAS 7H42 stop_sequence 5 departure_time 07:55:30 (1757915730) is less than the same stop arrival_time 08:02:20 (1757916140) - departure time must be equal to or greater than arrival time
- trip_id 3 CLEDE--CARNOT 8H30 stop_sequence 8 departure_time 08:49:40 (1757918980) is less than the same stop arrival_time 08:54:36 (1757919276) - departure time must be equal to or greater than arrival time
- trip_id ncv2_10 stop_sequence 0 departure_time 09:58:23 (1757923103) is less than the same stop arrival_time 09:59:58 (1757923198) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 37 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 ncvot_2_0 stop_sequence 1 doesn't have arrival or departure
- trip_id ncvot_2_0 stop_sequence 2 doesn't have arrival or departure
- trip_id ncvot_2_0 stop_sequence 3 doesn't have arrival or departure
- trip_id ncvot_2_0 stop_sequence 4 doesn't have arrival or departure
- trip_id ncvot_2_0 stop_sequence 5 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 3 errors
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id ncv2_36 and vehicle_id 68a32bab62a0742370db7c83 pairing in VehiclePositions does not match trip_id ncv2_11 and vehicle_id 68a32bab62a0742370db7c83 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 1(R) Rosa > Gares and vehicle_id 6880b5ebc6a234ad8a1d9d74 pairing in VehiclePositions does not match trip_id 3 8H15 and vehicle_id 6880b5ebc6a234ad8a1d9d74 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 1(R) Rosa > Verdun and vehicle_id 6880b5ebc6a234ad8a1d9d70 pairing in VehiclePositions does not match trip_id 4 RETOUR and vehicle_id 6880b5ebc6a234ad8a1d9d70 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 197 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 ncv2_35 is in TripUpdates but not in VehiclePositions feed
- trip_id E2.2_2 is in TripUpdates but not in VehiclePositions feed
- trip_id E2.2_3 is in TripUpdates but not in VehiclePositions feed
- trip_id 4 RETOUR is in TripUpdates but not in VehiclePositions feed
- trip_id E2.2_0 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 15 | 1 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. | 3 | 1 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 | 37 | 1 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 | 1 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 | 197 | 1 times (100 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-16 at 02:47 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsService alerts
Here is a display of service alerts contained in this feed at 2025-09-16 at 02:47 Europe/Paris.
Arrêt Hopital Stop moved
Dans l'attente de réalisation de travaux, l'arrêt hôpital n'est pas desservie par les ligne C et E, merci de vous reporter aux arrêts précédents ou suivants.
Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-16 at 02:47 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"alert": {
"cause": "CONSTRUCTION",
"descriptionText": {
"translation": [
{
"text": "Dans l'attente de réalisation de travaux, l'arrêt hôpital n'est pas desservie par les ligne C et E, merci de vous reporter aux arrêts précédents ou suivants."
}
]
},
"effect": "STOP_MOVED",
"headerText": {
"translation": [
{
"text": "Arrêt Hopital"
}
]
},
"informedEntity": [
{
"routeId": "zenbus:Line:556270001:LOC"
},
{
"routeId": "zenbus:Line:892310003:LOC"
},
{
"stopId": "Hôpital_1"
}
]
},
"id": "alert:68bfd785e11f3078719aa6c6"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1757983654"
}
}