Détails de la ressource
GTFS-RT (protobuff) de la position des véhicules
Cette ressource fait partie du jeu de données Réseau urbain Astrobus.
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
❌38 erreurs, 12 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 21/11/2024 à 08h05 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 12 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 zenbus:Vehicle:5166415361343488:LOC trip_id ATOUMOD036:ServiceJourney:6584075897798656x5:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:5166415361343488:LOC trip_id ATOUMOD036:ServiceJourney:6556412902637568x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:741670006:LOC trip_id ATOUMOD036:ServiceJourney:5060085219852288x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:5149698287468544:LOC trip_id ATOUMOD036:ServiceJourney:4644982938927104x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:728310006:LOC trip_id ATOUMOD036:ServiceJourney:6556412902637568x3:LOC 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 12 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id zenbus:Vehicle:5166415361343488:LOC route_id ATOUMOD036:Line:4809340465709056:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:5166415361343488:LOC route_id ATOUMOD036:Line:5131776580124672:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:741670006:LOC route_id ATOUMOD036:Line:5089804213551104:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:5149698287468544:LOC route_id ATOUMOD036:Line:5089173048393728:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:728310006:LOC route_id ATOUMOD036:Line:5131776580124672:LOC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 12 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id zenbus:Vehicle:5166415361343488:LOC stop_id FR:14366:ZE:5207259147665408:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:5166415361343488:LOC stop_id FR:14303:ZE:19280004:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:741670006:LOC stop_id FR:14366:ZE:615450039:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:5149698287468544:LOC stop_id FR:14366:ZE:1190003:ATOUMOD036 does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:728310006:LOC stop_id FR:14366:ZE:1190003:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle.id is not unique E052 2 erreurs
Each vehicle should have a unique ID
Exemples d'erreurs
- entity ID VM:ATOUMOD036:ServiceJourney:6556412902637568x2:LOC has vehicle.id zenbus:Vehicle:5166415361343488:LOC which is used by more than one vehicle in the feed
- entity ID VM:ATOUMOD036:ServiceJourney:5858591379554304x1:LOC has vehicle.id zenbus:Vehicle:5149698287468544:LOC which is used by more than one vehicle in the feed
Avertissements
schedule_relationship not populated W009 12 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id ATOUMOD036:ServiceJourney:6584075897798656x5:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:6556412902637568x2:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:5060085219852288x0:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:4644982938927104x2:LOC does not have a schedule_relationship
- trip_id ATOUMOD036:ServiceJourney:6556412902637568x3:LOC does not have a schedule_relationship
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 | 161 | 14 fois (48 % des validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 161 | 14 fois (48 % des validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 161 | 14 fois (48 % des validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 161 | 14 fois (48 % des validations) |
E052 | Each vehicle should have a unique ID | 16 | 9 fois (31 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 21/11/2024 à 13h00 Europe/Paris.
vehicle_positions (3) service_alerts (0) trip_updates (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/11/2024 à 13h00 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "VM:ATOUMOD036:ServiceJourney:5477981779656704x6:LOC",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 1,
"position": {
"latitude": 49.02027893066406,
"longitude": 0.4011729955673218
},
"stop_id": "FR:14478:ZE:6213133221756928:ATOUMOD036",
"timestamp": "1732190424",
"trip": {
"direction_id": 1,
"route_id": "ATOUMOD036:Line:5118765622624256:LOC",
"trip_id": "ATOUMOD036:ServiceJourney:5477981779656704x6:LOC"
},
"vehicle": {
"id": "zenbus:Vehicle:5073941951414272:LOC"
}
}
},
{
"id": "VM:ATOUMOD036:ServiceJourney:4767410897813504x1:LOC",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 5,
"position": {
"latitude": 49.02027893066406,
"longitude": 0.4011729955673218
},
"stop_id": "FR:14366:ZE:4921563608514560:ATOUMOD036",
"timestamp": "1732190291",
"trip": {
"direction_id": 2,
"route_id": "ATOUMOD036:Line:5118765622624256:LOC",
"trip_id": "ATOUMOD036:ServiceJourney:4767410897813504x1:LOC"
},
"vehicle": {
"id": "zenbus:Vehicle:5073941951414272:LOC"
}
}
},
{
"id": "VM:ATOUMOD036:ServiceJourney:5477981779656704x3:LOC",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 28,
"position": {
"latitude": 49.15726089477539,
"longitude": 0.22238899767398834
},
"stop_id": "FR:14366:ZE:658330001:ATOUMOD036",
"timestamp": "1732170940",
"trip": {
"direction_id": 1,
"route_id": "ATOUMOD036:Line:5118765622624256:LOC",
"trip_id": "ATOUMOD036:ServiceJourney:5477981779656704x3:LOC"
},
"vehicle": {
"id": "zenbus:Vehicle:5181291739742208:LOC"
}
}
}
],
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1732190458"
}
}