Allow GPS Calibration

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use the somewhere that you know the true elevation.
2. Often the reported elevation is off by some constant amount

What is the expected output? What do you see instead?
The true elevation.

We should allow end users to input an elevation offset and always add or 
subtract that from the reported elevation.

Original issue reported on code.google.com by sandordo...@google.com on 1 Jun 2010 at 11:09

[GoogleCodeExporter]

Yes, that would be really helpful.

Original comment by gill.sm...@gmail.com on 2 Jun 2010 at 11:18

[GoogleCodeExporter]

Except that at Alderney airport it was reporting 200ft too high and 50 mins 
later, at Bembridge Airfield, it was spot on.  How does a simple offset work 
for that?

Original comment by beards...@gmail.com on 24 Aug 2010 at 8:48

[GoogleCodeExporter]

Just curious - how did the gps measurement compare to the QNH-calibrated 
measurement in those cases?
(I'm assuming your comparison was against the official altitude that's in the 
charts)

Original comment by rdama...@google.com on 24 Aug 2010 at 9:16

[GoogleCodeExporter]

Btw, isn't this the same as issue 46 ?

Original comment by rdama...@google.com on 31 May 2011 at 7:24

[GoogleCodeExporter]

I'd support rdama in comment 3 that the solution proposed in issue 46 is 
superior for the reason given by Beards in comment 2.

Original comment by kenep...@gmail.com on 10 Sep 2011 at 10:46

[GoogleCodeExporter]

Original comment by jshih@google.com on 22 Jun 2012 at 12:01

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by jshih@google.com on 10 Sep 2012 at 10:48

• Changed state: WontFix