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.
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).

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: 

OGC seeks public comment on Hierarchical Data Format Version 5 (HDF5) Core Standard

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

 

The Open Geospatial Consortium (OGC) seeks public comment on the candidate Hierarchical Data Format Version 5 (HDF5) Core Standard.

Hierarchical Data Format Version 5 (HDF5) is a data model, a programming interface, and a storage model for keeping and managing data. HDF5 supports an unlimited variety of data types, and is designed to be flexible and efficient for large and complex data. Due to its use of customizable data types, HDF5 is extensible, allowing communities and their applications to evolve the use and functionality of HDF5.

HDF5 provides an encoding standard particularly suitable to scientific and engineering geospatial applications that employ complex multidimensional datasets to describe phenomena that change over time and/or space.

HDF5 is designed to be simple yet versatile. HDF5 is capable of supporting complex data relationships and dependencies through its grouping and linking mechanisms. Additionally, HDF5 is self-describing through its accommodation of user-defined metadata.

The candidate OGC HDF5 Core standard defines the HDF5 data model to allow implementers to develop HDF5 content and tools using the HDF5 or other storage models and programming interfaces.

HDF5 is already in use by the OGC community: OGC’s NetCDF Enhanced Data Model (OGC 11-038r2) can be fully described by the HDF5 data model because its storage format is also HDF5. However, the HDF5 data model includes several entities whose features go significantly beyond those of the NetCDF Enhanced model.

Furthermore, OGC members are using HDF5 as a standard format for more complex data types. In particular, HDF5 has been proposed as at least two standards for point cloud data in the OGC Point Cloud Domain Working Group, and has been demonstrated as a GDAL compliant format for images (KEA). HDF5 is also used as an open standard for other geographic data, such as the Bathymetric Attributed Grid (BAG) format, which is the basis for the International Hydrographic Organization’s standards.

The HDF5 data format and library was created, and is maintained, by the HDF Group. The group’s mission is to ensure long-term access to data stored in HDF5 and support its dedicated and diverse user community. The organization actively partners with users to understand their needs and challenges and to help them use HDF5 effectively. As a long-time OGC member, The HDF Group actively contributes to numerous standards activities. The HDF Group chairs the OGC HDF Standards Working Group, where the conceptual model was developed.

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 Symbology Conceptual Core Model

Status: 
Please note:  This Request is scheduled to close on 21st November 2018.
Open Date: 
Mon, 10/22/2018
Closing Date: 
Wed, 11/21/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the early development of a Symbology Conceptual Core Model (SCCM).

The Symbology Conceptual Core Model (SCCM) is an abstract, modular, and extensible model, with no encoding dependency, used for the portrayal of geographical data. The SCCM aims to offer a consistent approach to specifying data portrayal and symbology rules that can be applied to geospatial datasets as well as online geospatial data and mapping services. Existing OGC standards for styling and symbology can only be used with a few OGC standards (e.g. Web Map Service), so a more general and portable symbology model is required for use across the broad OGC standards baseline.

The SCCM aims to:

  • provide the flexibility required to achieve adequate cartographic styling for a variety of information communities; e.g. aviation symbols, weather symbols, thematic maps, etc, and;
  • achieve a high level styling interoperability without encoding dependencies (one symbology model, many encodings).

 

Potential implementations of the SCCM 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 an extension mechanism, integration of these standards for the purposes of cartographic representation could be greatly simplified.

Downloads: 
    

        OGC Symbology Conceptual Model: Core part (18-067) (PDF)
        
    
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 comment on candidate standard: Geographic Information — Well Known Text Representation Of Coordinate Reference Systems

Status: 
Please note:  This Request is scheduled to close on 5 November 2018.
Open Date: 
Thu, 10/04/2018
Closing Date: 
Mon, 11/05/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the candidate standard jointly developed by the International Organization for Standardization (ISO) and the Open Geospatial Consortium: “Geographic Information - Well-Known Text representation of coordinate reference systems” (CRS WKT).

Well-Known Text (WKT) is used as a compact machine- and human-readable representation of geometric objects and coordinate reference information, as specified two decades ago in the OGC and ISO standard “Geographic information – Simple feature access – Part 1: Common architecture.” This standard included a capability for describing coordinate reference systems as text. The original CRS WKT was subsequently extended in numerous incompatible ways, and had thus become non-interoperable.

