Putting together a lot of rules about how long a cache should
remain hidden is going to discourage a lot of people from the hobby
because one of its attractions is that it is simple and relatively
rule free. And you'd need a lot of rules to be fair, because there are
a lot of different situations.
The rules for when a cache should be removed should be simple, and
situation dependent. In order from most to least important:
1) If the property owner/manager wants the cache removed
2) If the cache is causing environmental damage (usually due to the
way people are hunting it)
3) If the owner isn't maintaining the cache
Wanting to remove a cache because you want to seek a different cache
in the same park is like asking someone to move out of their house so
your buddy can move in. It's fine if the owner volunteers. It's rude
otherwise.
> It's fine if the owner volunteers. It's rude otherwise.
I couldn't agree more. I plan many caching trips long in advance,
perhaps months. There a a limited number caches near my home so I try
to plan a trip (be it a day trip or longer) to try to cache in one some
hides farther from home.
I base which ones I will go after on the existing logs. If the logs say
it is a must find, then it is on my list. It just may take me 6 months
to get there. I would be very disappointed if the owner moved it from
the spot everyone enjoyed, just for some silly cache expiration rule.
>Wanting to remove a cache because you want to seek a different cache
>in the same park is like asking someone to move out of their house so
>your buddy can move in. It's fine if the owner volunteers. It's rude
>otherwise.
That's actually a brilliant way to look at it Marty since I pay for my living
space.
Parks are meant to be shared..... step aside buddy...
>step aside buddy...
Just for shits and giggles I measured my apartment and it turns out I'm paying
$1.50 per square foot per month.
My apartment has people above and below me so the actual land being used is less
but we'll dismiss that for now.
If you allocate an 1500 foot radius to a cache, than you've basically said that
other cachers can use this only once. (Yeah they can toss a frisbee in the area
but this isn't alt.rec.flying-disc)
That's 4700 square feet.
It's not developed land, and they're not storing all that much there so I'm
thinking they should pay 1% of what I do. (per square foot)
That's $70 a month
You may be on to something Marty!
You try taking a camp site away from the guy who got there first.
But remember, it's a federal offense.
Eric O'Connor wrote:
> If you allocate an 1500 foot radius to a cache, than you've basically said that
> other cachers can use this only once. (Yeah they can toss a frisbee in the area
> but this isn't alt.rec.flying-disc)
What rule says says you have to allocate a 1,500 ft radius to a cache?
I've found caches that were 100 feet from one another, placed by
different people.
There isn't one, although in various areas, local etiquette seems to
suggest that caches be at least a certain distance apart.
It's the result of one of those taste issues that geocachers will
never agree on: how hard should you have to work to get at multiple
caches?