OGC Requests

OGC seeks public comment on Part 1 of the Features and Geometries Candidate Standard

Status: 
Please note:  This Request is scheduled to close on 27 July 2018.
Open Date: 
Wed, 06/27/2018
Closing Date: 
Fri, 07/27/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on Part 1 of the Features and Geometry candidate standard.

The Features and Geometries candidate standard provides the requirements for defining and representing geographic features in geographic information systems, applications, databases, and data formats. This standard is being developed in multiple parts in conjunction with ISO / TC 211 and will impact or replace ISO 19107, ISO 19109, and ISO 19125. The major advantage to the approach taken with the multi-part Feature and Geometries standard is that the parts are each relatively small and focused in content and ease the burden of implementation of the standard.

The Implementation Standard Geographic information — Features and geometry – Part 1: Feature models describes how geographic information held in datasets and databases using a ‘feature model’ are structured, created, stored, queried, and manipulated.

Part 1: Feature models updates the General Feature Model with various representations, as well as how it determines the basic form of geographic information. This is derived from and extends ISO 19109, which, in its current form, only addresses schema-based data storage defined in UML, but leaves possibilities open for other non-schematic design systems.

The data structures described in the candidate standard have been made more flexible than in earlier versions of this and supporting standards. The Features and Geometry standard describes semantically-structured data sets aimed to represent reality, not the specific needs of a single application. This shifts the support of interoperability from creating transfer formats, to creating inclusive, flexible - and thereby interoperable - data stores that are usable by a wide range of applications.

Further parts will describe the distinction between planar and geodetic/ellipsoidal geometry, simple geometries, other geometry, and topology structures, while a set of parallel standards will define WKT (well-known text) and JSON (JavaScript Object Notation) for both features and geometry.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks public comment on Tile Matrix Set Candidate Standard

Status: 
Please note:  This Request is scheduled to close on 26 July 2018.
Open Date: 
Tue, 06/26/2018
Closing Date: 
Thu, 07/26/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the Tile Matrix Set candidate standard.

A Tile Matrix Set defines a tile indexing pyramidal system to allow easy retrieval of the appropriate tiles by a mapping service. In a tile matrix set, a tile can be uniquely identified by a tile column, a tile row, and a tile matrix identifier. A Tile Matrix Set is useful across many applications for sharing geospatial information.

In 2007, OGC approved and released the Web Map Tile Service (WMTS) standard. WMTS 1.0 provides a definition of a Tile Matrix Set. Over time, other OGC standards dealing with tiles in other ways needed to use the same definition. Unfortunately, these OGC standards could not use the definition independently because the definition was formally linked to the tile service and was limited to an XML encoding.

The Tile Matrix Set candidate standard decouples the concept of a tile matrix set from the WMTS standards so that any standard or application that requires the use of a tile matrix set can reference the concept directly. This candidate standard also adds an informative list of commonly used tile matrix sets with XML and JSON schemas and examples. A future Tile Matrix Set standard is anticipated to impact future revisions of other OGC standards such as GeoPackage and the next version of WMTS.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks public comment on new Earth Observation Exploitation Platform Domain Working Group

Status: 
Please note:  This Request is scheduled to close on 30 May 2018.
Open Date: 
Wed, 05/09/2018
Closing Date: 
Wed, 05/30/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks comments on the draft charter of a proposed Earth Observation Exploitation Platform Domain Working Group (DWG).

Earth Observation (EO) data captured by satellites has always been ‘big’ but an ever-increasing number of satellites capturing data at higher spatial and spectral resolutions has meant that client access to EO data has required larger and larger downloads, and even in-house IT infrastructure just to manage the volume of data. Thus, the incentive to create cloud-based, web-accessible platforms in which to access and analyse EO data on-the-fly has also grown in recent years.

This incentive has meant that cloud-based EO ‘Exploitation Platforms’ have been independently developed by many public organizations and commercial companies. However, their independent development has also hampered interoperability between these platforms. The next step in this data exploitation revolution, then, is to link the platforms together to create an ecosystem in which each platform can contribute its offered services to the implementation of more complex use cases.

For example, a scientist assessing climate changes may need data across several providers - from vegetation indexes, to predictive rainfall models and more - in order to answer a research question. Standardized elements of EO Exploitation Platforms could provide a single interface for this climate scientist where each ‘cloud’ talks to each other in the background, sharing the data, applications, tools and services between the platforms to generate a final ‘picture’ for the scientist.

