OGC Requests

Public comment requested: OGC Abstract Spec Topic 21 - Discrete Global Grid Systems

Status: 
Please note:  This Request is scheduled to close on 4 September 2020
Open Date: 
Wed, 08/05/2020
Closing Date: 
Fri, 09/04/2020
Description: 

The Open Geospatial Consortium (OGC) membership has proposed updates to the OGC Abstract Spec Topic 21 - Discrete Global Grid Systems (DGGS) document and is seeking public comment before approval. This version was jointly developed with ISO TC211 and has the same normative content as ISO/DIS 19170-1:2020.

The goal of a DGGS is to enable rapid assembly of spatio-temporal data without the difficulties of working with projected coordinate reference systems and complex geometries. DGGSs represent the Earth (or other planetary bodies) as hierarchical sequences of tessellations, each with global coverage and with progressively finer resolution. Each cell (or zone) in the tessellations has a unique identifier, so that individual observations can be assigned an identifier corresponding to both the position and size of the phenomenon being observed. This means that the resolution and precision of the data capture is inherently part of the stored data; not something that needs to be explained in metadata and therefore potentially overlooked.

Further, DGGS come with a standard set of topological queries that enable rapid data analysis of very large numbers of zones and, by their very nature, are well suited to parallel processing applications at multiple spatial resolutions - a boon for big data processing.

The changes in this revised edition compared to the previous OGC edition include:

  • Separation of the DGGS standard into common modules and an extension for Equal Area Earth DGGS;
  • Remodelling to incorporate new versions of ISO 19107, ISO 19111 & ISO 19112, and tighter integration with ISO 19115-1
  • Extending the common module to support up to three spatial dimensions and up to one temporal dimension;
  • Additional modelling of temporal geometry and temporal reference systems sufficient for spatio-temporal DGGS, introducing the concept of a zone as a region of space-time equivalent to a location or an era; 
  • Remodelling algebraic functions as spatio-temporal extension of ISO 19107 Query;
  • Explicit handling of Dynamic vs Static datums for Equal Area Earth DGGS.
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: 

Public comment requested: DGIWG 112 Defence Profile of OGC’s Web Map Service 1.3 - Revision

Status: 
Please note:  This Request is scheduled to close on 3 September 2020
Open Date: 
Tue, 08/04/2020
Closing Date: 
Thu, 09/03/2020
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on updates to two Best Practice documents concerning Defence Profiles: DGIWG 122 Defence Profile of OGC’s Web Feature Service 2.0; and DGIWG 112 Defence Profile of OGC’s Web Map Service 1.3 - Revision.

This request is for DGIWG 112 Defence Profile of OGC’s Web Map Service 1.3 - Revision
For DGIWG 122 Defence Profile of OGC’s Web Feature Service 2.0 please see: https://www.ogc.org/standards/requests/211

OGC Web Feature Service (WFS) and Web Map Service (WMS) are two of OGC’s most popular standards and are broadly used in the defence community. OGC WFS provides location-based/geospatial data over the web for visualization or analysis, while OGC WMS provides pre-rendered maps over the web.

The Defence profiles for the standards were created by the Defence Geospatial Information Working Group (DGIWG) in order to address specific requirements, recommendations and guidelines for implementations of the OGC Web Map Service and OGC Web Feature Service standards. Together with the DGIWG profiles for Catalogue Service for the web (CSW), Web Map Tile Service (WMTS) and Web Coverage Service (WCS) they built the basis for NATO STANAG 6523 - Defence Geospatial Web Service Edition 1(2020).

The revisions to the documents:

  • address comments and change requests from OGC testbeds and partners
  • clarify and simplify requirements
  • add informative information to support implementation
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: 

Public comment requested: DGIWG 122 Defence Profile of OGC’s Web Feature Service 2.0

Status: 
Please note:  This Request is scheduled to close on 3 September 2020
Open Date: 
Tue, 08/04/2020
Closing Date: 
Thu, 09/03/2020
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on updates to two Best Practice documents concerning Defence Profiles: DGIWG 122 Defence Profile of OGC’s Web Feature Service 2.0; and DGIWG 112 Defence Profile of OGC’s Web Map Service 1.3 - Revision.

This request is for DGIWG 122 Defence Profile of OGC’s Web Feature Service 2.0.
For DGIWG 112 Defence Profile of OGC’s Web Map Service 1.3 - Revision please see: https://www.ogc.org/standards/requests/212

