OGC Requests

Request for Comment on Geospatial eXtensible Access Control Markup Language (GeoXACML)

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 Geospatial eXtensible Access Control Markup Language (GeoXACML). 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 Geospatial eXtensible Access Control Markup Language (GeoXACML) Draft Implementation Specification (OGC Document 07-026) defines a geo-specific extension to the eXtensible Access Control Markup Language (XACML) OASIS standard. "Access control systems" enable management of access to information only until it is obtained by the user and stored locally, as opposed to "rights management systems" that remain in force regardless of where the content of the original resource is located or reproduced.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for GeoXACML. 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: 

OGC Seeks Comments on Sensor Observation Service Candidate Standard

Status: 
Please note: This Request is scheduled to close on 1 December, 2010.
Description: 

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the candidate OGC Sensor Observation Service (SOS) Standard Version 2.0. The SOS candidate interface standard is designed to provide access to sensor observations, sensor descriptions, and digital representations of observed features in an interoperable and standardized way. Further, the SOS 2.0 candidate standard provides means to insert new sensor descriptions or observations.

 

The OGC Sensor Observation Service revision incorporates several enhancements. These include a modular restructuring of the document, new KVP and SOAP bindings, redesign of the observation offering concept, and reliance on the OGC Sensor Web Enablement Service Model. SOS 2.0 is highly modular and follows the OGC core/extension design pattern. The main SOS 2.0 document incorporates the core as well as the transactional extension, result handling extension, enhanced operations extension, binding extension, and a profile for spatial filtering of observations. An additional document specifies the extension for the operation to retrieve metadata about the observations stored by a service.

 

The proposed OGC SOS 2.0 standard and information on submitting comments on this document are available below.  The public comment period closes on 1 December 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] 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 requests comment on the Range Subsetting Extension to the OGC Web Coverage Service Interface Standard

Status: 
Please note: This call is now closed.
Closing Date: 
Sat, 09/07/2013 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) is seeking comments on the candidate OGC Web Coverage Service (WCS) Interface Standard Range Subsetting Extension.

The OGC Web Coverage Service (WCS) Interface Standard defines an open standard interface to access multi-dimensional spatio-temporal coverages, such as satellite imagery, image time series, point clouds, and meshes. The candidate WCS Range Subsetting Extension document establishes a standard way to extract specific fields from the range set of a coverage during server-side processing of a coverage in a WCS GetCoverage request. This operation is very common in many application domains, for example in remote sensing where it is known as “band” or “channel” subsetting and in climate modeling where it is called “variable extraction”.

All OGC standards are free. The candidate OGC WCS Range Subsetting Extension Standard can be downloaded below.

The OGC WCS Standards Working Group will consider all comments when preparing a final draft of the candidate standard. The comment period ends 7 September 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: 

GML in JPEG 2000 for Geographic Imagery (GMLJP2) Implementation Specification: Request for 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 simple features profile. OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification Profile. The purpose of this Request for Comment (RFC) is to obtain comments on the proposal for technologies and needed interfaces required for GML in JPEG 2000 for Geographic Imagery (GMLJP2) Implementation Specification. Documentation of this draft specification can be downloaded here:

Candidate Submission: Mon, 2005-05-23 17:00
Close request period: Fri, 2005-06-17 17:00
TC and PC vote to issue request: Mon, 2005-06-27 17:00
Begin request period: Wed, 2005-07-27 17:00
 

Downloads: 


The Geography Markup Language (GML) is an XML grammar for the encoding of geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, and value objects. JPEG 2000 is a wavelet based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file. The "GML in JPEG 2000 for Geographic Imagery (GMLJP2) Implementation Specification" defines the OGC standard method of using GML within JPEG 2000 images for geographic imagery.
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 Candidate GeoAPI 3.0 Interface Standard

Status: 
Please note: This Request is scheduled to close on 1 May 2010.
Description: 

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the candidate OGC GeoAPI 3.0 Application Programming Interface.

The GeoAPI standard provides a set of Java language interfaces based on the ISO 19100 series of geospatial abstract models for metadata and feature geometry as well as two OGC Abstract Specifications for metadata and coordinate reference systems. In addition to producing this set of Java language interfaces, the OGC GeoAPI 3.0 Standards Working Group is producing a test suite through which developers implementing the Java interfaces can test their implementations.

The GeoAPI project emerges from the earlier OGC Geographic Objects effort and is the result of the collaboration of participants from various institutions and software communities. The GeoAPI project's goal is to provide a set of interfaces in the Java language to help software projects produce high quality geospatial software. This work is not expected to cover all OGC standards.

