Amok ghost elevation generated by Locus out of the blue

Michael Bechtold shared this problem ago

Solved

Hi Menion, planning a trip through Canada for next year I used local BRouter successfully.

Looking at the result, the elevation graph shows two amok locations, where Locus introduces by itself a jump by 2000m, then goes back a bit later to correct route.

I was able to manually remove the first amok points, but failed with the second. Trying the elevation correction by Locus, this even brought back the first spike I had removed.

Can you pls. try attached? I could not find the spikes that Locus shows.

TXs and cheers

Michael

Files:

The same problem 0

Replies (5)

Michael Bechtold ●

Version 4.3.2

URL

Menion ●

Hi Andrew,

"Fill elevation" create a correct chart for me, so it looks like an incorrect elevation data. Suggest to delete "Locus/data/srtm/N53W120.hgt" file and try to use "Fill elevation" function again.

Menion

URL

Michael Bechtold ●

Sorry, Menion, for disturbing you. If I had thought about where manual tracks get their elevation from, I would have spared this post ...

Thank you!

URL

Menion ●

No problem Michael, it was a five minute task for me :).

So problem solved? It were some old elevation files? Seems that source of these HGT files should be updated.

Menion

URL

Michael Bechtold ●

Yes, they were from 2017 - update is a good advise ... For Europe I am using Sonny's, partly 1", but for Canada I missed to update - so far ...

URL