Home, Home1, Home2... how do I avoid multiple copies of same location on my device?

I posted the same issue a while back and I never got it resolved. There was a suggestion of grouping them together but I'm afraid I didn't really understand what was meant and never managed to resolve the issue.

Six months on from that post I still struggle with Basecamp. I just want to plan a route like I used to on Mapsource and don't want the complications that Basecamp seems to have introduced. I'm a dinosaur at heart I guess :rolleyes:

If you send multiple copies of the same things to your Zumo you'll get multiple copies.

The simplest way is to load everything into Basecamp and do your editing there. On your device clear all the data from it, this includes any files in the GPX folder. Then send the data from Basecamp in one go to your device.

Note this problem isn't a Basecamp problem. It's the way devices like the Zumo and Nuvi operate, you cannot use Basecamp (or Mapsource) to edit the data on the device. Handheld devices operate differently, with them Basecamp can edit data directly on the device itself.

If you send multiple copies of the same things to your Zumo you'll get multiple copies.

If I create two routes in Basecamp and both start or finish at my home, when I send the routes to a blank Zumo I end up with Home and Home 1 on the Zumo. Basecamp knows that both routes start at the same waypoint, and you can edit the routes on the Zumo once they are there to use the same waypoint. So why this cannot be done when the Zumo connects / transfers is unclear.

The simplest way is to load everything into Basecamp and do your editing there. On your device clear all the data from it, this includes any files in the GPX folder. Then send the data from Basecamp in one go to your device.

Yep. Not only the simplest way, but the only way it seems. If you read my original post you can see that is what I am reduced to doing already. Unfortunately you can't just nuke the data on the Zumo in one operation - as this also deletes the tracks stored on the device - which then breaks other bits of the software on Zumo (like "where I've been"): so you end up having to delete trips and favourites separately which is tedious as anything.

Note this problem isn't a Basecamp problem. It's the way devices like the Zumo and Nuvi operate, you cannot use Basecamp (or Mapsource) to edit the data on the device. Handheld devices operate differently, with them Basecamp can edit data directly on the device itself.

Not quite true - this inability to edit what is on the Zumo is recently introduced. In earlier times you could actually edit what was on the Zumo from within Basecamp. Not sure why they changed - but my view is that if they are going to make such changes it would be nice if they didn't then have whatever weird bug they have that results in multiple copies of waypoints accumulating on the device. Sounds like for whatever reason Garmin have not messed up hand-held devices yet, and so they operate still like Zumo's used to. Overall, the thing that is causing the multiple waypoints is Basecamp, so I don't agree that it is not a Basecamp issue.

Sorry but nuvis have always had that problem because of the way they work, it's nothing to do with Basecamp. You can't edit data whether you use Basecamp, Mapsource or any other 3rd party mapping program, and I use a few.

As for Zumos, I don't have one but it's difficult to see what has changed in Basecamp that would lead to a change on the Zumo. You may be getting confused because on most of the Zumos (so I understand) you have to import routes and favourites, having sent the relevant gpx file to the Zumo. If you then send another gpx file with amended data then the imported data will be different. That's not the same though as editing data on the device.

As for Garmin 'not having messed up hand held devices yet', they operate in a different way from the nuvi and Zumo range. If anything was 'messed up' it was the original operating architecture of the nuvi, dezl and zumo range :)

As for Zumos, I don't have one but it's difficult to see what has changed in Basecamp that would lead to a change on the Zumo. You may be getting confused because on most of the Zumos (so I understand) you have to import routes and favourites, having sent the relevant gpx file to the Zumo. If you then send another gpx file with amended data then the imported data will be different. That's not the same though as editing data on the device.

I had a Zumo 550 for 7 years before I got my current 590, and so have used every version of Basecamp, and whatever there was before (so long I can't remember). You'll just have to trust me that you certainly could edit what was on the Zumo in the past, and can't now. I'm not so technical, but I know enough to know that. You are right that when you send a route to the Zumo it 'imports' it before you can use it, but you can send multiple routes in one transfer so your multiple GPX file idea doesn't seem to apply.

Anyhow, while your thoughts on why the problem is not really a problem is an interesting diversion, unless I am missing something it seems you don't actually have any ideas beyond the one I outline in my original post (delete everything on the Zumo and then import it again each time you want to update a route). The reason I posted my question (and the other chap who also has this issue) is that as a bit of workflow that is pretty dire, and I wondered if there is any way to fix it that is less awful than the one I'm using. Do you have any such ideas?