Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPX export does not have correct altitudes in rtept - ele Element #1053

Closed
bm98 opened this issue Sep 21, 2023 · 3 comments
Closed

GPX export does not have correct altitudes in rtept - ele Element #1053

bm98 opened this issue Sep 21, 2023 · 3 comments
Assignees
Labels
Milestone

Comments

@bm98
Copy link

bm98 commented Sep 21, 2023

Issue found with LNM V 2.8.12 64-bit rev af00442 Win10 64bit

When exporting a GPX (Garmin Exchange Format) with MultiExport
The Route - - Items do not carry the correct altitude except for the Airports
all others seem to have the Cruise Alt

the Track seems to report with a profile but I cannot derive the unit from the numbers...

See attached files:
LNMPlan
GPX export
HTML export which is correct as far as I can see

IFR Galeao-Antonio C Jobim Intl (SBGL) to Congonhas Intl (SBSP).zip

It would be helpful to have the correct altitudes reported in the GPX export
Thank you :)

@albar965
Copy link
Owner

Thank you for the files and the description! 👍

I can confirm this. The track has the correct flown altitude (elements "ele") but the route does not. The units are always meters according to Wikipedia - GPS Exchange Format - Units.

I'll change the route to contain the altitudes from the calculated profile but will keep the actually flown altitude in the track. Hope this makes sense.

Alex

@albar965 albar965 self-assigned this Sep 22, 2023
@albar965 albar965 added the bug label Sep 22, 2023
@albar965 albar965 added this to the Release 2.8.13 milestone Sep 22, 2023
@bm98
Copy link
Author

bm98 commented Sep 22, 2023

Thank you - I am looking mostly for the route (used as Plan)
leaving the track as flown profile makes perfectly sense..
and thanks for confirming meters.
I don't remember having flown this route with LNM so that examples track with dates of 1970 may be artificial?
Trk seems not related to the route in the example (lat, lons don't match at all)
But I might have messed up here - don't know.

@albar965
Copy link
Owner

I don't remember having flown this route with LNM so that examples track with dates of 1970 may be artificial?

The time is simulator UTC. Means it is whatever time you've set in the sim. Exporting here gives me the correct sim time and not epoch.

Trk seems not related to the route in the example (lat, lons don't match at all)

You have to clear the track before flying (File -> Reset all for new flight). Otherwise you'll get a track from the previous flight(s).

A logbook entry also gets a track assigned which starts at takeoff and ends at touchdown. You can save this from the logbook table context menu Files ... This one does not contain previous flights.

Alex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants