Cache O'Plenty

Fill your container with rocks to help weigh it down. Then it won't pop back up. Then remove the rocks when dry.

I just worked on part of the Route 66 series yesterday. We had a find rate of over 60/hr for the first couple of hours. It then dropped a bit as we were also picking up any non-Route 66 caches along the way. Found our first cache at 6:39 am (sunrise) and our last at 5:35 pm (sunset). Total of 473 caches (avg = 43 caches/hr). So, yes, it can be done. Friend of mine did the Route 66 in one day. Total of 806 caches. 6:00 am to midnight (44.7/hr). Record for one day is much higher than that though.

I have a personal stamp (online for <$15) that I use for all but the smallest logs. You can read it. My handwriting, not so much! My caching buddy and I also have a stamp with both names for when we are caching together. I used labels in the past but didn't like that they take up so much room and don't adhere very well. Don't like business cards (the signature isn't on the log anyway) as they just take up too much room in the smaller caches and get wet, etc. I've seen signature items (tokens, hand made items, etc.) but the signature should still be on the log.

We wish we had your problem here in the US. Our trains don't go "high speed".

OK. Forget the "justification" issue. I do like the "warning" idea, let's just start with that idea. The cacher can then just confirm that they intend to log it a second time. There have been many times the unintended double log has caused sometimes significant research by cachers to find the extra log. Especially new folks. Just look at the number of forum questions on the topic. Just make it so the default is that a cache can only be logged once unless some positive action is performed to confirm it. A cache could be coded by the CO to allow it, as an idea. Fixing the "app" infers there is a problem with the app. If multiple logging is allowed, then the app is working properly anyway. It just doesn't poll the database and issue a warning of a duplicate log. But, then we are back to the initial problem of no warnings of any kind.

Understand that there are some ancient reasons for logging multiple finds for the same cache. And, there may even be a few current reasons (I can't think of any). But with the advent of smartphones, the number of duplicate Found It logs has greatly increased. And it isn't readily apparent to the cacher that his phone double(or more) logged it. Perhaps it's time for a programming change..... Identify all new caches as "Single Find Only". Then allow the CO to trip a switch during the cache page development stage to allow this to be bypassed with justification to the Reviewer. That way, those smartphone submittals would only show up once. The default should be "Sigle Find per cacher". Perhaps a message could be generated to the cacher whenever a duplicate log is submitted. In the meantime, lets get the "delete log" page to include a comment to the cacher that explains why his Found It log has been deleted. Has been asked many time but never implemented.

If you're concerned the reviewer will use the info to solve the puzzle and thus go out and grab the cache, remember that you are already supplying him with the coordinates to the final anyway. I believe, as most have said, the requirement is there to demonstrate that the puzzle is solvable and doesn't violate any guidelines.

The special "My Finds" query does not count toward your 5 PQs per day limit. You are referring to the button at the very bottom of the PQ page, right? If it's grey, then you ran it within the last 3 days. Otherwise, it should work.

I second this one! It's just the proper way to do things.

We see a lot of these types around here. Generally, they are either electrical outlet boxes or just the cover plate attached with magnets. Both are OK to me as long as I don't have to use a screwdriver to remove the cover plate. If it doesn't come off using a fingernail I assume it's a real box and I look elsewhere. Depends on the location of the box, of course. If it's mounted on a tree in the woods, then I know it's not "live". But if it's on a light pole or transformer box that's active, it's the fingernail test.

We don't do that here. We allow the true FTFer to find it and claim the FTF. We do what we call "beta testing" where we don't watch where the cacher hides it. We then get the coordinates from him and use them to "find" it, as a test of the coordinates. Since we most likely see the container and kinow roughly where he is hiding it, we don't think it's appropriate for us to claim a FTF. After the FTF is claimed we go back and log a find if the CO allows it.

the "My Finds" query does not count toward your 5 per day.

There is a Trackable still in it's inventory. Some event owners do not archive the event until the inventory is cleared.

Concur with the other responses. Make them new caches. Only one of them is actually a duplicate of the original anyway. You said the others would be "placed a short distance away from the originals". And one of those isn't even the same container. Yep, new caches = new smilies.

STF? TTF? Never heard of such a thing. Who remembers who came in second in the World Series?

Yes, we always add a new log (carry some in my wallet). We do not remove old logs. If there isn't any room for a new one (i.e. nano cache), we post a NM log. Those nanos require more maintenance.

But don't Challenge caches require that the tasks be Geocaching associated? Such as 100 finds per day, 366 dates of the calendar, one of each type cache in one day, etc.... Notes relative to the history of the site don't seem to meet the "associated" rule, to me. There may a way to work it out though.

If you go to GC.com maps, you'll find that there are two caches in the area but neither are at the stop sign.

Not too long ago I found a $20 bill near a cache. Used it to by the next round for my cache buddies at the next meet & greet. I doubt I'll ever duplicate that experience!!

I would suggest that all of the Cache Owners that have caches in the restricted areas should disable their caches for the duration. Their note on the disabling log should state the reasons and when they will be enabled again. I'm pretty sure the reviewers would allow a long period for these reasons. In effect, the areas affected have become "Temporary No Trespassing" areas.

My wife is a commercial property manager. I've asked her this very question about permission as it pertains to shopping malls/centers. Her response is: I will not give even verbal permission as it then becomes an issue of responsibility. The insurance company will take bigtime objection. And she will NEVER sign an agreement or permission slip. Although she is responsible for the day-to-day management of the shopping center, she is not the owner. I imagine the same applies to Wal-Mart managers - they are not the owners of the property. It even becomes more murky when you realize that the ownership of the various segments of a shopping center can be complicated. The Wal-Mart may own the building but not the parking lot. And don't even bother asking Security! The fewer opportunities for headaches, the better.

You can do it by dropping the coin into the cache and then retrieving it. Two logs. A bit tedious after a while. I'm not sure about the etiquette though for someone else's coin or travel bug. I imagine it's different in different regions. If it were your own coin, that's fine (some do it to track their own travels).

Are you sure that you are logged in? If not logged in, you might not get the actual links.

BTW - Discovered that if you inadvertently delete the actual ignore list, you can have the system create a new one. Just go to any cache and "ignore" it. The system should generate a new "Ignore" Bookmark list if one already doesn't exist. I don't know if it will repopulate the new one with previously ignored caches. It might.

If you use GSAK, you can use the search function (the "logs" tab) and set the parameter to >1 for "found it logs". Others have reported that this will find multiple logs. Might have to set it for a specific person (yourself!).