Airport GIS and Special Activity Airspace (Military)

1. Airport GIS and Special Activity Airspace (Military)

2. Topics • From Aeronautical Information Services (AIS) to Aeronautical Information Management • From publications (paper) to data (digital) • Quality management • Airport Management • Digital survey standards • Airport Layout Plans and Metadata • Airport ATC operations management • Special Activity Airspace

3. Topics • From Aeronautical Information Services (AIS) to Aeronautical Information Management • From publications (paper) to data (digital) • Quality management • Airport Management • Digital survey standards • Airport Layout Plans and Metadata • Airport ATC operations management • Special Activity Airspace

4. Definition of Aeronautical Information Management services • Manage and deliver the information necessary to operate within the airspace system • Airport Operations • Airspace • Flight Planning • Weather • Services are the “glue” holding NAS together: • Mission essential – Used for strategic, tactical and operational air traffic control • Safety essential – Used for air navigation, separation assurance • Example services • Aeronautical Information Publications • NOTAMs • Pilot Weather briefings • Aeronautical Charts • Flight Planning Tools

5. Topics • From Aeronautical Information Services (AIS) to Aeronautical Information Management • From publications (paper) to data (digital) • Quality management • Airport Management • Digital survey standards • Airport Layout Plans and Metadata • Airport ATC operations management • Special Activity Airspace

6. Airport Management • Survey Data logger and submission • Survey standardization • Airport Layout Plan (ALP) and Airport Metadata submission • ALP Submission Repository • Feature Extraction • Airport Office Routing • Airport GIS Services and Analysis • Airport Surface NOTAMs • Terminal Procedure Design • Airport improvements and performance metrics

7. FAA Advisory Circular 150/5300-18 Guidance for airport survey Standards-based Information management Multiple uses for a single survey Airport GIS – A foundationhttp://airports-gis.faa.gov/

8. Airport NOTAMs Survey Process Standardization • “Chain of Custody” • Digital from the beginning • Based on standards • Benefits • Cost effective • Acquire once and use many times AirportManagement Survey Airport GIS FacilityPlanning Obstacle Charts Airport Layout TerminalProcedures

9. LandXML Survey collection and transmission Supported by survey collection system manufacturers Supported by CAD and GIS software Enables survey collection to CAD/GIS AIXM / AirMAT Airport Surface data content model Features, Attributes, Relationships, Data capture rules International standards Enables information storage, exchange and multiple use Airport GIS Data StandardsEnabling digital capture and delivery

10. Notice to Airman: TWY S CLOSED BETWEEN P and E xxxxxxxxxxxx xxxxxxxxxxxx Airport GIS ServicesDigital Airport NOTAMs

11. AIXM Requirements • FAA AIM Group is implementing AIXM throughout our programs • Airports GIS currently supports various file formats • Oracle, PostgreSQL/PostGIS, ESRI Shape, AutoCAD DWG, KML • Airports GIS’s development pipeline includes support for AIXM • Planning for this now

12. Approach • Planning ahead for future Airports GIS needs with our current mapping capability decisions • Current: Thin Client, Customizable, Visualization • Future: AIXM, Redlining & Annotation, 3D • Standards Based • Web Mapping Service (WMS) • Standard set of parameterized HTTP requests • Extended WMS with Luciad • To satisfy the unique requirements of Airports GIS

13. Findings (1) • Luciad WMS: • Provided the OGC standard WMS foundation • Provided access to the LuciadMap core functionality • Luciad WMS extensions: • To meet the specific needs of Airports GIS • ex. addition of parameters specific to the Airports GIS project workflow framework (project #, etc.)

14. Findings (2) • Benefits of Luciad’s Java based API toolkit • Reusability of code across applications • Near linear horizontal/vertical scaling • High quality image outputs • Clear scalability path provides application growth • Luciad WMS: Thin client / Server with WMS (distributed visualization) • LuciadMap / Lucy: Thick client for future functionality (editing, redlining) Airports GIS v.1 Custom Java Code with Luciad API Airports GIS v.# notes & edits notes & edits

15. Next Steps • Initial version of e-ALP built with Luciad WMS will be available Fall 2009 • Next version of e-ALP will incorporate additional tools & advanced configuration • Redlining • Editing / Customization • Annotations notes & edits notes & edits

16. Summary • Airports GIS is in the beginning stages of visualization implementation • Received positiveresults with first prototype • Current and future mapping criteria and ability to use AIXM considered in decision to use Luciad WMS

17. Topics • From Aeronautical Information Services (AIS) to Aeronautical Information Management • From publications (paper) to data (digital) • Quality management • Airport Management • Digital survey standards • Airport Layout Plans and Metadata • Airport ATC operations management • Special Activity Airspace

18. SWIM and AIM • The FAA’s System Wide Information Management (SWIM) Program is providing NextGen infrastructure for data exchange • Aeronautical Information systems will need to conform to SWIM’s architecture • Exchange of complete information facilitates efficiency in the NAS • Want to create a complete operating picture of the NAS • This presentation focuses on editing SUA and ATCAA definitions

19. Goals of AIM in SWIM Context • End-to-end SUA and ATCAA digitization • From definition to implementation • NASR will store digitized SUA and ATCAA definition data • SAMS will manage operational status and schedule • ERAM will report actual hot/cold status back to SAMS • All exchanges using AIXM • Support field requirements • The generated data should be used to create legal definitions • This includes user-friendly definitions that reference geographical borders (“geoborders”) like rivers, roads, etc. • Allow for communication between FAA and military stakeholders

20. Current Status • SUA data is digitized by NACO and stored in NASR • Not truly “digital”: complex shapes are stored as textual descriptions • Cannot compute accurate metrics • Cannot display true geospatial representations of shape • ATCAA data is not nationalized • Each facility manages its own ATCAAs • Facilities may have conflicting definitions of same ATCAA • ERAM requires a single definition

21. Current Status, cont’d • Demo built on LuciadMap software • Shape generation through CAD editing • Displays any background and standard aeronautical data (ARINC, DAFIF) for visualization • Want to support design within context • Mockups of website • Need feedback from users about what and how they want to communicate

22. Demonstration of Software

23. Conclusion • The FAA has a need for better information management to support decision-making • SWIM and AIM are providing the tools • Will require change in detail of procedures with few changes to FAA 7400.2 • In the end, we get better data and a streamlined process

24. Technological Details

25. Architecture of Demo • Data stored in Postgres database • Interactions with database done through Apache CXF (FUSE Web Services FrameworK) web services • LuciadMap communicates only with web services • All data is stored and read as AIXM 5.0 • Using the SAA extensions

26. LuciadMap • LuciadMap has proven to be useful as a tool for generating airspace editing capabilities • Primary issue with LuciadMap is lack of documentation • LuciadMap’s AIXM 5 capabilities are strong • By end of development, Luciad had implemented ability to read new AIXM 5 documents using user-provided XSDs