In 2015, OGC and ISO adopted a major revision of the CRS WKT specification that allowed a rigorous description of coordinate reference systems and coordinate operations in WKT, following the data model described in OGC Abstract Specification, Topic 2, which is also published as ISO 19111:2007 - Spatial referencing by coordinates. However, OGC AS Topic 2 and ISO 19111:2007 have recently been revised. The revision of CRS WKT tracks the changes made to the CRS data model.

The new edition of the CRS WKT standard aligns with the coordinate reference system model described in ISO 19111:2018. Specifically the changes from the 2015 edition are:

  • Extension to describe dynamic geodetic and dynamic vertical coordinate reference systems - coordinate reference systems in which coordinate values on the surface of the earth change with time due to tectonic deformation including a time reference (coordinate epoch) for coordinates referenced to a dynamic CRS;
  • Extension to describe geoid-based vertical coordinate reference systems;
  • Extension for the description of datum ensembles, groups of realizations of one terrestrial or vertical reference system that for low accuracy purposes may be merged ignoring coordinate transformation;
  • A rigorous description of temporal coordinate reference systems;
  • The removal (deprecation) of image coordinate reference systems; and
  • The remodelling of scope and extent information.

 

This latest edition of CRS WKT cancels and replaces the 2015 version (also published as ISO 19162:2015), which has been technically revised. The candidate CRS WKT standard was prepared by the OGC CRS Standards Working Group and Technical Committee ISO/TC 211 Geographic information/Geomatics.

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 draft charter for Artificial Intelligence in Geoinformatics Domain Working Group

Status: 
Please note:  This Request is scheduled to close on 25th September 2018.
Open Date: 
Tue, 09/04/2018
Closing Date: 
Tue, 09/25/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the draft Geospatial Artificial Intelligence (GeoAI) Domain Working Group (DWG) Charter.

Artificial Intelligence (AI) and Deep Learning (DL) technologies have started to be coupled with geoinformatics and are bringing geospatial intelligence to various domains, including autonomous transportation, predictable healthcare, sustainable urban planning/design/development, among others.

For example, AI-assisted volunteered geographic information (such as OpenStreetMap data) accelerates the development of Spatial Data Infrastructures (SDI) from satellite imagery. Also, deep learning techniques provide micro-level prediction of human mobility and environmental exposure across different geographic areas in epidemiology. Further, autonomous vehicles gather, manage, and analyze massive amounts of geospatial data from a combination of GPS, cameras, and other traffic sensors and navigate with high-level human-like perception by using Deep Learning. Clearly, many fields can benefit from combining Artificial Intelligence with geospatial data.

The GeoAI DWG has been chartered to identify use cases and applications related to AI in geospatial domains such as healthcare, smart home, and autonomous cars. The GeoAI DWG will provide an open forum for broad discussion and presentation of use cases with the purpose of bringing geoscientists, computer scientists, engineers, entrepreneurs, and decision makers from academia, industry, and government together to develop, share, and research the latest trends, successes, challenges, and opportunities in the field of AI with geospatial data. The GeoAI DWG will aim to investigate the feasibility and interoperability of OGC standards to use and re-use geospatial data in AI applications, as well as describe gaps and issues that could lead to new geospatial standardization within the GeoAI domain community.

 
Comment: 

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

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 MetOcean profile and extensions to WCS 2.1

Status: 
Please note:  This Request is scheduled to close on 20 September 2018.
Open Date: 
Tue, 08/21/2018
Closing Date: 
Thu, 09/20/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the MetOcean profile and extensions to WCS 2.1.

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 proposed Statistical Domain Working Group

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

 

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

The Statistical DWG is proposed to identify requirements and use cases of how geospatial and statistical standards can support the integration of geospatial information into statistical systems for the purposes of broad discovery, analysis, and use.

The statistical domain is evolving to move from the traditional capture of data through surveys such as census, to a more dynamic integration of data from across a wide range of domains that can make statistics more timely, more accurate, and better understood.

Geospatial information is a key data source in transforming the way that statistics are produced as it has the potential to fit into every component of the Generic Statistical Business Process Model.

