Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Cmonbus.
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
❌58 erreurs, 197 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 15/09/2025 à 16h17 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 15 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 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 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 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 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 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 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 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
Avertissements
ID in one feed missing from the other W003 197 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 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
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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 15 | 1 fois (100 % 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 | 1 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 | 37 | 1 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. | 3 | 1 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 | 197 | 1 fois (100 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 16/09/2025 à 00h27 Europe/Paris.
service_alerts (1) vehicle_positions (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
service_alerts trip_updates vehicle_positionsService alerts (infos trafic)
Voici un aperçu des informations de trafic présentes dans ce flux le 16/09/2025 à 00h27 Europe/Paris.
Arrêt Hopital Arrêt déplacé
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.
Flux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 16/09/2025 à 00h27 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"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": "1757975233"
}
}