Sadie

I would refrain from "touched" with the use of this TB otherwise... <user name> marked <travel bug name> <user name> handled <travel bug name> <user name> saw <travel bug name>

The reason this started is because a cacher did not have the cache approved because the guideline was "too vague". Based on the other thread, the cache was about 400 feet away. I was listing the reasons why a cacher would place a cache near another cache. Am I wrong in the assumption that this is the reason this discussion started? As I think about it, perhaps this debate should be over the use "arbitrary". It seems pretty common that folks misunderstand it's usage and it is constantly having to be explained. If the guideline said "Although there is no specific technical reason for this distance, .10 mile (528 feet) does make a good seperation between caches to prevent saturation" or something like that.

Now thast this is a seperate thread... Before going into the reasons that the guidlines are incomplete as to why the list of exceptions are not more eloabrate, should we first My ideas on the main reasons caches are placed too close. 1) Cacher doesn't know the other cache was there. - Premium member only cache nearby and cacher isn't premium member. That's understandable - Part of a multi the cacher has not completed yet. - Cacher did not check prior to placement. 2) Cacher knew the other cache was there - forgot. - didn't care. Guidelines are for other folks. - thought it should be good enough. What other reasons are there? Cache is too close because the guidelines do not suffeciently elaborate on the conditions that allow it? I'm not sure about that one.

I can't wait until then! In the meantime, I can kick puppies. grrr....

Since I do not have opposable thumbs, I can't open an ammo can or plastic storage boxes. Having these locations does make possible to leave my "signature' without messing up the cache location.

Woof! Woof!

Woof!

I think this one is the cutest.

As the caveman suggested, here's the link to caches along a route. A lot of it involves Pocket Queries, which are a premium member benefit. Otherwise you will need to pick and chose the caches along the way. Good luck to you!

I would be very hesistant on a blanket statement that the entire geocaching community is paranoid about glass containers. Sure, there are a few places that they are acceptable contaners, and few that they may even be the best container for the location. They may not be as durable as an ammo can, but not all coountries have the availability of ammo cans that we enjoy here. Also, clear containers have a (slighly) lower chance of being destryed by a bomb squad. - woof

Woof!

The problem with the current guidelines, as Yamahammer and I see it, is that garage sale gatherings ARE okay technically. If it doesn't have to be "about geocaching", the event can be about just about anything, as long as only geocachers are there. I personally agree with GrnXnham. I'm cool with just about any event, as long as the details are clear on the cache page and I can make an educated decision about whether it's the event for me. But if there is going to be a regulation, I think it should be on the side of event CONTENT. If you're going to not allow a "kind" of event, it should be the Geo Bowling and "Smack n' Chat " that go, and retain intrinsic caching/outdoor activity sort of affairs. From the guidelines: When you have your "Monthly Geo ChowDown at Dennys", how do you ensure that the primary attendees at the restaurant are actually geocachers? These events seem to go against the spirit of the "law" way more than caching expedition trips. Am I to understand that every time a cacher waves hello to someone that it should be an event? Woof