Duplicate routes and waypoints on device

The way to do it is as you describe, although by carefully organising your data in Basecamp you can minimise the times when you get duplicate waypoints. Really it's not surprising. If you send a waypoint with the same name to your nuvi and you meant it to be a separate waypoint but it overwrote the first you wouldn't want that either, so to be safe a copy is made.

Yes, I get what you say but it's a bit irritating when you change a route on Basecamp to find everything gets duplicated on the device, at least with Windows and plenty of other software you will always get the option to overwrite or create a duplicate. I assume Basecamp is not really looking at the device contents in real-time but is dealing with the update as a separate batch operation?

With handheld devices Basecamp can directly access the data. On the nuvi range because of the way they work it cannot.

So the issue really has nothing to do with Basecamp but more to do with the nuvis design.

Ok, that explains why not everyone is having this problem and reassures me that I am not going completely mad :)

Many thanks for your speedy replies.

As you learn and use BC, you will certainly end up with more data than you will want to use on any specific trip. So in the long run, you will not want to send the total "My Collection" ever to your device. In addition, deleting everything from your device before sending to it all of what you need for a trip will avoid duplications that are on the device but not in BC. The following thread discusses some workflow and data management strategies, it is in the Mac section, but the discussion applies to Mac and PC: https://forums.garmin.com/showthread.php?304117-Workflow-in-basecamp

Thanks - I'll certainly try out those recommendations once I've completed the current trip.

I do all my routes with Mapsource.

I never delete any waypoints from my Nuvis (40 and 765T) before transferring routes to them.

I never get duplicate waypoints.

When I tried doing routes in Basecamp using existing waypoints and transferring the routes to the Nuvis I always got duplicate waypoints.

Basecamp is the problem. Basecamp should be capable of using existing waypoints without having to duplicate them. It should not be necessary to purge the device every time you want to transfer a route to it. It is not necessary when using their ancient unsupported software. Why is it required when using their current supported software.

Can you say "workaround"?

..ken...

@kganshirt

I'm curious as to what happens when a route with a Waypoint using an existing name on your device but different coordinates is uploaded to your device from MapSource. Does it give you the option to transfer the point to with new name (or automatically rename it), replace the existing Waypoint on the device or ignore the transfer?

@kganshirt

I'm curious as to what happens when a route with a Waypoint using an existing name on your device but different coordinates is uploaded to your device from MapSource. Does it give you the option to transfer the point to with new name (or automatically rename it), replace the existing Waypoint on the device or ignore the transfer?

I don't know. The way I work that can't happen. When I want to mess with routes in Mapsource that will include waypoints I either load the waypoints from the last backup file from the device or, if it's time to do another backup of the device anyway, I just upload the waypoints from the device to work with. Even with 400-ish waypoints it only takes (literally) a couple of seconds.

In order to cause such a situation as you describe I would have to not load the existing waypoints from either the backup .GDB file or from the device and then create a new waypoint that coincidentally is the same as an existing one. I'm not sure why I would ever work that way.

I do sometimes do routing where I want to create new waypoints using Mapsource and a map (and possibly with some assistance from aerial views in Google Earth). I mostly do this for motorcycle trips which will include a component of offroading. In this case I typically will use a topo map in Mapsource and aerial views in Google Earth to find the jumping off spot where I leave the paved road(s) and begin the offroad portion and create a named waypoint there.

In such a situation I always load the existing waypoints for the device I will be using for the trip before I start creating the new waypoint(s) and routes. So I can't create such a situation as you describe.

If it actually matters, I could do a test for you, eg. open a new Mapsource file, create a waypoint with the same name as one that exists on the device but with different coordinates and see what happens when I try to transfer it. The way Garmin carefully coordinates their device development "standards" it's possible the results might vary a wee bit from device to device. :)

...ken...