Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Nemus.
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
❌117 erreurs
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 31/01/2025 à 08h02 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 36 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 161 trip_id T44 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 107 trip_id T25 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 46 trip_id T6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 51 trip_id T18 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 111 trip_id T15 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 36 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 161 route_id 44 does not exist in the GTFS data routes.txt
- vehicle_id 107 route_id 25 does not exist in the GTFS data routes.txt
- vehicle_id 46 route_id 6 does not exist in the GTFS data routes.txt
- vehicle_id 51 route_id 18 does not exist in the GTFS data routes.txt
- vehicle_id 111 route_id 15 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 30 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 161 stop_id 131 does not exist in GTFS data stops.txt
- vehicle_id 107 stop_id 144 does not exist in GTFS data stops.txt
- vehicle_id 46 stop_id 243 does not exist in GTFS data stops.txt
- vehicle_id 51 stop_id 115 does not exist in GTFS data stops.txt
- vehicle_id 111 stop_id 115 does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 14 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 46 at (48.74605,-0.444735) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 15 at (48.793858,-0.563329) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 42 at (48.61044,-0.389632) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 54 at (48.85084,-0.411861) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 43 at (48.654816,-0.528408) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
vehicle.id is not unique E052 1 erreur
Each vehicle should have a unique ID
Exemples d'erreurs
- entity ID 324136 has vehicle.id 127 which is used by more than one vehicle in the 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 591 | 23 fois (88 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 591 | 23 fois (88 % 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. | 197 | 22 fois (85 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 463 | 21 fois (81 % des validations) |
| E052 | Each vehicle should have a unique ID | 6 | 6 fois (23 % des validations) |
| W001 | Timestamps should be populated for all elements | 4 | 4 fois (15 % des validations) |
Contenu du flux GTFS-RT
Impossible de décoder le flux GTFS-RT
Le flux GTFS-RT doit être accessible en HTTP, sans authentification et utiliser le format Protobuf.