elevation profiles of GPX recordings are often "wrong"

[Wegi]

I use Osmand to record trips via GPS. Sometimes there are elevation values of 0 in the GPX files. I think these are due to insufficient GPS reception. These values are shown in the elevation profile and for ascent/descent values, which render these unusable for me. e.g. a trip which has an ascent of 300m is shown as 1100m, because of some 0 elevation values. When I load the same GPX file in other viewers, these 0 values seems to be ignored, as they show the (almost) correct ascent/descent values. 

My question is, if there is the possibility to ignore those "0 values" also in Osmand?

[Peter B]

Plesse provide an example (gpx-file).

[Wegi]

Sent via PM

[Andy Henderson]

On Thursday, 18 July 2019 13:15:13 UTC+1, Wegi wrote:

I use Osmand to record trips via GPS. Sometimes there are elevation values of 0 in the GPX files. I think these are due to insufficient GPS reception. These values are shown in the elevation profile and for ascent/descent values, which render these unusable for me. e.g. a trip which has an ascent of 300m is shown as 1100m, because of some 0 elevation values. When I load the same GPX file in other viewers, these 0 values seems to be ignored, as they show the (almost) correct ascent/descent values. 

My question is, if there is the possibility to ignore those "0 values" also in Osmand?

FWIW, I tried calculating total ascent from a recorded GPX and - even though I didn't see the '0' values - the results were unusable. I believe that's because GPS height positioning is relatively inaccurate so even if you were to travel on a perfectly flat road, you would still see changes in elevation - which would contribute to your total climb. I got results that were clearly wrong, so I abandoned that project.

Andy