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
❌102 erreurs
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 20/12/2024 à 08h01 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 33 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 155 trip_id T14 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 84 trip_id fe0cafba8bb5489af06e1e80b73083d4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 83 trip_id 4e637fdf2204bad094066faa2c3c0cc7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 44 trip_id T7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 59 trip_id T26 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 28 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 155 route_id 14 does not exist in the GTFS data routes.txt
- vehicle_id 84 route_id 248 does not exist in the GTFS data routes.txt
- vehicle_id 83 route_id 248 does not exist in the GTFS data routes.txt
- vehicle_id 44 route_id 7 does not exist in the GTFS data routes.txt
- vehicle_id 59 route_id 26 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 28 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 155 stop_id 144 does not exist in GTFS data stops.txt
- vehicle_id 84 stop_id 2780 does not exist in GTFS data stops.txt
- vehicle_id 83 stop_id 1643 does not exist in GTFS data stops.txt
- vehicle_id 44 stop_id 288 does not exist in GTFS data stops.txt
- vehicle_id 59 stop_id 198 does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 12 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 44 at (48.658913,-0.358263) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 59 at (48.662384,-0.563255) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 72 at (48.790062,-0.518343) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 87 at (48.791466,-0.453222) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
- vehicle.id 46 at (48.746094,-0.445698) 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 318229 has vehicle.id 23 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 | 562 | 24 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 451 | 23 fois (79 % 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. | 189 | 21 fois (72 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 430 | 20 fois (69 % des validations) |
| E052 | Each vehicle should have a unique ID | 6 | 6 fois (21 % des validations) |
| W001 | Timestamps should be populated for all elements | 4 | 3 fois (10 % des validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 21/12/2024 à 19h38 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/12/2024 à 19h38 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1734806324"
}
}