I use BaseCamp mainly for designing (road bike) cycling trips. Of course, I do not want to be sent via unpaved roads - but unfortunately BaseCamp is far too strict with this avoidance. It is ridiculous to suggest a detour of 8 km just to avoid 4 m on gravel. I'd love to have options to a) ignore unpaved segments shorter than a user-defined length, and b) define an acceptable ratio between the length of an unpaved section vs. the extra mileage.
I know that both options aren't that easy to implement because there will usually be many unpaved segments which could all be included in the suggested route, hence giving the optimiser a pretty hard time. A cheap alternative (in terms of CPU load) would be a setting for the speed reduction due to the bad surface – a value of 95% would probably exclude all but very short unpaved sections while low values around 20% would be fine for those on touring bikes etc. who experience only slightly reduced performance on gravel.
Another helpful feature would be the option to change the routing for a via point using the right-click menu. I think of a key 'activity' with a sub-menu listing the different activity types. This will be of even more use in the Windows version of BaseCamp where using different activities is really cumbersome.
