OGC Requests

OGC DGGS Standards Working Group seeks public comment on new tasks of work added to its charter

Status: 
Please note:  This Request is scheduled to close on 26 September 2019.
Open Date: 
Thu, 09/05/2019
Closing Date: 
Thu, 09/26/2019 - 23:59
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on new work tasks added to the charter of the Discrete Global Grid Systems (DGGS) Standards Working Group (SWG).

The original goal of the DGGS SWG was to deliver an implementation standard. However, the fundamental and cross-cutting nature of DGGS resulted in the OGC DGGS being published as an OGC Abstract Specification that defines a conceptual model. In recognition of the nature of the relationship between DGGS and other OGC standards, much of the originally forecast effort to draft specific DGGS encoding standards can instead be accommodated by a mixture of extensions, changes, or best practice guides to/for existing OGC Standards. The DGGS SWG is therefore working with relevant OGC Working Groups as necessary to embed linkages between DGGS and other standards in the OGC Standards baseline. The new tasks proposed for the DGGS SWG address these linkages.

The goal of DGGS is to enable rapid assembly of spatial data without the difficulties of working with projected coordinate reference systems. DGGSs represent the Earth as hierarchical sequences of equal area tessellations, each with global coverage and with progressively finer spatial resolution. Individual observations can be assigned to a cell corresponding to both the position and size of the phenomenon being observed - meaning that the resolution and precision of the data capture is inherently part of the stored data, and not something that needs to be explained in metadata - and potentially overlooked.

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

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: 

OGC seeks public comment on draft charter for new Environmental Data Retrieval API Standards Working Group

Status: 
Please note:  This Request is scheduled to close on 19th September 2019.
Open Date: 
Thu, 08/29/2019
Closing Date: 
Thu, 09/19/2019 - 23:59
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the draft charter for the new Environmental Data Retrieval API Standards Working Group (SWG).

The Environmental Data Retrieval API SWG will standardize some APIs, defined with OpenAPI Version 3, to retrieve various common data patterns from a data store.

Much environmental data is truly 'Big Data', in that it cannot be readily copied and distributed in sensible timescales for many uses. By specifying precisely just the data required in a convenient pattern familiar to the user, a service provider can extract and serve the requested data, simplifying access for the user, and hiding the service implementation details, while being scalable both in terms of the underlying data volumes and the number of supported simultaneous users.

Using stable, standardized, service APIs based on simple data retrieval patterns will improve the access and use of data and information across different domains, including geospatial, facilitating more innovation and value.

A goal of the SWG is that these standardized APIs will be consistent with the strategic direction established by OGC members for OGC API standards, such as OGC API - Features and the future OGC API - Common.

The service APIs will support both traditional and cloud-based approaches to computing and also enable a mix of public and private business models on a 'level playing field'. For example, no one country is capable of supplying weather forecast data at the highest useful resolutions for the whole globe, so a distributed scalable approach is essential, enabling both advanced countries and the Least Developed Countries to contribute to global strategic initiatives of sustainability and development.

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: 

OGC requests public comment on the recharter of the OGC Observations and Measurements (O&M) Standards Working Group

Status: 
Please note:  This Request is scheduled to close on 18 September 2019.
Open Date: 
Wed, 08/28/2019
Closing Date: 
Wed, 09/18/2019 - 23:59
Description: 

 

The Open Geospatial Consortium (OGC) requests public comment on the recharter of the OGC Observations and Measurements (O&M) Standards Working Group (SWG).

OGC members have proposed a revision of the SWG Charter to reflect the group’s modified scope of work: to update the existing O&M standards to conform to modern web architecture requirements and best practice, and create a new OGC standard for JSON encoding of O&M data.

The O&M standard was originally defined within the OGC Sensor Web Enablement Initiative in 2003-2007. Version 2.0 of the standard was co-published as the OGC Abstract Specification Topic 20 and ISO 19156:2011. The latest version of OGC Abstract Specification Topic 20 is from 2013. As such, the standard requires revising to accommodate technical issues discovered in various standard implementations and harmonization with recent W3C/OGC standardization work on sensor network terminology and concepts defined in the Semantic Sensor Network (SSN) and Sensor, Observation, Sample, and Actuator (SOSA) ontologies. The ISO 19156 revision will be carried out by the ISO/TC 211 in parallel, and in close co-operation with the O&M SWG revision work on the OGC O&M encoding Standards.

Standards-based exchange of observed, measured, or modeled data are key enablers for many critical online consumer and governmental services. Examples of these data sets include: weather, air quality, and other kinds of environmental observations and forecasts; traffic monitoring data; health monitoring; building and construction safety measurements; various remote sensing data; and industrial process monitoring. The Observations and Measurements family of Standards defines a conceptual level data model as well as encodings for these datasets.

The OGC Observations and Measurements - XML Implementation (OGC 10-025r1) Standard defines an XML encoding for the concepts defined in OGC Abstract Specification Topic 20 and will also be revised to accommodate the changes to the OGC Observations and Measurements Abstract Specification.

