Wrong elevation gain during recording

Hello Mike,

agree that this is little bit confusing. Problem here is, that what you see during track recording ARE REAL values measured by your device. They are usually quite noisy, so when Locus save after end of recording your track, there is a mechanism that optimize these values to some more logical results. So after save of track, you see already optimized values.

Doing this optimization also during track recording is currently quite complicated and I CPU & battery consuming, so I decided to do it after track is saved, just once.

Anyway as I wrote, I agree that this is not a perfect solution because it is little bit confusing if you do not know it.

OK, i already thougt that this a problem between condensed and real data.

but i also checked the altitude thats shown in the sidepanel.

it looks quite reliable, it shows the correct data all the time.

so is it possible to change the elevation gain from real data to counter of the altitude thats shown in the panel?

i mean: shown altitude +1 --> shown elevation gain +1

i am well aware that the result would not be perfect, but better than the current which is completely unrealistic.

the result in the overview is perfect, so this should be retained

Hi Menion,

as already mentioned above there is a sever difference between the recorded meters in altitude during track recording and the data you see when the track is saved.

Data during track recording

Saved track data

Data in the statistics file.

1) As you said the data shown during track recording are real values measured by the device used. If you use a barometric supported device and you have set Locus to barometric the values shown are the barometric ones.

2) If you use a non barometric device and the correct setting the values shown should then be the GPS data.

3) What does Locus do when you save the track record referring to point 1 and point 2? What values are shown when saved.

4) The data shown in the statistics file always stay untouched independently if track saved or not. What kind of values are used there?

Barometric obtained meters in altitude are pretty well in accuracy whereas GPS data in altitude blow. But this is not your business Menion, you have done your job darn well.

This all is a bit confusing and a few nice explaining words in the program which pop up with respect to the program points your gonna use would be a fine idea and avoid stumpling.

Have a nice day

Regards Rudi

Hello Rudi,

1, 2) Barometric data are automatically merged with measured and computed values so in the end, there is nothing like "barometric" only altitude.

3) when track is saved, measured values are always stored, not some optimized. So when you then export recorded track to GPX, you always get file with real measured values. Useful info for some self-check or test on any analyzing web site. After data are saved, Locus compute new optimized values, that are shown in chart.

4) ah you are correct - values in laps are not filtered so they show real measured (unrealistic) altitude values

--------

Anyway, I see here clear problem that should be improved and visible values should be united. So I absolutely agree, there should be no (at least not big) difference between values from current track recording and values visible on already stored track.

I'm writing this as a task on June and I'll try to improve it. If during June, there will be no change, kick me little bit ;). Thanks

this sounds good.

Thank you.

Many thanks Menion, you're the very best. I think about you in July when I'm driving the Kammweg in Krušných hor.

Have a nice day

Rudi