Event Service Web Processing Service Data Management Service Aviation Client

110 Copyright © 2013 Open Geospatial Consortium.

13.2 Registry Service

The OWS-9 Aviation Registry was used to host resources shared between multiple OGC services e.g. ISO metadata pertaining to datasets common to multiple WFS implementations Snowflake, Comsoft, Styling information shared between multiple Feature Portrayal Services FPS implementations Envitia, Luciad, and ISO Service metadata describing the Services deployed in OWS-9. The efficient retrieval of metadata task was also implemented using the Aviation Registry by designing queries to retrieve only the relevant excerpts of the metadata desired by clients. The participants used InsertUpdateGet transactions to create User accounts, publish common resources, and efficiently retrieve resources using complex filtered queries. No functional or performance issues were encountered during the OWS-9 initiative.

13.3 Event Service

Compared to the ES used in the previous OGC test beds, major improvements have been implemented during OWS-9, particularly features summarized under the term “Advanced filtering functionality.” These included “Event Service Update Intervals”, “Stored Filters”, “AIXM Features as Geometry Operands”, “Spatial Filtering of Non-spatial Features”, “Simple Altitude Queries” as well as “Selective Metadata Retrieval”.

13.4 Web Processing Service

Implementation of WPS profiles to support ePIB map generation and geometry processing, including calculation of topological relations between two AIXM 5.1 features in ellipsoidal space. Supported topological relations: INTERSECTS, DISJOINT, EQUALS, TOUCHES, CROSSES, OVERLAPS, CONTAINS, WITHIN, COVERS, COVERED_BY.

13.5 Data Management Service

Within the OWS-9, a set of functionalities to provide reliable and efficient management of communications between aircraft and services located on the ground were implemented and tested: ฀ DMS service discovery; which mainly concerns the process of finding and setting the processing options to be done at the DMS by the aircraft and dispatch client. ฀ DMS basic pass-through; which handles the forwarding of requestresponse and notifications between aircraft client and OGC web services. ฀ Reliable messaging. ฀ Data compression expansion ฀ Data filtering. Copyright © 2013 Open Geospatial Consortium. 111 ฀ Dispatch synchronization.

13.6 Aviation Client

Aviation clients were implemented and tested that provide map-centric displays with intuitive user interface giving access to data from entities such as Web Feature Service, Event Service, and the Data Management Service. The continuing evolution of these clients provided rich set of capabilities and features that help to demonstrate the OWS-9 Aviation scenario and to perform testing and integration with a wide variety of service components. OGC ® Engineering Report OGC 12-147 Copyright © 2013 Open Geospatial Consortium. 112 Annex A ‐ SWIM Compliance Assessment Introduction The purpose of the SWIM Compliance Assessment is to provide information to the OGC and FAA on: ฀ The alignment of SWIM compliance requirements and OGC standards. ฀ The applicability of a SWIM requirement to OWS-9 services, clients, or components. In recognition that some SWIM compliance requirements appear to be focused on FAA programs that operate in the SWIM environment, we need to envision a future where there is a bi-directional flow of information between OGC services and FAA programs. From this perspective, we would appreciate your input on SWIM requirements that would not be applicable to web services data exchanges involving external entities. Completing the Matrix Please enter a compliance value from 0 to 100 in the Self-Assessment Column. ฀ Make your best subjective estimate of the compliance. ฀ It is acceptable for you to enter less than 100 in the Self-Assessment column if your service, client, or component doesn’t clearly meet the requirement due to the maturity of your service, client, or component solution. ฀ It is acceptable to enter NA in the Self-Assessment Column with an explanation for why that requirement doesn’t apply to the project or is not being complied with. The Notes column of the Assessment Table provides you with the opportunity to: ฀ Provide the rationale for your assessment. ฀ Comment on the applicability of the SWIM requirement to your service, client, or component. Copyright © 2013 Open Geospatial Consortium. 113 File Naming Convention Please add a hyphen to the name of this file and then enter your company name and then upload to the SWIM Compliance Analysis folder on the OGC portal at OGC Web Services, Phase 9 Thread 1 - Aviation SWIM Compliance Analysis. For example – SWIM Compliance Assessment-SpeedSquared.docx 114 Copyright © 2013 Open Geospatial Consortium. Assessment Identification: Company: ___________________________ Point of Contact Name and E-mail: ______________________________________________ OWS-9 Service Client Component: __________________ Reference Requirement Self-Assessment compliance Notes Comments

4.1 Technology Acquisition