mountainman38

This is a great idea! It would be really cool if all you guys with the hair-raising stories would list what caches you were going for, so we can read other's logs, and get an idea of where they are.

This thread hasn't gotten much love for awhile, so I thought I'd bump it up. I don't have an Amateur Radio license, but I do have a GMRS license. I've enjoyed using my Baofeng dual band 2-way to chat with family and friends, and feel like it would be great for group caching trips.

It has been five years, what do you think you are accomplishing with this post? Helping.

It's interesting that you mention the blue frownie face. I was recently caching up in the mountains where I had no cell coverage. When I saved a DNF log on a cache (using c:geo on my phone), my map showed a blue frownie -- which I thought was really cool. Unfortunately, once I got back in a coverage area and was able to post my DNF, the cache just showed up as unfound again. I was very sad.

The Lederhosen bug needed to be rescued from it's lonely outpost in northern Idaho. I wanted to put it next somewhere worthy, and time has slipped by without me finding a time/opportunity to put it somewhere worthwhile. If the TB owner asked me to move it along, I would.

That's what vacations are for! Washington is great in the summer. You could come out and help me move Mr. Lederhosen into his next home - assuming this state's oldest unfound 5/5 (GC1G5BY) is still there, and we can find it.

I've held on to it for so long because it seems like it deserves a special home for it's next stop. I should have found something sooner, most likely.

I don't know if this question is directly related, but it's bugging me right now. I did T5 cache in northern Idaho a few years ago (GC1F6YC), which took a lot of work, planning, and time (and was a great experience). Because it's only been found a few times, I was surprised to get an email a few days ago stating that the CO was "parking" a TB in it for a friend. What is "parking"? My understanding is that if you want to log a TB into a cache, then it needs to go into the cache (like the one I retrieved from the cache, and have special plans for this summer). I realize it's not a "Found it" log, but I guess I'm a little jealous of someone claiming activity (even the CO) on a cache like this one.

As a selective cacher, I would thoroughly enjoy a place to read about others experiences with difficult caches. These caches might be ones in the middle of nowhere that took a back packing trip to get to, up a mountain with rock climbing gear, underwater, on a remote island, etc. - sort of like the extreme geocaching thing from awhile back, I guess. Since I often use my dual sport motorcycle (when the weather is good) or 4WD truck to get to caches, hearing others stories of such things would be interesting, as well.

Heh?! I'm that unusual? Kinda sad.

It seems that if ones satisfaction in life is found in claiming thousands of meaningless caches, no matter how they were claimed, there are other larger issues to deal with. Then again, I lost all interest in just signing my name to another boring log book after about 100 finds, so this may just be me.

I would strongly suggest that you contact your local reviewer, explain your thought process for your cache placement, and see what they say. It has been a few years now, but I had a situation very similar to yours. I found a great spot for a cache, but it was less than the 0.1 mile minimum from another cache. It WAS across a canyon, requiring a mile or more of hiking to get from one to the other. I contacted my local reviewer, explained my situation, and they told me they would be fine with publishing my cache where I wanted it to go. Sadly, I was not able to put it there due to state park restrictions (I found out my spot was in an archeologically sensitive area), but I was pleased that the reviewer was willing to work with me.

There should really be a "LIKE" button that I could hit for posts like this!

Guess I better find it quickly then!

I'm glad that it's still in play, and think it's a rather nice testament to the responsibility of the community that it's still up and running. I also appreciate the fact that Groundspeak has allowed it to continue, since (from my perspective) there are far too few tough caches like this.

Why would this be exactly, Swineflew? Do you have some sort of sixth sense that tells you these difficult caches, which are very much appreciated by a certain segment of the geocaching community, should be done away with because it causes some controversy with entitled cachers who think they should be able to claim all caches everywhere, whether they can get to them or not? Spare us your armchair quarterbacking.

Actually, it is a community cache -- hence my reason for posting. It's understandable that you wouldn't know the history of the cache, but the CO hasn't found a cache since 2005, so they are not considered to be actively caring for it (don't know how the "Last Online Activity" thing works). Cachers, generally ones with little experience, will periodically go look for this cache, complain bitterly about how unsafe and ridiculous it is, then claim it as a find since they saw it (60 feet or so up a tree). People from the community will let them know this isn't how it works, they will get angry about it, a reviewer will step in to help them see the light and change their logs, and the reviewer will then delete the extra postings. So yeah, it is a community issue.

I agree with this. If it was me, I would delete the rude notes, as well as the fake "found it" logs. A cache page is not a forum thread, and it's inappropriate to use it as such. Mind you, the cache owner should remove that bit that basically said it was okay to write notes: That is a bad, bad thing to put on a cache page...as witnessed by people bashing the cache hide. And, yes, the cache owner can edit the cache page, as well as delete logs. B. Those people bashing the hide should stop their entitled whinging and accept that they're not gonna have all caches plopped in their laps to sign with zero effort. Just got to post a note on a similar hide in Idaho today -- seems like new cachers need to do some more reading of the rules.

This idea sounds great (too bad I'm way too far away to try it)! The one problem I see is with the train. Have you checked to see if trains will actually stop at a specific point along their route to let you off, then schedule a rendesvous to pick you up again? I can see this happening back in the early parts of the last century, but it seems less likely nowadays.

These are my thoughts exactly. I visited a 4.5 star difficulty cache 4 times before I finally found it, and was very proud of my effort. After enough people complained about the cache, the CO changed it to a guard rail magnet and lowered the difficulty to a 1. I think this is really poor form. I emailed the CO to tell them they should archive the cache, then re-publish a new one in the same spot with different ratings. They never responded.

That is an AWESOME cache! I would love to do a tree cache someday -- especially one with a puzzle at the end.

It took me about 6 months of caching to reach this point. Now I generally get caches only if they're somewhere new (new state, for instance), or have some other interest factor. Just getting easy cache after easy cache is like watching the same television program over and over and over, just on different tv's.

I agree with this method. I don't want to be rude and say nothing, but on completely unremarkeable caches I don't feel like praising what isn't there. "Found it" covers it for me.

Okay, what are "your parts"? When I was doing land surveying in the Puget Sound area, I saw a LOT of devil's club and stinging nettle. The devil's club has nasty thorns, but is a very woody plant, so it doesn't offer much in the way of support -- we got a lot of practice slicing it down with machetes. The worst thing about thrashing through the woods near Seattle was the profusion of blackberry vines EVERYWHERE. We literally had to chop paths through the forest with machetes, just to get anywhere. Fortunately, most geocaches aren't placed on property corners, so blackberries shouldn't be as much of an issue. On the east side of the state, we have poison ivy to worry about. I must have rolled in the stuff while looking for a cache by the Spokane river, because I got a raging case of rash from it. The stuff will spread amazingly well once you get it, so be very careful to not touch the rash and then any other part of your body before you wash your hands.

Uhhh... No one. Ever. From numerous accounts I've read through the years, the best you can do is just leave it behind you and hope that in the future you meet officers like Clan Riffster, and not Officer Shades (aka "I'M THE LAW - START WETTING YOURSELF IN FEAR NOW!!!"). That was my point earlier -- even if someone is wrongly harassed/detained, there seems to never be any backlash against the officer/police department. They ARE the law, so who are you going to complain to?