RaeRae7133

Palmetto, I think you're dead on Out of curiosity, what tools do you use for coord checks?

Not looking for any one to have to archive their caches - I was just suggesting an alternative idea to the proximity guideline. If you took my post to mean otherwise, I apologize for not being more clear I've got a decent number of finds under my belt, but it's difficult to know the placement of a final stage of a puzzle cache - I certainly don't think a cacher should have to find all the caches in an area before placing one. I totally understand the reasons for the proximity guideline, but it does make it difficult for newcomers to join in the fun - would you disagree? Perhaps Groundspeak could develop a tool to help hiders better identify nearby caches - ie, place your coordinates for the new cache, it lets you know how close other caches (including multi and puzzle caches) are from this location)?

The Cache Owner of the nearby Multi that you're having problems with on your two Listings has 6 caches Hidden. What exactly would you put as the upper limit? That particular cache owner I think is fine. I'm looking at areas like in San Francisco, where one cache owner has basically taken over the whole city

Definitely reason to get frustrated You find that perfect spot, you develop hints and a description based on that spot, and it's 5 darn feet to close to another cache. This has happened to me with each of the 3 caches I have tried to hide. I've done research, mapped out the other nearby caches, but the darn puzzle ones get me each time. The proximity rule doesn't seem to always work. For example, in downtown San Francisco, there are TONS of unique and awesome places to hide caches - always a challenge (especially because the building make GPS signals difficult to get). So that little tiny log-only cache stuck in a planter prevents anyone else from hiding anything. Living in a densely cached area makes it hard to participate in the other side of this hobby. Sure, I could go out and hide it far away, but the chances of me being able to maintain that are much smaller. Instead, I would love to see a rule that limits hiders from placing too many caches within a certain area. Seems like a cacher takes over an entire city near me and makes it hard for anyone else to participate.

This hobby is getting awfully frustrating to me. The proximity guideline is just that - a guideline. Not a rule. I've been working to create unique caches with fun and challenging hints, only to be told that they are too close to another cache. This is my 3rd attempted hide that this has happened to. I'm sorry to say that this totally ruins the fun of the hide for me. You want to hide something in a place that you can easily maintain, that you put a lot of thought into, etc. But when it's maybe 5 feet too close to another cache - come on! I guess I'm going to stick to just finding. This is so disappointing, and I wish it wasn't like this.

We like to choose a different city each time we go out caching. I run a PQ for no micros, active caches, then I print out the map. We usually take the driving path that makes the most sense, although we try to hit the longer hikes first so we don't get lazy!

By request, here are pictures of my spiders If you do any geocaching in Northern California or Minnesota, you may find them!

I leave hand made beaded spiders in each cache big enough to fit them. It's fun to see them mentioned in a user's log!

I like having a record of all the caches I find - I have a display case with trinkets from all the caches I've found. For that reason, I don't really like microcaches. It's fun to find them wedged into small places, but I take a lot of joy out of finding a little trinket and leaving a trinket. I also really love swapping travel bugs, so I generally prefer larger caches.

This is obviously racially and ethnically objectionable.And the cache owner should delete it.Really? So if ANY person objects to ANY posting in a log, the cache owner should delete the log? If I read and object to something you wrote in your last Found It log the cache owner should delete it? Suppose I was a HUGE fan of the Carolina Panthers, and I objected to this log because in my interpretation the panther shirt worn by a gorilla makes the team look bad. Should that log be deleted too? I think that's the problem with the TOS, it's a little too open to interpretation, if you ask me. But if you read the TOS literally then yes, that post could be deleted. It would be nice to add an addendum that was something like "However, cache owners retain the ultimate right to decide what is appropriate in their cache."

If your read the TOS, this definitely is in violation, and that's basically what this argument comes down to.

We used to live in Sunnyvale, but now we live in San Mateo. Welcome!

There's a great little underwater cache near Foster City, CA http://www.geocaching.com/seek/cache_detai...de-9f82a03c0138

I usually pick a few caches, and then plot them on Google Maps. (We try to explore a new city each time we geocache). We depend on the print out of Google Maps to help us get to the general vicinity, then we use the compass on our iPhones to help us get directly to the spot.