Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

When does a geocached area become "saturated"?

+0
−0

The 161m (0.1mile) rule in Geocaching is a pretty infamous one. However, the rules also state this:

Please don't hide a cache every 600 feet just because you can. The two main goals of the saturation guideline are to encourage you to seek out new places to hide caches rather than putting them in areas where caches already exist, and to limit the number of caches hidden in a particular area, especially by the same hider. Groundspeak may further restrict cache listings in areas where cache saturation becomes a concern.

So when exactly does an area become saturated and need further restriction? I've come across lots of areas with caches every 161m or so, some ridiculously riddled with caches. Is there any example of this rule being put into practice?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

This post was sourced from https://outdoors.stackexchange.com/q/1374. It is licensed under CC BY-SA 3.0.

0 comment threads

2 answers

+0
−0

It's probably a very subjective measure, but I think that the area is too saturated when I spend more time searching for cache as walking to other location.

For bicycle cachers it may be a bit else, but after finding 5 caches 500 meters from each other (5-6 minutes walk) I want to skip the next and simply walk half an hour without thinking and looking around.

However, if I have to walk an hour to next cache (4km or more) I think that there are simply too few caches.

My text applies to forest areas, but this is where I like to cache at most.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

This post was sourced from https://outdoors.stackexchange.com/a/3574. It is licensed under CC BY-SA 3.0.

0 comment threads

+0
−0

This is highly subjective, but I'll give it a shot.

Let's take a site of local significance, like a statue or memorial. All in all, only one cache is "needed" to "cover" this area. More caches will just be for people wanting to: A) Find more caches for the sake of the numbers, B) Hide more caches for the sake of numbers. Of course, this is not a "wrong" way to go geocaching, but having ten caches close up to one cathedral is probably too many, because they don't add anything new; they are just yet-another-cache for this area.

Encouraging people to hide their caches in different, unique and lesser-known places is a good way to make people see an otherwise unknown place. Putting a limit on the density of caches "forces" hiders into thinking of the well-known spots and instead be more creative in their search of a good spot.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

This post was sourced from https://outdoors.stackexchange.com/a/1380. It is licensed under CC BY-SA 3.0.

0 comment threads

Sign up to answer this question »