
- Avoidance-Enabled-issue
- 12-07-2009
If you were Registered and logged in, you could reply and use other advanced thread options
I have an issue with a certain road (telling me to take a left then a right
then a right and another left - to get me back onto the same road) and I
reported the map info to Garmin.
I got back a few very personal emails from a human - not some " Thank you
very much for informing us " message from a message server. I was asked for
specifics on my map version, unit version etc, then: Reply from Garmin Map
Support:
- 1 year of POI excellence and low clearance avoidance. One year ago after seeing a horrible bridge collision I decided to investigate low clearance avoidance tools.
- Global Positioning System
- 2010-05-27
- 1 year of POI excellence and low clearance avoidance. One year ago after seeing a horrible bridge collision I decided to investigate low clearance avoidance tools.
- Garmin GPS
- 2010-05-27
- 1490T volume issue
- Garmin GPS
- 2010-07-24
- Local Time issue
- Global Positioning System
- 2010-04-23
- SVN49 Issue
- Global Positioning System
- 2009-06-25
- COM port issue with TOPO!
- Satellite Navigation
- 2009-05-30
- Route avoidance settings in receiver?
- Garmin GPS
- 2008-05-19
- Meridian Platinum Time issue
- Magellan GPS
- 2007-09-10

> to do with the traffic. I would try it (when you can) with the
> traffic avoidance enabled and disabled and see if it acts any
> differently. However, I don't expect it will.
> For sure leave the U-Turn avoidance off.
> What the unit sees is an "expensive" left turn at that intersection. It
> is at enough of an acute angle that the unit is treating it as something
> to avoid.
> With those, turning the U-Turn avoidance off will sometimes help. But
> not always. There are oddballs here and there (not often but some) that
> no matter the settings the unit just won't like the turn because it is
> of such an angle that taking the "block around" is preferable to it.
> Now I'm not saying it REALLY is preferable. Don't get me wrong.
> I will pass this route and turn along to our software engineers for a
> look. But I can't promise a change in the behavior. It's one of those
> things where if you make a change for this, you can "break" a lot of
> other things and cause bigger problems.