Tuno
December 23rd 09, 08:58 PM
The 0912 cycle was pretty quiet because the FAA was too busy mucking
up the 0913 edition. A couple of issues users should be aware of:
(1) The "Restrictive Airspace Name" field in the subject release is
missing the first character for most (if not all) airspace records.
Those those of you in Atlanta now hail from Tlanta, and those if you
in Houston are now proud Oustonians. How this made it past QA is a
good question, but not to worry -- your health care will soon be
brought to you with the same attention to detail. (ps this error be
visible to you OpenAir (.txt) users; .sua files use a different ARINC
field for naming.)
(2) The FAA NACO decided to start encoding circular areas in MOAs
differently. Previously they occupied only one record, nice and neat
and tidy. Now they use two, the second containing a bogus location
field, which if proceessed according to the ARINC specification, will
give you unwanted lines in graphical renderings. (This one required a
hack^h^h^h^hfix to the software on www.justsoar.com, now in place.)
And who knows what else they "fixed" that we haven't uncovered yet ...
MC and HNY,
~ted/2NO
up the 0913 edition. A couple of issues users should be aware of:
(1) The "Restrictive Airspace Name" field in the subject release is
missing the first character for most (if not all) airspace records.
Those those of you in Atlanta now hail from Tlanta, and those if you
in Houston are now proud Oustonians. How this made it past QA is a
good question, but not to worry -- your health care will soon be
brought to you with the same attention to detail. (ps this error be
visible to you OpenAir (.txt) users; .sua files use a different ARINC
field for naming.)
(2) The FAA NACO decided to start encoding circular areas in MOAs
differently. Previously they occupied only one record, nice and neat
and tidy. Now they use two, the second containing a bogus location
field, which if proceessed according to the ARINC specification, will
give you unwanted lines in graphical renderings. (This one required a
hack^h^h^h^hfix to the software on www.justsoar.com, now in place.)
And who knows what else they "fixed" that we haven't uncovered yet ...
MC and HNY,
~ted/2NO