Détails de la ressource
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- VehiclePosition
Cette ressource fait partie du jeu de données Réseau urbain et scolaire Guingamp-Paimpol Mobilité.
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
❌31 erreurs
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 30/01/2025 à 08h15 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 8 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 162 trip_id 1-739180545 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 153 trip_id 1-621543425 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 71 trip_id 1-604766209 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 51 trip_id 1-705363969 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 65 trip_id 1-453312513 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 8 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 162 route_id 44 does not exist in the GTFS data routes.txt
- vehicle_id 153 route_id 37 does not exist in the GTFS data routes.txt
- vehicle_id 71 route_id 36 does not exist in the GTFS data routes.txt
- vehicle_id 51 route_id 42 does not exist in the GTFS data routes.txt
- vehicle_id 65 route_id 27 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 8 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 162 stop_id 17570 does not exist in GTFS data stops.txt
- vehicle_id 153 stop_id 16640 does not exist in GTFS data stops.txt
- vehicle_id 71 stop_id 17139 does not exist in GTFS data stops.txt
- vehicle_id 51 stop_id 17205 does not exist in GTFS data stops.txt
- vehicle_id 65 stop_id 17609 does not exist in GTFS data 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 162 at (48.412117,-3.42185) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 153 at (48.551586,-3.375188) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 71 at (48.54522,-3.393826) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 51 at (48.402035,-3.46236) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 65 at (48.47344,-3.272227) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
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 | 162 | 18 fois (60 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 162 | 18 fois (60 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 158 | 18 fois (60 % 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. | 140 | 18 fois (60 % 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. | 4 | 4 fois (13 % des validations) |
| W001 | Timestamps should be populated for all elements | 4 | 3 fois (10 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 31/01/2025 à 00h53 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 31/01/2025 à 00h53 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1738281206"
}
}