The complexity of bringing together survey, administrative, and big data with geospatial information and earth observation is driving an increased need for standardisation to support better statistical outputs. A few of the specific challenges under consideration within the proposed DWG include:

  • Data integration – how can semantic web technology be used to improve the integration of geospatial and statistical datasets?
  • Data Capture – how can geospatial data be used to include the capture and georeferencing of survey, administrative and big datasets used in the production of statistics?
  • Data processing – as geospatial objects do not fit within traditional database structures these are currently handled externally to the rest of the statistical process through dedicated geospatial systems.
  • Data exchange – given the lack of interoperability between statistical and geospatial data architectures, frameworks, metadata and standards, how can data be shared through a service orientated approach?
  • Data analysis – a lack of comparability between geographic datasets at a national, regional, continental and global level makes international analysis difficult.
  • Knowledge – there is a lack of understanding within the statistical community of the geospatial tools and standards that can support the statistical system, and a corresponding situation with the geospatial community.

 

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 version of OpenSearch for Earth Observation Suite of Standards

Status: 
Please note:  This Request is scheduled to close on 3rd August 2018.
Open Date: 
Wed, 07/04/2018
Closing Date: 
Fri, 08/03/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the latest version of the OpenSearch for Earth Observation (OpenSearch-EO) Suite of Standards.

The OpenSearch specification allows syndication of search results that can then be aggregated by one large index. It provides a simple to use description of the search interface, which is called OpenSearch Description document (OSDD). A client (e.g., a browser) can use this description to check which response formats are supported and how a query/filter can be formulated.

This OGC suite of standards specifies an Earth Observation extension to OpenSearch (OpenSearch-EO) that defines query parameters to permit the filtering of search results with fields related to Earth Observation, as well as a search response model supporting different search response encodings. This revision updates the extension primarily to include additional examples for developers. Further, two new encodings of the OpenSearch-EO conceptual model have been developed as new standards: one for encoding metadata using GeoJSON or JSON-LD and one for encoding of responses to OpenSearch-EO queries in GeoJSON or JSON-LD. These standards further integrate with the OGC Standards Baseline in that the GeoJSON responses are provided as OWS Context documents.

OpenSearch-EO specifies a series of parameters that can be used to constrain search results. In short, provision is made to filter results by sensor information, acquisition, processing parameters and other information.

This specification is complementary to the OpenSearch Geo and Time Extensions (OGC 10-032 [RD.3]) and recommends its use for spatial and temporal queries especially for EO collection and EO product metadata. Further, it defines a default response encoding based on Atom 1.0/XML [RD.22].

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 3D Tiles Candidate Community Standard

Status: 
Please note:  This Request is scheduled to close on 1 August 2018.
Open Date: 
Mon, 07/02/2018
Closing Date: 
Wed, 08/01/2018 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the 3D Tiles Specification 1.0 candidate Community standard.

3D Tiles is a publicly available open specification for streaming massive heterogeneous 3D geospatial datasets for visualization. To expand beyond existing 2D and 2.5D streaming of map tiles and terrain, 3D Tiles support 3D models such as point clouds, 3D buildings (exterior and interior), trees, imagery, BIM/CAD models, and terrain. 3D Tiles is currently implemented in more than a dozen software products.

Bringing techniques from graphics research, the movie industry, and the game industry to 3D geospatial, 3D Tiles defines a spatial data structure and a set of tile formats designed for 3D, and optimized for streaming and rendering. The tile formats are:

  • Batched 3D Models – for 3D buildings, terrain, BIM/CAD models, etc.
  • Instanced 3D Models – for trees, bolts, valves, etc.
  • Point Clouds – for massive point clouds, including per-point attributes.
  • Composite – a tile of tiles to allow aggregation.

 

A Community standard is an official standard of the OGC that is developed and maintained external to the OGC. The originator of the standard brings to OGC a “snapshot” of their work that is then endorsed by OGC membership as a stable, widely implemented standard that becomes part of the OGC Standards Baseline. In 2016, OGC approved a work item on endorsing 3D Tiles as an OGC Community Standard, and now this effort is ready for consideration for approval by OGC members.

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