Mac/Windows Software

Basecamp Windows Basecamp to Montana route transfer problem

Basecamp to Montana route transfer problem

Former Member over 11 years ago

I created a short route on Basecamp 4.3.5 using the CNNA 2015.10 map and the Automobile activity. It looks perfect (19.2 miles). Running Win7.

If I use Basecamp and simply drag the route onto the Internal Storage of my Montana to transfer the route, the route is horribly messed up when I try to load it on the Montana (56.1 miles). Note: Montana is set to Automobile activity as well.

HOWEVER, if I manually export the route from Basecamp as a GPX file and then manually copy the GPX file to the internal storage on the Montana (Garmin\GPX folder), the route will load fine.

So I compared the two GPX files (one manually exported, the other created by Basecamp on the Montana) and they are very different. The exported one is much larger and has many more RouteExtensionPoint elements in the XML.

Can someone please explain why Basecamp can export a GPX file that works, but doesn't create the exact same GPX file when you drag a route onto the Montana to transfer it? And why is broken?

0 Former Member over 11 years ago

Thank you for letting us know about this. We will look into it.

0 Former Member over 11 years ago

Would you be willing to post to me your GPX files?

0 Former Member over 11 years ago

Even better, can you e-mail them to [email][email protected][/email]. Then we will have a log of it.

0 Former Member over 11 years ago

I sent an email to win.basecamp with six GPX files zipped up. I created three versions of a route from my house to the local motorcycle meeting point, a Sheetz gas station 19.2 miles away.

The first route has no via points, so BC can figure the fastest way there.
The second route has several via points to shape the route to stay on nicer back roads. This was done with the Automobile activity.
The third route is a duplicate of the second, but with the activity set to Direct. I noticed that things work if the activity is set to Direct in BC and then drag/drop the route on the Montana internal storage.

There are two versions of each route in the zip file. One that was manually exported (File -> Export -> Selection). Those files have the route names in them. The other version are the GPX files that BC created on the Montana for each route (Route.gpx, Route0.gpx, etc).

I tried loading the routes that BC created on the Montana and got the bizarre results. I also noticed that I got the banner message about recalculating routes because the maps didn't match. I can assure you that the maps do match. I just reloaded the maps via BC the day before. All that is on the Montana is the CNNA 2015.10 and the default global base map.

0 Former Member over 11 years ago

Great I have written a case for this and we will be able to look into it. Thank you for your patience.

0 Former Member over 11 years ago

I got a reply via email from Garmin. Their guess is that the Montana is recalculating the route using the basemap instead of CNNA when I drag/drop the route onto "Internal Storage". At their suggestion, I unchecked the "Always match map" option in the Device Transfer settings and it seemed to transfer a new batch of routes correctly.

Interestingly, CNNA 2015 does NOT show up under my Montana in Basecamp when I connect it. I only see the worldwide basemap.

So for the moment (while waiting for another reply), I have the "Always match map" unchecked and have disabled the worthless basemap on the Montana in the profiles that I would use.

I suspect that BC needs to get smarter about figuring out what maps are installed on a device and doing a better job of matching if the "Always match" option is selected. Like prompt the user to pick the map if it canit find a match or something...