Saturday, March 10, 2012

FTF Runs - My thoughts

This past week,  a challenge cache was published requiring the finder to find 3 caches in 7 states after the challenge itself was published. The CO's had this to say when he published the cache.

When this cache was published, the intent was to let people who like to explore and travel, have the opportunity to roll it up in this one multi state challenge.

As it turned out, there was an FTF race involving four cachers broken up into two teams. All four shared the FTF. The CO then said....


It never dawned on us that there would be a FTF competition culminating it two separate caching groups taking off at different times and making non-stop six-state marathon runs. As it turned out, one group found the final and went to grab caches, the other grabbed the caches, then went to sign the log. But, believe it or not, they were actually finishing the entire challenge at the same moment!

After talking to both teams, it is really too close to call.

In the spirit of friendly competition, and acknowledging the incredible effort put forth by both teams, they can all claim a Co-FTF.
 

I never was an FTF hound. Hell, I don't even go after FTF's in my own area even though we don't have FTF hounds like the Fox Valley area does. Some caches can sit for a day or two in my area before being found unless a certain cacher with 3 letters and 2 numbers in his name decides to make a visit then just write "FTF TFTC" in the logs, but that's a topic for another discussion.

I'm amazed at what extremes that some people would go to to get an FTF. Big Jim has said he drove 50 miles to get an FTF recently. A cacher in the Fox Valley area waded through brutal cold water to a small island to snag an FTF - in his street clothes - no waders. I thought that was insane. I'm sure he got pneumonia after that.

Then to hear of two teams taking a super long road trip just to claim an FTF???

Please. Now that is insane. At today's gas prices, I just cannot imagine the gas that they racked up along the way.

I still roll my eyes or shake my head when I hear what people will do to get an FTF. Soon as the notification comes in on their phones, bam, they are out the door. No matter what they were doing. I'm sure some were fucking their wives or girlfriends when the notification would come in. They would stop fucking, get dressed, and rush out and get the FTF. That seems to be the mentality of FTF hounds  these days.

I prefer to just take my sweet time and relax and find the cache at my own pace without worrying if another FTF hound is on his way. Most publications are at night when the reviewer is home from work so night FTF runs are common. The problem with night FTF runs is that one cannot appreciate the beauty of nature around them when it's dark out. That is one reason I geocache - so I can appreciate nature when I'm out in the woods looking for a cache.

Feel free to flame me if you want. 

Wednesday, February 1, 2012

My thoughts on Munzees

I just wanted to post my views on Munzees. I'll make it short and sweet. Basically it's a lazy version of geocaching. You find a container containing a QR code and scan it with the Munzee app on your smartphone. That's it. You don't even need to write a log though that option is available.

The one bad thing about Munzees is that they don't seem to have placement rules like geocaching does. In geocaching, the rule is that caches have to be at least 528 feet apart. Munzees just have to be 150 feet apart. However, there is nothing that prevents Munzees and Geocaches from being practically next to each other. I found one Munzee that was just 30 feet away from a geocache that I previously found and that can pose a problem, especially for newbies. Some may not be able to tell the difference between the two. 

Another thing about Munzees - there is no difficulty level or terrain level listed on the page of each munzee. A player has no idea what he is looking for when he gets there. At least with a geocache page, a D/T is listed as well as a cache description, size, and hints.

Munzees are not my thing. Probably never will be, but at the moment, I'm looking for local munzees in my area so I am aware of their locations when I decide to place a cache in the future. I have no intentions of putting a cache near a munzee that is already there. I also will make sure if a munzee is placed near my cache, I'll be sure to make an adjustment by either moving my cache a few feet away from the Munzee or if that's not possible, make sure my cache container does not look like that of the nearby Munzee's. This will reduce any chances of confusement.

Overall my thoughts on Munzees is that I feel it is just a passing fad and will eventually die with time as not everyone has a smartphone. 

Saturday, January 21, 2012

Types of caches I won't do


I decided to start blogging again about my geocaching adventures. 

Today I wanted to re-write about types of caches that I won't do for the most part. I'll talk about cache types as well as cache locations, sizes, etc. I wrote about this in my previous blog, which has since been deleted. I decided to write about this again.


Let's start with cache types. Of my 990 total finds as of today, 900 of them are traditional caches. Just 36 are puzzle finds and 32 are multi caches. The rest are rare caches like events, virtuals, letterboxes, earthcaches and wherigos. I won't get into those right now as I want to discuss puzzles and multi-caches.


