All is good unless the device recalculates and it is pretty hard to keep it from recalculating at some point.

On my Nav VI, I experimented with auto recalculate, recalculate off and prompt but I was never happy with any of them because they each came with pitfalls.........If we want to ride/drive ...

So I saved the simple route that I created on the device and looked at the code on my computer and compared it to the same route created in Basecamp.

The obvious thing that I see that is different between the 2 files is that the Basecamp route includes callouts for waypoint extensions and the ...

I played with this a little more. Instead of using Basecamp, I created a simple route on the device itself and I was able to change a shaping point to a via and back again without affecting the route. It also did not move the points. It behaved exactly as I would have thought and just as it does in ...

Sorry to resurrect this older thread but I stumbled across this while trying to figure out why my new DriveSmart 86 was screwing up my GPX routes whenever I used the 86 itself rather than Basecamp to manually change a VIA (orange flag) to a shaping point.

I thought it was a very simple thing to do ...

The BMW Nav IV is basically a Zumo 660. The Nav V is basically a 590 and I think the worst model they had for using custom GPX files. The Nav VI is a lot better - it is closer to the XT.

Not sure which of the BMWs your buddy has but there are two things that I do that help with the BMV Nav VI: I ...

Thanks.

There are about 5 of us sharing GPX routes that 2 of us are creating in Basecamp. We have Zumo 660, BMW Nav VI, Zumo XT and now Drive65 (I think that is the correct model).

I am trying to make sure we all stay on the same GPX route taking into consideration all the idiosyncrasies of ...

OK, I am confused now.

Doesn't the Zumo automatically do a route calculation every time it imports a custom GPX file? Isn't that what we are seeing on the screen while it loads the routes - the % complete countdown screen? It seems to me that this import process would take care of any map mismatch ...

I checked the "Device Transfer Options" and the only box checked was the 2nd one that related to forcing the exported route to use the map on the device. I unchecked this box and changed the name from the lower left pane, exported the route to both of my Zumos and the name I changed it to did appear ...

@Rofor - I'll check the "Device Transfer Options" tonight.

@Danham - Mine is a Windows 10 computer and there is no box shown for auto naming as you show. Looks totally different.

Thanks.

Got a question on the route name: When I double click on the route, I do not see a check box for auto naming. Has this been deleted on current versions Basecamp?

I would like to be able to use my own naming convention but as it is now, when I create a route, I am stuck with whatever Basecamp ...