The candidate OGC GeoAPI 3.0 Interface Standard and information on submitting comments on this document are available below. The public comment period closes on 1 May 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: 

OGC Calls for Participation in Geo4NIEM Initiative to enhance geospatial capabilities for the the US National Information Exchange Model (NIEM)

Status: 
Please note: This Request is closed as of 4 March 2013. 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: 
Mon, 03/04/2013 - 05:00
Description: 

RFQ Issued Date: 14 February 2013
RFQ Written Comments due
: 5pm EST on 21 February 2013
Proposals Due Date
: 5pm EST on 4 March 2013

Go Directly to the Request for Quotation Document
Go Directly to the Request for Quotation Clarifications

 

Overview

The Open Geospatial Consortium (OGC®) has issued a Request for Quotations/Call for Participation (RFQ/CFP) to solicit proposals in response to requirements for the OGC Geo4NIEM Project. The Geo4NIEM Initiative will result in recommendations to enhance the geospatial capabilities within the National Information Exchange Model (NIEM). Sponsors have identified specific Information Exchange Packages (IEPs) from Department of Homeland Security (DHS), Justice/Law Enforcement domain, and the Maritime domain as representative examples for investigation in this initiative.

The RFQ/CFP is available below. Deadline for submitting questions on the RFQ/CFP is 5pm EST on 21 February 2013. Responses are due by 5 pm EST on 4 March 2013.

The Point of Contact is Lew Leinenweber: techdesk [at] opengeospatial.org (techdesk [at] opengeospatial.org).

Geo4NIEM Initiative sponsors are:

  • Program Manager – Information Sharing Environment (PM-ISE)
  • National Information Exchange Model – Program Management Office (NIEM PMO)

The focus of Geo4NIEM project will be to address requirements in the context of the following information exchange domain areas:

Justice/Law Enforcement. The Justice/Law Enforcement domain in NIEM is defined by the Global Justice XML Data Model (Global JXDM). The Global Justice XML Data Model (Global JXDM) is an XML-based framework that enables the US justice and public safety communities to effectively share information at all levels.

Maritime Domain Awareness. The Maritime domain supports the effective understanding of anything associated with global maritime that could impact the United States' security, safety, economy, or environment. NIEM facilitates this understanding through effective, timely sharing of vital, secure information among many key partners by representing vessels, people, cargo, and maritime locations and activities.

