yeah. contour lines can suck if your not used to them. id prolly end up in ohio if i tried land nav up that way lol i tried using them to nav in canada few years back ..i was stumped lol
got a lil hilly section out in the place we hike. got to get a topo downloaded for it and try some stuff.
got a lil hilly section out in the place we hike. got to get a topo downloaded for it and try some stuff.
So I started off with an aversion to try to go too far based on this.
Shot my azimuths on the map just fine, added 10 for declination. Did all the map layout fine. Stand at the starting point, shoot your azimuth, find something on that angle, walk to it. Pace count wasn't totally possible due to the fact that their is almost no flat ground your working on. Take a check of the time when starting. Run the azimuths, get into the general area and start terrain association- or in my case terrain DISassociation.... LOL. So in EVERY CASE I looked at the terrain, tried to relate the squiggly lines to the ground, move around a little bit, double checked features and really thought I was "right there." Leave a piece of tree tape on my last known trajectory, then made concentric circles out looking for the T- post with the marker on it.
In pretty much every case, had I actually went another 100 to 200 yards further, I was right on track- just reading the damn terrain wrong. Then I frittered away a lot of my time searching the area I "thought" was the correct territory for the T post.
Oddly enough, doing a land nav course here in the swamp the week or so before I left, I ran into all the points within a few yards.
I wonder how well those pedometers (? Foot step counters), would work in this situation? It wouldn't be cheating, it's not a GPS. But it would be easier than trying to pace count while climbing on your belly up the damn hills.
Comment