OGC Web Feature Service (WFS) and Web Map Service (WMS) are two of OGC’s most popular standards and are broadly used in the defence community. OGC WFS provides location-based/geospatial data over the web for visualization or analysis, while OGC WMS provides pre-rendered maps over the web.

The Defence profiles for the standards were created by the Defence Geospatial Information Working Group (DGIWG) in order to address specific requirements, recommendations and guidelines for implementations of the OGC Web Map Service and OGC Web Feature Service standards. Together with the DGIWG profiles for Catalogue Service for the web (CSW), Web Map Tile Service (WMTS) and Web Coverage Service (WCS) they built the basis for NATO STANAG 6523 - Defence Geospatial Web Service Edition 1(2020).

The revisions to the documents:

  • address comments and change requests from OGC testbeds and partners
  • clarify and simplify requirements
  • add informative information to support implementation
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: 

Public comment requested: GeoSPARQL Standards Working Group re-charter

Status: 
Please note:  This Request is scheduled to close on 6th August 2020.
Open Date: 
Thu, 07/16/2020
Closing Date: 
Thu, 08/06/2020
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the draft updated charter for the OGC GeoSPARQL Standards Working Group (SWG). The GeoSPARQL SWG will revise, and likely extend, the GeoSPARQL standard. Comments are due by August 6, 2020.

GeoSPARQL is a standard for the representation and querying of geospatial linked data for the Semantic Web.

Since the release of GeoSPARQL in 2012, there has been growth of both the Semantic Web and spatial information represented in Semantic Web form, with GeoSPARQL being widely used for spatial Semantic Web data.

As with many standards that see widespread use, suggestions for enhancements and extensions are made by users as they extend beyond the requirements used to define the original standard. Additionally, subsequent technological developments or knowledge gained in the use of the standard leads to new requirements.

The overall mission of the GeoSPARQL SWG is to ensure that the features of GeoSPARQL remain up-to-date with the Semantic Web community whose needs now outstrip the current content of GeoSPARQL.

This revision will likely result in a major update of GeoSPARQL that will form a new base Semantic Web standard for people working with spatial data. The update will include consideration of backwards-compatibility with GeoSPARQL 1.0 as a key requirement.

More information on the need to update GeoSPARQL is contained in the draft charter.

Comment: 

Please submit your comments using the following link: charter-requests [at] opengeospatial.org (Click here to submit comments) Please refer to the following template for the contents of your message: Comments Template.

Subscribe: 

Charter requests are not currently able to be subscribed to.

OGC Requests: 

Public comment requested: Routing Standards Working Group Draft Charter

Status: 
Please note:  This Request is scheduled to close on 2 July 2020.
Open Date: 
Thu, 06/11/2020
Closing Date: 
Thu, 07/02/2020
Description: 

Using geospatial information to plan routes for travel and logistics is among the most common uses of geospatial and location-based technologies, with countless routes being generated daily by smartphone users, logistics companies, and others. In support of this, road network data, routing & navigation algorithms, and route calculation services are now available from many different providers and sources. While this diversity in the marketplace is generally beneficial to consumers of route information, it makes accessing, integrating, overlaying, or comparing routes from different routing services overly complex.

The OGC API - Routes will enable a simple method for an application to query any number of routing and/or data providers, even across multiple modes of transport, and present the resulting routes to the user in a single place. The capability for a client to request and retrieve routes from a routing API provider and share routes between applications will improve interoperability for many users, communities, and enterprises.

  • For providers of routes, the API and route exchange model will provide a simple model to publish and offer those routes as resources for use by other systems.
  • For developers building infrastructures, the API will provide common methods to describe and leverage existing routing engines and algorithms using modern APIs - saving the time and costs associated with developing and deploying custom interfaces.
  • For users, applications, and enterprises, the capability to get routes via a common API, regardless of the underlying routing data, engines, or algorithms will provide a significant step forward in geospatial interoperability and modularity.

The proposed OGC API - Routes will provide the methods and apparatus for the execution of basic commands to retrieve, update, share, and delete routes, and will interface with other geospatial resources that use OGC APIs. The proposed route exchange model will provide a method to share routes, regardless of the underlying proprietary data, routing engine software, or algorithms.