Indeed, the ESA EO Exploitation Platforms built to date all share a common set of functionalities ripe for standardization:

  • Data provisioning;
  • Information visualization and analysis;
  • Data processing; and
  • User Authentication, Authorization, and Accounting.

 

This Domain Working Group will bring together service and technology providers of Earth Observation Data Exploitation Platforms in order to define a standards-based framework for the platforms’ interfaces that addresses and unifies the platforms through this common set of functionalities.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: charter-requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

OGC Requests: 

OGC seeks public comment on new Interoperable Simulation and Gaming Domain Working Group

Status: 
Please note:  This Request is scheduled to close on 28 May 2018.
Open Date: 
Mon, 05/07/2018
Closing Date: 
Mon, 05/28/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks comments on the draft charter of a proposed Interoperable Simulation and Gaming Domain Working Group (DWG).

Gaming systems and technologies, while originally developed for entertainment, are increasingly being used as an interoperable mechanism for simulation of real world activities. Such gaming systems traditionally relied upon fictitious or highly-simplified representations of the world. However, recent years have seen widespread use of realistic depictions of environments and capabilities that can represent large areas of the Earth.

Considerable innovation and enhancements in virtual environment fidelity, as well as reductions in system costs, are expected to result from increased use of cloud, mobile, and immersive technologies. However, most computer-based gaming systems have technical architectures that are different from traditional simulation systems. This DWG will assess how gaming systems might be leveraged for geospatial use cases, including how existing individual vehicle and system operations may be significantly enhanced by interoperation with game-based simulations.

Additionally, the DWG will examine how geospatial data can fit into standard formats and conceptual models compatible with the fast and deterministic storing, retrieval, and rendering of high-quality 3D virtual environments that is required by simulations.

This DWG will provide a forum for the discussion of requirements and use cases for standards and the registration of implementations related to use and re-use of geospatial data within the Interoperable Simulation and Gaming (ISG) community, as well as broader discussion of ISG topics and research activities.

Further, the DWG will aim to increase awareness of the advantages of ISG in general, to define the qualities of ISG systems, to enhance their interoperability, and to support activities to standardize operations within and among them related to the use and re-use of geospatial data

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: charter-requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

OGC Requests: 

OGC Seeks Public Comment on update to Abstract Specification Topic 2: Referencing By Coordinates

Status: 
Please note:  This Request is scheduled to close on 21 May 2018.
Open Date: 
Thu, 04/19/2018
Closing Date: 
Mon, 05/21/2018 (All day)
Description: 

 

Third edition of this Abstract Specification describes the requirements for creating coordinate systems referencing locations in space and time.

The Open Geospatial Consortium (OGC) seeks public comment on the third edition of the Abstract Specification Topic 2: Referencing By Coordinates.

Aligned with the draft third edition (2018) of ISO 19111, Geographic Information - Referencing by coordinates, the Abstract Specification describes the data elements, relationships, and associated metadata required for spatial referencing by coordinates, expanded from a strictly spatial context to include time. The document was prepared by the OGC Coordinate Reference Systems Standards Working Group in close collaboration with ISO Technical Committee ISO/TC 211, Geographic information/Geomatics.

In addition to describing a coordinate reference system, the Abstract Specification provides for the description of a coordinate operation between two different coordinate reference systems, or a coordinate operation to account for crustal motion over time. With such information, spatial data referenced to different coordinate reference systems can be referenced to one specified coordinate reference system at one specified time. This facilitates spatial data integration. Alternatively, an audit trail of coordinate manipulations can be maintained.

This third edition cancels and replaces the second edition (OGC Topic 2 of 2008), which has been technically revised. This document also incorporates the provisions of OGC Topic 2.1 of 2010, which is to be cancelled.

