|
Post by fuzzybelly on Jun 28, 2013 10:29:55 GMT -9
Is there any cacher etiquette rules to follow as to how long potential cache GZ's can be held with groundspeak while a cache page is being worked on? In addition, is there a limit to the number of held spots by a single cacher who might be working on a number of them at once.
I could see this holding up other potential hides that are ready to be published.
|
|
|
Post by GreatlandReviewer on Jun 28, 2013 13:31:48 GMT -9
The answer to both questions is there is not a formal Groundspeak limit to how long a cache location can be held for development or the number of caches "reserved" by a cacher. As a courtesy, Reviewers will hold a location at a cacher's request while they develop the cache page or a multiple cache project. One month tends to be the norm, but some projects stretch out longer. Puzzle and multi-cache development are two specific examples where requesting that a location(s) be reserved so the puzzle or final stages can be developed around the final location without running the risk of having to redo the puzzle or rework the cache page because a new cache is placed in the middle of things. Cachers developing a cache series or wanting a cache published at a specific time on a specific day can also request that a location be reserved. Cache series (like the USFW Blue Goose Chase) take time to develop and a cacher could be chasing their tail trying to place all their caches ahead of other cache hiders. When cachers request a specific day/time publishing, the cache page is reviewed per the guidelines, locked, and put in the publishing queue. Subsequent caches placed too close to these locations will be flagged for proximity errors. This very rarely happens. The process for reserving a cache location is described in the Reviewer's Corner of the May Newsletter which may be downloaded from the GeocacheAlaska! newsletter archives.
|
|