OGC Requests

GML 3.1.1 common CRSs profile: Request for Public Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called GML 3.1.1 common CRSs profile. OGC invites public comment on a candidate profile specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification Profile. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for GML CRS support profile. Documentation of this draft specification can be downloaded here:

Candidate Submission: Tue, 2005-10-11 17:00
Close request period: Fri, 2005-11-11 17:00
TC and PC vote to issue request: Thu, 2005-12-08 17:00
Begin request period: Sat, 2006-01-07 17:00
 

Downloads: 


This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of commonly-used Coordinate Reference Systems (CRSs) plus related coordinate Conversions.

This profile can be used without a GML Application Schema, and such use is assumed in this document. However, a GML Application Schema that uses this profile could be specified. For example, an Application Schema could specify a specialized "TransverseMercatorConversion", as discussed in Annex F. Or an Application Schema could allow or require more information to be encoded for an OperationParameter (such as specified in Subclause 14.3.2 and wctsOperationParameter.xsd of OGC Discussion Paper [OGC 05-013]).

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] 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 Comments on Modular, GML-based Web Coverage Service 2.0

Status: 
Please note: This Request is scheduled to close on 14 April 2010.
Description: 

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the draft OGC Web Coverage Services (WCS) Interface Standard Version 2.0.  The OGC WCS standard supports electronic retrieval of geospatial data as "coverages" - that is, digital geospatial information representing space/time-varying phenomena such as satellite imagery or digital elevation models. The WCS 2.0 draft has several significant enhancements over previous versions. WCS 2.0 is harmonized with the Geography Markup Language coverage model, leading to increased interoperability across OGC standards. Further, WCS 2.0 is highly modular and follows the core/extension design pattern, which allows for standard that is easier to understand and implement.

The WCS standard defines a standard interface and operations that enable interoperable access to single or multi-dimensional geospatial coverages.  Services implementing this standard provide an interface with a standard set of operations for accessing original or derived sets of geospatial coverage information. An important aspect of the WCS standard is that it allows access and retrieval of raw, unprocessed imagery, which is often required by rendering and processing services. Further information about WCS can be found at the WCS Service page ( http://www.ogcnetwork.net/wcs ) of the OGC Network.

The proposed OGC WCS 2.0 standard and information on submitting comments on this document are available below. The public comment period closes on 14 April 2010.

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

The OGC Seeks Comments on Candidate GeoPackage Standard

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Closing Date: 
Thu, 02/07/2013 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks public comments on the current draft of the candidate OGC GeoPackage (GPKG) Standard. The GPKG Standards Working Group will consider all comments when preparing a final draft of the candidate standard.

Mobile device users who require geospatial application services and associated data and who operate in disconnected or limited network connectivity environments frequently do not have open, available geospatial data to support their applications. Applications include such things as mobile workforce data capture and updates, volunteered geographic information, and real time annotations of map data in an emergency event.

The candidate OGC GeoPackage (GPKG) Standard provides an open, non-proprietary, platform-independent container for distribution and direct use of all kinds of geospatial data. The GeoPackage container and related API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world.  Standard APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services.  

Future enhancements to the GeoPackage standard, a future GeoPackage Web Service standard, and modifications to existing OGC Web Service (OWS) standards to use GeoPackages as exchange formats will allow OWS to support provisioning of GeoPackages throughout an enterprise or information community.

Interoperability of GeoPackage implementations by several participants is being tested and will be demonstrated in the 15 January 2013 OGC Web Services Testbed (OWS-9) Demonstration. The current reference implementation bases, SQLite and SpatiaLite, are open source resources developed by OGC members. The SQLite reference implementation is sponsored in part by the SQLite Consortium, which includes a number of OGC members. SpatiaLite is built on OS-Geo open source libraries by the president of GFOSS.it and others.

The current draft of the candidate OGC GeoPackage (GPKG) Standard can be downloaded below:

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 Calls for Comment on revision to OGC Web Services Common Standard

Status: 
Please note: This Request is scheduled to closed on 20 May 2009.
Description: 
The members of the Open Geospatial Consortium, Inc. (OGC®) request comments to a revision to the OpenGIS® Web Services Common Standard. This document specifies many of the aspects that are common to multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily parameters and data structures used in operation requests and responses. Examples of common usage are how to handle bounding boxes, exception processing, URL requests, URN expressions, key value encoding, and so forth.

The primary use of OWS Common is as a normative reference for other OWS standards. Those standards currently include the OpenGIS Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS) Standards. Rather than continuing to repeat this material in each Implementation Standard, each standard normatively references each relevant part of OWS Common.