The changes in this edition compared to the previous edition are:

  • inclusion of applicable modern geodetic terminology;
  • extension to describe dynamic geodetic reference frames;
  • extension to describe geoid-based vertical coordinate reference systems;
  • extension to allow triaxial ellipsoid for planetary applications;
  • extension to describe three-dimensional projected coordinate reference systems;
  • addition of 'datum ensembles' to allow grouping of related realizations of a reference frame where for lower accuracy applications the differences are insignificant;
  • clarification in the modelling of derived coordinate reference systems;
  • remodelling of the metadata elements scope and extent;
  • addition of requirements to describe coordinate metadata and the relationship between spatial coordinates.
  • additional modelling of temporal coordinate reference system components sufficient for spatio-temporal coordinate referencing;
  • consolidation of the provisions of OGC Abstract Specification Topic 2.1 (Spatial referencing by coordinates - Extension for parametric values) into this document;
  • change in name from 'Spatial referencing by coordinates' to 'Referencing by coordinates', due to the inclusion of the non-spatial coordinate reference system subtypes of parametric (from Abstract Specification topic 2.1) and temporal.
  • the correction of minor errors.

The various OGC Abstract Specifications provide the conceptual foundation for most OGC standards development activities. Open interfaces and protocols are built and referenced against Abstract Specifications, thus enabling interoperability between different brands and different kinds of spatial processing systems. The Abstract Specification provides a reference model for the development of OGC Implementation Standards.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks public comment on version 1.1 of CDB standard

Status: 
Please note:  This Request is scheduled to close on 30 April 2018.
Open Date: 
Thu, 03/29/2018
Closing Date: 
Mon, 04/30/2018 (All day)
Description: 

OGC seeks public comment on version 1.1 of CDB standard

Minor update to CDB standard brings guidance on metadata, vector network priority, and more.

The Open Geospatial Consortium (OGC) seeks comments on the candidate CDB version 1.1 standard. CDB version 1.1 is a minor revision and is fully backwards compatible with Version 1.0.

The CDB standard defines a conceptual model, as well as rules for implementing the model, for the storage, access, and modification of a synthetic environment data store as required in high-fidelity simulation and mission rehearsal, such as for battlefield simulation. The standard addresses the challenge of full plug-and-play interoperability and reuse of geospatial data in a modeling and simulation environment. CDB data stores can also be exposed by OGC web services, such as a Web Map Service (WMS) or Web Feature Service (WFS) to permit visualization of the content outside of the traditional simulator hardware environment.

The main revisions for this version of the CDB standard are:

  • Detailed guidance on how to implement geospatial metadata in a CDB data store. This guidance is independent from the metadata standard that an organization wishes to use;
  • Incorporation of additional guidance requested by the CDB user community on such topics as vector network priority and significant size;
  • Updates to the CDB schema to add additional lights and feature types as well as spelling corrections and changes to support geospatial metadata;
  • Numerous minor changes to correct ambiguous wording, incorrectly formatted tables, spelling errors and so forth.

​​​​​​​

A detailed description of the changes to the CDB standard can be found in the CDB 1.1 release notes.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks public comment on Web Services Security Candidate Standard

Status: 
Please note:  This Request is scheduled to close on 2 April 2018.
Open Date: 
Thu, 03/01/2018
Closing Date: 
Mon, 04/02/2018 (All day)
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the OGC Web Services Security Candidate Standard.

For years various implementations of OGC Web Services have integrated some degree of security through Information Assurance (IA) controls . However, these implementations break interoperability, as they each extend the functionality of OGC Web Service (OWS) standards differently. As such, interoperability between secured OGC Web Services and clients is limited to systems custom-built to work with an IA implementation.

The objective of the OGC Web Services Security Standard is to allow the hosting of OWS on HTTPS, the implementation of IA controls and to advertise its existence in an interoperable way with no impact to existing implementations using a backwards-compatible approach. No changes to existing OGC Web Services standards are required. The approach used in this candidate standard is based on existing functionality in the OGC Web Services Capabilities document in a consistent manner.

Uptake of the standardized approach as a build-in to new OGC Web Services standards will ensure security interoperability.

This standard has come as a result of research undertaken during OGC Testbeds 11, 12, and 13, part of OGC’s Innovation Program.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks public comment on GML in JPEG 2000 (GMLJP2) v2.1 Candidate Encoding Standard

Status: 
Please note:  This Request is scheduled to close on 29 March 2018.
Open Date: 
Tue, 02/27/2018
Closing Date: 
Tue, 03/27/2018 (All day)
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the GML in JPEG 2000 (GMLJP2) v2.1 Candidate Encoding Standard.

The GMLJP2 Candidate Encoding Standard defines how the Geography Markup Language (GML) is to be used within JPEG 2000 images and other gridded coverage data for adding geospatial content to imagery, such as the geographic coordinates of the image, annotations, or references to features.