Notably, and in addition to the revision of the O&M XML Implementation Standard, there is an identified need to standardize an O&M data encoding for formats like JSON/GeoJSON. These formats are preferred in modern Web APIs, including those conforming to the OGC API - Features - Part 1: Core Draft Standard (OGC 17-069r2).

Both the Observations and Measurements conceptual data model and its standardized XML encoding are used extensively in Spatial Data Infrastructures such as in the EU INSPIRE. There is also on-going work to additionally provide INSPIRE O&M datasets in JSON/GeoJSON based formats, but no standard has yet been identified describing an interoperable way of doing this.

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: 

OGC seeks public comment on Geospatial Coverages Data Cube Community Practice Document

Status: 
Please note:  This Request is scheduled to close on 19 September 2019.
Open Date: 
Tue, 08/20/2019
Closing Date: 
Thu, 09/19/2019 - 23:59
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the Geospatial Coverages Data Cube Community Practice document.

Data Cubes for geospatial information provide the means to integrate observations and other types of geospatial data for use in multiple applications through simplified access and efficient analytics. Using the geospatial ‘Coverages’ (e.g. rasters and imagery) data structure, the Community Practice document defines requirements for a geospatial coverages data cube infrastructure and guidelines for enhancements and extensions to the basic core.

A Data Cube is a multi-dimensional ("n-D") array of values. Even though it is called a “cube,” it can be 1-dimensional, 2-dimensional, 3-dimensional, or higher-dimensional. The dimensions may be coordinates or enumerations, e.g. categories. A Geospatial Coverage Data Cube is a Data Cube established on the basis of the Geospatial Coverage standard with a grid system for data with one or more coordinate dimensions for space and time.

The document captures effective practices for Geospatial Data Cubes based on several communities that have implemented and are running operational geospatial data cubes. The objective of the document is to promote coordination and common terminology that could lead to federated Geospatial Data Cubes Services.

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) 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 new Geopose Standards Working Group

Status: 
Please note:  This Request is scheduled to close on 5 September 2019.
Open Date: 
Thu, 08/15/2019
Closing Date: 
Thu, 09/05/2019 - 23:59
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the draft charter for the new Geopose Standards Working Group (SWG).

The main purpose of this SWG will be to develop and propose a standard for geographically-anchored poses (geopose) with 6 degrees of freedom referenced to one or more standardized Coordinate Reference Systems.

The combination of position (up/down [z], left/right [x] and forward/backward [y]) and orientation (pitch, roll, and yaw) with 6 degrees of freedom for objects in computer graphics and robotics is usually referred to as the object’s “pose.” Pose can be expressed as being in relation to other objects and/or to the user. When a pose is defined relative to a geographical frame of reference or coordinate system, it will be called a geographically anchored pose, or ‘geopose’ for short.

An object with a geopose may be any real physical object. This includes objects such as AR display devices (proxy for a user’s eyes), vehicles, robots, or even a park bench. It may also be a digital object like a BIM model, a computer game asset, the origin and orientation of the local coordinate system of an AR device, or a point-cloud dataset.

All physical world objects inherently have a geographically-anchored pose. Unfortunately, there is not a standard for universally expressing the pose in a manner that can be interpreted and used across the range of modern computing platforms.

The ability to specify the geopose of any object will aid in interoperability between real world 3D spatial computing systems, such as those under development for autonomous vehicles, augmented reality (AR), 3D map visualization, or any digital representation of the physical world or part therein (digital twins).

Members of the Geopose SWG will work towards defining an interoperable way to express, record, transform, and share the geopose of objects in a consistent manner across different applications, users, devices, services, and platforms.

One example of the benefit of standardized geoposes concerns traffic awareness and management: describing the pose of moving cars and people in a universally consistent manner could lower the incidence of accidents and road deaths. The same real-time geopose of a vehicle or pedestrian could be shared and displayed in different systems including:

  • a traffic visualization on a screen in another car,
  • shown directly at its physical location in the AR glasses of a pedestrian that is around the corner for the car, or
  • in the real-time world model used by an autonomous vehicle or delivery robot to help it navigate the world and avoid other vehicles or pedestrians.

​​​​​​

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: 

Charter requests are not currently able to be subscribed to.

OGC Requests: 

OGC requests public comment on draft charter for new ‘OGC API - Catalogues’ Standards Working Group

Status: 
Please note:  This Request is scheduled to close on 4 September 2019
Open Date: 
Wed, 08/14/2019
Closing Date: 
Wed, 09/04/2019 - 23:59
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on the draft Charter for a proposed ‘OGC API - Catalogues’ Standards Working Group (SWG).

The purpose of this Standards Working Group is to develop a new version of the OGC Catalogue Service standard for the World Wide Web.

The current versions of the catalogue standards (i.e. CAT 2.0, CAT 3.0) — developed in the early 2000s — are implemented in an operation-oriented XML/RPC manner that has contributed significantly to building distributed catalog systems but this legacy no longer fits with current web search and discovery practices.

The next version ("OGC API - Catalogues") will remedy this shortcoming and bring OGC catalogue standards into closer alignment with both modern Web usage and the practices laid out in the Spatial Data on the Web Best Practices document jointly developed by OGC and W3C.

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: 

Charter requests are not currently able to be subscribed to.

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: 

Pages