sardude wrote:
The standby call info was a little sketchy, but "operator error" looks to be the root cause.
Oh, you mean I have to know how to read the GPS
before I use it?
Some of the most lost hikers I've ever met in the back country had a GPS.
One has to be able to:
1. Be able to associate what's on the GPS with the terrain around them.
and
2. Be able to associate what's on the GPS with what's on your map.
Knowing one's latitude and longitude is of precious little value in terms of navigation if you can't associate it to your map and what's around you. You
are carrying a topo map, aren't you? GPS's are great but they are electronic and can break or the batteries can die. A topo map is not only a back up but is also a good planning tool because you can see a wider area at a glance than that tiny little window on your GPS. That nice smooth canyon that you're following down may look all nice in that tiny GPS window, but down on ahead, it "cliffs out" when it joins a main canyon. Had you looked at your map, which shows more area, you'd have chosen a different route.
By the way, a lot of GPS's are set to NAD83/WGS84 coordinates. Maps are pretty much all drawn to NAD27 coordinates. You either need to know how to convert between the two or better still set your GPS to the same coordinate system as your map.
If you ever have to report a location,
make sure to include the coordinate system. I heard of one case where SAR air resources were using WGS84 and ground resources were using NAD27. The air resources dropped the ground search team off at the "wrong" spot (from the perspective of the ground search team). You wouldn't want SAR to be searching off somewhere else when it's you or one of your loved ones that's injured or lost, now would you?
HJ