24
Copyright © 2013 Open Geospatial Consortium.
The workflow illustrated in Figure 6 describes the process used by the Client to request a subscription from an Event Service ES. The Client sends the subscription request to the
DMS including an ES endpoint and the DMS forwards the request to the appropriate ES. Upon receipt of the data updates or notifications from the ES, the DMS maps the update
interval if required to the consumer reference to verify that update interval specifications are being satisfied. Additionally, the DMS performed data validation,
filtering, and prioritization in accordance with its re-configured set of technical rules. This processed data was sent to the Client and a copy or summary was sent to the
Dispatcher.
Client DMS
ES Dispatcher
15.0 Subscription Request with ES endpoint 16.0 Subscription Request
17.0 Data Updates Notifications 18.0 Map Update Interval to Consumer Reference
19.0 Verify Update Intervals
23.0 Processed Data 24.0 Data Copy or Summary
20.0 Perform Data Validation 21.0 Perform Filtering
22.0 Perform Prioritization
Figure 6 Data Management Service Workflow – Subscription Request Receive Notifications
6.2 Component Descriptions
6.2.1 COMSOFT Web Feature Service
6.2.1.1 Overview
COMSOFT’s Aeronautical Information Management Database CADAS-AIM
DB
is a fully featured AIXM 5 database. It has been especially developed to natively support all
concepts of AIXM 5, including static and dynamic data, digital NOTAMs and custom application schemas. It is designed to serve as a base for integrating AIM products and
Copyright © 2013 Open Geospatial Consortium.
25 components such as electronic Aeronautical Information Publication AIP, Charting,
NOTAM Office, or Briefing with a central Aeronautical Database. A design principle is the interoperability with other systems. As the database is the core
of any integrated Aeronautical Information Manual AIM solution, an open interface that can be used independently from any platform and programming language is one of the
key features. For an optimal support of AIXM 5 CADAS-AIM
DB
provides the CAW- interface. In OWS-9, an extension to the WFS 2.0 specification was developed and
implemented for better support for dynamic feature data such as AIXM 5.
6.2.1.2 Purpose in OWS-9
In OWS-9, the CADAS-AIM
DB
was used as a WFS data store and DNOTAM event source. As a WFS data store, it hosts static BASELINE and PERMDELTA time slices
and dynamic data TEMPDELTA time slices. Time slices can be retrieved from and stored to the WFS. The retrieval operations support complex filters built of logical,
spatial, temporal and comparison operators.
When TEMPDELTA time slices are inserted, corresponding DNOTAM events are created and sent to registered Event Services by a Web Service message.
6.2.1.3 Accomplishments
Several accomplishments in different work areas were achieved. Data loading and service deployment
o Data loaded, validated, transformed and corrected from various sources: Productive European Organisation for the Safety of Air Navigation
EAD AIXM 4.5 data, mapped by the COMSOFT AIXM 4.5 to 5.1 Mapper to AIXM 5.1 data North America and Middle-
Northern Europe.
OWS-9 simulated airport, DONLON, data set, corrected according to AIXM schema and temporality model and enriched with
metadata US ePIB data set, General Mitchell International Airport and
Bradley International Airport, corrected according to temporality model and enriched with metadata
o Deployment of two WFS instances, one for North American data and one for Middle-Northern Europe data.
o Registering Event Services as recipients of DNOTAM messages, which are generated on data insertion at the Web Feature Service
26
Copyright © 2013 Open Geospatial Consortium.
Implementation o Calculation of airspace extents in full 2.5D and time, including composite
airspaces unions, intersections and subtractions and airspace parts based on borders references to GeoBorder features.
o Support for altitude queries on airspaces o Calculation of extents of non-spatial feature types runways, taxiways and
aprons and support for spatial filtering of non-spatial feature types. o Support for AIXM features as geometry operands by feature reference.
o Support for the WFS Temporality Extension. o Support for selective metadata retrieval.
Conceptual Work o Improving and finalizing the WFS Temporality Extension OGC
Discussion Paper, incorporating feedback from other participants. o Specification of altitude queries, of using AIXM features as geometry
operands and of selective metadata retrieval.
6.2.1.4 Challenges
