This object is in archive! 

Track correction problem by applying the height model

Holger Peschke shared this problem 7 years ago
Not a Problem

We did a ski mountaneering trip to the summit Zischgeles (3.004m) in Austria. On the top we spent around 30 minutes. After the trip I corrected the gpx trip by applying the online height model. After that the track is looking smooth but the maximum height recorded is now 2.953m. So we "lost" about 50m. (Corrected gpx file has now been uploaded to the topic.)

This problem I experienced alomst during every day on our 5 day trip, when we traversed the Sellrain mountains.


Are you aware of this problem?

Replies (1)

photo
1

Good day Holger,

I'm checking your recorded track ( btw. thanks for sharing of GPX files, it saved us a step).


Here are my observations:


1. uploaded to Garmin Connect web service, to check values there. I've enabled "Elev Corrections" on their web, so elevation values are computed by them and not used from GPX file. Here is the result .... for my own suprise, almost identical to Locus Map


01c2dc518d34f06adea67d6d2cb4ae3f


2. I'm trying some web services that allows to compute, display elevation, like

- https://www.freemaptools.com/elevation-finder.htm

- http://www.geoplaner.com/


All display very similar values. If you use offline elevation fill, results will be "better" ( closer to expected 3.000 m).


Not sure how may I help here more, because seems that all available data display similar values for this peak.


--------------


Generally, please be aware that precise values for peaks, mainly the sharp one like this, are very very complicated to correctly compute. Only option is to use very detailed elevation model.

I see option to download data from external site like we write here . From this site http://viewfinderpanoramas.org/dem3.html should be possible to download 1'' elevation data ( Locus Map offline mode use 3'' ) that should give even more precise values.


Hope I helped you. Feel free to ask if you have any additional questions.

Replies have been locked on this page!