The 30 day public comment period begins April 20, 2009 and closes on May 20, 2009. Comments will be reviewed and processed by the OGC Membership. The intent is to edit the OWS Common standard and move the revised document to be an approved OGC standard. The OpenGIS® Web Services Common Standard Request for Comment document can be downloaded below.

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] 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 Comments on NetCDF Enhanced Data Model Extension Standard

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC®) membership seeks comments on an OGC candidate standard, the Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Encoding Standard. This document specifies an extension to the existing OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0.

The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena. NetCDF (network Common Data Form) is widely used internationally to communicate and store many kinds of multidimensional data, although it was originally developed for the Earth science community. The netCDF data model is particularly well suited to providing data in forms familiar to atmospheric and oceanic scientists: namely, as sets of related arrays. NetCDF was developed and is maintained and actively supported by the Unidata Program Center (http://www.unidata.ucar.edu) of the University Corporation for Atmospheric Research (UCAR).
 
The netCDF classic data model has previously been established as the core OGC CF-netCDF standard. With this extension to the core standard for the enhanced data model, complex data structures can be represented very easily, allowing for more efficient programming. In performance-critical applications, the enhanced model provides significant benefits. Moreover, if existing HDF5 (Hierarchical Data Format, release 5) applications that depend on groups, user-defined types, unsigned types, or strings produce or use these data, the netCDF enhanced data model is required. The recently introduced candidate NetCDF Enhanced Data Model Extension Encoding Standard is the latest step in a longer-term plan for establishing CF-netCDF as an OGC standard for binary encoding, which will enable standard delivery of data in binary form via several OGC service interface standards, including the OGC Web Coverage Service (WCS), Web Feature Service (WFS), and Sensor Observation Service (SOS) Interface Standards.
 
The candidate OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Encoding Standard and information about submitting comments on this document are available below. The public comment period closes on July 1, 2012.
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: 

OpenGIS® Sensor Model Language (SensorML): Request for Public Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS® Sensor Model Language (SensorML). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed encodings required for OpenGIS® Sensor Model Language (SensorML). Documentation of this draft specification can be downloaded here:

Candidate Submission: Wed, 2006-02-01 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-05 16:00
Begin request period: Fri, 2006-05-05 16:00
 

Downloads: 

This document specifies models and XML encoding for the core SensorML. SensorML provides a common framework for any process and process chain. Within SensorML, sensors and transducer components (detectors, transmitters, actuators, and filters) are all modelled as processes that can be connected and participate equally within a process chain, and which utilize the same process model frame as any other process.
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] 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 Web Services, Phase 6 (OWS-6) Request For Quotation and Call For Participation

Status: 
Please note:  As of October 31, this Request is CLOSED to further proposals.
Description: 
RFQ Issuance Date: 21 July 2008
OWS-6 Bidder's Conference: 8 August 2008
Proposal Due Date: 5 September 2008

 


Overview

OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate specifications into OGC's Specification Program, where they are formalized for public release. In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include test beds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards.

The OWS-6 sponsors are organizations seeking open standards for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommended to the sponsors that the content of the OWS-6 initiative be organized around the following threads:

  1. Sensor Web Enablement (SWE)
  2. Geo Processing Workflow (GPW)
  3. Aeronautical Information Management (AIM)
  4. Decision Support Services (DSS)
  5. Compliance Testing (CITE)

OWS-6 Sponsors

  • U.S. National Geospatial-Intelligence Agency (NGA)
  • Joint Program Executive Office for Chemical and Biological Defense (JPEO-CBD)
  • GeoConnections - Natural Resources Canada
  • U.S. Federal Aviation Agency (FAA)
  • EUROCONTROL
  • EADS Defence and Communications Systems
  • US Geological Survey
  • Lockheed Martin
  • BAE Systems
  • ERDAS, Inc.

OWS-6 Threads

1) Sensor Web Enablement (SWE)

The OGC Sensor Web Enablement framework has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. OWS-6 will focus on integrating the SWE interfaces and encodings into cross-thread scenarios and workflows to demonstrate the ability of SWE specifications to support operational needs. Emphasis for SWE during this phase of the OWS test-bed will be on:

  • CCSI-Enabled CBRN Sensors into the SWE Environment
  • Build on Georeferenceable imagery accomplishments of OWS-5
  • Harmonize SWE-related information models: SensorML, GML, UncertML, MathML
  • Apply GeoRM, Trusted Services, and security models in SWE environment
  • Events-based architecture including WNS

2) Geo Processing Workflow (GPW)

