Listing archived caches in a pocket query

[fishiam]

I was attempting to find a simple way to list out archived caches in my area that I found in the past. The main reason for dong this is to see what areas might have opened (in the cache rich city of Seattle) due to cache archivals. In composing a pocket query, I can select for caches that I have found and that were not active. But that only results in a list of disabled caches.

 

Now I realize this would likely be a little used option, but would it be possible to make listing archived caches an option in a pocket query? Probably there are reasons not to, but if the archived ones were restricted to caches that were published before archiving, that would leave out all those that never got past the submission stage.

[+Stunod]

Your "ALL FINDS" PQ will list the archived caches you have found. A program like GSAK will even filter the entire PQ down to just the archived ones.

 

You cannot get PQ's of archived caches any other way than thru your "ALL FINDS" PQ.

[+S&G.Davison]

It's a shame that the archived ones cannot be more easily identified. The only way I do it is to download a known set of caches on a weekly basis and when they have not appeared in a download file for 2 weeks I mark them as archived.

 

Sue

[+alexrudd]

Now I realize this would likely be a little used option, but would it be possible to make listing archived caches an option in a pocket query?

Little used? It's often been requested (try a forum search), but the answer has always been "NO!"

[+Prime Suspect]

Now I realize this would likely be a little used option, but would it be possible to make listing archived caches an option in a pocket query?

Little used? It's often been requested (try a forum search), but the answer has always been "NO!"

Actually, the answer was, "Here's this new function in Pocket Queries that will include the archived caches that you've found".

 

That's not exactly a NO!

[+S&G.Davison]

really useful to know the archived ones you have found.. this does not prevent you going to find a cache you have not yet found which is where I would have thought these requests are coming from.

 

Sue

[+bwmick]

I use gsak, I thought that PQ's imported archival too, found out I was wrong on my last trip. turns out I searched for several that had been archived. Any reasoning on why Archived are not included? (aside from the obvious take up valuable space in PQ, which a check box do not include would take care of. Geocaching is as much about what was there as it is about what is there now for me.)

 

bwmick

[+beejay&esskay]

Any reasoning on why Archived are not included?

bwmick

 

I believe the official reason is that to include archived caches would encourage the use of local databases, rather than going back to Groundspeak to get the current information.

 

(Yes, I know there are arguments against that...but I think Jeremy has heard all of them and remains adamant.)

[+robert]

I use gsak, I thought that PQ's imported archival too, found out I was wrong on my last trip. turns out I searched for several that had been archived. Any reasoning on why Archived are not included? (aside from the obvious take up valuable space in PQ, which a check box do not include would take care of. Geocaching is as much about what was there as it is about what is there now for me.)

There are a variety of reasons caches are archived. In some instances because the land manager may no longer want people searching for a cache on the property. By archiving the cache, Groundspeak takes it out of PQ's so people won't search it. By keeping stale data on your machine, you're putting your own self at risk for (1) searching needlessly for archived caches that are no longer there and (2) searching in places you may no longer be welcome.

[+alexrudd]

Actually, the answer was, "Here's this new function in Pocket Queries that will include the archived caches that you've found".

 

That's not exactly a NO!

That's only for one special Pocket Query, and doesn't help me identifying old ones from my offline database. Right now I have to go through any caches that are likely archived and manually go to the webpage and check, then download the individual .GPX. Apparently that's the price the servers have to pay since I'm too stupid to know what "archived" means and would go run out looking for archived caches on private property.

[+bwmick]

sad truth is I am more likely to go where I am not wanted by not updating them in the PQ's. I still collect the data from GS but like the functionality of GSAK. my problem with just doing a write over of the GSAK database is that it reduces the number of logs I can view when in the field (paperless and all that.)

Edited August 28, 2006 by bwmick

[+Stunod]

sad truth is I am more likely to go where I am not wanted by not updating them in the PQ's. I still collect the data from GS but like the functionality of GSAK. my problem with just doing a write over of the GSAK database is that it reduces the number of logs I can view when in the field (paperless and all that.)

 

You can use the LAST GPX date field in GSAK to filter out any caches that did not update with your most recent GPX file...thus removing archived caches from your GSAK database.

