Closed GoogleCodeExporter closed 8 years ago
Androzic shows altitude "as is" that is provided by GPS receiver. GPS status
application shows the same altitude (with respect to its +15 meters, which I do
not understand).
Original comment by andrey.g...@gmail.com
on 9 Jan 2011 at 10:55
Sorry, I didn't notice the +49m (for me) of GPS status.
I guess that GPS receiver gives an altitude related to a theoretetical sphere.
Since earth is an ellipsoid (flattened on the poles), the +15m or +49m seems to
be the difference between sphere and ellipsoid at a given latitude.
Since I use androzic for hicking in montains, altitude accuracy is a concern. I
have now the way to get it.
Thanks.
Original comment by jean.3...@gmail.com
on 10 Jan 2011 at 4:32
Thanks for that notice. I will look at details of GPS altitude and convert this
issue to feature request. This behavior sounds reasonable if you are right.
Original comment by novikov
on 10 Jan 2011 at 10:02
Original comment by novikov
on 11 Jan 2012 at 10:03
Issue 196 has been merged into this issue.
Original comment by novikov
on 11 Jan 2012 at 10:03
Original comment by novikov
on 15 Jan 2012 at 6:43
GPS Receivers give 2 standartized vaues of altitude:
1. Altitude above/below mean-sea-level (geoid)
2. Geoidal separation, the difference between the WGS-84 ellipsoid and geoid.
Different programs may differently interpret values of altitude (as altitude
above ellipsoid or geoid).
Original comment by uazi...@gmail.com
on 19 Jan 2012 at 8:16
Implemented in 1.3
Original comment by novikov
on 30 Jan 2012 at 9:33
Hello.
You say it is implemented in the 1.3.1 version, but I am using the 1.4.1
version and I have always about +45 meters of error (I'm living in France). I
dont't find in the menus how to activate the correction (if any). May you help
me please ?
Original comment by grall29...@gmail.com
on 17 Mar 2012 at 3:02
I live in Italy and I notice +105 meters of error, other useless apps detect
correct altitude.
May you help me please ?
Original comment by fguide...@gmail.com
on 28 May 2012 at 11:20
This depends on the smartphone used. On my previous SEx8mini the error was not
the same as with my actual. Samsung ace.
Original comment by jean.3...@gmail.com
on 28 May 2012 at 12:36
i've the same problem on Galaxy S3
Original comment by hugues.d...@gmail.com
on 26 Jun 2012 at 3:26
Original issue reported on code.google.com by
jean.3...@gmail.com
on 6 Jan 2011 at 10:11