This GPW thread aims to build on the progress of previous testbeds with a focus on maturing the interoperability and capabilities of OGC web services in a service-oriented architecture with particular emphasis to address OGC web service security issues. To satisfy mission-critical goals, the architecture must not only provide for integration of a wide variety of service capabilities and resources, it must do so and ensure authenticity, integrity, quality and confidentiality of services and information. To meet these goals, the following task areas have been identified:

  • Asynchronous Workflow and Web Services Security
  • Data Security for OGC web services
  • Data Accessibility
  • WPS Profiles - Conflation; and Grid processing
  • GML Application Schema Development & ShapeChange Enhancements

3) Aeronautical Information Management (AIM)

The Aviation Information Management (AIM) subtask is a new thread within OWS to develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) in an OGC Web Services environment. The AIM subtask shall focus on evaluating and advancing various AIXM features in a realistic trans-Atlantic aviation scenario setting by devising and prototyping a Web Services Architecture for providing valuable aeronautical information directly to flight decks, Electronic Flight Bags (EFB) and hand-held devices (such as PDAs and Blackberries) while the airplane is at the gate or en-route to its destination (for the purposes of OWS-6, the aeronautical information in the latter case does not depend on the knowledge of the airplane's location).

AIXM was developed by the Federal Aviation Administration (FAA) and Eurocontrol as a global standard for the representation and exchange of aeronautical information. It was designed as a basis for digital aeronautical information exchange and for enabling the transition to a net-centric, global aeronautical management capability. AIXM has been developed using the ISO 19100 modeling framework and has two major components: a conceptual model presented in the form of an UML class model and a data encoding specification which was developed using the OGC Geography Markup Language (GML). Both have been tailored to the specific requirements for the representation of aeronautical objects, especially the temporality feature that allows for time-dependent changes affecting AIXM features. More information about AIXM is available on www.aixm.aero. In support of the above objectives, the OWS-6 AIM thread shall perform tasks in the following areas while ensuring that the integrity of data is preserved throughout all data exchange operations:

  • Use and enhancement of Web Feature Service and Filter Encoding specifications in support of AIXM features and 4-dimensional flight trajectory queries,
  • Prototype of Aviation client for retrieval and seamless visualization of AIXM, Weather and other aviation-related data, emphasizing time and spatial filtering in order to present just the right information into a given user context anytime, anywhere,
  • Architecture of standards-based mechanism to notify users of changes to user-selected aeronautical information.

4) Decision Support Services (DSS)

Decision Support Services having an emphasis on applications of geospatial and temporal information has been a recurring thread in previous OWS testbeds. This thread focuses on presenting and interacting with data obtained from the sensor web and geoprocessing workflows in the most effective ways to support analysis and decision making. The focus for DSS in OWS-6 builds on portrayal, WMS Tiling, and integrated client work from OWS-4, with additional work on 3D visualization and integration of the built environment and landscape. This thread will encompass these capabilities and task areas:

  • ISO 19117 and OGC SLD Portrayal
  • 3D Portrayal of GML with Fly-through
  • Hosting CityGML data with WFS
  • Outdoor and indoor 3D route and tracking services
  • WMS performance (tiling)
  • Integrated Client for multiple OWS services

5) Compliance Testing (CITE)

Validating compliance with an OGC specification means verifying that a software product has implemented the specification correctly by testing the software interface for response and behavior that is outlined in the specification. Verifying compliance to the standard is necessary in order to achieve interoperability. As a result, geospatial application vendors desire to provide their potential costumers a means to verify adherence to OGC standards as a measurable discriminator for the interoperability of software products. Similarly, users desire assurance that acquired software components will interoperate with their existing investments in OGC-compliant technology. The Conformance and Interoperability Test and Evaluation (CITE) thread is intended to provide the geospatial industry (consumers and vendors) a methodology and tools that will test compliance with OGC web services.

The OGC Interoperability Program and the OGC Specification Program have achieved a great deal of momentum as a result of the multiple OGC web service specifications that have recently been published. Key consumers in the geospatial industry are modernizing their enterprises based on the applicability and interoperability of OGC web services. The major geospatial industry consumers require verifiable proof of compliance with OGC specifications in order to reach the desirable outcome of interoperability. Furthermore, as the OGC technology stack has matured, a group of interfaces has emerged that represents a baseline of technology needed to implement a fully interoperable, end-to-end spatial data infrastructure. The CITE threads in previous OWS projects have made significant progress towards having a complete suite of compliance tests for this baseline of interfaces.

A major focus of OWS-5 was on achieving consensus on the format and content of an Abstract Test Suite (ATS). The OWS-5 CITE participants agreed to follow the ISO guidance for writing Abstract Test Suites. The ATS are used to develop Executable Test Suites which are the scripts that the TEAM Engine runs to conduct an automated compliance test. A major focus of OWS-6 CITE will be in clearly documenting the approach to defining Abstract Test Suites. This will be a great benefit to the OGC community as the OGC Architecture Board (OAB) requires that new specifications be published with an accompanying ATS. In addition, a focus of OWS-6 CITE will be to expand the usability of the existing OGC compliance tests by "tailoring" these tests for specific schema profiles and/or data.

