Falsche Höhenmeter Berechnung im Routenplaner? Locus Map Classic?
Not a Problem
Wenn ich mit Locus Maps eine Route plane, werden mir generell mehr Höhenmeter angezeigt, als in anderen Apps (z.B. Ride with GPS).
Ich habe auf Mallorca eine Tour zum Cap Formentor geplant. Da werden über 1800hm angezeigt. Die exportierte GPX nach Ride with GPS zeigt aber nur ca. 930hm an.
Das kann eher stimmen.
Die Wahoo Aufzeichnung sind auch immer weniger Höhenmeter, als vorher mit Locus geplant. Ca. 30% weniger.
Auch importierte Routen von offiziellen Rundfahrten, werden mit mehr Höhenmeter angezeigt, als die Touren offiziell beschrieben sind.
GPX anbei.
Ich denke Locus Map berechnet zu viele Höhenmeter. Kann das sein?
Viele Grüße Stephan
Files:
Mallorca_5._Tag...
The same problem 
Hi Stephan,
each service or app uses different 3D landscape model and different algorithm for calculating elevation gain. Seeing the detailed elevation graph of the route you've sent it is quite clear that the terrain in many parts of the route is rugged and variable. Locus Map's accurate model catches all these terrain details which in result gets quite a high number of the total elevation gain:
Other apps and services usually tend to generalizing such terrain details and their result may seem more "real" because people are prone to overlooking slight ups and downs on the route and reflect only heavy uphills or downlhills.
Nevertheless, as we've often been experiencing similar reports, we added an option in Locus Map 4 to set user's own "elevation threshold" tweaking the main algorithm so that the result seems more real (the threshold omits all hills up to 20 m from the total calculation)
Hi Stephan,
each service or app uses different 3D landscape model and different algorithm for calculating elevation gain. Seeing the detailed elevation graph of the route you've sent it is quite clear that the terrain in many parts of the route is rugged and variable. Locus Map's accurate model catches all these terrain details which in result gets quite a high number of the total elevation gain:
Other apps and services usually tend to generalizing such terrain details and their result may seem more "real" because people are prone to overlooking slight ups and downs on the route and reflect only heavy uphills or downlhills.
Nevertheless, as we've often been experiencing similar reports, we added an option in Locus Map 4 to set user's own "elevation threshold" tweaking the main algorithm so that the result seems more real (the threshold omits all hills up to 20 m from the total calculation)
I analyzed the problem:
1) Stephan original track has quite wrong elevations values which sum up to a completey wrong altitude gain of 1996 m. Locus app and Locus Webplaner automatically applies a "elevation threshold" of 5m during import which calculates to an still wrong gain of 1697 m.
He wrotes that this is not a recorded track - but a planed track with Locus Maps. So the problem is within Locus'planer, and in detail in the elevation files he uses.
2) I guess he didn't used Locus Web planer, cause it calculates a total elevation gain of 886 m which is quite ok. If he had used Sonny 1" elevation files within the app, Locus Classic app calculates 972 m which seem also quite near to reality. So I think probably he used Locus Classic or Locus 4 with the usual unaccurate SRTM 3"-files which are offered by Locus for download.
3) In general Locus Web planer is lacking a function to correct the elevation values of imported GPX-tracks. If I import Stephans' track into Locus Web planer it displays the wrong elevation gain of this track (1697 m) without any function to replace its wrong values by the accurate values (Sonny 1") which Locus Web Planer usually uses.
I analyzed the problem:
1) Stephan original track has quite wrong elevations values which sum up to a completey wrong altitude gain of 1996 m. Locus app and Locus Webplaner automatically applies a "elevation threshold" of 5m during import which calculates to an still wrong gain of 1697 m.
He wrotes that this is not a recorded track - but a planed track with Locus Maps. So the problem is within Locus'planer, and in detail in the elevation files he uses.
2) I guess he didn't used Locus Web planer, cause it calculates a total elevation gain of 886 m which is quite ok. If he had used Sonny 1" elevation files within the app, Locus Classic app calculates 972 m which seem also quite near to reality. So I think probably he used Locus Classic or Locus 4 with the usual unaccurate SRTM 3"-files which are offered by Locus for download.
3) In general Locus Web planer is lacking a function to correct the elevation values of imported GPX-tracks. If I import Stephans' track into Locus Web planer it displays the wrong elevation gain of this track (1697 m) without any function to replace its wrong values by the accurate values (Sonny 1") which Locus Web Planer usually uses.
Is there a way to find out, which file is for which tile of the country after download? So that I can delete the rest?
Sonny I made an upvote on your suggestion. Hopefully menion will implement it some time soon.
When I'm back at home, I will test your files. ;)
Will Locus recognize the the elevation data for the region is there or will it download and replace it with the original locus data?
Is there a way to find out, which file is for which tile of the country after download? So that I can delete the rest?
Sonny I made an upvote on your suggestion. Hopefully menion will implement it some time soon.
When I'm back at home, I will test your files. ;)
Will Locus recognize the the elevation data for the region is there or will it download and replace it with the original locus data?
The altitude data will only be downloaded if you say so in the store.
Then your LIDAR will be overwritten. It is therefore best not to download anything from the store. I get all my altitude data from Sonny. Then I'm sure it's always the best.
The altitude data will only be downloaded if you say so in the store.
Then your LIDAR will be overwritten. It is therefore best not to download anything from the store. I get all my altitude data from Sonny. Then I'm sure it's always the best.
That worked now!! Now I get about 970 elevation meter for the tour, that seams to me fits more. :)
But the only way to copy the files is with the PC. No direct access to the folder from mobile phone device. :(
Not very comfortable. Locus Maps should use your 1" in general for download within the app.
But now I get many thin elevation lines. That looks a bit chaotic. See Screenshot. Any idea to solve this problem?
Any option to change that in openandromaps maps or theme?
:)
That worked now!! Now I get about 970 elevation meter for the tour, that seams to me fits more. :)
But the only way to copy the files is with the PC. No direct access to the folder from mobile phone device. :(
Not very comfortable. Locus Maps should use your 1" in general for download within the app.
But now I get many thin elevation lines. That looks a bit chaotic. See Screenshot. Any idea to solve this problem?
Any option to change that in openandromaps maps or theme?
:)
All elevation lines are doubled now. :(
Don't understand that.
All elevation lines are doubled now. :(
Don't understand that.
Replies have been locked on this page!