Routing: GPSMAP 66sr vs GPSMAP 65s [Bug 67]

[ewald.gruen]

What could be the reason that the 66sr (v5.50) provides much worse route suggestions than the 65s (v4.50) despite using the exact same OSM map? When I select "Hiking", I am guided along county roads instead of forest paths.

examples

65s_routing.png

66sr_routing-1.png

66sr_routing-2.png

[Gr] edited to add firmware versions

[GPSrChive]

You have routing method set to 'Based on Activity' for each, so we would need to check first which activity was used on each device and what the individual settings are for each of those activities.

[ewald.gruen]

The 'Activity' was set to 'Hiking' on both devices. I don't know how to check the 'individual settings', but I most likely use the defaults, because I never changed anything in that regards. The profiles are set as following:

• 66sr: "Current profile is Hike"
• 65s: "Current profile is Recreational"

[GPSrChive]

To check unique settings for each 'Routing Activity', you must first select the activity in 'Setup > Routing > Activity' (instead of 'Prompted'). Then configure routing avoidances etc. as desired, and return selection to 'Prompted' again when finished.

Now, when you are 'Prompted' to choose a routing activity, the saved configuration for the selected option will be loaded and used to determine your route along with the enabled maps, etc.

These configurations are 'Profile' dependent, so if you make changes while in the 'Hiking' profile, then switch to another profile, they will not apply.

[ewald.gruen]

Thanks! They were indeed set differently, but the sad news is that correcting the setting does not solve the problem. The 66sr selects the same county road for both "Minimize Time" and "Minimize Distance" and the 65s selects the same forest path for both "Minimize Time" and "Minimize Distance". I am at a loss.

[GPSrChive]

We will again request you share screen captures from each device that clearly demonstrate this behavior, and then we will make certain the correct people at Garmin see them.

[ewald.gruen]

One out of many possible examples

link

(https://www.komoot.com/plan/tour/d01AvJ ... 07,13.928z):

• Device: GPSMAP 66sr
• Activity: Hiking
• Calculation Method: Minimize Distance

maps

66sr_topo_vs_topoactive_vs_otm_vs_freizeitkarte.png

(Maps from left to right: TOPO Germany, TopoActive Europe,

links

OpenTopoMap, Freizeitkarte)

It is possible to force the route to the correct path by adding a via point

link

(https://www.komoot.com/plan/tour/d01AvJ ... 07,13.928z):

map

66sr_freizeitkarte_via_point.png

(Map: Freizeitkarte)

No issue on neither the 65s nor the 64s:

• Device: GPSMAP 65s
• Activity: Hiking
• Calculation Method: Minimize Distance

map

65s_freizeitkarte.png

(Map: Freizeitkarte)

[GPSrChive]

After doing some testing with a GPSMAP 64s, 65s, 66sr, and Montana 7x0, we have determined more information is still needed.

Please provide waypoint coordinates for the exact position those routes were all started from, and if you can also upload a screen capture of the Freizeitkarte map zoomed in on that location and in high detail, that would be great....

Thank You!

[ewald.gruen]

Start

https://www.openstreetmap.org/node/256598424

End

https://www.openstreetmap.org/node/1195530749

maps

66sr_freizeitkarte_route-1.png

66sr_freizeitkarte_route-2.png

66sr_freizeitkarte_route-3.png

66sr_freizeitkarte_route-4.png

[Wojtas81]

Tested it with Freizeitkarte map on Oregon 700 (v6.00) and the routing is the same, ie. incorrect (county roads).
But when I select Cycling profile and under menu Avoidances, Unpaved Roads are disabled, everything works as expected (ie. shortest route is really shortest via forest paths).
So using Cycling profiles instead of Hiking could be used as workaround.

Of course, everything works as expected with original Garmin TopoActive Maps (including Hiking profile). Only third-party maps have this issue.

Anyway, this bug is not specific to 66sr. Rather 64 and 65 have better routing with third-party maps than many other devices.