Threshold for altitude changes
My altimeter pressure sensor does have 0.3m fluctuation and I'm unable to filter them away with locus because locus does record each 0.1m altitude change.
It doesn't help to change altitude filter light to filter very strong because it does only smooth changes out a little bit.
And I notice that some flattening does happen on track save action. It does get reduced from 69m record climb value to 41m climb in saved track statistics on 2 hours testrun on same position. Well my pressure sensor is accurate enoght that even a simple integer convertion would nearly solve this issue.
What about a threshold for altitude changes? Store only new hight values if a specific amount of climb or descent change is reached?
We don't need to round, we just need to skip altitude change flickering from uphill to downhill.
messurement after filtering -> value which get recorded with threshold handling
stard with "record climb only until 1.0m descent"
100.1 -> 100.1
100.4 -> 100.4
100.2 -> 100.4
100.3 -> 100.4
100.5 -> 100.5
100.7 -> 100.7
100.9 -> 100.9
101.1 -> 101.1
100.9 -> 101.1
101.2 -> 101.2
100.9 -> 101.2
100.4 -> 101.2
100.2 -> 100.2 (1.0m threashold reached, switch to descent mode, record decent only until 1.0m climb)
99.9 -> 99.9
100.1 -> 99.9
99.7 -> 99.7
Important: threshold handling have to be applied after filtering because not filtered values would easily hit the threshold.
There is only one minor problem: we get a rough transition from 101.2 to 100.2 but this could easyily fixed by postprocessing on track save if we care about it.
I don't like postprocessing solutions for the whole problem because I would like to rely on the record screen climb indicator.