My qualifying caches for 1 year plus
My qualifying caches for 6 months to a year
How to find a qualifying cache
These challenges require you to find a cache that has not been found for a defined period of time, usually, but not always, at least a year. I am slowly compiling a list of such caches within the UK and further afield. They are:-
There are individual variations amongst the above caches. For example, some require that a cache used to qualify for one of the above challenges may not then be used as the qualifying cache for any other similar challenges. Some require that the find of the qualifying cache (i.e the cache being resuscitated) be on or after the publication date of the challenge cache.
If you know of a similar cache that is not listed above, please contact me, BaSHful, and I will add it.
To all owners of Resuscitation caches: Please feel free to link to this page.
Top of page
|27||16/01/2016||17/03/2017||426||3.0||2.5||View||footsore & weary|
|28||07/02/2016||17/03/2017||404||2.0||2.0||View||Mr Jimmy O|
|33||14/03/2015||28/06/2017||837||1.0||1.5||View||Dhinged & Bracketed|
|43||30/09/2016||18/10/2018||748||3.0||2.0||View||Mr E Seaker|
Top of page
I've identified over 60 qualifying caches, including those above, but just list a few of the recent ones below (as at late July 2012).
Top of page
I.e. Identify a cache that you've already found that already qualifies.
This is a possible route to go, though it does have some issues and is unlikely to produce a 100% result.
First you need to be a GSAK user.
Next you need a "MyFinds" database loaded with a "MyFinds" pocket query.
You now need to capture the found log immediately prior to yours. This is the tricky bit. (I believe it is impossible to capture that specific single log.) Trying to capture all logs, unless you have very few finds, will take a very, very long time because of the API restricts how many you can get per hour. Your best bet is to use the "Refresh cache data" API and capture the last 30 logs for every cache you've found. If you have more than 6000 finds you will need to break it down into chunks of 6000 or less and do on successive days. Note: If there have been more than 28 finds of a cache since your find then this method will not capture the necessary log. However, if there have been that many finds then this is not a likely candidate for resusciatation.
Finally, you need to download, install and run the LonelyCaches macro. Note: You are likely to get a message saying that the macro contains deprecated commands. At the time of writing (23/02/2013) the macro still functions. It may not in the future.
Please contact me, BaSHful, if you can suggest any improvements on the above or have an alternative way of identifying qualifying caches.
I.e. Identify a cache that you hav'n't found but which if you do provides you with qualification.
Here you are in luck. The web site Project GC will identify all possible candidates (and it does much, much more than this!). If you have not already done so, you must register with the site, giving them your GeoCaching name, for it to work for you.
Once registered, in the black bar across the top, click on "Maps" and select "Not found caches" from the drop down menu. Select cache location to suit you. It will accept just a country or you can restrict it to a region and/or county. Alternatively, add the "Center/radius(km)" filter and use that. Most important is to add the "From" filter. This is where you put in a date of one year ago (or six months ago).
The output is a map followed by a list of all the caches identifed. By default the map shows caches you've found with a smiley face. These can be turned off by hovering over the stacked sheets symbol at the top right of the map and unselecting "Found". Your own caches are shown with a star (and can't be turned off).
Beware the page will also display caches that have never been found. Also the web site is never fully up-to-date so always check on the Groundspeak site to see if a cache has been logged in the last few hours or days
Top of page