SeeYou incorrect waypoint altitudes

On Sat, 01 Feb 2020 07:38:03 -0800, soaringjac wrote:

On Saturday, February 1, 2020 at 7:14:46 AM UTC-8, Paul Remde wrote:
Hi,

I suspect that one of 2 things is happening.
- You may be using a bad turnpoint database. I recommend the data
found he
http://cumulus-soaring.com/seeyou.htm#Downloads
- If you are viewing a flight log, SeeYou can automatically use the
take-off and landing elevations and the SeeYou ground elevation
database to offset all the flight log points to account for barometric
pressure changes. It is a very nice feature.

You may want to check-out my SeeYou Tips document.
http://cumulus-soaring.com/seeyou/SeeYou-Tips.pdf

Best Regards,

Paul Remde

On Friday, January 31, 2020 at 9:59:13 PM UTC-6, soaringjac wrote:
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!

Thanks Paul! I am not using any turnpoint database and not viewing any
flight log. I am just trying to mark some local landmarks as waypoints
to put into my S100 vario. Im going to play around with it a bit more
and see if i can figure out whats going on, but to me it seems like the
see your elevations are not accurate. I guess i can always create the
waypoints and then edit their altitudes based on the alt i get from
google earth, which kind of sucks

Post one of the problematic turnpoints here so we can see what might be
wrong. CUP files are just plaintext, so almost any program that can
display a text file can display it for cut'n pasting - even Word.


--
Martin | martin at
Gregorie | gregorie dot org

On Saturday, February 1, 2020 at 9:43:59 AM UTC-8, Martin Gregorie wrote:
On Sat, 01 Feb 2020 07:38:03 -0800, soaringjac wrote:

On Saturday, February 1, 2020 at 7:14:46 AM UTC-8, Paul Remde wrote:
Hi,

I suspect that one of 2 things is happening.
- You may be using a bad turnpoint database. I recommend the data
found he
http://cumulus-soaring.com/seeyou.htm#Downloads
- If you are viewing a flight log, SeeYou can automatically use the
take-off and landing elevations and the SeeYou ground elevation
database to offset all the flight log points to account for barometric
pressure changes. It is a very nice feature.

You may want to check-out my SeeYou Tips document.
http://cumulus-soaring.com/seeyou/SeeYou-Tips.pdf

Best Regards,

Paul Remde

On Friday, January 31, 2020 at 9:59:13 PM UTC-6, soaringjac wrote:
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!

Thanks Paul! I am not using any turnpoint database and not viewing any
flight log. I am just trying to mark some local landmarks as waypoints
to put into my S100 vario. Im going to play around with it a bit more
and see if i can figure out whats going on, but to me it seems like the
see your elevations are not accurate. I guess i can always create the
waypoints and then edit their altitudes based on the alt i get from
google earth, which kind of sucks

Post one of the problematic turnpoints here so we can see what might be
wrong. CUP files are just plaintext, so almost any program that can
display a text file can display it for cut'n pasting - even Word.


--
Martin | martin at
Gregorie | gregorie dot org

All you need to do to replicate is to make a waypoint in seeyou and note the elevation, then go to google earth or something similar and get the elevation for the same location. Most likely it is pretty different. In a couple cases for me its almost 1000' difference

This is *not* what happens for typical users. If it did everybody would be screaming. So no us just going and trying is not going to help you because it works fine except as noted near fine resolution peaks etc. So again, just post the waypoints you are seeing errors for.