- OGC® Standards
- OGC Standards List
- Specification Profiles
- Abstract Specification
- OGC Reference Model
- OGC Schema Updates
- Public Engineering Reports
- TC Policy Directives
- GeoDRM Reference Model
- Best Practices
- Discussion Papers
- Deprecated Documents
- Retired Documents
- Requests (RFP's, RFQ's...)
- White Papers
- Change Requests
- Submit Change Request or Requirement
OGC Public Engineering Reports
Documents that present technology issues being considered in the Working Groups of the Open Geospatial Consortium Technical Committee. Their purpose is to create discussion in the geospatial information industry on a specific topic. These papers do not represent the official position of the Open Geospatial Consortium nor of the OGC Technical Committee. Schemas for some of these documents can be at the Discussion Paper Schema Repository.
| Document Title (click to download) | Version | Document # | Editor | Date |
|---|---|---|---|---|
AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report |
0.4.0 | 09-129 | Nadine Alameh | 2010-02-16 |
| This AIP-2 Engineering Report (ER) describes a set of transverse technology Use Cases developed and applied in the GEOSS Architecture Implementation Pilot Phase 2 (AIP-2). Such Use Cases define reusable activities within a service-oriented architecture, tailored for the GEOSS environment. This report contains the general Use Cases that were specialized by community Working Groups to implement several specific Societal Benefit Area (SBA) Scenarios in AIP-2. The SBA Scenarios and specialized use cases are defined in separate AIP-2 ERs. This AIP-2 ER will be offered for consideration by the GEOSS Best Practice Registry editors and to OGC Technical Committee for consideration as a Best Practice. | ||||
Authentication IE Enginerring Report |
10-192 | Jeff Harrison | 2011-01-03 | |
| Results of the Auth IE are presented in this Engineering Report document and serve as guidance to both implementers and organizations deploying solutions that involve basic authentication. It is the belief of the Auth IE participants that if such a document is made available to the community more OGC implementing products will natively support authentication. | ||||
End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2 |
1.0 | 09-182r1 | Josh Lieberman | 2010-02-16 |
| This Architecture Implementation Pilot, Phase 2 Engineering Report (AIP-2 ER) describes the practice of deploying, documenting, and registering contributed resources from the point of view of classes of GEOSS users who rely on GEOSS to support discovery and access to those resources. It emphasizes two paradigms for the GEOSS Common Infrastructure: 1) Service-oriented infrastructure for development of service-based community applications by technically advanced users; and 2) Content-oriented search facility and Web-based access mechanisms for end-users with a range of technical skills and domain knowledge. "End-to-end" here refers to the bidirectional connection between desired discovery practices and goals on the user end; and the required resource interfaces and documentation on the provider end. | ||||
Fusion Standards Study Engineering Report |
0.3.0 | 09-138 | George Percivall | 2010-03-21 |
| This OGC Engineering Report (ER) provides discussions and recommendations for information fusion, with a focus on geospatial information. In this ER, fusion is discussed in three categories: sensor fusion, object/feature fusion, and decision fusion. Recommendations in this ER will be considered in the planning of future activities including the OWS-7 Testbed. | ||||
Ocean Science Interoperability Experiment Phase 1 Report |
08-124r1 | Luis Bermudez | 2011-01-03 | |
| This OGC Engineering report details lessons learned and best practices defined as part of the Phase 1 Ocean Science Interoperability Experiment (Oceans IE). The Oceans IE was performed to investigate the use of OGC Web Feature Services (WFS) and OGC Sensor Observation Services (SOS) for representing and exchanging point data records from fixed in-situ marine platforms. The activity concluded that for the Oceans community use of in-situ sensors that the OGC Sensor Observation Services (SOS) was better suited than the use of OGC Web Feature Services (WFS) for this purpose. | ||||
Ocean Science Interoperability Experiment Phase II Report |
09-156r2 | Luis Bermudez | 2011-01-04 | |
| This OGC Engineering Report documents the work performed by the participants of the Ocean Science Interoperability Experiment Phase II. This work is a follow-on to the OGC Oceans IE Phase 1 activity. Specifically, this IE addressed the following tasks: • Automated metadata/software installation via PUCK protocol. • Offering of complex systems (e.g. observations systems containing other systems) such as collection of stations. • Linking data from SOS to out-of-band offerings. • Semantic Registry and Services. • Catalogue Service-Web Registry. • IEEE-1451/OGC-SWE harmonization As a result of this experiment, a number of recommendations and conclusions were identified. | ||||
OGC® Engineering Report: Water Information Services Concept Development Study |
11-013r6 | Luis Bermudez, David Arctur | 2011-07-14 | |
| The purpose of this report is to recommend appropriate architectures and procedures for migrating the CUAHSI HIS to the OGC-based WaterML 2.0 encoding (profile of OGC O&M standard) and OGC web services such as Sensor Observation Service (SOS), Web Feature Service (WFS), Web Mapping Service (WMS), Web Coverage Service (WCS), and Catalogue Service for the Web (CSW). This report may be used as the basis for future OGC Interoperability Program initiatives. | ||||
OGC® NSG Plugweek Engineering Report |
09-140r2 | Paul Daisey | 2010-07-30 | |
| The Open Geospatial Consortium (OGC®) conducted a series of tests that examined the interoperability, suitability and performance of National System for Geospatial- Intelligence (NSG) Profiles provided by the National Geospatial-Intelligence Agency (NGA) of four OGC Standards, Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS), and Catalog Service (CAT). In the study, vendors, users, and other interested parties conducted Technology Integration Experiments (TIEs) and mutually refined clients, services, interfaces and protocols in the context of a hands-on engineering experience expected to shape the future NGA, NSG and Geospatial Intelligence (GEOINT) web based distribution. | ||||
OGC Fusion Standards Study, Phase 2 Engineering Report |
10-184 | George Percivall | 2010-12-13 | |
| This Engineering Report summarizes two phases of the Open Geospatial Consortium (OGC®) Fusion Standards study and of the fusion prototypes developed during the OWS-7 Testbed which occurred between the two study phases. Recommendations from the first phase of the study were implemented in OWS-7. Based upon the results of OWS-7, responses to two Requests for Information and a multi-day workshop, this report provides a cumulative set of recommendations for advancing fusion based on open standards. | ||||
OGC OWS-6-AIM Engineering Report |
0.3.0 | 09-050r1 | Hans Schoebach | 2009-07-27 |
| This report establishes a baseline for the technical architecture, its alternatives and issues for implementing the use cases as specified in the OWS-6 AIM thread RFQ including the temporal WFS supporting the temporal FE 2.0 operators, the Event Service Notification architecture and the client EFBs. | ||||
OGC SAA Pilot Study Engineering Report |
11-055 | Steve Miller | 2011-11-23 | |
| This OGC® document describes the architecture used for the implementation of the SAA Dissemination Pilot Study demonstrations. This includes an overview of the implemented components and workflows, and discussions of lessons learned. | ||||
OWS-6 3D Flythrough (W3DS) Engineering Report |
0.3.0 | 09-075r1 | Arne Schilling | 2009-08-05 |
| This document describes the 3D portrayal server components which were used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective pf this activity was to efficiently stream and display GML 3 content in internet or wireless networks with limited bandwidth, especially focusing on the CityGML application profile. The server for delivering landscape and city models is implemented as Web 3D Service (W3DS) that is designed as portrayal service. | ||||
OWS-6 CITE TEAM Engine Engineering Report |
0.3.0 | 09-072 | James Ressler | 2009-08-05 |
| This document summarizes the work done on the TEAM compliance test engine and DGIWG Profile compliance test by Northrop Grumman for the CITE thread of OWS-6 in 2008-2009. | ||||
OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report |
0.3.0 | 09-007 | Scott Fairgrieve | 2009-10-09 |
| This document outlines the concepts, best practices, and lessons learned gathered from integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC Sensor Web Enablement (SWE)-based architecture. The document also specifies a web service interface for interacting with CCSI sensors and defines the basis for a profile that can be used to represent CCSI sensor definitions, data, and commands in SWE formats. | ||||
OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS |
0.3.0 | 09-006 | Keith Pomakis | 2009-08-05 |
| This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the development of SOAP/XML and REST interfaces for the Web Map Tiling Service (WMTS). | ||||
OWS-6 Geoprocessing Workflow Architecture Engineering Report |
0.3.0 | 09-053r5 | Bastian Schäffer | 2009-10-09 |
| This document covers Geoprocessing Workflow best practices and methods in a SOA environment. A RESTful approach was also conducted in this testbed, but no specific implementation details were available to be included in this ER; also, the RESTful workflow approaches and technology used in this testbed was essentially same as that used in OWS-5. | ||||
OWS-6 GeoProcessing Workflow Thread Summary ER |
0.3.0 | 09-063 | Lewis Leinenweber | 2009-09-11 |
| This OGC® document summarizes work completed in the GeoProcessing Workflow thread of the OWS-6 Testbed, it is applicable to the OGC Interoperability Program testbed. | ||||
OWS-6 Georeferencable Imagery Engineering Report |
0.3.0 | 09-034 | Genong (Eugene) Yu, Liping Di | 2009-07-29 |
| This document discusses considerations about and recommendations for approaches for georeferenceable imagery under the Sensor Web Enablement thread during OGC Web Services Phase 6. This is an extension to the work described in the previous engineering report number OGC 08-071 . Georeferencealbe imagery is “a referenceable grid that has information that can be used to transform grid coordinates to external coordinates, but the transformation shall not be required to be an affine transformation”. Geolocation of georeferenceable imagery refers to the techniques described in ISO 19130, such as sensor models, functional fit models, and spatial registration using control points. | ||||
OWS-6 GeoXACML Engineering Report |
0.3.0 | 09-036r2 | Jan Herrmann, Andreas Matheus | 2009-07-24 |
| The aim of this OGC Engineering Report is to show how to provide access control for OGC Web Services (OWS). In the first part of this document we will briefly introduce the relevant details of XACML 2.0, OGC GeoXACML 1.0 and some related profiles. | ||||
OWS-6 GML Profile Validation Tool ER |
0.3.0 | 09-038r1 | Clemens Portele | 2009-08-14 |
| This document outlines an approach for validating data accessed from a Web Feature Service. Two types of validation are supported: • XML Schema validation against the GML application schema • Validation of additional constraints encoded in Schematron This report describes the validation tool, the types of constraints that have been tested and documents the results. | ||||
OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report |
0.3.0 | 09-067r2 | Akiko Sato, Nobuhiro Ishimaru, Guo Tao, Masaaki Tanizaki | 2009-10-09 |
| This document described the Outdoor and Indoor 3D Routing and Services which are used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective is to enhance a network topology for the current CityGML specification based on the knowledge acquired through the development and experimental evaluation of this project. | ||||
OWS-6 Secure Sensor Web Engineering Report |
0.3.0 | 08-176r1 | Andreas Matheus | 2009-07-29 |
| The main purpose of this Engineering Report is to introduce standards-based security solutions for making the existing OGC Sensor Web Services, as described in the OWS-6 SWE baseline, ready towards the handling of sensors in the intelligence domain. | ||||
OWS-6 Security Engineering Report |
0.3.0 | 09-035 | Rüdiger Gartmann, Lewis Leinenweber | 2009-10-09 |
| This Engineering Report describes work accomplished during the OGC Web Services Testbed, Phase 6 (OWS 6) to investigate and implement security measures for OGC web services. This work was undertaken to address requirements stated in the OWS-6 RFQ/CFP originating from a number of sponsors, from OGC staff, and from OGC members. | ||||
OWS-6 SensorML Profile for Discovery Engineering Report |
0.3.0 | 09-033 | Simon Jirka, Arne Bröring | 2009-07-29 |
| This document defines a basic SensorML profile for discovery purposes. Besides a minimum set of metadata also the structure of according SensorML documents is defined in order to ensure a consistent metadata description. This goal is achieved by a set of Schematron rules that can be used to validate if a given SensorML document complies with the profile described in this engineering report. | ||||
OWS-6 Sensor Web Enablement (SWE) Engineering Report |
0.3.0 | 09-064r2 | Ingo Simonis | 2009-09-11 |
| This OGC® document summarizes work completed in the OWS-6 Sensor Web Enablement (SWE) thread. | ||||
OWS-6 Styled Layer Descriptor (SLD) Changes ER |
0.3.0 | 09-015 | Craig Bruce | 2009-09-11 |
| This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Styled Layer Descriptor (SLD) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. | ||||
OWS-6 SWE Event Architecture Engineering Report |
0.3.0 | 09-032 | Thomas Everding, Johannes Echterhoff | 2009-07-29 |
| The document describes an abstract event architecture for service oriented architectures. Furthermore various techniques for implementing an event architecture and working with events are discussed. | ||||
OWS-6 SWE Information Model Engineering Report |
0.3.0 | 09-031r1 | Thomas Everding | 2009-07-16 |
| This OGC® document is an OGC Engineering Report for the “Harmonization of SWE Information Models” activity within the OWS-6 SWE thread. The document discusses relations between OGC standards SensorML, SWE Common and GML and investigates solutions for increased synergy between these standards. This activity also created UML models of the data types used in SWE and GML. This report shows how UncertML can be integrated into different SWE encodings, namely SWE Common and Observations and Measurements. This report further discusses the integration of MathML and EML into the SWE environment with an emphasis on SensorML processes and processing. This document does not discuss the SWE information model related aspects of catalog entries for sensor services and discovery. This topic is covered in a separate Engineering Report. | ||||
OWS-6 SWE PulseNet™ Engineering Report |
0.3.0 | 09-073 | James Ressler | 2009-08-05 |
| This document summarizes work delivered on the Sensor Web Enablement (SWE) thread of OWS-6. In particular, Northrop Grumman’s contribution from PulseNet™ to the Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC SWE-based architecture. | ||||
OWS-6 Symbology-Encoding Harmonization ER |
0.3.0 | 09-012 | Craig Bruce | 2009-08-17 |
| This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the harmonization of OGC Styled Layer Descriptor (SLD) and Symbology Encoding (SE) symbology formats with ISO 19117 symbology format, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. | ||||
OWS-6 Symbology Encoding (SE) Changes ER |
0.3.0 | 09-016 | Craig Bruce | 2009-09-11 |
| This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Symbology Encoding (SE) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. | ||||
OWS-6 UTDS-CityGML Implementation Profile |
0.3.0 | 09-037r1 | Clemens Portele | 2009-07-20 |
| This OGC document specifies a CityGML-based application schema for a subset of an Urban Topographic Data Store (UTDS) as specified by the US National Geospatial-Intelligence Agency (NGA). The particular focus of this implementation profile was to test the applicability of CityGML to UTDS data. This document specifies the implementation profile as well as the findings. | ||||
OWS-6 WPS Grid Processing Profile Engineering Report |
0.3.0 | 09-041r3 | Bastian Baranski | 2009-07-24 |
| This OGC Engineering Report describes and reviews the Grid Computing related activity completed during the OGC OWS-6 Interoperability testbed. The document describes the WPS processes deployed in the different demonstration scenarios and offers recommendations to the OGC community as to how to better harmonize the standards work of the OGC with Grid Computing platforms and related concepts and technologies. | ||||
OWS-7 - Authoritative Data Source Directory Engineering Report |
10-086r1 | Andrew Turner | 2010-08-18 | |
| This document presents the Authoritative Data Source Directory (ADSD) engineering suggestions and results of the OGC OWS-7 ADSD thread. This group focused on creating a workflow for geospatially referencing, finding, and federating data sources with associated authority and relevance. | ||||
OWS-7 - Towards secure interconnection of OGC Web Services with SWIM |
10-155 | Andreas Matheus | 2010-08-18 | |
| This Engineering Report provides guidance and generate action items for the OGC standardization effort to properly enable security in the near future such that a seamless, interoperable but secure interconnection between OGC Web Services and FUSE ESB technology stack as selected by use in the System Wide Information Management (SWIM) System of the US Federal Aviation Administration (FAA) can be achieved. | ||||
OWS-7 Aviation – AIXM Assessment Report |
10-131r1 | Debbie Wilson | 2010-08-18 | |
| This report shall focus on evaluating the ability to: - Serve, filter and update AIXM 5.1 data via the OGC WFS-T 2.0 interface - Recommend guidelines or cross-walks for interpreting the new AIXM 5.1 schedules in conjunction with the Timeslice model in a web services environment | ||||
OWS-7 Aviation – FUSE Deployment Engineering Report |
10-130 | Debbie Wilson | 2010-08-18 | |
| This document describes the integration results of deploying OGC Web Services on the FAA chosen Enterprise Service Bus (ESB) – FUSE. Snowflake Software were commissioned to evaluate the impacts of the FAA SWIM security requirements for both secure messaging and user authentication and gain an understanding of the requirements for deploying OGC web services into the Apache FUSE Enterprise Service Bus (ESB). | ||||
OWS-7 Aviation – WXXM Assessment Engineering Report |
10-132 | Bruno Simmenauer | 2010-08-18 | |
| The document describes the results of using OGC Web Services for accessing and using WXXM data, notably within aviation scenarios involving rerouting procedures motivated by the sudden closure of airspace areas caused by the eruption of a volcano. The focus of this document will be to evaluate the ability to encode and serve associated operational data with WXXM 1.1.1. | ||||
OWS-7 Aviation Architecture Engineering Report |
10-079r3 | Thomas Everding | 2010-09-09 | |
| The document describes the architecture that was implemented in the Aviation thread of OWS-7. The document provides an overview of the architecture and describes the implemented components. In addition it discusses “eventing” and notification techniques relevant for the aviation domain. | ||||
OWS-7 CCSI-SWE Best Practices Engineering Report |
10-073r1 | Scott Fairgrieve | 2010-06-30 | |
| This document seeks to define the Best Practices for integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) compliant and potentially other CBRN-based sensors into an OGC Sensor Web Enablement (SWE)-based environment. The document focuses on the practical application of SWE services and encodings for describing and interacting with CCSI sensors and data and draws heavily from and expands upon work performed in the OGC Web Services Phase 6 (OWS-6) testbed to define methodologies for integrating CCSI sensors into a SWE-based environment both now, by building upon the OWS-6 work, and in the future, by defining CCSI profiles of the SWE specifications. | ||||
OWS-7 Dynamic Sensor Notification Engineering Report |
10-061r1 | Johannes Echterhoff, Ingo Simonis | 2010-06-30 | |
| This document is applicable to scenarios where moving sensors need to be tracked and their entry into an area of interest needs to be detected. The document presents a detailed discussion of different approaches for encoding tracked object position. Two approaches for implementing dynamic sensor tracking and notification are described, one based on the Sensor Alert Service specification and the other based on the Sensor Event Service specification. An overview of standards and specifications relevant for and related to dynamic sensor tracking and notification is provided. | ||||
OWS-7 Engineering Report - Aviation Portrayal |
10-127r1 | Roger Brackin | 2010-08-18 | |
| This document describes the requirements, design, technical implementation and technology trialed for the Feature Portrayal service chain used in OWS-7. This includes the interfaces to the OWS Data Services deployed, the feature portrayal servers, the interfaces to clients and the registry information model and interface. | ||||
OWS-7 Event Architecture Engineering Report |
10-060r1 | Johannes Echterhoff | 2010-08-02 | |
| This document is applicable to use cases in which event-driven architecture principles are applied in Spatial Data Infrastructures. The document specifies publish/subscribe functionality for OGC web services. This is done by first defining an abstract publish / subscribe model and then deriving functional requirements from this model. | ||||
OWS-7 Feature and Statistical Analysis Engineering Report |
10-074 | Theodor Foerster, Bastian Schäffer | 2010-08-18 | |
| This Engineering Report (ER) is a deliverable for the OGC Web Service 7 testbed. The focus of this ER is using the OGC Web Processing Service (WPS) interface standard for Feature and Statistical Analysis (FSA). Specifically, the ER documents how to enhance interoperability of FSA processes that are hosted as WPS processes on the Web. This ER is coordinated with the Feature and Decision Fusion (FDF) WPS Profiling ER. | ||||
OWS-7 Information Sharing Engineering Report |
10-035r2 | David Rosinger, Stan Tillman | 2010-09-08 | |
| This Engineering Report describes an investigation and evaluation of various methods of sharing information within a collaborative environment accomplished during the OGC Web Services Testbed, Phase 7 (OWS-7). The intent of the OWS-7 Information Sharing activity was to move toward a standardized method of sharing geospatial data between Integrated Clients and potentially catalogs. This report reviews past OGC work within this area, makes recommendations based on the best parts of previous collaboration techniques, and provides recommendations for encoding documents for use in information sharing. | ||||
OWS-7 Motion Imagery Discovery and Retrieval Engineering Report |
10-087 | Wenli Yang, Liping Di | 2010-08-18 | |
| This Motion Imagery Discovery and Retrieval Engineering Report (ER) documents the metadata used to tag geolocation of Motion Imagery (MI) for discovery, retrieval and linkage with other data sources over the same location, especially the metadata information required to geometrically co-register multiple motion images at pixel level so that data recorded at different times (e.g., different days) and/or by different providers for common or overlapped FOVs can be compared and pixel level changes among the different images can be accurately detected and delineated. This ER reflects one of the achievements during the OWS 7 Sensor Fusion Enablement (SFE) thread, which builds on the OGC Sensor Web Enablement framework that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. | ||||
OWS-7 Motion Video Change Detection |
10-036r2 | Stan Tillman | 2010-08-18 | |
| This Engineering Report documents the development effort to build a Web Processing Service (WPS) to perform a change detection algorithm on two motion video streams. It will examine the WPS Motion Video Change Detection architecture from various viewpoints in order to describe its purpose, data models, functional decomposition, and interaction between distinct computational components. | ||||
OWS-7 Web Processing Service Profiling Engineering Report |
10-059r2 | Christian Kiehle, Theodor Foerster | 2010-08-18 | |
| The overall scope of this OWS-7 Engineering Report is to clarify how to write and register a WPS profile. WPS profiles enable clients to search and identify equivalent WPS-based processes distributed on the web. Therefore, this ER provides guidelines for designing WPS Profiles based on WPS interface specification 1.0.0. | ||||
OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed |
10-094 | David Arctur | 2010-10-22 | |
| The OGC Web Services, Phase 7 (OWS-7) Testbed was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. | ||||
OWS-8 AIXM 5.1 Compression Benchmarking |
11-097 | Jérôme JANSOU, Thibault DACLA | 2011-12-19 | |
| AIXM stands today for the de-facto standard for Aeronautical Information Publication, used by air control service providers from Europe, USA and Australia. With version 5.1, it reaches a level of maturity allowing the support of Digital NOTAMs, as the first official version of these messages was published this year. In a near future, AIXM will be carried inside WFS requests but also into notification messages along WS event services. This last channel will be the one dedicated to D-NOTAMs. As D-NOTAM is aimed at aircrafts pilots, their transmission to the aircraft will use air/ground data link. Today, datalink communications lack bandwidth and future datalink will still have a limited capacity. | ||||
OWS-8 Aviation – WXXM Engineering Report |
11-072r2 | Wenny Rahayu, Torab Torabi, Andrew Taylor-Harris, Florian Puersch | 2012-01-25 | |
| This OGC™ document specifies the advancement of WXXM and Weather Concepts in the OWS-8 Aviation Thread. The focus is on investigating and demonstrating the applicability and suitability of WXXM in producing accurate, real-time aircraft weather radar data using OGC™ Web Coverage Services (WCS) to be used by meteorological applications and services supporting aviation. Such applications provide information which enhances safe and efficient tactical and | ||||
OWS-8 Aviation Architecture Engineering Report |
11-093r2 | Johannes Echterhoff | 2011-12-19 | |
| This OGC® document describes the architecture implemented in the OWS-8 Aviation thread, including general workflows. The document contains a summary description of the various components within the architecture. An introduction to the Access Control System is provided. Furthermore, the document describes relevant aspects of handling events and notifications. Lessons learned – for example regarding the AIXM Temporality Model – as well as scenarios and accomplishments are documented as well. | ||||
OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report |
11-086r1 | Jan Herrmann, Andreas Matheus | 2012-01-25 | |
| This engineering report describes how to provide access control for WFS-T 2.0 instances in the OWS-8 Authoritative AIXM Data Source scenario. | ||||
OWS-8 Bulk Geodata Transfer Using GML Engineering Report |
11-085r1 | Panagiotis (Peter) A. Vretanos | 2011-11-07 | |
| This document describes the work done during the OWS-8 test bed investigating methods and apparatus for distributing individual geospatial data sets and/or collections of data sets in a consistent manner between machines that may or may not be connected via a network. The investigation focuses on the initialization of a target WFS, from a source WFS, for the purpose of GeoSynchronization. Data, schema, metadata and/or topology are exported from a source WFS, transferred to a target WFS (either electronically or physically via some media) and then imported into the target WFS. From that point on, the two WFS's are maintained in synchrony using a Geosynchronization Service (see OGC 10-069r2). | ||||
OWS-8 Bulk Geodata Transfer with File Geodatabase |
11-114 | David Danko, Lance Shipman, Paul Ramsey | 2011-11-16 | |
| This document provides an overview of the File Geodatabase API and documents the testing performed in the OWS 8 Testbed. | ||||
OWS-8 CCI Portrayal Registries Engineering Report |
11-062r2 | David Burggraf, Ron Lake | 2011-11-17 | |
| The OWS-8 Cross Community Interoperability (CCI) thread was built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artifacts. This OGC engineering report aims to present findings from the portrayal registries as part of the CCI subthread | ||||
OWS-8 CCI Schema Automation Engineering Report |
11-064r3 | Clemens Portele, Reinhard Erstling | 2011-11-23 | |
| This OGC® document specifies improvements to the processing of information represented in or referenced from an application schema in UML to create derived, implementation level resources, in particular: • XML Schema documents to represent types and their properties • Schematron schema documents to represent constraints • XSLT-Stylesheets to create KML instances of features The documented improvements have been specified, implemented in the ShapeChange tool and tested in the context of schemas developed as part of the NGA's Topographic Data Store (TDS) schemas. The work is a continuation of the work documented in OGC® document 10-088r2, the OWS-7 Schema Automation Engineering Report. | ||||
OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report |
11-063r6 | Gobe Hobona, Roger Brackin | 2011-11-23 | |
| The OWS-8 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artefacts. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving data retrieved from heterogeneous data models that are available through web services conformant to OGC standards. The engineering report will briefly introduce relevant details of the semantic web and mediation. The document will make recommendations on establishing a semantic mediation architecture that uses OGC web services and emerging practice from the semantic web community. Based on the scenario adopted by the CCI thread, the document will also discuss the pros and cons of adopting relevant standards. The engineering report will offer recommendations on how specific OGC standards may be adopted or modified in order to support semantic mediation. | ||||
OWS-8 Digital NOTAM Refactor |
11-106r1 | Rob Atkinson, James Groffen | 2011-12-19 | |
| AIXM is a GML Application Schema described in UML using the relevant ISO / OGC standards from the 19100 series. The Digital NOTAM Events Specification (DNES) is an extension of AIXM that can describe notices to airmen using the AIXM standard. This document has been produced in conjunction with the Domain Modelling Cookbook - a practical guide to domain modelling following a series of best practices developed by the CSIRO and other OGC members. Where possible, documentation of the refactor effort for Digital NOTAM to be compatible with these practices is incorporated into the domain modelling cookbook. | ||||
OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE |
11-089r1 | Daniel Tagesson | 2011-11-23 | |
| This OGC® document gives guidelines to portrayal of AIXM according to ICAO aviation symbology using SLD/SE. | ||||
OWS-8 Geoprocessing for Earth Observations Engineering Report |
11-116 | Peter Baumann | 2011-12-19 | |
| Ad-hoc processing of Earth Observation (EO) data available through online resources is gaining more and more attention. Expected benefits include - More versatile EO data access - More convenient EO data access - Consequently, broadened use and exploitation of EO data - An important step towards integration of EO data into automatic chaining and orchestration - More efficient EO data access: indicating the exact desired result and evaluating processing code close to the coverage data source (i.e., on the server) minimizes network traffic, one of today’s critical performance limiting factors. | ||||
OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report) |
11-113r1 | Ingo Simonis | 2011-11-23 | |
| This report aims at providing an information model for the usage of video moving target indicator data (VMTI), ground moving target indicator (GMTI) and tracking information (STANAG 4676) in the context of standardized spatial data infrastructures compliant to OGC and ISO standards. If possible, precedence was given on using the OGC Sensor Web Enablement suite of standards, as this suite provides a homogeneous suite of standards to express sensor and sensor observation data in the context of OGC. This means that all encodings are based on Observation and Measurements version 2 (O&M) and implemented as an application schema according to the rules of Geography Markup Language version 3.2 (GML). An information model – so called ‘bookmark’ – to conserve the trace from a moving object back to the original base data is discussed briefly. | ||||
OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report |
11-095 | Stephan Meissl, Peter Baumann | 2011-12-19 | |
| This Engineering Report describes progress on EO-WCS in the course of OWS-8. | ||||
OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report |
11-096 | Stephan Meissl, Peter Baumann | 2011-11-23 | |
| This Engineering Report describes progress on EO-WCS in the course of OWS-8. | ||||
OWS 7 Engineering Report - Geosynchronization service |
10-069r2 | Panagiotis (Peter) A. Vretanos | 2010-08-02 | |
| This candidate standard describes a service that allows data collectors to propose changes to be made to a data provider's features. A change proposal can be made to create new data or to modify/delete existing data. Proposed changes are reviewed (either manually or automatically) an are either accepted or rejected. Accepted changes are applied to the feature(s). The service also maintains a log of all changes applied to each feature that can be used for replication. | ||||
Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed |
11-139r2 | David Arctur | 2011-12-19 | |
| The OGC Web Services, Phase 8 (OWS-8) Testbed was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for OWS-8 was conducted from March to September 2011. | ||||








Join OGC LinkedIn
Follow OGC on Twitter
RSS Feeds