This revised version 2.1 adds support for referenceable grid coverages via a recently published Coverage Implementation Schema (CIS) extension GMLCOVRGRID, which provides additional capabilities for this standard such as support for a wide range of sensor models described with SensorML 2.0 or with GML-based application profiles.

Sensor models envisioned for use with this standard include mathematical descriptions of imaging systems located on satellite and airborne platforms. A full example closely based on the Community Sensor Model for frame cameras is available here.

The standard will appeal to: developers intending to implement geospatially enabled JPEG 2000 encoders and readers; developers of both WFS and WCS who wish to provide support for JPEG 2000 formats; and developers who wish to use GML to give imagery a geospatial context.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks public comment on ‘SensorThings API Part 2 – Tasking Core’ Candidate Standard

Status: 
Please note:  This Request is scheduled to close on 22 March 2018.
Open Date: 
Tue, 02/20/2018
Closing Date: 
Thu, 03/22/2018 (All day)
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the OGC SensorThings API, Part 2 - Tasking Core Candidate Standard. The OGC SensorThings API is a free and non-proprietary lightweight interface specification that simplifies and accelerates the development of Web-based Internet of Things (IoT) applications.

The OGC SensorThings API provides an open, geospatial-enabled, and unified way to interconnect the IoT devices, data, and applications over the Web. Part 1 was released in 2016 and allowed management and reception of observations or measurements made by IoT sensors. Part 2 provides a mechanism to tell the sensor/actuator what to do

Application developers can use this open standard to connect to various IoT devices and create innovative applications without needing to individually integrate the heterogeneous protocols of the different IoT devices, gateways, and services. System manufacturers can embed the OGC SensorThings API in their IoT hardware and software platforms so that the different platforms’ IoT devices can effortlessly connect with other servers that implement the standard. Because device location communication is useful in almost every IoT application, an open, lightweight, widely used standards-based location encoding is part of the SensorThings API.

This new standard is designed specifically for resource-constrained IoT devices and the Web developer community. The candidate standard follows REST principles and uses an efficient MQTT transport and the flexible OASIS OData URL conventions.

The candidate OGC SensorThings API Standard was designed to be compatible with a rich set of proven and widely-adopted open standards, such as the Web protocols and the OGC Sensor Web Enablement (SWE) standards, including the ISO/OGC Observation and Measurement Encoding Standard. Thus, the OGC SensorThings API is extensible and can be applied in both simple and complex use cases.

At a high level, the OGC SensorThings API provides two main functionalities: Sensing, and Tasking. Each function is handled by a part. The Sensing part, an official OGC standard since 2016, provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems.

This, the Tasking part, provides a standard way for parameterizing - also called tasking of - task-able IoT devices, such as sensors, actuators, drones, or even satellites.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

OGC seeks public comment on Web Coverage Service (WCS) 2.1 Candidate Standard

Status: 
Please note:  This Request is scheduled to close on 19 March 2018.
Open Date: 
Thu, 02/15/2018
Closing Date: 
Mon, 03/19/2018 (All day)
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the Web Coverage Service (WCS) 2.1 candidate standard.

The OGC Web Coverage Service (WCS) standards suite defines methodology to access coverages (regular and irregular grids, including spatio-temporal datacubes, point clouds, and general meshes) from the Web. OGC has offered WCS standards since 2005, reflecting the importance and maturity of providing such data to Web clients.

The definition of a coverage is given by the OGC Coverage Implementation Schema (CIS). In 2017, CIS 1.1 was released as a backwards-compatible extension of coverages to CIS 1.0, with a unified grid model supporting any kind of spatio-temporal sensor, image (timeseries), simulation, and/or statistics data.

WCS 2.1 allows CIS 1.1 coverages to be served in addition to CIS 1.0 coverages. Hence, WCS 2.1 is backwards compatible with WCS 2.0: any service passing the WCS 2.1 conformance tests will also pass the WCS 2.0 tests. Further, all WCS 2.0 extensions remain applicable in the context of WCS 2.1.

By supporting the more general datacube model of CIS 1.1, the WCS 2.1 standard will simplify access to spatio-temporal ‘big datacubes’, with an operation spectrum ranging from simple subsetting in space and time up to complex spatio-temporal analytics through Web Coverage Processing Services (WCPS).

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.

OGC Requests: 

Pages