Basecamp completely disregards avoidances

So I have noticed that there are some roads that Garmin thinks are still there, but they are dead-end streets. I have been adding these as avoidances as I discover them, however, basecamp will still route through them. Many times it is not even the best route. It is a little annoying because I am still learning my way around my area of work (I am an inspector so I drive a different route daily) so I don't know every dead-end and though I try to make a mental note of them if I haven't driven that particular route in a while or only a few times I tend to forget. Is there a better way?

  • I am having a similar problem with avoidances. Sometimes they work as expected, sometimes BC disregards them.

    I know that map errors can make it appear like Basecamp is ignoring avoidances.  The most common for me is the unpaved avoidance.  I have experienced many cases where BC routed over unpaved roads and refused to route over paved roads.  I have also experienced BC refusing to route along stretches of main roads.  It will route along neighborhood streets to get around such sections.  I have never found an explanation for such behavior other than the conjecture that someone reported a map error claiming that stretch of road is closed in order to try to reduce traffic.

  • Yes I agree, map errors - and they are numerous in my experience - can cause similar issues.

    In my case, I can eliminate that as the root cause because the problem goes away when I use a different (but similar) profile. 

    ie. Using a different profile will result in BC respecting the area avoidances. 

    As a test, I created a new custom profile from the same base profile (Motorcycling) as my problematic custom profile. 

    I set all of the same road type and feature type avoidances.   

    Using this test profile, the area avoidances are respected.

    This contradicts my earlier belief that Area Avoidance are not respected in Custom Profiles.

    I have been using BC to plan routes since 2012 and I have now reached my limit.

    Does anyone have a suggestion for an alternative - I'm not interested in roure planning on my phone/tablet.  I don't have the eyesight for that.

    cheers

  • It’s like Garmin has a mind of its own—“Oh, you want to avoid this dead-end? Too bad, I know a shortcut!” I sometimes imagine it laughing at me as I drive into another dead-end.

  • I don't point the finger at Garmin for errors like incorrect dead-ends.  Those are mapping errors.  Map makers Here, OSM, and Google Maps all have them.  Garmin uses Here, who seems really slow to fix errors compared to Google.  I don't know about OSM in that regard.  Regardless, I am only defending Garmin as not to blame for map errors,  Beyond that, I am not a fan, specifically for the awful routing algorithms in their newest motorcycle satnavs where the "Faster" option means routing over faster roads seemingly regardless of additional time and distance, and for how their Windows software has yet to allow for an installation to work for all users on that system.