OGC Requests

OGC seeks public comment on Symbology Conceptual Core Model (SymCore)

Status: 
Please note:  This Request is scheduled to close on 13 September 2019.
Open Date: 
Mon, 08/12/2019
Closing Date: 
Fri, 09/13/2019 - 23:59
Description: 

 

The Symbology Conceptual Core Model (SymCore) is the basis for defining symbology rules for the portrayal of geographic data. The model is modular and extensible (one core model, many extensions), and also encoding agnostic (one symbology model, many encodings).

The work by the SymCore Standards Working Group that led to this proposal was done as a continuation of the OGC Symbology Encoding standard (SE 1.1), only with a focus on modularity and extensibility.

SymCore provides a consistent approach that:

  • Provides the flexibility required to achieve adequate symbology rules for a variety of information communities, e.g. aviation symbols, weather symbols, thematic maps, etc, and;
  • Achieves high-level styling interoperability without encoding dependencies.

As such, Symcore defines a more general and portable symbology model for use across the broad OGC standards baseline that can be applied to geospatial datasets as well as online geospatial data and mapping services.

Potential implementations of SymCore are expected to enhance OGC standards such as the Web Map Service, Web Feature Service, GeoPackage, and others. By sharing a common core, and using the extension mechanism, integration of these standards for the purposes of cartographic representation could be greatly simplified.

Last year, authors of the SCCM standard requested early public feedback in advance of finalizing the candidate standard to ensure that the work was reflecting the community’s needs. This announcement marks the start of the formal public comment period as the standard moves towards adoption.

Downloads: 

OGC Symbology Conceptual Model: Core part (18-067r2) (PDF) [note that this is a new revision, posted August 20, 2019]
 
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 major revision to OGC Abstract Specification Topic 0 - Overview

Status: 
Please note:  This Request is scheduled to close on 20 June 2019.
Open Date: 
Tue, 05/21/2019
Closing Date: 
Thu, 06/20/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on an update to Abstract Specification Topic 0 - Overview.

The purpose of the OGC Abstract Specification is to create and document a conceptual model that enables the creation of the consistent, interoperable, high quality OGC Implementation Standards.

The OGC Abstract Specification is comprised of a number of Topic volumes. Topic 0 provides an overview of the OGC Abstract Specification. Each Topic addresses a specific conceptual model, such as for metadata or geometry, as a foundation unit upon which to build OGC standards. The complete set of Topic volumes collectively form the OGC Abstract Specification. The Abstract Specification is an evolving baseline. This update to Topic 0 is a major revision deleting many obsolete topics and adding several new topics.

The Abstract Specification, while being implementation-neutral, provides robust technical concepts for discussing issues of interoperability. The Topic 0 Overview provides a summary of all the Abstract Specification Topics as well as guidelines developed by OGC for the development of technical standards. The Topic 0 also discusses how OGC conducts a community-based consensus processes to define, test, edit, and approve standards for interfaces and encodings that enable interoperability of geospatial content, services, and applications. For example the “core and simple standards” guideline discusses methods to consider the comprehensive scope of applications when developing a new standard while recognizing that the best standards are as simple as possible.

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 candidate Sensor Model Language (SensorML) v2.1 standard

Status: 
Please note:  This Request is scheduled to close on 14 June 2019.
Open Date: 
Thu, 05/16/2019
Closing Date: 
Fri, 06/14/2019 (All day)
Description: 

 

SensorML is a machine-readable language for describing sensors, actuators, and processes surrounding measurement. SensorML is a key component of OGC’s Sensor Web Enablement (SWE) suite of standards. SWE is concerned with establishing interfaces and encodings that enable a “Sensor Web” through which applications and services are able to access sensors of all types - from the commonplace sensors associated with mobile phones to high-precision remote sensing platforms such as satellites - as well as the observations generated by them, over the Web.

The primary focus of the Sensor Model Language (SensorML) is to provide a robust and semantically-tied means of defining processes and processing components associated with the measurement and post-measurement transformation of observations. This includes sensors and actuators as well as computational processes applied pre- and post-measurement.

The main objective is to enable interoperability so that sensors and processes can be better understood by machines, utilized automatically in complex workflows, and easily shared between intelligent sensor web nodes.

The recently published version 2.1 of the GMLJP2 imagery standard additionally supports SensorML descriptions, thereby giving GMLJP2 the ability to support “raw” sensor model imagery. Sensor model images are useful because they contain geospatial information that is lost upon processing into rectified ‘map’ images. Besides being processed into map images, sensor model images may be used, for example, for precision mensuration or to construct 3D models of ground structures. Such physical and replacement sensor model descriptions are being compiled into a sensor model repository by the OGC Naming Authority.

