Can BaseCamp remove or block a road?

Black Gap road in the Smoky Mt. NP has been a horse trail for over 20 year. It is a big short cut form Balsam Mt. to Maggie Valley. I have been reporting the map error for years but nothing happens. I just did another report from BaseCamp. I am getting tire of insetting 5 to 10 waypoints to keep BaseCamp from using the road. It there a way to tell BaseCamp not to use the road for routing? City Navigator NT 2014.4

Thanks
  • Don't believe there is, at least I can't find it in the PC version. Mapsource had it ... but that won't help a mac user either :)
  • Not that I know of. Now that the newer Garmin units have the ability to avoid specific roads or areas let's hope that BaseCamp catches up.
  • Former Member
    0 Former Member over 11 years ago
    It there a way to tell BaseCamp not to use the road for routing.


    I don't know about the Mac version but I'm pretty sure the Windows one doesn't have that ability. MapSource, the predecessor to BC, did though.

    IMO such as feature is of little use unless your device(s) also support creating avoidances and they can be transferred to it.
  • I'm hoping that BaseCamp and the Zumo 590 I just bought will eventually do just this.
  • Most of the nuvis from 2013 on appear to do so (my 2508 does) so fingers crossed you get your wish :)
  • Thanks for the info, my Nuvi 3597 has the feature but I sure don't want to have to use the Nuvi to alter the base camp route. How does it need to be implemented in BC? Seems like two things are needed. Do not use this section for this route and do not use the section for any route. Do we need one waypoint or two to define the section? My problem is caused by bad information on the map, I think my last map error report was the first time I used the BC map error report. Maybe it will get fixed this time.

    Thanks
  • I do a lot of route planning in that area (headed there next week, in fact) and I have to say that the Garmin/Navteq maps are very sloppy about what's dirt and what isn't. So avoidances are useless.

    For that and some baked-in routing oddities closer to home, I have always relied on waypoints to force the desired route and I don't see a built-in avoid/block function being much more useful or convenient than that, but maybe I'm misunderstanding the question.

    It would also be nice if BC displayed dirt roads using something other than missing sections, as it is impossible to tell if the road disappears (which happens in the NC/TN mountains) or turns to dirt, or is a map error.

    -dan
  • The real problem is as you stated, the maps. I have avoidance for unpaved roads on but as you noted it almost never works. The road in question has been a horse and foot trail for the last 20 year. I don't think the maps know which roads a dirt and which are paved. I as you add waypoints but in cases where the road is a big short cut, it takes a lot of trail and error to find where to place the waypoint or waypoints. I just start dragging and undo until I find the midpoint.
  • Former Member
    0 Former Member over 10 years ago
    BaseCamp can only read the data that is coded into the Map. If the map data is incorrect, there is nothing that BaseCamp can do about it. If you keep reporting map errors, and I know you all have, then maybe eventually HERE (Navteq) will fix it. They are the ones that code the map.
  • This feature has been on our Wish List since the newer Zumos started supporting this feature. The main issue with per road avoidances is the fact that the roads change every time there is a map update, so the feature would end up being difficult to use for any user with lifetime maps. We have considered area based avoidances. I know this wouldn't be as specific, but they don't get broken every 3 months.