Groundspeak has published an update to the Cache Listing Guidelines as of 21 February 2007. The update provides clarification on current guidelines as well as additional flexibility for the cache hider. Please remember to review these new guidelines before placing a cache.

There is also a summary and discussion in the Groundspeak forums.

However the main benefit  to come out of this, in my opinion, are the revisions to the Cache Saturation rules where it states:

"The cache saturation guideline applies to all physical stages of multicaches and mystery/puzzle caches, as well as any other stages entered as "stages of a multicache." The guideline does NOT apply to event caches, earthcaches, grandfathered virtual and webcam caches, stages of multicaches or puzzle caches entered as "question to answer" or "reference point," or to any "bogus" posted coordinates for a puzzle cache. Within a single multicache or mystery/puzzle cache, there is no minimum required distance between waypoints."

The italics are mine. What it means is it is now possible to have caches ranging over an area and as long as the placer does not put a physical container or marker at a waypoint, other caches or waypoints with a physical container or marker can be within 161 metres of that waypoint. Example: Two cachers can use the same sign as the basis of answering a question.

To enforce this, ensure you use the correct waypoint type when creating the cache. The reviewers have an automated tool that shows minimum distances and this now exempts these waypoint types. Of course this will not work if an older cache does not have its waypoints listed as the correct type (or at all) and if you run into this issue, either politely (remember our ethics) ask the cache owner or one of the reviewers to sort it out.

Conversely, if you have a multi or puzzle cache with incorrect waypoint types (or none at all), please review the caches and post the waypoints. Remember that waypoints do not have to be visible to cachers - they can be set to be visible to the cache owner and reviewers only.

An interesting point in the same area of the rules is that the statement "The reviewers use a rule of thumb that caches placed within .10 miles (528 feet or 161 metres) of another cache may not be published on the site. This is an arbitrary distance and is just a guideline," has not been changed. This implies that there are grounds to bend this rule under some circumstances. The word may is not will. It is even spelt differently. See the link below about downloads for other cachers interpretations on this. It would have to be an extremely convincing arguement in NZ though I think. It is interesting to see a legal definition of the word may which might surprise many.

There are also other changes. My summary is:

• Clarification that a log has to be signed.
• In the interest of file security, caches that require the downloading, installing or running of data and/or executables may not be published (see a rather heated discussion here).
• Cannot solicit (expanded from non-commercial).
• Cannot require an account to be set up on another website as a requirement to find a cache.
• Off Limit caches have had their definitions update to reflect an international audience.
• ALR's (Additional Logging Requirements) only apply to Mystery/Unknown cache types.
• Earthcaches are re-listed as approved cache types. By the way, the cache saturation guidelines don't apply to these.
• Virtual cache finders have to prove they were "physically at the location," instead of  they were "really there."

As always, any change will cause both outcry and approval. Just remember that if you have a new type of cache or one that pushes the boundaries, to discuss it with the reviewers prior to any attempt at publishing it. Failing any agreement there, see the top of the cache listing guidelines where Groundspeak lists options. Remember that there is a big world outside of NZ and thinking outside the square to expand the game is always good. 

Kiwicaching will always assist in obtaining permission from landowners and relevant agencies for cache placement. Send a Private Message if you are having issues and we will see what we can do from our (expanding) list of contacts.

Happy Caching.

Discuss this article on the forums. (0 posts)