Archived Caches
-
- 10000 or more caches found
- Posts: 1067
- Joined: 13 October 03 11:45 am
- Location: Travelling Australia using a Garmin Montana 650T
Archived Caches
Hi All,
How can I run a pocket query (or series of them) in order to determine which caches in my GSAK database have become archived?
Any Type>Any Container>That is not active>Within State Victoria . . .etc does not collect them all.
Regards
Ian
How can I run a pocket query (or series of them) in order to determine which caches in my GSAK database have become archived?
Any Type>Any Container>That is not active>Within State Victoria . . .etc does not collect them all.
Regards
Ian
- TEAM LANDCRUISER
- Posts: 476
- Joined: 04 February 04 9:28 pm
- Location: Port Kennedy WA
- Contact:
-
- It's all in how you get there....
- Posts: 2185
- Joined: 28 March 03 6:00 pm
I don't think you can do it.
I was making a list of archived caches of NSW, but they finally removed my reviewer access just days after starting it, short of maybe politely asking one of the reviewers to make a query on your behalf (which I personally DO NOT recommend, as they both are busy people), maybe if we start a thread - a pinned thead - in each state asking for geocachers to list or to email you the gpx files of archived caches...
just a thought
I was making a list of archived caches of NSW, but they finally removed my reviewer access just days after starting it, short of maybe politely asking one of the reviewers to make a query on your behalf (which I personally DO NOT recommend, as they both are busy people), maybe if we start a thread - a pinned thead - in each state asking for geocachers to list or to email you the gpx files of archived caches...
just a thought
- maccamob
- 10000 or more caches found
- Posts: 915
- Joined: 04 April 03 6:37 pm
- Location: Hoppers Crossing, VIC
- Contact:
AFAIK, Pocket Queries do not include archived caches, only active and disabled ones. The best way I've found so far to identify the archived caches in your database is to upload the latest of each of your pocket queries, then sort your GSAK database on the 'Last Updated' field. You can safely assume that any caches with a "Last Updated' date <i>before</i> the dates of your last queries have been archived. You can then manually 'Toggle the Cache Archive Status' in GSAK for those caches. This method is a bit laborious, but it's also foolproof. If you mistakenly 'archive' a cache, the next PQ you load will fix it. Otherwise, if there aren't a lot of probable archived caches in question, you can check each of them on-line to make sure.
I had exactly the same question, and Riblit showed me this trick...
In GSAK, sort all your caches by last updated, the vast majority will have the same date, IE, the last time you did a full GPX update.
Now, in 99.9% of cases, any cache that has not been updated, is probably offline/archived.
I tried it, it was 100% right for me.
I then visited each one by double clicking to bring up the online page, downloaded and processed the single gpx files for each one and now I am up-to-date. This saw me with another 30-40 archived ones that were not marked as such in GSAK.
In GSAK, sort all your caches by last updated, the vast majority will have the same date, IE, the last time you did a full GPX update.
Now, in 99.9% of cases, any cache that has not been updated, is probably offline/archived.
I tried it, it was 100% right for me.
I then visited each one by double clicking to bring up the online page, downloaded and processed the single gpx files for each one and now I am up-to-date. This saw me with another 30-40 archived ones that were not marked as such in GSAK.
- Team Red Roo
- 5500 or more caches found
- Posts: 375
- Joined: 02 May 03 9:30 pm
- Location: Armadale WA
- Contact:
Maccamob and Riblit are correct (AFAIK), in this being the only way to update GSAK, but I don't think that it is good enough for geo.com to archive a cache without letting us know about it.
I've emailled them today with a new request and several constructive suggestions, on how they might possibly go about it, and at the same time keep processing time down.
I'll post the reply on this thread when I receive one.
Wayne
I've emailled them today with a new request and several constructive suggestions, on how they might possibly go about it, and at the same time keep processing time down.
I'll post the reply on this thread when I receive one.
Wayne
-
- 400 or more spectacular views seen
- Posts: 259
- Joined: 09 March 04 2:17 pm
- Location: N51° 04.195' W115° 22.044'
- Contact:
Hmm a smell a possible feature for GSAK/gc.com.auideology wrote:we can produce an automated list of archived caches
does someone know how they could be imported into GSAK?
gc.com.au could generate a simple xml page with just a list of all known archived caches.
GSAK can then have an option where it goes and grabs that page and checks the current database to see if any of the caches in it are in the list, if so it marks them as archived/disabled or whatever it may be.
-
- Posts: 1329
- Joined: 29 March 03 6:04 pm
- Location: Gladesville, Sydney
- Contact:
I like the sound of the list from gc.com.au solution, but I think the same logic could be built into GSAK, although it's really not far off already (you can toggle archived in bulk after applying an "updated since" filter I believe).
It pays to be wary if you don't always load the same PQ, or if your parameters change. For example, "All of NSW" loaded on Oct 1, then one starts loading "Nearest 100km" instead after that. One might accidentally archive the caches outside 100km just because they stopped getting imported. Even more problematic, and likely, is having a PQ that returns the maximum 500 caches. As more caches are planted, more caches drop off the end of the PQ and may be incorrectly inferred as archived.
- Rog
It pays to be wary if you don't always load the same PQ, or if your parameters change. For example, "All of NSW" loaded on Oct 1, then one starts loading "Nearest 100km" instead after that. One might accidentally archive the caches outside 100km just because they stopped getting imported. Even more problematic, and likely, is having a PQ that returns the maximum 500 caches. As more caches are planted, more caches drop off the end of the PQ and may be incorrectly inferred as archived.
- Rog
here's a gpx file of archived caches: http://geocaching.com.au/gpx/archived.gpx
comments:
- i!
comments:
- the secondary site doesn't like to publish lists of archived caches, so we've had to guess them. the algorithm we use is that if a cache disappears for a couple of days, it's probably been archived. this is quite dodgy, but it's better than nothing. if the cache reappears at any time, it's counted as unarchived.
- apparently the reasoning behind not publishing a list of archived caches was that sometimes the secondary site tells a landowner that a cache has been deleted. so, in this spirit, we've only included the waypoint code, ie no coords, etc. this should be enough to wash against your data to flag the caches as archived. (sadly, the GPX specification doesn't allow for waypoints without coordinates, so we've had to include coordinates but set them to zero.)
- we'd like to put in the archived="yes" tag but it's in the secondary site's private namespace. if we publish more gpx files we will probably use the opencaching namespace provided we can figure out what it is!
- we've tested importing this into gsak, but have no clue about how to merge these with another database and flag the caches as deleted. perhaps clyde can help out here!
- i!
I did ask Clyde about a macro to do just this but he doesn't think gc.com will take kindly to it.Perhaps Clyde can add something to GSAK to scrape this info direct off the gc.com website pages?
I beleive the solution has to come from gc.com, not from us sorting through each cache that hasn't been updated recently on our pocket queries.
Speaking of gc.com, I am still waiting from them to get back to me about my subscription enquiry.. time for a follow up.
-
- 10000 or more caches found
- Posts: 1067
- Joined: 13 October 03 11:45 am
- Location: Travelling Australia using a Garmin Montana 650T