Downloads: 

Proposals for cost reimbursement are due by September 5, 2008.

Click a link to download the .zip archive:
DOWNLOAD COMPLETE PACKAGE
Complete OGC Web Services, Phase 6 (OWS-6) RFQ (zip format)

OGC Web Services, Phase 6 (OWS-6) Bidder's Conference Information


A Bidder's Conference is currently scheduled for 8 Aug 2008, 10am-noon US Eastern time.
Time: 14:00 UTC, 4:00 PM CEST, 10:00 AM EDT, 9:00AM CDT, 7:00 AM PDT
Phone line: +1 512-225-3050 passcode:36429#.
WebEx will also be used; connection instructions to be sent out before the meeting.

Clarifications to OWS-6 RFQ/CFP

The following clarifications apply to the Request for Quotation/Call for Participation in OGC Web Services, Phase 6 (OWS-6) as issued on 21 July 2008. This list will be updated as additional clarifications are needed. The most current list will always be posted here:

Clarifications have been posted .

 


OGC Requests: 

OGC seeks comment on candidate Earth Observation profile of coverage standard

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Closing Date: 
Tue, 11/01/2011 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate Earth Observation profile for the OGC Web Coverage Service (WCS) 2.0 standard. This profile will facilitate on-line data access to Earth Observation data products.

The OGC WCS 2.0 standard defines a general interface and operations that enable interoperable access to geospatial coverages, such as sensor data, satellite imagery, digital elevation models, and climate/ocean data. The candidate OGC Web Coverage Service Application Profile for Earth Observation products (EO-WCS) defines an interface for interoperable access to Earth Observation data.

The rapid increase of computer power and network accessibility, along with implementations of the OGC WCS standard, make it possible for applications to deliver user selected sensor, image, and statistics data, including human modifications of the Earth's surface and atmosphere. As use of the standard increases, an increasingly wide variety of data will conveniently be brought together in applications such as environment, natural resources, planning, disaster management and public security.

The candidate Earth Observation profile for the OGC Web Coverage Service (WCS) 2.0 standard documents are available for review and comment below.

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: 

The OGC Seeks Comments on Candidate GeoPackage Encoding Standard

Status: 
Please note: This call is now closed.
Closing Date: 
Fri, 11/08/2013 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks final “last-call” public comments on the current draft of the candidate OGC GeoPackage (GPKG) Encoding Standard. The GPKG Standards Working Group (SWG) will consider all submitted comments for minor and editorial changes when they prepare a final draft of the GeoPackage Standard.

The candidate OGC GeoPackage Encoding Standard provides an open, non-proprietary, platform-independent SQLite container for distribution and direct use of all kinds of geospatial data, including vector features and tile matrix sets.  GeoPackage can be used by mobile device users who require geospatial application services and associated data in disconnected or limited network connectivity environments where open, sharable geospatial data to support their applications is frequently unavailable. GeoPackage supports applications that involve creation of geospatial data products in enterprise computing environments, data product distribution to other computing environments, mobile workforce data capture and updates, and volunteered geographic information.

The GeoPackage and the related GPKG SQLite Configuration and GPKG SQLite Extension API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world.  Standard configuration and APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services. 

All OGC standards are free and publicly available. The candidate OGC GeoPackage Encoding Standard can be downloaded below.

OGC will also release the candidate OGC GeoPackage (GPKG) Encoding Standard on GitHub, a web-based hosting service for software development projects, on 1 November 2013.  See http://opengis.github.io/geopackage/.

The GeoPackage SWG will consider change requests for the candidate GeoPackage Standard that have been posted through 8 November 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.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: 

Request for Comment on Image Geopositioning Service (IGS)

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS Image Geopositioning Service (IGS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Image Geopositioning Service (IGS) Draft Implementation Specification defines an Image Geopositioning Service (IGS) interface to services that perform triangulation. (NOTE: The name of this service has not yet been formally agreed upon.) Accompanying this draft specification is a separate OpenGIS Image Geopositioning Metadata Geography Markup Language (GML) Draft Application Schema, which is structured to provide consistency between the IGS and other OGC Web Services (OWS) specifications.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for the IGS. Documentation of this draft specification can be downloaded below:

Candidate Submission: Thur, 2007-03-22
TC and PC vote to issue request: Fri, 2007-04-20
Begin request period: Tue, 2007-05-15
Close request period: Thu, 2007-06-14

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