Let's start with puzzles. Of my 36 puzzle finds, I estimate about 75% or so are field solves, meaning I gather information off a marker and go to find the final. The other 25% are solved at home. And those were the easy ones like Sudoku puzzles, simple internet searches, etc.

I'm not about  to waste my time trying to solve most of the puzzles listed on the geocaching website as most of them make me go ...





Fuck that. I would rather just grab my GPS and go out the door and go find the caches instead of sitting at my computer and going...




If a puzzle is simple enough, yeah, I'll give it a shot. Otherwise, no. Anytime I download a pocket query, I filter out the blue question marks. Areas like Green Bay and Appleton are so saturated with those, it is not even funny. I'll discuss that in a future post another day. Right now, for me, puzzles are just not fun.


Another type of cache that I try to avoid for the most part are multi-caches. I find one stage that contains the coordinates to the next stage or the final. Those are actually less common than puzzles and I really don't mind doing multi's. The problem with multi's is that I have no idea where the next stage is until I find the first way point. Some multi's require the cacher to drive across town for the next stage. Hell, some stages are across the country. I make sure to read the page before I attempt the cache. If the multi is along the same trail, sure I'll do it. But if I have to go out of my way to get it, I might put the coords in my GPS to attempt the final another time or I'll just ignore it.


When I first started geocaching three years ago, I had a pocket PC with a bluetooth GPSr. The software I was using to cache made it a little difficult to enter manual waypoints. So I avoided multis because of that. Entering multis on my current GPSr, a Garmin ETrex Venture HC, is so much easier. I can enter coords in seconds and off I go. But as I have said, I have no idea where the next stage will take me.


Maybe someday I'll go on a run focusing solely on multi's, but for the most part, I generally avoid those.


Now let's talk about locations when geocaching.


Cemeteries - For the most part, I avoid cemeteries with the exception of Sweetlife's WSQ caches. I just don't think cemeteries should be a geocaching playground. A cache should not be placed in a cemetery just for the sake of placing a cache in a cemetery. With Sweetlife's series, most of them are either just off the grounds or very easy finds. I can grab and go and not attract attention and still take the time to look at some markers.


But when I have to hunt and hunt for a bison tube  in a pine tree next to several markers, that's where the problem lies. I should not have to search for a cemetery cache and I especially should not have to do so next to a marker. Hell, there was one in Manitowoc that has a micro in a pine tree - with 4 gravestones surrounding it. I walked away from that one without attempting to find it.


Cemetery caches is a touchy issue and I believe geocaches in cemeteries are banned in one state if not more. I cache in cemeteries with discretion. If GZ is next to markers or appears to be tough to find, I walk away.


Roundabouts - I have never attempted roundabout caches for the simple fact that it is unsafe and in a super high muggle area. One has to cross the street to get to the middle of the roundabout then try and find the cache while dozens of cars are circling the roundabout wondering why that moron is in the middle of the roundabout looking for something. Personally I feel roundabout caches should be banned, Thankfully I've only had to encounter one such cache and I just drove by it without stopping. 


Intersections and roadside - Most intersection and roadside caches should be easy to find IMO despite the muggle factor. I found a magnetic keyholder under a park bench once in a high muggle area. All I had to do was sit, bend down like I was tying my shoe, and retrieve the container. But if is something I have to search for, I won't bother. I feel like 1000 eyes are watching me if I attempt to search. Based on the D-rating, I'll either attempt it or avoid it. I obviously won't try D3-D5 caches in a high muggle area and I'll at least make a half assed effort in D1-D2 caches to determine if it is something I can still find despite the muggle factor,


There was one cache in Gillett hidden inside a bush - at the side of a highway with several cars going by. I did the half assed effort thing and determined I would have to do a real search there in order to find the cache. With dozens of cars going past me, I decided against it and just walked away. I didn't even log the DNF.


Pine Tree micros - Whether in the city or in the woods, pine tree micros are tough. But it is even tougher when there is a row of several pine trees standing next to each other and with the typical GPSr having an accuracy of about 30 feet, it could be in any one of them. If I had a team with me, I might still make the attempt. But looking for a micro in 5 pine trees is like looking for a needle in a haystack. Fuck that. I just walk away from that too. I'll still attempt single pine trees though - within reason.


To sum it up, everyone plays the game their own way. I play mine and I just wrote about it. How do you play yours? Feel free to comment below.