Route from track does not recalc path correctly on Nuvi

Former Member
Former Member
By "path" I mean the line I want my route to go:

I have an imported a track file into an empty list. It imports to Basecamp without any error. It displays properly in Basecamp. If I convert it to a route, that also works correctly and shows it is taking the desired path. If I double click on the TRACK, I get the track points, 832 of them. If I double click on the ROUTE that was built from the track, it lists 2 via point names, the start and finish. The route box shows no other track points, and I see no shaping points. But, if I recalculate the this resultant route, it's path remains the same as it was originally built (the long way), which is correct and the desired behavior.

If I load this route onto my Nuvi 1490, the Nuvi will recalculate the route going the straightest way and NOT follow the desired path.

In the List where I have imported this track and done the conversion to the route, I tried deleting everything except the route in that list. Recalc in Basecamp, it still shows the correct path being taken. Export to the Nuvi, no dice, still calculates the shortest path between start and end waypoints.

Any way to fix that behavior?

Happy to share sample files. The original track came from a KMZ file out of Google Maps. Also tried KML.
  • No, but there is a work around. Converting a track to a route simply produces a start and finish point so your nuvi simply calculates a route based on that.

    To send a route to your nuvi that follows it exactly create a new route in BaseCamp based on the start/finish. Now add via points so it follows the route you want, then send that route to your nuvi. Note that is still no guarantee the routes will match exactly. Once it's loaded to your nuvi look at it again in BaseCamp to ensure it matches. If not add additional viapoints as necessary.
  • Former Member
    0 Former Member over 7 years ago


    That defeats the purpose of importing the track in the first place. Respectfully your workaround isn't a workaround. With the exception of 2 points, your workaround is equivalent to don't import, do it from scratch. If I've got to build a complicated route from scratch I can find the start and end on my own.
  • Not quite, if you've imported the track you've got something to go on. You can insert sufficient viapoints so that the route matches the track.