Author Topic: Magnetic N. Pole shift may cause scenery changes  (Read 3423 times)

bradl

  • Full Member
  • ***
  • Posts: 195
Magnetic N. Pole shift may cause scenery changes
« on: January 07, 2011, 07:49:04 pm »

This isn't just specific to FSDT, but to all scenery designers in general, so it may be something FSDT should keep in the back of their mind.

Reference: http://www2.tbo.com/content/2011/jan/05/060831/shift-of-earths-magnetic-north-pole-impacts-tampa-/news-money/

This is causing KTPA to renumber 18L/36R and 18R/36L to 19L/1R and 19R/1L, respectively. Rationale behind it is obvious: Magnetic N. Pole has moved. But the key thing to note is that magnetic heading for the runways is 184 and 004 respectively.

San Antonio may fall victim to this, as they have a 12/30 setup, which the 12s are 126, and the 30s are 306. With that shift, this could go to a 13/31.

It could be that all runways that close in magnetic heading could be affected, resulting in all sceneries being updated. The problem is that the current flight sims (excluding X-Plane) will have the old data. Flight might even have the old data. But just something to think about in case runways change, and magnetic headings for those runways do not.

BL.

simbio

  • Full Member
  • ***
  • Posts: 189
  • FSDreamTeam developer
Re: Magnetic N. Pole shift may cause scenery changes
« Reply #1 on: January 07, 2011, 10:30:24 pm »
It's not so difficult to change a scenary for this aspect, the only big problem is when they built a new runway or make architectural change.
Exemple: Terminal 5 in Heathrow or the fifth runway (10-28) in Atlanta in 2006; is always difficult to find info and photo.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50875
    • VIRTUALI Sagl
Re: Magnetic N. Pole shift may cause scenery changes
« Reply #2 on: January 08, 2011, 05:15:12 am »
It could be that all runways that close in magnetic heading could be affected, resulting in all sceneries being updated. The problem is that the current flight sims (excluding X-Plane) will have the old data. Flight might even have the old data.

Yes, but the fact the sim use data which was current when the sim was published, it's exactly what prevents the scenery to change, since the magnetic variation database in Flight sim is static.

You might not have the most current real-world situation, but at least you won't get strange problems in navigation, as long you keep using the scenery which comes with the sim.

The issues starts to surface if you use AIRAC updates, for example for you FMC, because at a certain point runways will not match the scenery anymore, and so will all the headings expressed in magnetic courses, like airways or VOR tracks.

In an ideal world, if you start to apply updates, you should update *everything*, navigation databases, navaids and approaches in the sceneries, all the navaids in all .BGL, and of course the charts used. Everything should be ideally taken from the same source, which might be very difficult to do, especially if you have sceneries coming from many developers, which can even include conflicting data. I find it's way easier, instead, to not update anything, and stick with the data the sim came with.