Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

Add list of archived caches but still available

–3 votes
What about creating list of archived caches that are still on position and available?

I think it is easy to filter it becase there is lot of cases where cache has "archived" log but after that date comes new and new FI logs. In most of cases owner archived cache but dont't remove box.
asked Jan 10 in Feature requests by drobec (3,090 points)
edited Jan 10 by drobec
I don't think it would work. People fight for every point, archived or not. Who do you think would be cleaning these old caches? It is responsibility of owner, but other cachers still leave it as they found it for the others.

3 Answers

+4 votes
My guess is Groundspeak would frown upon a tool which is designed to encourage people to find archived caches. One of the reasons caches are archived whilst the box is still there is if the landowner has complained and having cachers continue to find the cache after the small issue has been resolved may turn it into a much larger issue giving Geocaching bad press and making other relationships harder.
answered Jan 10 by mole125 (17,830 points)
–2 votes

I think that this list could be good tool for community or better for reviewers as they  could ask local people for adoption or removal of box (if original owner is so irresponsible and left box somewhere hidden).
Three or four years ago we've found during event cache (glass jar) that was more than 2 years archived and people loged it normally

answered Jan 10 by drobec (3,090 points)
Groundspeak rules state that they won't unarchive caches for adoption.
+4 votes

I think that that would be a bad idea. Archived caches are usually archived for a reason. As some of the others have mentioned, sometimes it is very much not supposed to be found after it has been archived.

Groundspeak has one more level of sanctions to prevent people from logging caches that are long gone: They can be locked as well. When a cache is locked, no further logs can be added to it. It is not typically mentioned on the cache page itself and is only made visible to those who try to add logs to it.

The locked state does not care whether you

  1. Found the cache well before it was even archived (if for instance you are behind on your field notes) or if
  2. Have just recently discovered that there is a cache that you simply have to have and thus went ahead and logged. 

Locked means locked - for everyone. Any list such as the one suggested here would increase the amount of logs that archived caches get. That would very probably lead to an increase in locked caches, which would not only hit the second category above, but also the first.

For further reference on the concept of locked caches there is some context here - a forum thread in which I complain about not being allowed to log a webcam cache that I had ample documentation for having found back in 2013 - to no avail, I might add.

There is another reason to not list archived caches: Sometimes there are regrets. The cache owner may regret having published it and the rewiever might do the same. That may happen if for some reason adequate landowner permission has not been obtained or if permission is revoked - or that the searching cachers destroy some delicate nature or historical landmark. In those cases there is a wish to get the cache off the grid as soon as possible. Unfortunately, once a listing has been made public, it can only be archived (and locked) - its publication cannot be revoked.

In that case, there is no interest on the part of whoever wanted it archived to have it listed anywhere. It should remain that way.

answered Jan 10 by Funky_Boris (5,260 points)
That's a very good summary of the situation.

As a side note it is actually possible for a cache to be unpublished and happens occasionally - but generally it is a very bad idea as it makes the log for anybody who has logged it disappear and so no longer apply in stats, count towards challenges etc.