Downloaded caches

[+allswell]

Is there a way to mark the caches that have been downloaded. I know when you find a cache it puts a check mark along with it. When you do a new search a mark of some sort would make it easier to search for either new or just adding more to your gps

 

allswell

[+Fuchsiamagic]

Is there a way to mark the caches that have been downloaded. I know when you find a cache it puts a check mark along with it. When you do a new search a mark of some sort would make it easier to search for either new or just adding more to your gps

 

allswell

Go to the 'Hide and Seek' page and click on 'Go' without entering a zip code. On the next page, just tick the 'Exclude hidden/found items from results' box. Or run a customised pocket query excluding your finds.

[+Miragee]

Welcome to the Forums!

 

Since you are a Premium Member, you can request Pocket Queries that only contain caches you have not found yet. If you use a program like GSAK (Geocaching Swiss Army Knife) to keep track of the data, you can have a separate database for the caches you have Found along with the Default database of caches you have not Found yet.

[+Prime Suspect]

Is there a way to mark the caches that have been downloaded. I know when you find a cache it puts a check mark along with it. When you do a new search a mark of some sort would make it easier to search for either new or just adding more to your gps

 

allswell

Looks like everyone answered the question they wanted to answer, instead of the one you actually asked.

 

The answer is No. There's no practical way of doing that, and that's a good thing. People change cache coordinates; temporarily disable them; archive them, etc. What you're proposing is just a way to retain stale data while only adding new data. You don't want to retain stale data. Pocket Queries are meant to be a current snapshot of a collection of caches. They're not meant to create a long a long-term database.

[+derangedlunatech]

I can see a good and practical application or this - if you have PQs that overlap physically, it would be kinda nice to have some way to filter out caches that appear in PQ A when you run PQ B...

 

But generally speaking I agree - it would not be good to spend a day looking for a cache that had been archived a month ago...

Edited June 25, 2008 by derangedlunatech

[+allswell]

Thanks Prime and deranged. I see your points. I will experiment with pq's I have not yet looked into them so not sure how it works I do use GSAKand down load to it before transfering to my gps.

[+StarBrand]

I can see a good and practical application or this - if you have PQs that overlap physically, it would be kinda nice to have some way to filter out caches that appear in PQ A when you run PQ B...

 

Oh but you can - run your PQ by date placed instead of a simple radius and there will never be any overlap.

[+derangedlunatech]

Oh but you can - run your PQ by date placed instead of a simple radius and there will never be any overlap.

 

How exactly do you mean?

 

The way I have changed mine in the last few days is by cache size. But that has its limitations as well.

 

(BTW - when I said overlapping physically, I don't mean the entire search overlaps - I mean that I have different centers for the search, and parts of some of the circles overlap)

Edited June 27, 2008 by derangedlunatech

[+Prime Suspect]

I can see a good and practical application or this - if you have PQs that overlap physically, it would be kinda nice to have some way to filter out caches that appear in PQ A when you run PQ B...

 

Oh but you can - run your PQ by date placed instead of a simple radius and there will never be any overlap.

Except you're still retaining stale data, and won't get informed of when, for example, a disabled cache goes back on line, because your data for that cache is never getting updated.

 

The OP needs to ask himself if, as you can get 2,500 caches per day delivered by PQ, what he's asking is really necessary.