Not readily seeing this scenario already submitted in the forums, but may have missed it.
There has been extensive debate regarding quality vs quantity of caches and the reasons why cachers hunt/hide caches. Quality cachers gripes generally narrow down to the inability to readily identify the unique types of caches they are seeking or getting their own caches to stand out from the masses. Numbers cachers generally don’t want additional placement restrictions or burdens to slow down cache placements.
My suggestion below would build on the existing attribute system. This would add one question to the cache reporting form or to the attribute form, with a generic default for those who don’t want to bother with the system. This would allow the CO to declare a primary attribute indicating why they chose this location to place a cache and allow seekers to narrow down their search list to the types of sites/caches they are looking for. Based on the “When you go to hide a geocache, think of the reason you are bringing people to that spot. If the only reason is for the geocache, then find a better spot." – (Briansnat) perspective, I’d prefer it to be on the cache reporting page to encourage cachers to more actively think about their placement location.
The question I would add is – “I want to bring other cachers to the center of this 528 foot circle because it is” – followed by the dropdown list below
• a Unique scenic view*
• Historically significant
• a Physical challenge to get here
• Critical to my puzzle solution
• Critical to the cache name/theme
• Kid friendly*
• Educational
• Culturally significant
• a Quickie/Park-n-grab*
• In an area that needs more caches (just say so. Locals may take time to find it, but travelers through the area may opt to skip this in favor of a more unique site)
• Undeclared/other (suggest explaining on cache page)
Asterisked selections above are the only reasons that have established attribute symbols. The default would be “undeclared”, so that the process won’t hold up CO’s who are in a hurry and don’t want to take this time consuming extra step during the submission process, or for CO’s who don’t want their cache relegated to a specific box. Existing caches would get an “undeclared” until the CO updates it. Additional dropdown choices could be added if other placement reasons are noted.
This primary attribute should show up on the cache page as the first attribute, in a different color than black. It be searchable in the PQs separately from the overall attributes. Caches should be distinguishable (ie color coded) and selectable (shutting off the ones you’re not interested in, the way cache type currently is) on the mapping.
Incorporating these additional attributes into the existing attribute selections would not be much help. Running a PQ in my area specifically including the “scenic” attribute yields numerous caches for which it would be a stretch to consider scenic at all, let alone be the primary reason for going there.