2KA,

I haven't dived into the gory details of the NASR, but after browsing
the SUA table of the primary data, the format descriptions for all the
tables, and the class B-E shapes in the "Additional" data, I have the
following observations:

* The APT table can be used in conjunction with the FAA NFD (what I'm
using on www.justsoar.com) to provide the comm frequencies missing
from the latter. (They have a common key.)

* Similarly, the SUA table provides active times missing from the NFD,
for Restrictive, Alert, and MOA areas.

(Alas the good news seems to end there.)

* The SUA table does not provide precise descriptions of the
restrictive areas. Arcs and circles, instead of being described by
[center, radius, begin point, end point, and direction to travel], are
lists of approximated points. They are not suitable for navigation
purposes, and I believe the NASR description even says so.

* The shapes data (for class B-E) have nice vector renderings (I used
TNTatlas), but this data appear to be 2 dimensional only, and also not
suitable for navigation purposes. (To be useful for navigation, top
and bottom elevations must be provided.) It seems this data are useful
only for 2D plotting. Also, at least the Class B file is out of date;
I got the 20 Dec 07 - Feb 08 download, but it still has the old
Phoenix Class B.

I don't want to discourage you from your project, but potential users
should be aware of these limitations.

I do think that creating an airport turnpoint list from the APT table
would be very useful. I hope you don't mind if I add this feature to
what I provide on justsoar.com.

2NO