The SensorML v2.1 Standard specifies a means to create a general mathematically-based model for transforming an initial state (for example, the location and orientation of a camera) to a final state (the ground point of origin of the light entering the camera) via a serial processing chain. The standard also provides an associated XML implementation. The main change of SensorML 2.1 from SensorML 2.0 is the addition of setEncodedValues in both the standard and in the XML implementation to provide a method to more concisely encode arrays, as compared to setArrayValues.

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 update to GeoTIFF standard

Status: 
Please note:  This Request is scheduled to close on 23 June 2019.
Open Date: 
Tue, 05/14/2019
Closing Date: 
Sun, 06/23/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on v1.1 of the GeoTIFF standard. The GeoTIFF v1.1 standard formalizes the existing GeoTIFF specification version 1.0 by integrating it into OGC’s standardization process. Additionally, v1.1 aligns GeoTIFF with the on-going addition of data to the EPSG Geodetic Parameter Dataset.

The Geographic Tagged Image File Format (GeoTIFF) specifies the content and structure of a group of industry-standard tag sets for the management of georeferenced or geocoded raster imagery using Aldus-Adobe’s public domain Tagged Image File Format (TIFF). GeoTIFF defines a set of TIFF tags provided to describe all "Cartographic" information associated with TIFF imagery that originates from satellite imaging systems, scanned aerial photography, scanned maps, digital elevation models, or as a result of geographic analyses. The goal is to provide a consistent mechanism for referencing a raster image to a known model space or earth-based coordinate reference system, and for describing those coordinate reference systems.

The GeoTIFF format is used throughout the geospatial and earth science communities to share geographic image data. That usage inevitably leads to identification of new requirements and needs for profiles, extensions, and improvements to the original GeoTIFF Specification. The OGC is well established as a forum for standardization in the GeoTIFF producer and user communities and, as such, it provides an inclusive standardization process for those communities. This candidate standard is the first step in the process of integration of the GeoTIFF specification into OGC’s standardization process, with the adjustment of a minor revision in order to allow the use of the modern EPSG register, allowing backward compatibility with Revision 1.0.

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 requests public comment on draft charter for new Blockchain and Distributed Ledger Technologies (BDLT) Domain Working Group

Status: 
Please note:  This Request is scheduled to close on 15th March 2019.
Open Date: 
Fri, 02/22/2019
Closing Date: 
Fri, 03/15/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the draft Charter for a proposed Blockchain and Distributed Ledger Technologies (BDLT) Domain Working Group (DWG).

Distributed Ledgers are collections of replicated, shared, and synchronized digital records that are stored across multiple sites. The technologies used to implement such ledgers (Distributed Ledger Technologies aka DLT) include the Blockchain, which is a digital ledger of records arranged into linked and cryptologically-validated chunks of data called blocks. By far the most widely cited application of Blockchain technology is in the finance sector where it can be used as a cryptocurrency, the two most notable examples being Bitcoin and Ethereum.

However, other applications for DLT and Blockchain are now gaining popularity. There is potential use of DLT in, for example, land registration, city services, space, pan-government registries, and justice. Location can play a key role in many of these application areas. For example: the location of financial transactions can determine what taxes apply; the location of the boundary of a property forms the basis of its registration; and the location where evidence is discovered in a crime scene can have an impact on judicial proceedings.

At present, there are numerous DLT services and networks available. There is however no standard for how those DLT should encode geospatial information such as locations, coordinates, and coordinate reference systems. The various DLT have therefore implemented ad hoc geo-encoding approaches. This situation is likely to lead to a problem of limited interoperability between information held in different DLT networks.

Given the immutable nature of Blockchain and DLT, the need for standardization of the information encoded within them is time-critical: any poorly encoded geographic information will remain inherent to a given ledger for as long as it is in use.

The purpose of the BDLT DWG is to build understanding of Blockchain and Distributed Ledger Technologies, as well as the potential requirements for geospatial standardization within those technologies. Further, the BDLT DWG will identify gaps and issues that should be addressed to improve geospatial standardization in Blockchain and DLT.

In October 2018, OGC published the Discussion Paper Geospatial Standardization of Distributed Ledger Technologies with the purpose of improving the understanding of Blockchain and distributed ledger technologies. One recommendation of the Discussion Paper was to form the OGC BDLT DWG.

