OGC Requests

Status: 
Please note:  This Request is scheduled to close on 23 August 2014.
Description: 

The OGC seeks public comment on a candidate OGC® Moving Feature Encoding Standard. Part I of this candidate standard provides a standard way of encoding moving feature data in an XML encoding in the form of an OGC Geography Markup Language (GML) application schema. Part II provides a standard way of encoding moving feature data in a simple CSV (comma-separated value) format.

The candidate OGC® Moving Feature Encoding Standard is available below. Comments are due by 23 August 2014.

The advance of mobile computing and internet-connected sensors (including sensors and GPS transponders in cell phones and notebook computers) brings with it a rapid rise in applications for moving feature data, typically representing vehicles or pedestrians. Many innovative moving feature applications will require the overlay and integration of moving feature data from different sources. Examples can easily be imagined for disaster risk management, traffic information services, security services, navigation for robots, aviation or maritime traffic monitoring, and wildlife tracking and conservation. Most current applications, however, are limited to single-source moving feature data.

More efficient moving feature data exchange will result in a requirement for massive data handling. The CSV style encoding provides an efficient and easily understood standard for encoding lightweight data records, which will be important for many applications involving large data volumes and real-time response. The GML application schema style encoding for Moving Features provides for the encoding of more complex spatial information.

This standard addresses only “rigid” moving features, such as vehicles, as opposed to those that deform, such as flood water, and it does not address moving features whose descriptions contain other moving features that must be updated as the feature moves, such as control surfaces on an unmanned aerial vehicle (UAV). It also is for archived Moving Feature data only, and not for live feeds from sensors.

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 [dot] opengeospatial [dot] 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.

Status: 
Please note: This Request is scheduled to close on 17 July 2014.
Description: 

The Open Geospatial Consortium (OGC®) membership seeks public comment on the Unified Geo-Data Reference Model for Law Enforcement and Public Safety (LEAPS) Services, with the intent to establish this model as a new OGC Best Practice. The the Unified Geo-Data Reference Model for Law Enforcement and Public Safety (LEAPS) Services can be downloaded below. Comments are due by 17 July 2014.

Open standards are essential if diverse systems are to provide law enforcement, civil security and public safety stakeholders with current and accurate role-based location information. The Unified Geo-Data Reference Model for Law Enforcement and Public Safety (LEAPS) Services specifies a framework that can be used to support interoperability at the data and services level. 

The Unified Geo-Data Reference Model for Law Enforcement and Public Safety (LEAPS) Services document is the result of work undertaken since 2010 within the UAE Ministry of Interior's Abu Dhabi Police General Headquarters GIS Center for Security (GIS CS).

The GIS CS is an active member of the OGC Law Enforcement and Public Safety Domain Working Group (LEAPS DWG), which provides a unifying forum in which local, national, regional and international law enforcement, civil security and public safety forces can work collaboratively on issues related to law enforcement, civil security and public safety.

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 [dot] opengeospatial [dot] 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.

Status: 
Please note: This Request closed on 13 December 2013. 
Description: 

The Open Geospatial Consortium (OGC®) is seeking comments on the candidate standard, "OGC® OpenSearch Geo and Time Extensions". This document extends the implementation of the popular OpenSearch technologies so that users can take advantage of the geospatial search capabilities enabled by OGC standards. 

Different types of content require different types of search engines. OpenSearch (http://www.opensearch.org) provides a standard way of describing search engine capabilities so that they can be leveraged by search client applications like modern Web browsers. The OGC® OpenSearch Geo and Time Extensions candidate standard provides a very simple way to configure OpenSearch for spatial and temporal queries over distributed repositories of contents having geographic and time properties, and for syndication of these search results in one large index.

Digital resources are becoming more complex and diverse, and this is especially true with respect to sensor data and Web connected sensors. Such data is increasingly becoming discoverable and usable through open interfaces that implement OGC standards (http://www.opengeospatial.org/standards), but most of this data remains undiscoverable via popular search engines. The OGC OpenSearch Geo and Time Extensions candidate standard specifies how to enhance search engines and configure them to access sensor data servers, so that users can query resource URLs through search combinations of time extents, geographic areas or location names, and likely keywords. 

The OGC® OpenSearch Geo and Time Extensions draft standard includes work undertaken within the GENESI-DR (Ground European Network for Earth Science Interoperations - Digital Repositories) project funded by the 7th Framework program of the European (EC Grant Agreement no. 212073) and the follow-up project GENESI-DEC (Ground European Network for Earth Science Interoperations - Digital Earth Community) funded by the same program (Contract nº RI-261623). The document was further supported by the ESA HMA (Heterogeneous Missions Accessibility) initiative and related projects.

The following organizations submitted this document to the Open Geospatial Consortium:

  •    Terradue Srl
  •    FGDC
  •    FortiusOne, Inc.
  •    EDINA
  •    Cubewerx Inc.

Download the candidate OGC OpenSearch Geo and Time Extensions Standard below.  Comments are due by 13 December 2013.

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 [dot] opengeospatial [dot] 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.

Syndicate content