Messages

(Note: To view gpx tracks I do not use services that calculate gpx altitude data from their own terrain model, so this should not be a source of error)

It is also possible if the altitudes are (partially) GPS based ( even if optimized ), the online service internally filters noisy data. If altitudes are SRTM based, there is nothing to filter, as it is smooth.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Hmm I now viewed it via two other well known osm Apps too and it's the same - I don't think they use a filter by default

Thanks for explaining! I only noticed it when using "optimize gps altitude", because the lowest and highest points had different values when viewing the gpx outside Locus. When using the "replace" option it is indeed quite fluent and seems to stay pretty much identical outside of Locus.
(Note: To view gpx tracks I do not use services that calculate gpx altitude data from their own terrain model, so this should not be a source of error)

But since I intend to mostly use the "replace" option it isnt really a problem for me anyway, so thanks for the help.

Thanks for your reply, I got me the Pro Version meanwhile and did some testing. It seems like that altitude optimization via smrt is done after saving the track, and optimized values are only visible inside Locus, so if I export the gpx it contains the standard gps altitude data, is that correct?

Hi! I would like to ask some information on altitude tracking before I go ahead and buy the pro version -

1.I am particularly interested how the  option to "optimize gps altitude" via smrt will work? Is it smoothing the curve in post or calibrating the gps from time to time etc?

2. Can I import LIDAR data and will the above optimization then use this data instead?

thanks in advance!