Comment: 

Comments can be submitted to a dedicated email reflector for a twenty-one 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

Subscribe: 

Charter requests are not currently able to be subscribed to.

OGC Requests: 

OGC requests public comment on draft charter for new Portrayal Domain Working Group

Status: 
Please note:  This Request is scheduled to close on 7th March 2019.
Open Date: 
Thu, 02/14/2019
Closing Date: 
Thu, 03/07/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the draft Charter for a proposed Portrayal Domain Working Group (DWG).

The Portrayal DWG is being established to address a gap in the OGC standards baseline with regards to the portrayal of geospatial data, including the standardization of portrayal rules, registry data, styles, and encoding formats. Portrayal concerns the way that information, in this case geospatial data, is presented to humans. Cartography, one form of map portrayal, is one of the oldest of human graphical portrayal skills.

Traditionally, conveying spatial information involved the use of maps. However, as the types and complexity of geospatial information has changed in-step with technological advances, so have the requirements for the portrayal of this information. For example, it is now common for geospatial data to be portrayed (visualized) in areas such as 3D, augmented reality, and gaming & simulation. Additionally, multi-dimensional portrayal is rapidly expanding as advances in information technology and computer graphics make more visualization alternatives available. 

Many of these technology advances are currently being considered across several OGC Domain and Standards Working Groups. However, they often consider only a portion of the portrayal challenge or address a portrayal solution tailored to a specific issue and not a broader approach within a unified framework. 

OGC will benefit from a coherent organization to ensure that common and consistent frameworks and approaches are applied to portrayal issues. 

The Portrayal Domain Working Group, therefore, will bring together a community to define a common portrayal framework, provide direction to portrayal Standards Working Groups, and provide guidance to other Domain Working Groups on portrayal concerns. 

OGC membership has registered a concern that without a portrayal framework with updated consensus standards and Best Practices, divergence will continue in the community and interoperability will be inhibited. External to OGC, multiple communities of interest such as the Defence Geospatial Information Working Group (DGIWG), the U.S. National System for Geospatial-Intelligence (NSG), the American, British, Canadian, Australian, and New Zealand (ABCANZ) Armies program, the meteorological and oceanographic community, and the International Hydrographic Organization (IHO) have advocated for increased portrayal capabilities supported by OGC standards. 

Comment: 

Comments can be submitted to a dedicated email reflector for a twenty-one 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

Subscribe: 

Charter requests are not currently able to be subscribed to.

OGC Requests: 

OGC Seeks Public Comment on MetOcean profile and extensions to WCS 2.1

Status: 
Please note:  This Request is scheduled to close on 15th March 2019.
Open Date: 
Wed, 02/13/2019
Closing Date: 
Fri, 03/15/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the MetOcean profile and extensions to WCS 2.1. A public comment on these documents was also held in 2018, but the documents have been renamed and the schemas updated, so a second round of comment is sought.

The Meteorological and Oceanography (MetOcean) community works with massive datacubes of content organized in 4-dimensional space and time. Extracting valuable information from these datasets requires efficient query and delivery of the content perfectly suited to the user’s needs.

The MetOcean community relies upon the OGC Web Coverage Service (WCS) to search and deliver such content. The community has developed a new profile and two new extensions to WCS 2.1 to address MetOcean requirements. The MetOcean Profile fully exploits the multi-dimensional nature of WCS2.1, which is built on the new OGC Coverage Implementation Schema (CIS) 1.1. The GetCapabilities file size is reduced by almost 2 orders of magnitude, making discovery much easier.

As the WCS2.1 core provides only general metadata, the MetOcean Profile adds community-specific metadata to this core.

Additionally, the MetOcean Profile introduces the terms “Groups” and “CoverageCollections” as a way to both efficiently access the data, and structure the return of data. The main benefit of Groups is in creating a structure that reflects the organization of the intended use of data, rather than its underlying structure. This provides a hierarchical way of nesting services. The main benefit of CoverageCollections allows for the identification of collections of data for easier access to the data.

Two extensions have also been developed to facilitate retrieval of coverage data according to the operational requirements of those using MetOcean data. One extension specifies how to extract a corridor based on a trajectory from a multidimensional coverage. The other extension defines how to extract data contained within a polygon defined either by a set of points or the radius and position of a circle point.

Through the addition of community-based metadata, Groups & CoverageCollections, and the two new operations, the efficiency of both MetOcean data access and retrieval has been increased substantially.

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 GroundwaterML v2.3 Candidate Standard