[+Prime Suspect]

Actually, the answer was, "Here's this new function in Pocket Queries that will include the archived caches that you've found".

 

That's not exactly a NO!

That's only for one special Pocket Query, and doesn't help me identifying old ones from my offline database. Right now I have to go through any caches that are likely archived and manually go to the webpage and check, then download the individual .GPX. Apparently that's the price the servers have to pay since I'm too stupid to know what "archived" means and would go run out looking for archived caches on private property.

Why do you have old cache data in an offline database? I've never understood this. Last week's pocket query is about as useful as last week's TV Guide. I throw both of them away when they're out of date. That way, I don't end up with out-of-date info in my GPS.

[+bwmick]

Your right, the difference is that sometimes having old logs is useful, you know when someonee 10 logs ago posts new coordinates that have'nt been put into the top of the cache page yet. gsak adds the new PQ logs to the ones it already stored, making it a useful tool when used with cachemate. Lots of logs lots of stuff to look at when you are sitting at a cache site saying to yourself, HUH. I get why TPTB don't want to list it in PQ's they are the listing service and if they made it too easy anyone could have a web site with all the latest information on it. however from my way of caching it makes it a little tougher.

 

bryan

[+Fish Below The Ice]

Why do you have old cache data in an offline database? I've never understood this. Last week's pocket query is about as useful as last week's TV Guide. I throw both of them away when they're out of date. That way, I don't end up with out-of-date info in my GPS.

What bmwick said. Also, I'm trying to do my bit to lessen the load on GS's servers: rather than running a whole set of PQs every week to cover the area that I'm interested in, I laid down a baseline of all the caches in the area and run a weekly PQ that gives me only caches that have changed in the past seven days. This means I'm running only a couple PQs each week rather than the half dozen or so it would take to get the same list of caches from scratch every time.

 

dave

[+robert]

Also, I'm trying to do my bit to lessen the load on GS's servers: rather than running a whole set of PQs every week to cover the area that I'm interested in, I laid down a baseline of all the caches in the area and run a weekly PQ that gives me only caches that have changed in the past seven days. This means I'm running only a couple PQs each week rather than the half dozen or so it would take to get the same list of caches from scratch every time.

How many caches do you need to receive at one time? People keep using the server load issue, but I can't think of a time when I've needed any more than one or two PQ's for a day of caching. My GPS won't hold over 1000 (minus the waypoints I have in there for waymarks, etc.) which is 2 PQs. Even then I can't find 1000 caches in a day.

Edited August 29, 2006 by robert

[+bwmick]

edited for snarkiness

Edited August 29, 2006 by bwmick

[+fizzymagic]

Last week's pocket query is about as useful as last week's TV Guide.

While I agree with you for the most part, there is one thing that last week's PQ has that this week's does not: logs.

 

The limit of the most recent 5 logs, together with the proliferation of useless cut-and-paste logs, frequently means that important information about the cache is missing from the PQ.

 

Of course, in my opinion, that's not a sufficient justification for inclusion of archived caches in PQs.

[+robert]

you all are right.

 

please, please please post explicit directions so I can do things the way that you do as I have seen the error of my ways.

 

not so sincerely

 

bryan

 

2 minute search of the GSAK support forums provided this thread, but looks like there are other threads about it over there. I don't suggest turning this into a GSAK support forum though

 

Glad to be of service!

Edited August 29, 2006 by robert

[+alexrudd]

sad truth is I am more likely to go where I am not wanted by not updating them in the PQ's. I still collect the data from GS but like the functionality of GSAK. my problem with just doing a write over of the GSAK database is that it reduces the number of logs I can view when in the field (paperless and all that.)

 

You can use the LAST GPX date field in GSAK to filter out any caches that did not update with your most recent GPX file...thus removing archived caches from your GSAK database.

...if you don't use the [ ] updated in the last 7 days option to save space, time, and processing power....

 

I agree with bwmick: not including archived caches actually makes it easier to go for them since I don't have the updated information.

 

If it's that much of a concern (and I still don't understand why), why not just delete the coordinates from the archived caches in the PQ's? That would help those of us using GSAK to clear out stale caches AND people wouldn't go hunting after archived caches.