This object is in archive!
Weird altitudes in recorded tracks
Closed
I have recorded tracks during hikes and, while the recorded positions are correct, I consistently get wrong elevation changes, no matter what setup I use (altitude filtering, SRTM data, ...)
The same problem 
Hi Phil,
could you please give us more details, how you know the elevation is incorrect? What is your reference measurement or elevation data?
Michal
Hi Phil,
could you please give us more details, how you know the elevation is incorrect? What is your reference measurement or elevation data?
Michal
Hi Michal,
All the tracks attached to my first message are in the same area, where the elevation is everywhere above 100m (see for instance the IGN topo map on https://www.geoportail.gouv.fr/carte). In some of these tracks, eg on April 11, April 17 and April 20, some negative elevation have been recorded! If you plot these tracks eg with GPS Track Editor (http://www.gpstrackeditor.com/) you will see that at points where the tracks cross, (very) different elevations have been recorded.
On the track recorded this morning (attached) the elevation appears correct
Hi Michal,
All the tracks attached to my first message are in the same area, where the elevation is everywhere above 100m (see for instance the IGN topo map on https://www.geoportail.gouv.fr/carte). In some of these tracks, eg on April 11, April 17 and April 20, some negative elevation have been recorded! If you plot these tracks eg with GPS Track Editor (http://www.gpstrackeditor.com/) you will see that at points where the tracks cross, (very) different elevations have been recorded.
On the track recorded this morning (attached) the elevation appears correct
Hi Phil,
does it mean (your latest attachment) the problem you posted firstly, cannot be simulated again?
Michal
Hi Phil,
does it mean (your latest attachment) the problem you posted firstly, cannot be simulated again?
Michal
Hi Michal,
what this means is that the problem is not systematic (I shouldn't have written "consistently"); see for instance today's track (attached) which is quite bad.
Phil
Hi Michal,
what this means is that the problem is not systematic (I shouldn't have written "consistently"); see for instance today's track (attached) which is quite bad.
Phil
Hi Phil,
what altitude manager settings do you used when you encountered the problem?
Michal
Hi Phil,
what altitude manager settings do you used when you encountered the problem?
Michal
Hi Michal,
since April 19 I have been using no altitude offset, no SRTM and no filter. Before then, I used light filter. On some of the oldest tracks, I also used automatic altitude offset correction (I don't recall precisely up to what date)
Hi Michal,
since April 19 I have been using no altitude offset, no SRTM and no filter. Before then, I used light filter. On some of the oldest tracks, I also used automatic altitude offset correction (I don't recall precisely up to what date)
Hi Phil,
I would recommend to turn on automatic altitude offset, optimize GPS values by SRTM data, turn barometer on and light-medium altitude filter. Raw GPS data are often quite incorrect.
Hi Phil,
I would recommend to turn on automatic altitude offset, optimize GPS values by SRTM data, turn barometer on and light-medium altitude filter. Raw GPS data are often quite incorrect.
Replies have been locked on this page!