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

Edge 830 Roundabout issues discovered today

Baz 8755
over 3 years ago

Before I set out for a ride today my Edge 830 decided to apply a firmware update (probably irrelevant to my issue).

Whilst out riding the weather turned and I decided to get the device to route me home.

During the ride I not only noticed that it told me to take the first exit on a roundabout that was correctly drawn on the map showing I had to take the second exit but it also showed that I show travel anticlockwise.

I don't use navigation very often but given todays discoveries I will be exercising caution on the occasions I do.

  • 0 over 3 years ago

    I have seen the incorrect exit number displayed on roundabout navigation prompts when using the Garmin cycle maps.  I don't know why it happens as the roundabouts in question are correct in OSM and when using third party maps.

  • 0 over 3 years ago in reply to Wongataa

    The strange thing is that in the top left of the screen it had a roundabout symbol that showed going round anti-clockwise

  • 0 over 3 years ago

    I find that this behavior sometimes happens when I return to my start location by using the feature that returns you by the route you have just ridden. So when you get to a roundabout, it takes you round the roundabout the way you had ridden earlier. 

    But, it ignores the fact that you also had ridden on the opposite side of the road and returns you on the correct side. It just seems to be roundabouts that do not get changed in the recalculation.

    Occasionally I also find it happens when planning a route taking me round a roundabout the wrong way and if I does, I just replot it. There seems to be a small glitch in the alogarithms at times.

  • 0 over 3 years ago

    Happens regularly to me too and we have quite a few roundabouts here (Switzerland). I always need to check the map to take the right exit. This issue exists since > 1 year, so it's not really firmware related. I assume it's a map quality issue. 

    Also there is often (but not always) an issue with the third exit, it then says "take three exit" instead of third. I assume that one is with Google, as the voice recognition is by google on the connected Android phone.