Draft specifications for a routing API and route exchange model were successfully demonstrated in the OGC Open Routing API Pilot, the OGC Smart City Interoperability Reference Architecture (SCIRA) Pilot, and other efforts. Coordination with W3C on OGC API - Routes has begun with discussions in the joint W3C/OGC Spatial Data on the Web Interest Group.

Comment: 

Please submit your comments using the following link: charter-requests [at] opengeospatial.org (Click here to submit comments) Please refer to the following template for the contents of your message: Comments Template.

Subscribe: 

Charter requests are not currently able to be subscribed to.

OGC Requests: 

Public Comment Requested: Standard SensorThings API Part 1 - Sensing V1.1

Status: 
Please note:  This Request is scheduled to close on 6 July 2020.
Open Date: 
Thu, 06/04/2020
Closing Date: 
Mon, 07/06/2020
Description: 

 

The OGC SensorThings API provides an open, geospatially enabled, unified way to interconnect Internet of Things (IoT) devices, data, and applications over the web. SensorThings is currently being used by organizations around the world in support of logistics, public safety, energy utilities, environmental monitoring, and more.

At a high level, the OGC SensorThings API provides two main functionalities, with each function handled by a specific part of the standard: Sensing and Tasking. 

Under public comment is a new version (v1.1) of the Sensing part, which provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The separate Tasking part provides a standard way for parameterizing - also called tasking - of taskable IoT devices, such as sensors or actuators.

Version 1.1 of the SensorThings API is mostly backwards compatible with v1.0. The main changes in v1.1 include:

  • An additional field for storing additional metadata that is useful for filtering. 
  • Additions to the service root page that allow users to easily see exactly which extensions and optional features a server implements. Additionally, the MQTT extension can now list the MQTT endpoints on the root page so that a user can discover those endpoints.
  • A fix for inconsistencies and incompatibilities surrounding the transmission of the specification version number in MQTT topics.

The first two changes should not impact clients implemented based on version 1.0. The third change, however, may cause some minor issues for some clients that are not using the version prefix in MQTT topics.

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.3 of GeoPackage Standard

Status: 
Please note:  This Request is scheduled to close on 4 June 2020.
Open Date: 
Tue, 05/05/2020
Closing Date: 
Thu, 06/04/2020
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the latest version of the GeoPackage Standard, v1.3.0. GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. Comments are due by June 4, 2020.

GeoPackage version 1.3.0 is a minor revision to the current version 1.2.1. All of the changes were carefully considered for impact on existing implementations. Any changes considered to have a significant impact on reverse compatibility were rejected or recast in order to limit their impact.

In addition to a number of administrative changes to improve readability, clarity, and correctness, the following substantive changes were incorporated into the draft GeoPackage 1.3 release:

  • Enforce alignment of Spatial Reference System (SRS) Identifiers between tables.
  • Clarify use of views in user-defined tables.
  • Relax Requirement 104 to allow use of schemas with attributes and extensions.
  • Allow metadata scopes to be extended.
  • Create new Requirement 152 to describe empty geometries.

 

Comment: 

Comments can be submitted 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. There are three ways to provide input into the candidate standard:

  1. Edit the document on GitHub: if you are familiar with GitHub, please make your proposed changes directly. Instructions are in the README.md file in that repository.
  2. Submit an "issue" on GitHub: GitHub offers a simple interface for posting an issue/comment. Just click the green "New Issue" button.
  3. Submit your comments requests [at] lists.opengeospatial.org (via email. )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: 

Public comment requested: CDB Version 1.2

Status: 
Please note:  This Request is scheduled to close on 21 May 2020.
Open Date: 
Tue, 04/21/2020
Closing Date: 
Thu, 05/21/2020
Description: 

The CDB Standard defines a conceptual model, and rules for implementing that model, for the storage, access, and modification of a synthetic environment data store as required in high-fidelity simulation or mission rehearsal, such as 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 be made accessible via OGC web services, such as a Web Map Service (WMS) or Web Feature Service (WFS), to permit visualization and analysis of the content outside of the traditional simulator hardware environment.

CDB Version 1.2 includes numerous minor edits for clarity as well as three substantive changes:

  1. The definition of the Primary Alternate Terrain Elevation dataset has been changed to improve compatibility with standard open source libraries used to read and process elevation data. These changes address an issue that ground simulation has with CDB gridded terrain meshes.
  2. Additional metadata is now provided so that additional file formats or encodings, such as GeoPackage, can easily be incorporated and used. This enhancement also enables applications to much more easily determine which file formats are being used for a specific layer.
  3. Two new volumes are added to the CDB Standard suite that describe how to use the OGC GeoPackage Standard for vector data in a CDB data store.
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: 

