Owd-Larrd / osmtracker-android

Automatically exported from code.google.com/p/osmtracker-android
GNU General Public License v3.0
0 stars 0 forks source link

GPS altitude not corrected by geoidal separation value #202

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. record a track
2. compare altitude data to a map

What is the expected output? What do you see instead?

expected Output is MSL_Height + geoidal_separation. Both are transmitted in the 
same $GPGGA sentence by most gps receivers. It seems that osm tracker ignores 
the geoidal_separation.

for further insight see http://www.tronico.fi/OH6NT/docs/NMEA0183.pdf Page 9

What version of the product are you using (See "About" screen)?

0.6.2

Make/model of your device, and Android version?

Sony/Xperia MINI - Motorola Defy+

Please provide any additional information below.

Original issue reported on code.google.com by tzie...@googlemail.com on 28 Aug 2012 at 9:48

GoogleCodeExporter commented 9 years ago
Hm... The app uses whatever altitude is returned by the Android SDK 
(LocationProvider), which doesn't account for geoid I'm afraid.

So until it's fixed in Android itself, I don't see an easy fix...

Original comment by nicolas@guillaumin.me on 29 Aug 2012 at 7:59

GoogleCodeExporter commented 9 years ago
how about an option then to set an constant offset to the recorded altitude. 
For germany for instant the geoidal_separation is -48 meters

There are also services on the web to get this value for given coordinates - 
look here http://www.unavco.org/edu_outreach/tutorial/geoidcorr.html

Besides that there are apps which shows the correct altitude - GPS Test is one 
of them:
https://play.google.com/store/apps/details?id=com.chartcross.gpstest&feature=nav
_result#?t=W251bGwsMSwyLDNd

Original comment by tzie...@googlemail.com on 29 Aug 2012 at 9:07