Hiding a Cache problems

[+signseekers]

Hi everyone. We have hidden over 700 caches but often come up with a problem when we first input our coordinates on the Hide a Cache page. If we input coordinates that are too near another cache immediately it comes up with a message to tell us that we need to relocate our cache because it is too near another one. This is great because it saves us a great deal of time. We very rarely get this message because we have already located nearby caches  but it is good to get a message when we have miscalculated.

However what is really annoying is when you hide a cache in a place and its location is ok because there are not other real caches too near. You complete all the details on the Hide a Cache page, have put your cache out in its location and then send it for review. The annoying part is when the reviewer then tells you you cannot place it in the location you have selected because a cache is nearby - not a normal cache but one which is part of a hidden multi stage. I just wish that the part stage caches linked to multis would show up when you input your coordinates on the Hide a Cache page like they do for normal whole caches. The reviewer then has to send it back so we can relocate it. It would waste far less time if the Geocaching  page would flag up the hidden part stages of multi caches when you input your coordinates like it does for the others.  Why doesn't the Hide a cache page flag these part stages? All it needs to say is that there is a cache too near please relocate even if it is a part stage of a multi. Sorry to rant on but it wastes a lot of time especially for our reviewers who work very hard on our behalf. Is there a way round this?

[Keystone]

This is a frequent complaint.  The problem is, if the cache hiding tool told you that a hidden stage of a multicache or mystery cache or Wherigo cache was nearby, then people would use that tool to "battleship" the exact location of a cache instead of solving the challenge designed for them by the cache owner.  If this suggestion was implemented, it would destroy the integrity of all cache types that feature hidden waypoints.

[+kunarion]

1 hour ago, signseekers said:

 All it needs to say is that there is a cache too near please relocate even if it is a part stage of a multi. Sorry to rant on but it wastes a lot of time especially for our reviewers who work very hard on our behalf. Is there a way round this?

 

Here's the info page on how to check for cache saturation: https://www.geocaching.com/help/index.php?pg=kb.chapter&id=22&pgid=199

One other thing I do is ask people at local Geocaching Events, when I see a great spot to hide a cache.  They found every cache in the area.  So they often tell me, "that's a cool spot and on a completely unrelated topic, have you searched for [this particular Multi] yet?"

 

Edited August 9, 2017 by kunarion

[+signseekers]

Thank you  Keystone for this..it is an excellent point to make...I appreciate your advice and reponse.

Edited August 9, 2017 by signseekers

[+signseekers]

Thanks Kunarion for your help and for the link on cache saturation. We are just about to look for the multi.

[+kunarion]

1 minute ago, signseekers said:

Thanks Kunarion for your help and for the link on cache saturation. We are just about to look for the multi.

 

Good luck!

[+signseekers]

Thanks for the replies. You have all answered our query..really appreciate your help. 

 

[+WarNinjas]

We have only had this problem a few hundred times.