Skip to content

Getting to the root of the matter. Traditional Geocache

Hidden : 3/5/2010
Difficulty:
2 out of 5
Terrain:
3 out of 5

Size: Size:   small (small)

Join now to view geocache location details. It's free!

Watch

How Geocaching Works

Please note Use of geocaching.com services is subject to the terms and conditions in our disclaimer.

Geocache Description:


This cache was placed with knee deep snow on the ground so it should be safe to say it is winter friendly but one never knows. Lots of trees down from the ice storm of 2008. Not too far off of the Blue Triangle trail and this area can be accessed easily from the Mid State Trail also. Good luck, have fun and remember life is too short not to cache in the rain.

Official Disclaimer: One of the few caches that I have placed while hiking, it was winter and I needed to scratch the itch by placing a few caches while snowshoeing. I stayed on the trail until I was close to where I wanted to place the cache. If you're bushwhacking more than about 100 feet you're either lost or doing it the hard way.

A not so short note on GPS accuracy. Any form of positional accuracy is typically defined by a number which is usually called the Circular Error Probability or CEP. The CEP is the number expressed in feet or meters that equals the radius of the circle that you are probably standing within 50% of the time based on the coordinates your GPS shows. The bad news is there is a 50% chance that you are outside of the circle. On a Garmin GPS the CEP is represented by the blue circle you see around your position icon so if the cache icon is within the blue circle when you find it the coordinates are essentially dead on regardless of what your “Distance to” says. It is also worth noting that the diameter of the blue circle is usually much larger than the +/- accuracy number shown on the display.

When I place my caches I usually use an external, powered antenna that generally gets my CEP down under 4 meters +/- after I let the unit average for 300 fixes or about 5 minutes. 4 meters +/- means that both coordinates could be high or low by as much as 4 meters or 13 feet and because +/- implies a radius this works out to an 8 meter or 26 foot diameter circle. What this means is that there is a 50% chance that the location for any particular cache is somewhere inside of a 8 meter diameter circle because Garmin uses this 50% number for consumer grade GPS accuracy CEP. When a second GPS or even the same GPS at a different time is used it will have a CEP or positional tolerance of maybe 8 or 9 meters +/- unless you put it down and let it settle for a few minutes. What this means is initially you can be anyplace inside of a 60 to 70 foot diameter circle for a given pair of coordinates with a 50% chance that you are outside of that circle. Tolerance stack-up is where this all really starts to become a problem, if the cache is actually on the eastern edge of my circular tolerance and your location is on the western edge of your circular tolerance it would appear that based on your numbers the cache is at least 75 feet or more away and the numbers are way off. Both of us believe that we are where we think we are but, the probability is that we are both wrong and we are likely to be wrong in different directions.

I welcome suggestions as to the accuracy of my numbers but please set your unit down and let it average for at least 5 minutes and then log the actual numbers.

The website link shown below has a great explanation on what to expect for GPS accuracy, his long term averaged numbers suggest that plus/minus 8 or 9 meters is about the best we can actually expect regardless of what the folks who market our GPS receivers say.
(visit link)

One more note, most GPS units do not have a built-in electronic compass they use a GPS compass when you stop moving, the unit very quickly loses its orientation and from your viewpoint the direction to the cache will bounce all over the place. This problem is exacerbated by the unit showing your position bouncing all over the place each time it takes a positional fix. The solution to this is to walk in a circle, with the track mode or breadcrumb mode on, around the suspected cache location to narrow your search area.

Additional Hints (No hints available.)