Dear LM users,
I have a question regarding "update elevation" feature and what/how it actually does. I am seeing (too) large increase in elevation after "update elevation" use on imported GPX tracks and on recorded ones.
I downloaded following GPX and followed it on bicycle:
https://drive.google.com/file/d/1DaYc2Gx8Fn1IBsduxEbepS9O_UNh5OXa/view?usp=drive_link
When I import it elevation shows:
![](https://i.ibb.co/pRQSYW3/Screenshot-20240606-210720-Locus-Map-Classic.jpg)
After "update elevation" it shows:
![](https://i.ibb.co/1TvYZqS/Screenshot-20240606-210610-Locus-Map-Classic.jpg)
According to my Garmin watch, actual measured elevation is very close to 1030m, rather then 1666m...
What could be the issue for this? I also noticed this in cases where I record track with LocusMap and later use "update elevation". The change in elevation is significant.
Thank you
I have a question regarding "update elevation" feature and what/how it actually does. I am seeing (too) large increase in elevation after "update elevation" use on imported GPX tracks and on recorded ones.
I downloaded following GPX and followed it on bicycle:
https://drive.google.com/file/d/1DaYc2Gx8Fn1IBsduxEbepS9O_UNh5OXa/view?usp=drive_link
When I import it elevation shows:
![](https://i.ibb.co/pRQSYW3/Screenshot-20240606-210720-Locus-Map-Classic.jpg)
After "update elevation" it shows:
![](https://i.ibb.co/1TvYZqS/Screenshot-20240606-210610-Locus-Map-Classic.jpg)
According to my Garmin watch, actual measured elevation is very close to 1030m, rather then 1666m...
What could be the issue for this? I also noticed this in cases where I record track with LocusMap and later use "update elevation". The change in elevation is significant.
Thank you