Re: vectors, waypoints, overlay

On Mar 19, 12:37�am, "Lumpy" <lu...@digitalcartography.com> wrote:

m...@sushi.com wrote:

http://www.lazygranch.com/images/misc/tower150.jpg
This is a photo of the tower. Vector is 150 degrees. Location is
N37.62406 W115.76771


I'm a little confused. Surely my ranch in Phoenix
is in the BEZ. I'm not getting "ray'd".

Is the photo listed above the tower INSIDE the
boundary that you see at bearing 150 from
the coordinates given above?

I guess what confuses me is that the waypoint is
called "tower150". There's obviously not a tower
at that waypoint. So does the naming scheme mean
"from this waypoint, there is a tower at bearing 150"?

If so, then I guess I don't get the name of "016".
I also don't get the name of "017"

I don't see anything on GE at waypoint "016" or "017".

Have I got you as confused as I am?

Lumpy

You sang all those car commercials?
You got it, Toyota.www.LumpyMusic.com


All easily explained. The computer analysis of the BEZ covered a
limited range.

To make a vector, I have a starting point, which is where I did the
visual targeting. In the case here, I took the vector while at the
waypoint tower150. The map program needs and end point to finish the
vector, so more correctly, it is a line segment. Here is the
procedure:
1) in mapsource, select the "route"
2) start the route at the observation point
3) zoom out
4) watch the angle notation until it matches what you measured
5) terminate the route at a distance way beyond what you think you
require

The terminate of the route requires a waypoint, which showed up as 016
and 017 in this example.

Unless I took the vector wrong, this tower is in free territory. I
calibrated the GPS before taking the measurement. I'm going to make it
a point to measure twice, once with the gps, and then with the
lensatic. Garmin Mapsource can use either true or magnetic vectors.
I've found it better just to measure a magnetic vector in the field
rather than try to compensate when measuring.