Page 1 of 1

Rookie Placement

Posted: Sun Sep 07, 2014 8:35 am
by Tmsr
While there are online guidelines for placing caches, and recommendations on the website that you find at least 20 caches before hiding one. I'd suggest that reviewers might look at considering some sort of minimum experience level before publication.
We all started off with no experience, and it's great to see more people playing the game, but frequently one goes to a rookie placement wondering if co-ords will be semi-accurate or the container concealed in some way. I do think that never having found a cache and being accepted for publication could prove a waste of reviewer's and geocacher time.
Classic example is http://coord.info/GC5AG5N where an experienced cacher found something on the ground a month ago (FTF! or will it be an OTF!?) and it was disabled and not replaced to date. Significantly, the owners have still not registered a geocache find so might not be too inspired about suitable containers or locations...
It's great to see new geocachers in the field - after a match nearby, the senior geokid spotted a pair lurking near a cache of ours yesterday and we were able to assist them, and in due course they'll find locating (and possibly hiding a geocache) a more easy proposition. Might it be worthwhile that Groundspeak introduces a reviewer requirement that at least a minimum of 3 geocaches be found before becoming a CO?

Re: Rookie Placement

Posted: Sun Sep 07, 2014 11:30 am
by fitzet
A previous, and similar, discussion.

viewtopic.php?f=20&t=3415

For what it's worth, I agree, X finds before publishing first cache.

Re: Rookie Placement

Posted: Sun Sep 07, 2014 7:28 pm
by tramyard
Similar story here http://coord.info/GC4GY8F

Re: Rookie Placement

Posted: Sun Sep 07, 2014 9:09 pm
by dino
Not in the guidelines so we are unable to enforce a rule like that here without global support. I think HQ have considered something like that but decided not to proceed.

To be honest I've seen some shocking bad placements by COs with hundreds of finds! You also have the problem for someone who caches as a team but wants to place on their own.