⇒ OGC: Open Geospatial Consortium
https://repository.oceanbestpractices.org/handle/11329/897
2024-03-28T15:43:17Z
2024-03-28T15:43:17Z
Development of Spatial Data Infrastructures for Marine Data Management; OGC - IHO Marine SDI Concept Development Study (CDS).
https://repository.oceanbestpractices.org/handle/11329/1551
2021-05-01T22:55:01Z
2019-01-01T00:00:00Z
Development of Spatial Data Infrastructures for Marine Data Management; OGC - IHO Marine SDI Concept Development Study (CDS).
Thomas, Robert; Idol, Terry
This engineering report presents the results of a concept development study on a
Marine Spatial Data Infrastructure (SDI), sponsored by the National Geospatial-
Intelligence Agency (NGA) - Maritime Safety Office (MSO), on behalf of the
International Hydrographic Organization (IHO) and the IHO MSDI Working Group
(MSDIWG), and executed by the Open Geospatial Consortium (OGC). The goal of
this study was to demonstrate to stakeholders the diversity, richness and value of a
Marine SDI – specifically data, analysis, interoperability and associated IT services
- including web services - in addressing needs of the marine domain.
The study included an open Request for Information (RFI) with the objective to
gather additional information to better support governments, agencies, nongovernmental
organizations and citizens, unlocking the full societal and economic
potential of the wealth of marine data at local, national, regional or international
levels. The RFI results also provide information and insight on the current state of
the Marine SDI. In addition to the RFI, a MSDI workshop and roundtable were held
to gather additional information from both expert panel members and the audience.
This engineering report presents an analysis of RFI, workshop and roundtable
responses and interactions which provided in depth information on requirements and
issues related to stakeholders, architecture, data, standards of current and a possible
future Marine SDI. In addition, this report will serve as the basis for improvement of
SDIs’ to support the marine domain. The responses will also be discussed with
potential sponsoring organizations that would provide funding opportunities for
possible Marine SDI Pilot(s) initiatives proposed for later this year, and in subsequent
years. All RFI, workshop and roundtable responses will contribute to Marine SDI(s)
moving forward. It will help to achieve greater interoperability, availability and
usability of geospatial Web services and tools across different types of marine spatial
data uses. In addition, these responses will provide identification of gaps, and
definition of core components of an SDI to be referenced by IHO MSDIWG and used
to define reference use-cases and scenarios for use in future pilot activities.
2019-01-01T00:00:00Z
Web Feature Service Implementation Specification with Corrigendum. Version 1.1.3.
https://repository.oceanbestpractices.org/handle/11329/1164
2019-11-23T12:13:36Z
2016-01-01T00:00:00Z
Web Feature Service Implementation Specification with Corrigendum. Version 1.1.3.
Vretanos, Panagiotis, A
This document describes the OGC Web Feature Service (WFS) operations. The WFS operations support INSERT, UPDATE, DELETE, LOCK, QUERY and DISCOVERY operations on geographic features using HTTP as the distributed computing platform.
In the context of this document, a transaction is a logical unit of work that is composed of one or more data manipulation operations. Since the manner in which geographic features are persistently stored is not addressed in this document, no transaction semantics, such as atomic failure, are assumed to exist. It is the function of a web feature service, in its interaction with the data storage system used to persistently store features, to ensure that changes to data are consistent. However, the document also acknowledges the fact that many systems do support standard concurrent transaction semantics and so proposes optional operations that will allow a web feature service to take advantage of such systems (e.g. relational database systems based on SQL).
Geographic features
This document adopts the same concept of a geographic feature as described in the OGC Abstract Specification (http://www.opengeospatial.org/specs/?page=abstract) and interpreted in the OpenGIS® Geographic Markup Language(GML) Implementation Specification [2]. That is to say that the state of a geographic feature is described by a set of properties where each property can be thought of as a {name, type, value} tuple. The name and type of each feature property is determined by its type definition. Geographic features are those that may have at least one property that is geometry-valued. This, of course, also implies that features can be defined with no geometric properties at all.
Processing requests
This section of the document outlines, in general terms, the protocol to be followed in order to process web feature service requests. Processing requests would proceed as follows:
A client application would request a capabilities document from the WFS. Such a document contains a description of all the operations that the WFS supports and a list of all feature types that it can service.
A client application (optionally) makes a request to a web feature service for the definition of one or more of the feature or element types that the WFS can service.
Based on the definition of the feature type(s), the client application generates a request as specified in this document.
The request is posted to a web server.
The WFS is invoked to read and service the request.
When the WFS has completed processing the request, it will generate a status report and hand it back to the client. In the event that an error has occurred, the status report will indicate that fact.
Note that “client application” may include Registries and other middleware, as well as conventionally understood “end-users”.
2016-01-01T00:00:00Z
Styled Layer Descriptor profile of the Web Map Service Implementation Specification [Corrigendum]. Version 1.1.0 (revision 4).
https://repository.oceanbestpractices.org/handle/11329/1163
2019-11-18T21:39:52Z
2007-01-01T00:00:00Z
Styled Layer Descriptor profile of the Web Map Service Implementation Specification [Corrigendum]. Version 1.1.0 (revision 4).
Lupp, Markus
This OGC® Implementation Specification specifies how a Web Map Service can be
extended to allow user-defined styling. Different modes for utilizing Symbology
Encoding for this purpose are discussed.
2007-01-01T00:00:00Z
Draft OpenGIS Web Notification Service Implementation Specification. Version 0.0.9.
https://repository.oceanbestpractices.org/handle/11329/1162
2019-11-18T21:40:30Z
2007-01-01T00:00:00Z
Draft OpenGIS Web Notification Service Implementation Specification. Version 0.0.9.
Simonis, Ingo; Echterhoff, Johannes
This OpenGIS© document specifies interfaces for requesting information describing the capabilities of a Web Notification Service, for managing registrations at such a service, for sending messages to registered users and for retrieving cached messages. It also proposes a common notification mechanism for OGC web services.
2007-01-01T00:00:00Z
OGC Sensor Alert Service Candidate Implementation Specification. Version 0.9.
https://repository.oceanbestpractices.org/handle/11329/1161
2019-11-18T21:41:19Z
2007-01-01T00:00:00Z
OGC Sensor Alert Service Candidate Implementation Specification. Version 0.9.
Ingo, Simonis
This OpenGIS© document specifies interfaces for requesting information describing the capabilities of a Sensor Alert Service, for determining the nature of offered alerts, the protocols used, and the options to subscribe to specific alert types.
2007-01-01T00:00:00Z
Reference Model for the ORCHESTRA Architecture (RM-OA). Version 2 (Rev 2.1).
https://repository.oceanbestpractices.org/handle/11329/1160
2020-05-06T23:05:25Z
2007-01-01T00:00:00Z
Reference Model for the ORCHESTRA Architecture (RM-OA). Version 2 (Rev 2.1).
Uslander, Thomas
This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It is an extension of the OGC Reference Model and contains a specification framework for the design of geospatial service-oriented architectures and service networks. The RM-OA comprises the generic aspects of service-oriented architectures, i.e., those aspects that are independent of the risk management domain and thus applicable to other application domains.
2007-01-01T00:00:00Z
OGC Common DataBase Volume 2 Appendices. Version 1.0.0.
https://repository.oceanbestpractices.org/handle/11329/1159
2019-11-18T21:42:38Z
2015-01-01T00:00:00Z
OGC Common DataBase Volume 2 Appendices. Version 1.0.0.
Graham, David
The full CDB specification, in its current, industry-maintained format and version, addresses the interoperability challenge of full plug-and-play interoperability and re-use of synthetic environment databases used for high fidelity simulation and mission rehearsal.
The first CDB specification was developed under a competitive contract awarded to CAE to meet requirements of the United States Special Operations Command. The CDB Specification was required to be open and non-proprietary as part of the original
requirements. The revision history of the industry-maintained specification is contained in the following document sections.
The CDB specification was been widely implemented by multiple, independent industry contractors for end-user simulation and mission rehearsal customers in many different countries over a period of ten years.
2015-01-01T00:00:00Z
OGC Common DataBase Volume 1 Main Body. Version 1.0,0.
https://repository.oceanbestpractices.org/handle/11329/1158
2019-11-18T21:43:45Z
2015-01-01T00:00:00Z
OGC Common DataBase Volume 1 Main Body. Version 1.0,0.
Graham, David
The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB
provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can
simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation
client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.
The application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM
and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.
The CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry.
The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships.
A CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications.
2015-01-01T00:00:00Z
OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response. Version 1.0.
https://repository.oceanbestpractices.org/handle/11329/1157
2019-11-18T21:44:40Z
2015-01-01T00:00:00Z
OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response. Version 1.0.
Percivall, George
Responding to an oil spill requires access to and understanding of many types of information. Effective, coordinated operations for the response are based on a shared, common picture of the situation. Interoperability provides shared situational awareness of
the crisis and the response activities. What is needed is a common picture of reality for different organizations that have different views of the spill so that they all can deal with it collectively.
Recent oil spills have provided lessons learned and recommendations on forming a Common Operating Picture for oil spill response. Through a joint project, industry is responding to the call, moving from recommendations to reusable best practices supported by open standards that can be deployed quickly in any region of the globe.
This architecture report is part of The International Association of Oil & Gas Producers and IPIECA Oil Spill Response - Joint Industry Project (IOGP–IPIECA OSR-JIP) to produce a recommended practice for GIS/mapping in support of oil spill response and for the use of GIS technology and geospatial information in forming a “Common Operating Picture” to support management of the response.
Interoperability seems to be at first a technical topic, but in fact, it is about organization. Interoperability seems to be about the integration of information. What it’s really about is the coordination of organizational behavior. The Oil Spill Response Common Operating Picture (OSR COP) project seeks to facilitate the coordination of organizational response to any oil
spill in the future.
2015-01-01T00:00:00Z
DGIWG – Web Map Service 1.3 Profile – Revision. Version 2.0.
https://repository.oceanbestpractices.org/handle/11329/1156
2019-11-18T21:45:33Z
2016-01-01T00:00:00Z
DGIWG – Web Map Service 1.3 Profile – Revision. Version 2.0.
Strobel, Stefan; Sarafinof, Dimitri; Wesloh, David; Lacey, Paul
This document defines specific DGIWG requirements, recommendations and guidelines for implementations of the ISO / OGC Web Map Service standard which is based on ISO 19128:2005 Web Map Server Interface / OpenGIS Web Map Server Implementation
Specification 1.3.0.
2016-01-01T00:00:00Z