Status: 
Please note:  This Request is scheduled to close on 13 February 2019.
Open Date: 
Mon, 01/14/2019
Closing Date: 
Wed, 02/13/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on an updated version of the ‘OGC WaterML 2: Part 4 – GroundWaterML 2 (GWML2)’ candidate standard.

The GroundWaterML2 standard (GWML2) describes a conceptual and logical schema for the exchange of groundwater data, as well as a GML/XML encoding. Changes in GWML2 version 2.3 include:

  1. The addition of a compact encoding using the OGC Sensor Web Enablement standards for information recorded along the length of a water well;
  2. An encoding strategy to connect a water well with this information using the OGC Observations and Measurements standard, and;
  3. A logical schema change that increases the maximum number of entries from one to many for two well construction properties.

 

All changes are backward compatible with the previous GWML2 schemas.

A significant portion of the global water supply can be attributed to groundwater resources. Effective management of such resources requires the collection, management and delivery of related data, but these are impeded by issues related to data availability, distribution, fragmentation, and heterogeneity: collected data is not all readily available and accessible, available data is distributed across many agencies in different sectors and often thematically fragmented, and similar types of data are diversely structured by the various data providers. This situation holds both within and between political entities, such as countries or states, impairing groundwater management across all jurisdictions.

Groundwater data networks are an emerging solution to this problem as they couple data providers through a unified data delivery vehicle based on open standards for data access and data content. The relative maturity of OGC data access standards, such as the Web Feature Service (WFS) and Sensor Observation Service (SOS), combined with the rise of water data networks, have created a need for a common groundwater data standard: GroundWaterML2.

The primary goal of this standard is to capture the semantics, schema, and encoding syntax of key groundwater data, in order to enable information systems to interoperate with such data. The GroundwaterML2 standard (GWML2) forms Part 4 of the WaterML 2 suite of 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 PipelineML candidate standard, to support the interchange of data pertaining to oil and gas pipeline systems

Status: 
Please note:  This Request is scheduled to close on 7 January 2019. 
This page previously linked to an outdated version of the candidate standard, so commenters are urged to re-download the correct version linked below.
Open Date: 
Thu, 12/06/2018
Closing Date: 
Mon, 01/07/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) is seeking public comment on the candidate PipelineML Conceptual and Encoding Model Standard (PipelineML).

PipelineML presents the concepts supporting the interchange of data pertaining to oil and gas pipeline systems, allowing pipeline operators to rapidly send and receive asset information to/from service providers in a manner that effectively promotes traceable, verifiable, and complete data management practices. This initial release of PipelineML addresses two critical business use cases that are specific to the pipeline industry: new construction surveys, and pipeline rehabilitation.

This candidate standard defines the individual pipeline components with support for lightweight aggregation. Additional aggregation requirements such as right-of-way and land management will, in the future, use the OGC LandInfra standards with utility extensions. Future extensions to PipelineML Core are planned to include, among others, cathodic protection, and facility & safety.

PipelineML was advanced by an international team of contributors from the US, Canada, Belgium, Norway, Netherlands, UK, Germany, Australia, Brazil, and Korea. The standard is a deliverable of the OGC PipelineML Standards Working Group (SWG).

Downloads: 
[previously, an outdated version was linked here. Please re-download the document to view the correct version]
 
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 adoption of two jointly developed OGC/W3C standards

Status: 
Please note:  This Request is scheduled to close on 27 December 2018.
Open Date: 
Tue, 11/27/2018
Closing Date: 
Thu, 12/27/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks comments on the possible adoption of the jointly developed OGC/W3C Time Ontology in OWL (OWL-Time) and Semantic Sensor Network (SSN) Ontology candidate standards. Both are published as W3C Recommendations and were prepared by the Spatial Data on the Web Working Group (SDWWG) - a previous joint W3C/OGC project now succeeded by the Spatial Data on the Web Interest Group. OGC is now seeking comment as to whether these documents should also be approved as OGC standards.

OWL-Time is an OWL-2 DL ontology of temporal concepts for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing and sharing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock or using another temporal reference system such as Unix-time, geologic time, or different calendars.

The Semantic Sensor Network (SSN) ontology is used for describing actuators, sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things.

OGC is seeking public input on if it should adopt these documents as OGC Standards.

Downloads: 

The Time Ontology in OWL and Semantic Sensor Network Ontology W3C Recommendations are available for download from W3C: Time Ontology in OWL (OWL-Time) and Semantic Sensor Network (SSN) Ontology.

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