OGC Requests

Public comment requested: IndoorGML v1.1

Status: 
Please note:  This Request is scheduled to close on 29th November 2019.
Open Date: 
Wed, 10/30/2019
Closing Date: 
Fri, 11/29/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) is seeking public comment on the v1.1 update to the IndoorGML standard.

The goal of IndoorGML is to represent and allow for exchange of the location information required to build and operate indoor spatial services such as indoor navigation systems. Several standards, such as CityGML, KML, and IFC, have been published to describe 3D geometry and semantics of buildings for outdoor/indoor spaces, but they lack some important features that are specific to indoor spaces. IndoorGML aims to provide complementary and additional encoding features for indoor space. In this respect, IndoorGML is a complementary standard to CityGML, KML, and IFC.

IndoorGML v1.1 introduces a new feature for level (i.e. storey or floor) information as an additional attribute of cell space to respond to the requirements from many indoor spatial applications. IndoorGML v1.1 is fully compatible with the previous version IndoorGML v1.0.

The OGC IndoorGML Encoding Standard was developed to provide a common schema framework for interoperability between indoor spatial applications. These cover a broad spectrum of application areas such as indoor location services, indoor web map services, indoor emergency control, indoor IoT sensors, guiding services for visually handicapped persons in indoor space, and indoor robotics. Cross-platform, vendor-neutral communication of indoor spatial information is essential to meet the market demands of these applications.

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: OpenFlight Scene Description Specification as an OGC Community Standard

Status: 
Please note:  This Request is scheduled to close on 28th November 2019.
Open Date: 
Tue, 10/29/2019
Closing Date: 
Thu, 11/28/2019 (All day)
Description: 

The Open Geospatial Consortium (OGC) is considering the OpenFlight Scene Description Database Specification (v16.0) for adoption as an official OGC Community Standard. Public comment is sought before approval.

The OpenFlight Scene Description Database Specification, commonly referred to as simply “OpenFlight,” is a 3D scene description file format used for real-time visual simulation of 3D terrain features and moving models, such as ground and air vehicles.

OpenFlight was submitted to OGC for consideration as a community standard by its creator and maintainer, Presagis. While OpenFlight databases are often created and edited using Presagis software tools, the format is widely adopted and, as a result, many tools exist in the marketplace that are able to seamlessly read and write OpenFlight files.

The OpenFlight file format supports both simple and relatively sophisticated real-time software applications. The full implementation of OpenFlight supports variable levels of detail, degrees of freedom, sound, instancing (both within a file and to external files), replication, animation sequences, bounding volumes for real-time culling, scene lighting features, light points and light point strings, transparency, texture mapping, material properties, and many other features.

An OGC Community Standard is an official standard of OGC that is considered to be a widely used, mature specification, but was developed outside of OGC’s standards development and approval process. The originator of the standard brings to OGC a “snapshot” of their work that is then endorsed by OGC membership so that it can become part of the OGC Standards Baseline.

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: OGC JSON Encoding Extension to Moving Features Standard

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

The Open Geospatial Consortium (OGC) is seeking public comment on the new OGC Moving Features Encoding Extension - JSON candidate standard. Comments are due 21 November, 2019.

This candidate standard defines how to encode and share the various movements of geographic features by using JavaScript Object Notation (JSON). Such a ‘moving feature’ is one whose location changes over time. For example, a car, a pedestrian, an airplane, a ship, etc.

OGC Moving Features Encoding Extension - JSON provides an IETF GeoJSON encoding for OGC Moving Features as an alternative to XML Core or Simple CSV. A moving feature contains a temporal geometry, whose location continuously changes over time, as well as dynamic non-spatial attributes whose values vary with time. The JSON Encoding Extension supports, 0- (point trajectories), 1- (lines), 2- (polygons), and 3-dimensional (polyhedrons) objects with locations and/or properties that vary over time.
The ability to attribute time-varying properties to an object (rather than just varying its location or trajectory), has utility and value in many current application areas, including: Location Based Services, Intelligent Transportation Systems, Disaster Risk Management Systems, and Smart City Applications. For example, the traffic congestion on roads and ‘hotspots’ of air pollution are typical moving features seen in the real world.

The representation of the following phenomena in a spatiotemporal domain is within the scope of this Encoding Standard:

  • Discrete phenomena, which exist only on a set of instants, such as road accidents;
  • Step phenomena, where the changes of locations are abrupt at an instant, such as administrative boundaries;
  • Continuous phenomena, whose locations move continuously for a period in time, such as vehicles, typhoons, or floods.
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 3D streaming Community Standard, I3S, receives update: public comment sought before approval

Status: 
Please note:  This Request is scheduled to close on 7th November 2019
Open Date: 
Tue, 10/08/2019
Closing Date: 
Thu, 11/07/2019 (All day)
Description: 

 

The Open Geospatial Consortium (OGC) seeks public comment on v1.1 of the candidate OGC Community Standard Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification. I3S v1.0 was approved as an OGC Community standard in 2017 Since then new features have been developed and implemented by the I3S community. The candidate Community Standard was submitted by Esri.

I3S is used to stream large three-dimensional (3D) datasets and is designed for performance and scalability. I3S supports 3D geospatial content as well as the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. I3S is designed to be cloud, web, and mobile friendly, and is based on modern web standards.

A single I3S dataset, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.

The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in the OGC Community Standard now available for public review and comment.

The changes included in v1.1 of the OGC I3S Community Standard include:

  • Addition of the Point Cloud Scene Layer (PCSL) type. A PCSL is designed to quickly display large volumes of symbolized and filtered point cloud data. A PCSL is scalable similar to Mesh-Pyramids and Point profiles that are currently supported in I3S V1.0. A PCSL relies on principles of bounding volume driven tree hierarchy, to organize a multi-LOD (Level of Detail) representation of the point cloud data structure. This in turn, allows for a quick discovery and selection of the appropriate LOD by a client application, whether its consumed on a mobile, web, or desktop platform.
  • For existing layer types, the addition of: Oriented Bounding Boxes; Attribute Domain Rules; Service Update Timestamp, and; Index hash table for improved performance.
  • Numerous editorial updates/corrections to improve readability.

 

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 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: 

Pages