GSAK question

[Ratz and company]

Is there a way that I can send only the waypoints to the GPS that have not been downloaded before?

[marc_54140]

I’ve not tried something like that, so I do not know if there is a way.

However, there are some things to consider. If you have some caches with similiar names, GSAK might end up assigning the same name to different caches.

I generally clear out my gps of all caches – except for half a dozen residence locations – and reload everything fresh.

Since you are loading anyways, cleaning out first would not take that long. I think this process helps in preventing little unexpected problems, as well as keeping the gps clear of junk.

If there are sepecific caches you want to keep, you can change the cache icon to something specific – like residence – and delete all by symbol.

Hope this helps …..

[Miata]

My experience with GSAK is if I don’t delete all waypoints like Marc, you should not get duplicate waypoints unless they are named different the second time.

I have in the past just slammed in the newest packet along with all of the old waypoints with no troubles. But you need to delete the waypoints of the caches you have found already.

This works OK if you don’t leave your home area, but to travel to a new area it makes things a lot cleaner to start from scratch. I have also came across waypoints that have been updated, and guess who had the old ones still loaded.

[NSLP1]

There are a couple user fields in GSAK that you could probably use, you could have a macro that sets one of those fields after you upload, then have your filters set to exclude anything with a certain value in the field.

Though I always clear my waypoints before loading them, then I know that I don’t have an archived cache in there.

note that I have started running a macro that clears out caches that I haven’t received in a gpx file in the last 60 (or 30) days to clear out disabled/archive caches as well.

After trying to show some family and friends about it, and having the first 2 of 3 we tried as DNF because they had been archive at least 6 months prior, I saw the need to keep the database cleaned up better. At least the 3rd was still active.

[Author]

Posts