BaseCamp 3.2.2 is available

GPX from GPS silently overwrites existing routes.

Before I understood that Send To should be used with data I want to be read from my GPS, I did an import of the Current.gpx file into the same List as the original routes and waypoints. The routes silently overwrote the ones in BC, destroying a couple hours changes. Fortunately, ctrl-Z worked to bring back the changes I'd made. I sure wish it wasn't silently doing this, as I may not have noticed until it was too late.

The routes silently overwrote the ones in BC, destroying a couple hours changes. Fortunately, ctrl-Z worked to bring back the changes I'd made. I sure wish it wasn't silently doing this, as I may not have noticed until it was too late.

Arrrrgh!! Falagar, say it ain't so?? Receiving data from a device is not treated the same way as imports?? No content checking to be sure the objects with duplicate names are actually duplicates?

...ken...

I just tried the following on my machine with BaseCamp 3.2.2:

1. Created a route in BaseCamp named it 'Test Route'.
2. Exported the route as gpx.
3. Made a change to the route (moved a via-point).
4. Re-imported the route -> It imports the old route and names it 'Test Route 1'.
5. Removed what I had imported.
6. Sent the route to GPS 62.
7. Disconnected/Reconnected the device.
8. Sent the route from the 62 to BaseCamp. -> It imports the old route and names it 'Test Route 1'.

If you don't delete the imported route (step 5), importing from the device won't do anything, that doesn't strike me as correct.

Now, we should definitely NOT be silently overwriting data when it happens to have the same name. BaseCamp didn't do this for me in my testing. Can you reproduce this behavior? If you can, can you sent me the data and the exact step you could get this to happen with?

I will also create a case about a message when importing data and finding duplicates.

4. Re-imported the route -> It imports the old route and names it 'Test Route 1'.
5. Removed what I had imported.

If you don't delete the imported route (step 5), importing from the device won't do anything, that doesn't strike me as correct.

It looks like Basecamp is not doing a further test to be sure that the new name is not also a duplicate of one in the collection. It should be kicking the new name back into the "Check for duplicate name" code with a flag that it has already appended the number. If there's still a conflict and the flag is set, increment the appended number and kick it back into the duplicate name check again until the name is unique.

Instead it seems to be passing it directly to the code to write it into the collection with the assumption that a single change will do the trick (probably a safe assumption most, but clearly not all, of the time).

...ken...

It should be mentioned that many of us, when playing with routing examples for motorcycle rides, will do exactly what you did when naming the second and subsequent test routes, e.g. we'll just append a number rather than coming up with a complete new name. So we might have "My bike trip n" in the collection where "n" will frequently be greater than 1. And all of the test routes from null to "n" will still be sitting there.

...ken...

Silent route overwrite test

1. In a new List in BC, create a test route with a few waypoints between start and end and rename the list as Test List or Import the attached example.
2. Send Test List to a GPS (Zumo665 in my case). Restart GPS
3. On the GPS, Where To?>page>Custom Routes>(select your test route)>Edit>Add/Remove Points>delete all waypoints except start and end. Restart GPS
4. In BC, select the Test List
5. File>Import>navigate to GPS and import Current.gpx.
6. Observe no warnings, no numbered copy, test route overwritten with waypoints between start and end removed.
7. ctrl-Z will recover the test route with the waypoints, but if one exits BC before noticing what happened, the undo buffer is cleared.

bug: BC routes on roads forbidden for bicycles

The newest releases of BC ignores roads, which are forbidden for cyclists, completely. This causes routing on these kind of roads (like motorways) even if the activity profile is set to bicycle. In Mapsource and on the GPS routing is fine.

In the attachment you can see bike route made in Openfietsmap (OSM cycle map) in some part of the Netherlands.
http://www.openstreetmap.org/?lat=52.07645&lon=5.42625&zoom=15&layers=O

Basecamp routes the cyclists over a major primary road (Randweg N224), forbidden to cyclists (indicated on the map with - - -). Mapsource recognizes this and routes through the village which is correct.

The test map can be downloaded here:
http://mijndev.openstreetmap.nl/~ligfietser/openfietsmap/test/OpenFietsMap%20(test).gmapi.zip

This behaviour does not apply to my maps only but also other OSM maps are affected as well, like the osm world routable maps from http://garmin.openstreetmap.nl as well as cycling maps from Onroute/Waypoint.

I support the findings of Openfietsmap.

I have tested with the OnRoute Motorkaart (motorcycle map) of Europe and the behavior with the slide in the middle or one to the left is much different than it was or is in BaseCamp for Mac or MapSource.

Also the Toll roads is different and more agressief.

The Openfietsmap is free for download. If you would like to test with the OnRoute maps, it's best to send a request for a Map and unlock code to [EMAIL="[email protected]"]Hans[/EMAIL] of Waypoint.

Thanks for reporting. As always, if you can reproduce this on a Garmin-supported map (not OSM), chances of this getting fixed are magnitudes higher. So if you are aware that this happens with a new Topo Deutschland (or similar), please let us know.

I know that there are some routing changes in the works, so I'll try to make sure this will get fixed. Right now I have no idea why this occurs, but there is a chance though that this might be something that will have to be addressed by the map builder.

It might also just be a bug. We'll have to see.

Am I the only one not able to view my custom maps BaseCamp?

All I see is a very low res map preview:

http://www.globalmapperforum.com/forums/attachments/announcement-news/1197d1313782975-garmin-raster-maps-basecamp2.jpg