Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Kicéo.
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
❌40 erreurs, 8 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 12/08/2025 à 09h14 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 12 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 163 trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 167 trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 351 trip_id TP893837 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 169 trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 375 trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 12 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 163 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 167 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 351 route_id SAEIVTEO.31 does not exist in the GTFS data routes.txt
- vehicle_id 169 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 375 route_id MOBICEO does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 12 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 163 stop_id STP-DEPART does not exist in GTFS data stops.txt
- vehicle_id 167 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
- vehicle_id 351 stop_id SAEIVTEO.7081 does not exist in GTFS data stops.txt
- vehicle_id 169 stop_id STP-DEPART does not exist in GTFS data stops.txt
- vehicle_id 375 stop_id STP-DEPART does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 2 erreurs
The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.
Exemples d'erreurs
- vehicle.id 351 at (47.915474,-2.823335) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 347 at (47.809765,-2.384624) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Vehicle position far from trip shape E029 2 erreurs
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.
Exemples d'erreurs
- vehicle.id 339 trip_id 4-5839060994 at (47.7139,-2.760858) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 356 trip_id 4-302186501 at (47.667145,-2.745581) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Avertissements
timestamp not populated W001 7 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- vehicle_id 49 does not have a timestamp
- vehicle_id 371 does not have a timestamp
- vehicle_id 90 does not have a timestamp
- vehicle_id 178 does not have a timestamp
- vehicle_id 45 does not have a timestamp
vehicle speed is unrealistic W004 1 erreur
vehicle.position.speed has an unrealistic speed that may be incorrect
Exemples d'erreurs
- vehicle.id 366 speed of 30.555555 m/s (68.35 mph) is unrealistic
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 192 | 30 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 | 294 | 25 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 294 | 25 fois (83 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 294 | 25 fois (83 % des validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 101 | 24 fois (80 % 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. | 23 | 16 fois (53 % des validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 16 | 13 fois (43 % des validations) |
| E052 | Each vehicle should have a unique ID | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 13/08/2025 à 03h28 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 13/08/2025 à 03h28 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1755048537"
}
}