Why does the route invariably alter once planned on the website and then exported to the in my case, Garmin XT?
-
Can someone explain why, pretty much any route I compile on the MRA website app, when exported to my Garmin XT, invariably changes the length, timing allocated and route selected?
Also I'm trying to align the track created when a route is uploaded, with the actual route, which also shows differences, when I haven't created any. I have the track set to a different colour and the box ticked to show on the map, with the widest line setting as well. Even though the differences might be relatively minor, they exist. Why?
-
What map are you using for Garmin devices it should be Here Maps? What export format are you using. I use gpx1.1 This means that the route is recalculated by the XT but if you use sufficient shaping points the route will replicate the route you've planned in MRA.
I'm a Garmin Zumo XT user and can replicate the route I've planned on My Route app (or basecamp for that matter) by taking the following actions.
Plenty of shaping points on the roads you want to be on. The variances exist because of differences in the routing algorithm between points in MRA and the XT unit. Garmin changed routing logic after about 2015-6 units 396 and 595 units on for faster time to mean main roads. I have 5 old Garmin units and this drove me nuts until I worked it out through reading info on the Zumoforums
https://www.zumouserforums.co.uk/viewtopic.php?t=1464
https://www.zumouserforums.co.uk/viewtopic.php?t=3139Disconnect explore from your zumo (its poor). Make all your routes "saved" see zumo forums. And if you want too create a theme which makes the track wider than the route line and you will have a nice user experience. I use MRA planner much more now instead of Basecamp as I can make new routes or alter routes on Tour using my phone or an Ipad rather than carrying a windows PC around to use BAsecamp.
-
Mzokk,
Thank you for responding and yes I use HERE, plus import the routes using gpx 1.1.
I have the track use set to widest and in bright red, so it is relatively easy to see the difference between it and the route, I also set the track visible on the map, however, only for each individual route, otherwise the map can look mad, with different routes applied!
I do insert plenty of waypoints + shaping points likewise, but it doesn't seem to make that much, if any difference.I'll have to stick with the niggle.......
-
It's not really an issue with MRA per se but rather an issue with the Zumo XT routing algorithm that strongly wants to use main roads when "Faster time is selected". If it's any consolation the XT does its own thing even with routes produced in "Basecamp" I also have a Zumo 340 and 390 which I use on an old R1150GS that I've had since 2004 and with "faster time" set on the units and in Basecamp they produce what you see (on basecamp) is what you get on the 340-390. Not so with the XT I'm afraid. I have an Africa Twin Adventure Sport as my main bike now and mainly use MRA on Android auto for navigation now. I still have the Zumo mounted and mostly use it for handling proximity warnings to certain POI's I've loaded. This is one area were Garmin are still much better than MRA.
