Détails de la ressource
GTFS-RT (protobuff) global, regroupant les horaires aux arrêts, la position des véhicules et les perturbations.
Cette ressource fait partie du jeu de données Réseau urbain Hobus.
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
❌122 erreurs, 2 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 23/01/2025 à 08h10 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 4 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 67515ef7cb498f5037dede09 trip_id 58 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 56 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 58 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 55 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 4 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 67515ef7cb498f5037dede09 route_id A does not exist in the GTFS data routes.txt
- route_id A does not exist in the GTFS data routes.txt
- route_id A does not exist in the GTFS data routes.txt
- route_id A does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 64 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 67515ef7cb498f5037dede09 stop_id 28 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 2 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 4 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 6 does not exist in GTFS data stops.txt
- trip_id 56 stop_id 8 does not exist in GTFS data stops.txt
stop_time_update doesn't have arrival or departure E043 49 erreurs
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Exemples d'erreurs
- trip_id 56 stop_sequence 0 doesn't have arrival or departure
- trip_id 56 stop_sequence 1 doesn't have arrival or departure
- trip_id 56 stop_sequence 2 doesn't have arrival or departure
- trip_id 56 stop_sequence 3 doesn't have arrival or departure
- trip_id 56 stop_sequence 4 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 1 erreur
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Exemples d'erreurs
- trip_id 58 and vehicle_id 67515ef7cb498f5037dede09 pairing in VehiclePositions does not match trip_id 55 and vehicle_id 67515ef7cb498f5037dede09 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Avertissements
ID in one feed missing from the other W003 2 erreurs
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Exemples d'erreurs
- trip_id 55 is in TripUpdates but not in VehiclePositions feed
- trip_id 56 is in TripUpdates but not in VehiclePositions 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 | 57 | 7 fois (88 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 57 | 7 fois (88 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 957 | 7 fois (88 % des validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 33 | 6 fois (75 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 8 | 5 fois (63 % des validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 366 | 4 fois (50 % 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.