mattshobe / flightmap

Automatically exported from code.google.com/p/flightmap
Apache License 2.0
0 stars 0 forks source link

Map not correctly rotated for magnetic variation #89

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The displayed numeric bearing looks correct. But the pointer looks like it's 
off by about the magnetic variation amount.

This is hard to debug without a good position simulator, because in the 
emulator, Location.getBearing() always returns 0.

Original issue reported on code.google.com by ph...@google.com on 13 Sep 2010 at 1:15

GoogleCodeExporter commented 9 years ago
With the simulator, now I can see the bug is actually with the map, not the 
tapcard. The two attached screenshots are from a replay of a real flight. The 
aircraft is on short final for runway 31 at KPAO. The map shows the airport off 
to the right (which is wrong). The tapcard pointer correctly shows the airport 
straight ahead.

I think the map rotation is off by the magnetic variation amount. Eyeballing 
it, it looks like 15 degrees, which supports that theory.

Original comment by ph...@google.com on 20 Sep 2010 at 11:06

Attachments:

GoogleCodeExporter commented 9 years ago
The bug was that the map should *not* be affected by the magnetic variation. 
That only matters for the numeric display of the track at the top.

Fixed in r317.

Original comment by ph...@google.com on 23 Sep 2010 at 4:18

GoogleCodeExporter commented 9 years ago

Original comment by ph...@google.com on 23 Sep 2010 at 4:19