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
❌274 erreurs, 6 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 20/01/2025 à 08h09 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 89 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 275 trip_id 2-153259933697 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 110 trip_id 2-152454627329 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 266 trip_id 2-152874057729 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 282 trip_id 2-153008340993 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 168 trip_id TRIPID-2794 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 89 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 275 route_id 9135 does not exist in the GTFS data routes.txt
- vehicle_id 110 route_id 9087 does not exist in the GTFS data routes.txt
- vehicle_id 266 route_id 9112 does not exist in the GTFS data routes.txt
- vehicle_id 282 route_id 9120 does not exist in the GTFS data routes.txt
- vehicle_id 168 route_id TAD does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 88 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 275 stop_id 732 does not exist in GTFS data stops.txt
- vehicle_id 110 stop_id 3339 does not exist in GTFS data stops.txt
- vehicle_id 266 stop_id 1706 does not exist in GTFS data stops.txt
- vehicle_id 282 stop_id 969 does not exist in GTFS data stops.txt
- vehicle_id 168 stop_id STP-DEPART does not exist in GTFS data stops.txt
All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 E015 1 erreur
All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 304 stop_id 3370 does not have location_type=0 in GTFS stops.txt
Vehicle position outside agency coverage area E028 7 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 353 at (47.707745,-2.558439) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 351 at (47.821423,-2.811683) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 307 at (47.76594,-2.500779) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 290 at (47.70588,-2.553047) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 178 at (47.688725,-2.547284) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Avertissements
timestamp not populated W001 6 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- vehicle_id 120 does not have a timestamp
- vehicle_id 298 does not have a timestamp
- vehicle_id 63 does not have a timestamp
- vehicle_id 37 does not have a timestamp
- vehicle_id 62 does not have a timestamp
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 106 | 30 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 106 | 30 fois (83 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 082 | 30 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. | 146 | 30 fois (83 % des validations) |
| W001 | Timestamps should be populated for all elements | 238 | 30 fois (83 % 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. | 25 | 19 fois (53 % des validations) |
| E015 | All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt | 20 | 11 fois (31 % des validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 13 | 11 fois (31 % 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 21/01/2025 à 05h55 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 21/01/2025 à 05h55 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1737435336"
}
}