54
Copyright © 2013 Open Geospatial Consortium.
o Additional aeronautical and weather data formats like AIXM 3.34.04.5, ARINC 424, DAFIF, ASTERIX, ASDI and GRIB.
o Raster format support GeoTIFF, TIFF, JPEG, JPEG 2000, GMLJP2, JPIP, PNG, GIF, ECW, MrSID, CADRGADRGUSRP, DTED, USGS
DEM, Oracle GeoRaster … for satellite imagery and elevation background data.
o Vector format support ESRI Shape, MapInfo MIFMAP, GML 23.1.13.2.1, SVG, DGN, DWG, OracleInformixMSSQL databases …
for vector-based background data. o Other formats: OBJ, OpenFlight, OGC KML 2.2 and GeoPDF.
6.2.14 Deployment characteristics
All development was done in Java, using the Java Development Kit JDK 1.6. The client application was developed on top of Luciad’s COTS product LuciadLightspeed. The
software runs on any operating system for which a Java Virtual Machine 1.6 or higher exists. For the 3D visualization, a graphics card with support for OpenGL 1.2 or higher is
required.
6.2.14.1 Challenges
A reoccurring challenge when working on the client is obtaining proper interoperability with all services and overcoming implementation differences. Adherence to the
specification of data formats and OGC services is only one step, as there is typically always room for implementation differences that impede interoperability in practice. We
therefore want to emphasize the usefulness of official compliancy tests such as the ones developed by OGC e.g. for the WMS, WFS and WCS, as they can help to increase
overall interoperability. It might be an idea for the future to develop official compliancy tests to verify the guidelines and best practices have been developed the past years with
respect to using OGC services in the Aviation domain.
6.2.14.2 Accomplishments
The key accomplishments for Luciad’s Aviation client component in OWS-9 included: Demonstration of and interaction with most of the service components provided
within the Aviation thread and with the Semantic Mediation WPS provided within the CCI thread.
Contribution of a rich client equipped with lots 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. Collaboration with OWS-9 service component providers on the developed
functionality and provision of feedback from a client’s perspective.
Copyright © 2013 Open Geospatial Consortium.
55
7 Data Provision via Web Feature Service and Event Service
7.1 Overview
This section describes the architecture for data provision used in OWS-9. In particular, the dynamic provision and processing of AIXM 5.1 data Feature updates via Digital
NOTAM events based on the service architecture of previous test beds using WFS-T and Event Service is described. Besides AIXM the support for providing weather data
encoded as WXXM 1.1.3 is illustrated. This includes the description of the used event encodings as well as the involved components. The advanced filtering functionality is
described per topic in detail. Finally, the issues and drawbacks which have been observed during OWS-9 as well as future work items are presented.
7.2 General Service Architecture
The data provision service architecture consists of two layers. Data subsccription matching mechanisms are served by Event Service ES implementations. Data storage
and provision functionality is supplied via Web Feature Service WFS, see section 7.2.1.
The data provision layers are accessed from the Data Management Service DMS and Aviation Clients via common requestresponse communication WFS, WCS and
subscriptions for certain data of interest ES. Filters on attributes, spatial extent, etc. are defined using the Filter Encoding Specification FES 2.0 for both WFS and ES.
Figure 15 - Data Provision Service Architecture.