The Geo4NIEM Project has been organized to address specific functional requirements to meet the following objectives:

  • Develop recommendations for the inclusion and standard use of embedded GML with NIEM IEP documents (IEPDs).
  • Develop recommendations for the standardized use of Naming and Design Rules and the use of adaptors (e.g. NIEM wrapper for GML).
  • Test and demonstrate use of a standardized embedded GML and adaptors within NIEM IEPDs.
  • Develop Architecture documentation and a fact sheet for the use of embedded GML and adaptors for use with NIEM IEPDs.
  • Develop Recommendations for the inclusion of a Geospatial Domain within NIEM.

 

    Click a link below to download individual files or a complete package for the RFQ/CFP.

    DOWNLOAD RFP/CFP PACKAGE (as .zip archive)

    Complete Geo4NIEM RFQ/CFP (pdf zip format)
    Complete Geo4NIEM RFQ/CFP (doc zip format)

    INDIVIDUAL FILES

    Geo4NIEM RFQ Main Body (pdf)
    Geo4NIEM RFQ Main Body (doc)
    Geo4NIEM RFQ Annex A (pdf)
    Geo4NIEM RFQ Annex A (doc)
    Geo4NIEM RFQ Annex B (pdf)
    Geo4NIEM RFQ Annex B (doc)

    RFQ/CFP RESPONSE TEMPLATES (not included in above package)

    Geo4NIEM RFQCFP Template Proposal (doc)
    Geo4NIEM Template Spreadsheet (xls)

    QUESTIONS:

    Prospective bidders are invited to submit written questions by email regarding the RFQ to the OGC Technical Desk email address here: techdesk [at] opengeospatial [dot] org.

     

    CLARIFICATIONS

    Response to questions and any other clarifications are posted here:

    OGC Requests: 

    Web Processing Service (WPS): 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 Web Processing Service (WPS). 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 interfaces required for Web Processing Service (WPS). Documentation of this draft specification can be downloaded here:

    Candidate Submission: Fri, 2005-09-16 09:00
    Close request period: Fri, 2005-11-11 09:00
    TC and PC vote to issue request: Fri, 2005-12-23 09:00
    Begin request period: Thu, 2006-02-02 09:00
     

    Downloads: 


    This document specifies the interface to a Web Processing Service (WPS). A WPS can be configured to offer any sort of GIS functionality to clients across a network, including access to pre-programmed calculations and/or computation models that operate on spatially referenced data. A WPS may offer calculations as simple as subtracting one set of spatially referenced numbers from another (e.g., determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. The data required by the WPS can be delivered across a network, or available at the server.

    This interface specification provides mechanisms to identify the spatially-referenced data required by the calculation, initiate the calculation, and manage the output from the calculation so that it can be accessed by the client. This Web Processing Service is targeted at processing both vector and raster data.

    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 7 (OWS-7) Request For Quotation and Call For Participation

    Status: 
    Please note: As of 1 December 2009 this Request will be CLOSED to further proposals.
    Description: 

    RFQ Issuance Date: 28 October 2009
    OWS-7 Bidder's Conference: 10 November 2009, 11:00-13:00 US Eastern
    Proposal Due Date: 1 December 2009, 5:00 p.m. EST.

    Go Directly to the Request for Quotation Document
    Go Directly to the Request for Quotation Clarifications
    Go Directly to the Bidder's Conference Information Overview

    OGC members who wish to observe OWS-7 may do so upon submission of the OGC Observer Agreement: http://bit.ly/8DvwvK

    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-7 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-7 initiative be organized around the following threads:

    OWS-7 is organized in three activity "threads":

    • Sensor Fusion Enablement (SFE)
    • Feature and Decision Fusion (FDF)
    • Aviation

     

    OWS-7 Sponsors

    U.S. National Geospatial-Intelligence Agency (NGA)
    U.S. Federal Aviation Administration (FAA)
    EUROCONTROL
    EADS Defence Communications Systems (DCS)
    U.S. Geological Survey (USGS)
    U.S. Army Geospatial Center (AGC)
    U.S. Joint Program Executive Office (JPEO)
    BAE Systems
    PCI Geomatics
    Lockheed Martin

     

    OWS-7 Threads

    In June of 2009, the OGC issued a call for sponsors for the OWS-7 interoperability initiative to advance OGC's open framework for interoperability in the geospatial industry.  Three meetings were conducted with potential OWS-7 sponsors to review the OGC technical baseline, discuss OWS-7 results, and identify OWS-7 requirements.  During the OWS-7 Concept Development phase, a Fusion Standards Study was also conducted, to better inform the requirements for OWS-7 development. 

    The definition of fusion resulting from the study was:

     "Fusion is the act or process of combining or associating data or information regarding one or more entities considered in an explicit or implicit knowledge framework to improve one's capability (or provide a new capability) for detection, identification, or characterization of that entity".

    There exist many fusion processes deployed in closed architectures with existing single provider software and hardware solutions. The problem in the study was to move those capabilities into a distributed architecture based upon open standards including standards for security, authorization, and rights management.

    In the study, fusion was discussed in terms of the three categories shown in the central column in Figure 1‑1:

    Figure 1-1

    Figure 11. Categories of Fusion

    The sponsors selected elements of the Fusion Study results to include in the two OWS-7 threads described below.  Sensor Fusion is addressed in the Sensor Fusion Enablement (SFE) thread. Object/Feature Fusion and Decision Fusion are addressed in the Feature and Decision Fusion (FDF) thread. 

    The threads of OWS-7 build upon the threads of previous OWS test beds, as shown in Figure 1-2. 

    Figure 1-2

     

    Figure 12. Evolution of OWS Testbed Threads

    The Sensor Fusion Enablement (SFE) thread builds on the Sensor Web Enablement (SWE) and Geospatial Processing Workflow (GPW) thread by including Sensor Fusion topics and applying workflow to sensor fusion.  The Feature and Decision Fusion (FDF) thread also builds on the OWS-6 Geospatial Processing Workflow (GPW) thread, as well as the OWS-6 Decision Support Services (DSS) thread, by including feature definition and workflow of GPW along with decision support topics.

    The third activity thread in OWS-7, the Aviation Thread, began as the Aeronautical Information Management (AIM) Thread in OWS-6, which addressed the use of web services, event notifications, and AIXM 5.0 for Electronic Flight Bag (EFB) applications in the aviation industry.  The Aviation Thread in OWS-7 represents an expansion of scope, to include flight planning and aviation operations more broadly.

    Sensor Fusion Enablement (SFE)

    The SFE Thread builds on the OGC Sensor Web Enablement (SWE) framework of standards that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. SFE will focus on integrating the SWE interfaces and encodings with workflow and web processing services to perform sensor fusion.  SFE will continue the development of Secure SWE architecture, as well as the interoperability of SWE and Common CBRN Sensor Interface (CCSI).

    Emphasis for SFE during this phase of the OWS testbed will be the following:

    • Motion Video Fusion. Geo-location of motion video for display and processing. Change detection of motion video using Web Processing Service with rules.
    • Dynamic Sensor Tracking and Notification. Track sensors and notify users based on a geographic Area of Interest (AOI). The sensor and the user may be moving in space and time.
    • Trusted SWE in an untrusted environment. Build on OWS-6 Secure Sensor Web development, to investigate secure SOS, SPS in more depth.
    • CCSI-SWE Best Practice. Building on OWS-6, develop an ER to be considered by the OGC Technical Committee as a Best Practice.

    Feature / Decision Fusion (FDF)

    The FDF Thread builds on OWS-6 GPW and DSS work, in particular to advance the state of information cataloguing, Web Processing Services (WPS) profiles, and the Integrated Client. The following task areas have been identified for Feature and Decision Fusion:

    • Schema Automation. Transformation from UML to profiles of GML and KML, including generation of constraints.
    • Data Discovery and Organization. Use of thematic categories in multi-media data discovery, including augmented metadata for quality of source, fitness for use, and uncertainty of the data values, propagated through usage and workflow.
    • Feature and Statistical Analysis. Workflow profiles for feature fusion, including statistical analysis, vector and topological processing. WFS, WMS and WMTS will be used to support statistical mapping.
    • Geosynchronization. Web services and client components to support synchronization of geospatial data and updates across a hierarchical Spatial Data Infrastructure (SDI).
    • Data and Analysis Sharing. The use of OWS Context for collecting links to web services and analysis results.
    • Integrated Client. A field-ready client application to support and display sensor information, cataloguing metadata, notification alerts, feature and statistical analysis, and OWS Context. This client will include an embedded WFS server for geosynchronization support.

    Aviation Thread

    This thread seeks to further develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) in an OGC Web Services environment.

    The US Federal Aviation Administration (FAA) and EUROCONTROL have developed AIXM as a global standard for the representation and exchange of aeronautical information. AIXM uses the OGC Geography Markup Language (GML) tailored to the specific requirements for the representation of aeronautical objects, including the temporality feature that allows for time dependent changes affecting AIXM features. FAA and EUROCONTROL are using AIXM as an integral part of their efforts to modernize their aeronautical information procedures and to transition to a net-centric, global aeronautical management capability. More specifically, AIXM is being used in the net-centric System Wide Information Management (SWIM)-related components of the US NextGen and European Union (EU)'s SESAR programs. Indeed, it is expected that the results of the Aviation Thread of OWS-7 will be contributed to both programs with a focus on recommended OGC specifications that can be applied in the definition and implementation of both SWIM environments. 

    WXXM is also jointly developed by FAA and EUROCONTROL, as a proposed standard for the exchange of aeronautical weather information in the context of a net-centric and global interoperable Air Transport System (ATS). WXXM also uses GML tailored to the specific requirements of aeronautical meteorology and is based on the OGC Observation and Measurement Model. WXXM development is harmonized and coordinated with the World Meteorological Organization (WMO), the organization traditionally responsible for standards in meteorology.

    The OWS-7 Aviation Thread will investigate and demonstrate the applicability of AIXM and WXXM along with relevant OGC specifications and web services to applications and tools that support Airline Operations Centers and Flight Dispatch applications. Such applications provide information for representing a Common Operating Picture; supporting flight planning (including General Aviation) and preparation (MET and AIM); calculating weight and balance; estimating fuel requirements; in-flight emergency response; etc. The primary focus in OWS-7 is on ground usage of the information, although provision of information packages to the crew, on the ground and in the air, is also of interest.

    To support the above goal, the OWS-7 Aviation Thread will cover the following tasks:

    • Evaluation and advancement of AIXM, in the areas of using and testing new AIXM 5.1 features, developing components/tools for generating, validating, converting, and parsing AIXM, addressing feature metadata requirements and performance constraints, and supporting the portrayal of AIXM information.
    • Evaluation and advancement of WXXM, focusing on the incorporation and demonstration new weather concepts such as the 4-D Weather Data Cube, including the impact of such concepts on the Event Notification Architecture, the support for probabilistic events, and the definition and usage of the time model in WXXM.
    • Advancement of the Event Notification Architecture developed and exercised in OWS-6 to support multiple sources of events and multiple types of events and data changes (AIXM, WXXM), and to investigate different delivery protocols (push/pull), registration and subscription lifecycle management approaches, and domain/schema-specific matching between events and subscriptions.
    • Integration of AIXM/WXXM in the FAA SWIM environment, focusing on investigating approaches for leveraging SWIM Interface Management, Messaging and Security capabilities, as well as enabling Aviation clients to access SWIM services in addition to OGC services.
    Downloads: 
    Proposals for cost reimbursement are due by 1 December 2009, 5:00 p.m. EST.
     
    For those who have done this before: Please do not reuse old templates, but use our new ones. Thanks!

    Click a link to download the .zip archive:

    DOWNLOAD COMPLETE PACKAGE


    Complete OGC Web Services, Phase 7 (OWS-7) RFQ (pdf  zip format)

    Complete OGC Web Services, Phase 7 (OWS-7) RFQ (doc  zip format)

    OR INDIVIDUAL FILES

    OGC Web Services, Phase 7 (OWS-7) RFQ Main Body (pdf)
    OGC Web Services, Phase 7 (OWS-7) RFQ Main Body (doc)

    OGC Web Services, Phase 7 (OWS-7) RFQ Annex A (pdf)
    OGC Web Services, Phase 7 (OWS-7) RFQ Annex A (doc)

    OGC Web Services, Phase 7 (OWS-7) RFQ Annex B (pdf)
    OGC Web Services, Phase 7 (OWS-7) RFQ Annex B (doc)

    OGC Web Services, Phase 7 (OWS-7) RFQ Annex C (pdf)
    OGC Web Services, Phase 7 (OWS-7) RFQ Annex C (doc)

    OGC Web Services, Phase 7 (OWS-7) RFQ Annex D (pdf)
    OGC Web Services, Phase 7 (OWS-7) RFQ Annex D (doc)

     OGC Web Services, Phase 7 (OWS-7) RFQ Template - Funding (xls)
    OGC Web Services, Phase 7 (OWS-7) RFQ Template - Proposal (doc)
     

    Clarifications

    Download the final clarifications from the bidder's conference.

    We will accept further questions through Thursday, 19-November, which I will post by Friday, 20-November. Then proposals are due by 1-December at 5pm US Eastern.

     

    Bidder's Conference Information

    The Bidder's Conference was held on 10 November 2009.  Further questions may be directed by email to techdesk [at] opengeospatial.org until Nov 19.

    The above Clarification document has been updated to reflect the questions presented during the Bidder's Conference.

    OGC Requests: 

    OGC Seeks Comments on "NIL Extension" to Geography Markup Language (GML)

    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: 
    Fri, 11/23/2012 - 05:00
    Description: 

    The Open Geospatial Consortium (OGC®) seeks public comment on the candidate "GML-NIL profile" of the OGC Geography Markup Language (GML) Encoding standard. GML is a widely used XML grammar for encoding information about geographical features. The GML-NIL profile provides a way to allow data providers to make a best effort to supply data according to an application schema, even if they do not have values for all feature properties. This is achieved by marking the application schema as a whole as ‘nillable=true’ and using OGC ‘nil’ URIs in links for missing data. This reverses the usual pattern which has a default value of nillable=false.   

     

    The GML-NIL pattern of use has been used informally for several years in Earth and environmental science applications, and this candidate standard merely aims to formalize and document the practice. It is expected to be useful in many applications where a heterogeneous community wishes to enable participation by a wide variety of members with different capabilities and data sources. The submission team is composed of members of the GeoSciML project.

     

    The candidate OGC GML-NIL standard documents are available for review and comment below.

    Downloads: 


     Nillable GML (12-110)   

     



    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® Catalogue Services Specification 2.0.1 (with Corrigendum) - ISO Metadata Application Profile (CSW2 AP ISO): RFP

    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® Catalogue Services Specification 2.0.1 (with Corrigendum) - ISO Metadata Application Profile (CSW2 AP ISO). 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 Application Profile required for OpenGIS® Catalogue Services Specification 2.0.1 (with Corrigendum) - ISO Metadata Application Profile (CSW2 AP ISO). Documentation of this draft specification can be downloaded here:

    Candidate Submission: Fri, 2006-01-20 15:00
    Close request period: Fri, 2006-03-10 15:00
    TC and PC vote to issue request: Thu, 2006-04-20 15:00
    Begin request period: Sat, 2006-05-20 15:00
     

    Downloads: 

    This application profile document specifies the interfaces, bindings, and encodings required to publish and access digital catalogues of metadata for geospatial data, services, and applications that comply with the given profile. Metadata act as generalised properties that can be queried and returned through catalogue services for resource evaluation and, in many cases, invocation or retrieval of the referenced resources.
    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