I like to use trip planner hubs to organize my trips by sections. For example: Home to Main, Acadia Area, Hampton Area, etc. How hard would it be to allow users to select any number of continuous day trips and add a hub header to the selected days? It improves organization for me and lets me add days while in the area.
I'm still looking for the value proposition of the "HUB". What function does the Hub provide that one cannot do by just adding trip days before/after any day in the Itinerary?
I'm still looking for the value proposition of the "HUB". What function does the Hub provide that one cannot do by just adding trip days before/after any day in the Itinerary?
As Pseabolt says, the main advantage is organization of your trip. If I'm going to multiple cities, it's nice to have the time in the city separate from other cities and the time spent getting to the city. There are some functional differences as well. For instance, if you choose lodging on a day in a hub, BaseCamp can propagate that lodging to the rest of the days in that hub. If you aren't planning on spending more than one night anywhere, then the value of hubs is minimal, but if you are planning multiple days in a place I find it handy.
I like to use trip planner hubs to organize my trips by sections. For example: Home to Main, Acadia Area, Hampton Area, etc. How hard would it be to allow users to select any number of continuous day trips and add a hub header to the selected days? It improves organization for me and lets me add days while in the area.
This would be marginally tricky, because we are treating hub days differently than travel days under the covers. However, it seems like you could already do what you're asking for. When you create a hub, you already get separate organizations for the hub days and the days spent getting to the hub. You can add days before or after any day just by using the context menu on the day badge.
As Pseabolt says, the main advantage is organization of your trip. If I'm going to multiple cities, it's nice to have the time in the city separate from other cities and the time spent getting to the city. There are some functional differences as well. For instance, if you choose lodging on a day in a hub, BaseCamp can propagate that lodging to the rest of the days in that hub. If you aren't planning on spending more than one night anywhere, then the value of hubs is minimal, but if you are planning multiple days in a place I find it handy.
Thanks for the feedback azdrmn.
I do see how it works and the Hub concept would appear to provide some value when planning an Itinerary that has several multi-day layovers with travel out and back during the layover days.
Is there any value in the Hub inherent in the Trip data once it leaves BaseCamp?
Currently the hub is a BaseCamp-only concept. We have been in talks with the device team to perhaps have that concept bridge the gap, but for now the short answer is no.
Thanks azdrmn. Glad to hear your are communicating with the zumo folks. If we could get that brand to play well with even the current level of data it would be a big plus.
