Poutnik <[email protected]> writes: > For me, it looks like both internal GPS units, in agreement with my > experience, do not provide geoid correction to the amplitude. Therefore > is is about 120' lower than the reference, what is about the correction > value for US region.
The Android specification is to return ellipsoidal height: https://developer.android.com/reference/android/location/Location.html and one can get the NMEA also and use either geoid height or GPGGA (orthometric) height: https://stackoverflow.com/questions/2791927/how-does-getaltitude-of-android-gps-location-works#2797026 https://stackoverflow.com/questions/9361870/android-how-to-get-accurate-altitude The real question is what's up with the external unit and how that works. If it's being connected in to replace the internal GPS and accessed via the same interface, it needs to report ellipsoidal height. But the fact that it shows the higher (presumably close to correct for orthometric height) value in satstat on both phones leads me to believe that the android location/altitude (misnamed) interface is being used to get the orthometric height from the bluetooth unit. That's the big mystery. The other mystery is that one of your phones seems to have the elevation correction map in OsmAnd and the other does not. Probably OsmAnd should change the symbol to something other than mountain, perhaps "EH", to indicate that it's showing ellipsoidal height, or make it red. -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
