Page 1 of 1
[closed] Altitude details in gpx files
Posted: Sat Nov 01, 2014 1:42 pm
by pinkyperk
I have created a track using an online mapping application (e.g. QLandkarte) with the maps 4Umaps.eu. I am able to extract elevation data for this track. When I transfer this gpx file to my phone and open up in AQ with the same 4umaps.eu, the application shows a much lower altitude figure. E,g, approx 200m less altitude for the ascent / descent over the track length of 16 km. The track length is identical in both applications. I have also created the same route in Alpenverein on my computer and transferred the gpx file to the phone and this time a slightly lower discrepancy, but in the other direction. i.e, ascent higher by 110 m and descent by 85 m. I am just wondering about these differences and how to judge the accuracy of the elevation date in either application. I would welcome any feedback on this. Thank you.
Re: Altitude details in gpx files
Posted: Sun Nov 02, 2014 9:05 pm
by Psyberia-Support
Hi,
The value of the elevation gain is a recurring subject. I've just included this in the online help with a complete description on how it's computed in the app, and how to understand this value compared to different values that can be found in other applications:
http://www.alpinequest.net/en/help/1.4/ ... statistics
In few words, there is not one gain value, it all depends on which scale you want it: some will only take into account altitude differences between mountain passes and summits (very under-estimated gain), some with take into account the differences between all following points (very over estimated gain). I cannot tell you how each other app compute this value, but our app will give you something in the middle, taking into account all the terrain changes, but not the noises from the GPS inaccuracies.
Don't hesitate to share your point of view.
Best regards
Re: Altitude details in gpx files
Posted: Tue Nov 04, 2014 8:32 am
by pinkyperk
Many thanks for your reply and the online help section is really useful. Certainly we are all aiming for an accurate ascent / descent calculation when designing a route and I hadn't realised that there were adjustments that could be made in determining this in AQ. I would agree that a figure just taking into account differences between passes and summits would be very inaccurate and some smoothing of data is necessary to get somewhere near the reality. I have noticed recently when using the tracker that the graph is a lot smoother, with spurious spikes in speed no longer showing which is certainly helping to provide a more accurate recorded measure of elevation. I will be a lot more mindful with regard to elevation in future and when walking a route comparing predicted ascent / descent with that actually recorded on the tracker. Regards David