soaringjac wrote on 2/2/2020 8:33 AM:
On Saturday, February 1, 2020 at 7:48:36 AM UTC-8, Eric Greenwell wrote:
soaringjac wrote on 1/31/2020 7:59 PM:
Just started using seeyou for the first time. I created some waypoints in seeyou and noticed the altitude shown for some of the waypoints are way off. I double checked the exact same point in Google earth and the difference is about 1000'. This isn't the case for all custom waypoints I made, but it is true for most of them. How are you guys creating accurate waypoints and waypoint altitudes. Kind of crazy that seeyou is so off!

For what purpose will you use the waypoints? If it's for task planning, the
correct elevation doesn't matter; if it's for potential landing places, you should
not depend on SeeYou, but on a more accurate source. SeeYou is a flight planning
tool, and it's your flight computer that needs elevation accuracy. I use official
databases as my first choice; for landing places not in the official databases, I
use databases from pilots I trust, sometimes from Google, perhaps topographic
maps. I also plan to arrive higher at those landing places, partly because the
elevation may not be known as accurately as airports on the charts.


Just adding a couple local landmarks to my S100, mainly going to use to see if I have glide to the various waypoints. Not doing any XC or competition stuff. I might try some databases but it seems a bit overkill for now. I just want a couple local landmarks.

I maybe be assuming the wrong things. What are you using as your flight computer,
and does it already have the local airports in it?

Usually, we use "landmark" for point of reference only, like a mountain peak or
bridge. By "landmarks", do you mean "places I could land safely?

--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to email me)
- "A Guide to Self-Launching Sailplane Operation"
https://sites.google.com/site/motorg...ad-the-guide-1