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

Major navigation issues with Garmin 1030 and 820 devices

When using on device navigation to a town less than 3 miles away and easily driveable on UK A and B roads, both my 820 (v11.20 ) and 1030(v7.50) with maps 2019.10 select a very circular on-road route of 39.5 miles and avoiding the most obvious roads. This also happens whilst riding in various locations and I can no longer use the devices for they were purchased for. As I'm on a road bike I've selected to avoid narrow trails and unpaved roads (however using these options makes little difference). When using the 1030 in Automobile mode it tells that there are no navigable roads in the area. Interestingly loading and activating OSM maps and disabling the Garmin maps on both devices they then work fine, but this is NOT what I paid Garmin for. I have a support case open with Garmin, but so far no progress from them. Anyone else had similar issues??

  • I don't think the Unpaved classification is the issue with this road.

    As dpawlyk said A roads globally have an issue in the UK, where the Bicycle Riding routing mode will avoid them by default with none of the available settings for that routing mode permitting their use

  • Very interesting discussion and goes some way to explain weird routing I’ve seen in the UK both on edge 1030/830 and on GC. 

    Hopefully Garmin can start to address this by cross referencing popularity routing more, isn’t this what popularity routing should help to overcome?

    Waiting a year for a map update isn’t really a solution. 

  • Hmm, this is from the OpenFiets Lines Style type.  These are the rules that are applied to translate OSM data in a Garmin Map when compiled by MKGMAP.

    # set toll and ferry flags
    highway=* & bicycle!=no {add toll=yes}

    If my understanding is correct what this means is if the line is any kind of highway and bicyle access tag is not no then add the value toll=yes (if not already previously set) into the Garmin Map.

    I'm not sure I can explain the logic of this one.  The add might be relevant as opposed to a set value and the logic might combine with other rules to set the correct access.  But it may certainly explain your testing with avoiding tolls.

  • Nice find. Yes, you are understanding it properly.

    "I'm not sure I can explain the logic of this one.".

    The openfiets map is for cyclists (it's not meant to be a general purpose map).

    It's (clever) logic. It's repurposing the classifications to make the map more useful for cycling.

    (Basically) toll roads don't ever allow cycling. That means, as far as cycling goes, these roads don't exist.

    Few cyclists want to ride on highways but they might need to once in a while.

    By classifying highways as toll roads, highways can be easily avoided with the avoidance but used if they need to.

    Openfiets also classifies cycleways as highways. That lets you use the "automobile" routing to create routes that prefer using cycleways.

    Using the Openfiets map for routing for actual automobiles would be weird.

    ==================

    The newer Edges work a bit differently than the older units with respect to routing options.

    The openfiets maps were created for the older units. The creators might have done a few things differently if they were creating them for the new units.

  • That's a good piece of detective work well done

    I used the Generic Routable map extensively over the weekend & it performed pretty well. 

    There is still a Garmin issue at some roundabouts where the turn prompt treats the entry & exit of the roundabout as two separate turns & zooms in to a ridiculously small scale on the entry turn that you can't see which exit you are supposed to take. This happens across all maps even the Garmin maps. In the US I don't think they have roundabouts but it's a headache for UK users

    The only other small issue was with auto/prompted Recalculation of a route between 2 points whilst travelling. Although I'd set the routing options to minimise distance when I deliberately went off course from the originally calculated route onto what I knew was a shorter route the navigation seemed to try & hold on to the original route for some distance with the recalculation suggesting a number of U turns before finally realising that my direction was somewhat shorter 

  • I have noticed this and was about to post about this until I saw this, I live in Thurso by John O' Groats a lot of the UK riders will be aware of this, however, if I plan a route on Garmin when out riding just to gauge how far it is, etc. 

    I use the route back to start option most direct and it keeps sending me down B roads i could be 2 miles from home yet pushing me down other roads giving me 5 miles instead.

    There are no motorways or major roads where i am for 200 miles, so its a bit frustrating, especially if i am somewhere i don't know  god knows where it will send me

  • With Thurso being on the junction of 2 A roads. They will no doubt be avoided by the garmin map routing for cycling. 

    Try installing the generic routable osm map of the UK from openstreetmaps.nl & disabling the built in garmin cycle maps. I've found the 3rd party map works much more reliably especially with A roads & courses seem to calculate quicker too

  • what OSM maps are you using. I'm in Canada and have the exact same problems. Dumb thing takes me on the craziest roads that no cyclist would ever use. plus add wonky km's and direction

  • Try these http://garmin.openstreetmap.nl/ I found for me in the UK the Generic Routable (New Style) seem to be the best

  • Can you provide an example start and end point for us to have a look please?