Public comment requested: draft charter for proposed MUDDI SWG

Status: 
Please note:  This Request is scheduled to close on 5th May 2020
Open Date: 
Tue, 04/14/2020
Closing Date: 
Tue, 05/05/2020
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the draft charter for the new OGC MUDDI (Model for Underground Data Definition and Integration) Standards Working Group (SWG). Comments are due by the 5th May, 2020.

The vast majority of street excavations occurring around the world are adversely impacted by a lack of usable information about buried infrastructure. Large-scale construction projects are frequently stalled, incurring delay claims and change orders that significantly increase costs. This situation occurs because the locations of existing utility installations were never properly recorded or depicted. Worse than this, the lack of knowledge about underground built environment dependencies and vulnerabilities often stands in the way of effective disaster response and recovery, costing not just money, but lives.

These costs and risks could all be mitigated if accurate, comprehensive underground built environment information were available and shared between responsible parties for rapid integration and analysis. An essential first step towards achieving this capability involves developing geo-enabled utility data models with inbuilt capabilities for enabling data interoperability and integration. The development and adoption of such models would deliver significant benefits by improving data interchange, integration, and application readiness. 

As such, the MUDDI SWG aims to create models and standards that fully represent underground infrastructure assets. Additionally, the MUDDI SWG will create mappings to/from other geospatial data models that characterize the underground environment that contains said assets.

The models to be designed by the MUDDI SWG participants will focus on those attributes most important for specific use cases - such as safe digging, construction design, and disaster resilience. The models have the capacity for extension to accommodate more complex use cases as the business value of data sharing and interoperability is established.

An additional value of developing standardized data models for selected underground utility components and environmental characteristics will be the opportunity to connect with models such as CityGML or BIM/IFC that principally address above-ground features, or GeoSciML/WaterML that cover a broad range of geologic and hydrologic phenomena. 

Ultimately, the work of the MUDDI SWG will contribute to the maximum reuse of data between different domains and computing environments. It will achieve this by enabling the use of standardized, interoperable data to model the entire interconnected built and natural municipal environment, from top to bottom, and at every scale - from small local jurisdictions to regional and national extents.

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) Please refer to the following template for the contents of your message: Comments Template.

Subscribe: 

Charter requests are not currently able to be subscribed to.

OGC Requests: 

OGC API - Features - Part 2: Coordinate Reference Systems by Reference

Status: 
Please note:  This Request is scheduled to close on 28 April 2020.
Open Date: 
Fri, 02/28/2020
Closing Date: 
Tue, 04/28/2020
Description: 

The Open Geospatial Consortium (OGC) seeks public comment on the OGC API - Features - Part 2: Coordinate Reference Systems candidate standard.

OGC APIs usher in a new age for location information on the web, enabling a much simpler way to share and access location information that is consistent with the architecture of the Web. The OGC API family of standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.

OGC API - Features provides the fundamental API building blocks to create, modify, and query ‘features’ on the Web (features are simply the digital representations of objects of interest in the real world). OGC API - Features is comprised of multiple parts, with each part being a separate standard. OGC API - Features - Part 2 extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference systems (CRS) other than WGS 84.

A key advantage to the OGC API - Features standard is the direct, fine-grained access to the data at the feature (object) level, providing greater flexibility for linking of resources on the Web. This OGC standard is consistent with the OGC/W3C Spatial Data on the Web Best Practices.

Specifically, the OGC API - Features - Part 2 standard specifies:

  • How, for each offered feature collection, a server advertises the list of supported CRS identifiers;
  • How the coordinates of geometry valued feature properties can be accessed in one of the supported CRS;
  • How features can be accessed from the server using a bounding box specified in one of the supported CRS; and
  • How a server can declare the CRS used to present feature resources, and optionally the coordinate axis order used.

 

Comment: 

Comments should be submitted via the OGC API - Features Issues Tracker on GitHub for this standard. Issues may be submitted for consideration through 28 April, 2020. All Issues will be assessed by the editing team.

Subscribe: 

To view comments as they are submitted, follow the  OGC API - Features Issues Tracker on GitHub.

OGC Requests: 

Pages