This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Map Updates for Errors?

Former Member
Former Member

I cannot seem to get an answer anywhere else, so please move to a more appropriate area as needed.

So with every map update, for whatever strange reason, my area seems to be a magnet for bizarre map problems where it refuses to allow a route to go through invisible and non-existant blockages. Note to the peanut gallery, this has nothing to do with avoidances - this is absolutely map errors.

This most recent update included these issues in the sample attached.  There is no way on my end to correct this obstruction, and Basecamp requires a detour.

You report these using the Basecamp Report Map Error function, but you never get a response. And it's hit or miss whether the issue is fixed with the next release.  But worse, even if there is a fix, you end up with a new issue like this that pops up out of nowhere somewhere else. This is a never-ending battle

I put arrow points on this sample so you can see the issue. It's a formatting thing of some sort. Due to the amount of time it takes to fix these, essentially for a Zumo, it extends the entire season, I think whatever this is should be correctable by the end user on their OWN installed map.  Essentially be allowed to erase an erroneous barrier that is negatively affecting the routing.  I know wish lists around here are right up there with asking for winning lottery numbers, but come on.  If you cannot fix a map and send out a fix in a couple of days like most maps, at least empower the users to fix the stupid stuff that shouldn't be showing up in the first place.

Thoughts?

 

  • Don't think I've tried to excuse the glitch. I've suggested you contact Garmin about it. All I said was that I've rarely seen a map issue, I know others, including you, have.

  • Former Member
    0 Former Member over 5 years ago in reply to SUSSAMB

    Well just fired up the new NA NT 2021.2 update and it's disturbing to see that this error was never touched, after reporting within Basecamp, on the website, and obviously here.

    Yes I also reported it to HERE, but as previously reported, the issue isn't present there. As such, this is TOTALLY a Garmin screw up.

    So Sussamb, are you going to try and elevate now?

  • Sorry but I'm just a user like you. I suggest you contact Product Support for help with this.

  • Former Member
    0 Former Member over 5 years ago in reply to SUSSAMB

    Hmm, so what's with PM threats? Either you are a moderator with inside connections, or are you just making stuff up?

  • Inside connections are not required to be moderators for these types of forums.  Frankly, for the amount of time SISSAMB spends on this forum trying to help others, even exceptionally rude people, Garmin should be sending him all sorts of free stuff.

    As to your issue, your only resource is to report it directly to Garmin.  If it were me, I would contact support via phone and inform them that there is a barrier when auto-routing on 1st Street along the Wisconsin-Illinois border near Lake Michigan between N42° 29.586' W87° 50.626' and N42° 29.586' W87° 50.625' and that the issue is not present on the HERE site.

    My experience in getting Garmin to address device firmware issues has been less than favorable.  You my want to consider the alternative of selling your device and moving on to a competitor.

  • Former Member
    0 Former Member over 5 years ago in reply to BTLAAKE

    LOL, more suggestions to do the same things that have already been done, MULTIPLE TIMES.  I can understand the compassion to come to his defense as you have a habit of doing the same things. It's OK, I get it.

    I'm very glad your 6 year old 2014 map is working fine for you. If you'd breakdown and bought a Map License, or Upgraded to a new unit, you'd then be affected.  Until then, your opinion carries very little, actually, zero weight.

    The point is, I have the process down crystal clear. No amount of parroting back these steps that have been taken are going to accomplish a thing, until someone within Garmin actually does the work on the other end.

    Thanks again, both of you. Now please mosey on and offer your self-proclaimed brilliance elsewhere. 

  • As you seem not to want any advice but simply to insult those trying to help I'm going to lock this thread. You have good advice from two of us, your choice now what to do.