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: 

OGC Web Services, Phase 8 (OWS-8) Request For Quotation and Call For Participation

Status: 
Please note: This Request closed on 14 January 2011.

 

Description: 

 

RFQ Issuance Date: 22 November 2010

OWS-8 Bidder's Conference: 6 December 2010, 10:00-11:30am US EST
Proposal Due Date:
14 January 2011, 5:00 p.m. EST.

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

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

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-8 sponsors are organizations seeking open standards for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommend to the sponsors that the content of the OWS-8 initiative be organized around the following threads:

  • Observation Fusion
  • Geosynchronization (Gsync)
  • Cross-Community Interoperability (CCI)
  • Aviation

OWS-8 Sponsors

  • U.S. National Geospatial-Intelligence Agency (NGA)
  • U.S. Geological Survey (USGS)
  • U.S. Army Geospatial Center (AGC)
  • U.S. Federal Aviation Administration (FAA)
  • EUROCONTROL
  • U.S. National Oceanic and Atmospheric Administration (NOAA)
  • U.S. National Aeronautics and Space Administration (NASA)
  • European Space Agency (ESA)
  • U.K. Defence, Science and Technology Laboratary (DSTL)
  • Lockheed Martin Corporation

OWS-8 Threads

In July 2010, the OGC issued a call for sponsors for the OWS-8 interoperability initiative to advance OGC's open framework for interoperability in the geospatial industry.  Two meetings were conducted with potential OWS-8 sponsors to review the OGC technical baseline, discuss OWS-7 results, and identify new requirements to be addressed in OWS-8.  The following organization and scope of activity threads resulted from consolidation of all sponsors’ requirements:

  • Observation Fusion
    • WCS 2.0 Earth Observation Application Profile, WCPS, Compliance Test Scripts
    • Detection, tracking, and bookmarking of moving objects in video, implemented using SWE and other OGC encodings and interfaces.
  • Geosynchronization
    • Geodata Bulk Transfer: The ability to distribute individual data sets and/or collections of data sets in a consistent manner offline and over networks.
    • Geosynchronization: Web services and client components to support synchronization and updates of geospatial data across a hierarchical Spatial Data Infrastructure (SDI).
  • Cross-Community Interoperability (CCI)
    • Advancement of semantic mediation approaches to query and use data based on different heterogeneous data models, which are available via OGC WFS.
    • Advancement of the use of style registries and styling services.
    • Advancement of the use of KML.
    • Advancement of the use of UML/OCL for Schema Automation on Domain Models.
  • Aviation
    • AIXM: Maturing the delivery, filtering and update of AIXM 5.1 using WFS-T/FE 2.0; continuing the development of reusable tools, benchmarking of compression techniques for enhanced performance, advancing styling and portrayal support, and validating the emerging metadata and GML profiles.
    • Event Notification Architecture: including Digital NOTAM Events.
    • WXXM and weather information: using coverages for encoding representative weather forecast and radar datasets, supporting on-demand Coordinate Reference System (CRS) specifications/transformations, exploring alternative distributed architectures for managing Units of Measure (UoM), demonstrating the applications of probabilistic Terminal Aerodrome Forecasts (TAF) decision making applications, and reviewing/validating the WXXM schemas.

Schedule of Events and Milestones

  • Request for Quotation / Call for Participation (RFQ/CFP): 22 November 2010
  • Bidders Conference (Q&A with WebEx): 6 December 2010. Go to the WebEx calendar here: http://opengeospatial.webex.com/ and look for the OWS8 Bidders event.
  • Last date for submitting questions or changes to the RFQ: 15 December 2010
  • Proposals due: 14 January 2011
  • Participant selections completed: 28 January 2011
  • OWS-8 Kickoff (3-day workshop in DC area, attendance required): 9-11 March 2011
  • OWS-8 Completion (final reports due): 30 September 2011

Live demonstrations of OWS-8 results will be conducted at the September 2011 OGC Technical Committee meeting in Boulder, Colorado USA 

Demonstration videos of the testbed results will be posted for public viewing within 30 days of testbed completion. 

Downloads: 
Proposals for cost reimbursement are due by 14 January 2011, 17: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 8 (OWS-8) RFQ (pdf  zip format)
Complete OGC Web Services, Phase 8 (OWS-8) RFQ (doc  zip format)

OR INDIVIDUAL FILES

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

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

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

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

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

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

Questions: Bidder's Conference

 A Bidder's Conference (webinar) was held Monday 6 December 201010:00-11:30am US EST to discuss all communications received since the RFQ release. You can download and view the “OWS8 Bidders Conference” video.

 

 

 

Clarifications Document

All Q&A, updates, and other information about OWS-8 from the Bidder’s Conference and other communications will be collected into a Clarifications document, and posted here for public access. Subsequent questions may be directed by email to techdesk [at] opengeospatial.org (techdesk [at] opengeospatial.org) until 15 December 2010. After this date, no further questions or clarifications will be posted. The Clarifications Document is here:

Clarifications - pdf
Clarifications - doc

OGC Requests: 

The OGC requests comment on the Scaling Extension to the OGC Web Coverage Service Interface Standard

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

The Open Geospatial Consortium (OGC®) is seeking comments on the candidate OGC Web Coverage Service (WCS) Interface Standard Scaling 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 Scaling Extension document specifies parameters to the WCS GetCoverage request that provide control over scaling of a coverage during its server-side processing. Scaling refers to retrieving gridded coverages in reduced resolution, such as for thumbnails or lower-resolution overview pictures.

All OGC standards are free and publicly available. Download the candidate OGC WCS Scaling Extension Standard below.  Comments are due by 19 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: 

OGC Request for Information on "Contextual State Description" Services

Status: 
Please note: This Request is closed.
Description: 

Introduction

With this Request for Information (RFI), The Open Geospatial Consortium Inc. (OGC) is soliciting input on technologies related to Contextual State Descriptions (CSD).  A CSD describes the "environment" or context in which a service chain executes. The objective of this request is to identify existing capabilities that can provide a robust metadata foundation for supporting agile, adaptive, autonomous processes capable of producing repeatable, predictable results with no intervention.

In August, 2004, the Open Geospatial Consortium Inc. (OGC) issued a call for sponsors for an OGC Web Services 3 (OWS-3) interoperability initiative, a multi-threaded test bed activity to advance OGC's open framework for interoperability in the geospatial industry.  Key Components of OWS-3 will Sensor Web Enablement (SWE) and Service Chaining.  Each of these components are described below followed by some potential uses for CSD in OWS-3.

Organizations with relevant technology regarding CSD are urged to respond to this RFI. Information on how to respond are at the end of this RFI.  The contents of the OWS-3 request for quotations (RFQ) will be based in part on the RFI response to the CSD RFI.

 

Sensor Web Enablement and OpenGIS SensorWeb™

A key component of OWS-3 will be Sensor Web Enablement (SWE), in which OGC members are developing standard interfaces and encodings that will enable real time integration of heterogeneous sensor webs into the information infrastructure. Developers will use these specifications in creating applications, platforms, and products involving web-connected devices such as flood gauges, air pollution monitors, stress gauges on bridges, mobile heart monitors, Webcams, and robots as well as space and airborne earth imaging devices. Several elements of SWE have already been developed and are being finalized before they are submitted to the OGC membership for adoption. CSD is a potential new element of SWE.

OWS-3 will combine the previous work on SensorWeb with the OWS-2 Image Handling and Decision support results to provide automated workflow management to produce value-added products. SensorWeb is the source of tremendous amounts of geospatial data, e.g.,  in-situ, imagery and simulation data.  The Decision Support component of OWS-3 will continue the work of OWS-2 Service Chaining to produce value-added information products derived from SensorWeb data.

 

Using CSD for Service Chaining

A major thrust of OWS-2 was Image Handling for Decision Support. The Image Handling component of OWS-2 increased the ability to access and process geographic imagery into value-added products using open web services.  The Decision Support component of OWS-2 demonstrated automated service chaining of imager processing services.  This automation was achieved with an emerging open specification of workflow management: BPEL.

This RFI seeks input on the technology related to Contextual State Descriptions (CSD).  A CSD could describe the "environment" or context in which a service chain "executes". A well-characterized service chain or workflow derives a repeatable result given equivalent sources, methods, and processing state or context.  A workflow script defines the order of service invocation in a service chain but the details of the services are hidden behind the web service interface. A CSD provides information about the distributed processing environment and resources that are hidden behind the interfaces.  A CSD is specifically designed to address environmental state descriptions, in such a manner that an equivalent state can be recreated at some future point to provide identical, repeatable results from a specified process, assuming identical sources, services and scripting are utilized.

When workflows are manually executed and interpreted, complexity can be addressed through human intuition and experience.  However, in an autonomous environment, complexity must be distilled into codified states, before business logic can be characterized to facilitate autonomous processing with any level of confidence.  Thus, a CSD is specifically designed to facilitate the autonomous processing of complex workflows in a predictable, repeatable fashion.

The promise of complex autonomous processing is the increased productivity of end user "analysts" that presently focus an inordinate amount of their time preparing data instead of analyzing it.  Thus, the transition of data into information into knowledge into some form of decision or course of action is largely still a manual process that cannot be reliably repeated.  True autonomous processing will not determine the ultimate course of action from a workflow, but can relieve the analyst from having to manually shepherd data through this workflow process, freeing them to focus on interpreting the derived knowledge into alternative courses of action in less time than the current process requires to develop a single course of action manually.

CSD does not describe the workflow business logic, but the contextual state that the workflow executes within.  Thus, the CSD would describe the systems configuration, the hardware configuration, the firmware used by each device, the operating system, including patches, the software configuration, including external dependencies (shared libraries), and any data.  All of this information characterizes the operational state or context of the system. Any change in this contextual state may result in discrepancies when the workflow is re-executed.

 

Potential use for CSD in OWS3

OWS-3 will apply service chaining to enable use of SensorWeb technologies for decision support.  This technology will allow sensor measurements and modeling predictions to be processed into higher-value information specific to a given decision making context.  CSD may be used to capture the state of the service chain including the SensorWeb components and the geo-processing services and the workflow management components.  Capturing this information in a CSD will allow for post-processing analysis of the decision support information.

For instance, this initiative could describe each of the sensor components of the current SensorWeb, as well as a corresponding set of metadata to describe the processing chain.  Quality metrics embedded within the data stream can describe the resultant accuracies associated with any point in the stream.  However, when a degraded signal is recorded within the sensor stream, there is no context to interpret the cause and effort on the resulting value-added information.  The CSD associated with this process could describe the environmental context or state that the SensorWeb was operating within to illustrate the reason for the degraded decision support information.

Due to the potential iterative nature of CSDs, a normalizing relationship structure must be provided to "relate" voluminous descriptive metadata references, without requiring these references to be redundantly embedded within a single CSD.  Several compelling technologies and standards currently exist to address these specific issues.  The net result of an CSD-enabled workflow would be a greater understanding of the situational context present when the SensorWeb was captured.  These concepts are not new and have often been referred to as "fusion", multi-INT/multi-Source, and/or horizontal integration.

CSD could be applied to the OWS-2 Image Handling results including automated image orthorectification.  In OWS-2, the orthorectification was accessible by a single web service request without exposing the underlying processing hardware.  While retaining this simple web service interface, CSD could be used to capture a description of the underlying processing environment.  For example, orthorectification may be performed by a cluster-based computing task with the processing load distributed across all available nodes in the cluster.  Depending upon the load on the system, the number of nodes available during processing time, the system resources allocated to each node and the system, the methods and availability of source materials (raw imagery and control information), and the business logic applied to the process (tiling inputs, parallel vs. serial processing, types of control applied), the resultant orthorectified images will be created with varying degrees of accuracies and latencies.  Once sufficiently populated, these accuracies and latencies (CSDs) can be mined to support the development of an adaptive system, whereby an orthorectification request can be fulfilled based on the degrees of freedom provided by varying the accuracies or latency in the fulfillment of this request.

 

Objective Requirements

The objective of this RFI is to identify existing capabilities that can provide a robust metadata foundation for supporting agile, adaptive, autonomous processes capable of producing repeatable, predictable results with no intervention.  These objectives are purposely abstracted to describe a wide variety of processes or workflows, beyond just computer system processes.

A CSD shall describe the contextual state of a process or workflow. The structure of a CSD shall be such that a subsequent re-execution of a specified process will generate equivalent results, assuming the state from which the original process executed can be faithfully replicated.  A CSD shall be capable of relating or referencing other external processes, services, or data as part of a contextual state.  External references embedded within a CSD should not require the inclusion of the full reference, but rather a form of relation that will support normalized, iterative references.  CSD shall not be explicitly tied to computer system processes or workflows, but must support a much broader, abstracted description of a process and/or workflow.

CSD is information, i.e., metadata, about the processing environment. OGC has adopted and implemented ISO 19115:2003, Geographic Information - Metadata in OGC Abstract Specification, Topic 11 - Metadata. While ISO 19115 is primarily for the description of datasets, it includes metadata to describe the processing history of a dataset.  While the objectives of CSD exceed the elements in ISO 19115, CSD implementations must utilize elements of ISO 19115 when appropriate in lieu of defining new terms for the same concept.

Methodologies need to be developed to couple CSDs with processes and workflows as logical metadata structures.  Methodologies need to be provided to extract the contextual state from a system, process or workflow and codify that state within a specified CSD. Additional methodologies need to be provided to extract a contextual state from a CSD to reconfigure (to the extent physically possible) a described system capable of re-executing the process or workflow associated with the CSD.  Methods need to be developed that can identify and codify the differences between two CSDs, forming the basis for determining whether two CSDs are essentially equivalent.  A CSD shall be capable of being described in a service context that will facilitate autonomous processing of CSD attributed processes and workflows.

 

Responding to this Request

Organizations responding to this request should send a short document to:

George Percivall
Executive Director, Interoperability Architecture
Open Geospatial Consortium

percivall [at] opengeospatial.org

A response to this RFI must contain the following information:

  • A description of the technology relevant to CSD
  • Descriptions of example implementations of the relevant technology
  • Applicability of the technology to OWS3, e.g., SWE and Service Chaining.

Documents in pdf format are preferred.

Submission of proprietary information is discouraged. Any response containing proprietary information must place that information in a separate file.  Do not send proprietary information unless your organization has previously executed a Non-Disclosure Agreement with OGC.

Any organization with relevant technology can respond to this RFI.  You need not be a member of OGC to respond.  There is no reimbursement for responding to this RFI. By accepting an RFI response, OGC implies no endorsement of the technology and there is no implied agreement that the contents of an RFI response will be reflected in the OWS-3 RFQ.

For more information about CSD Services, contact:

Brent Bursey
President, Great-Circle Technologies, Inc.,
703 764-9140,

BBursey [at] Great-CircleTech.com

The OGC is an international industry consortium of more than 250 companies, government agencies and universities participating in a consensus process to develop publicly available interface specifications. OpenGIS(R) Specifications support interoperable solutions that "geo-enable" the Web, wireless and location-based services, and mainstream IT. The specifications empower technology developers to make complex spatial information and services accessible and useful with all kinds of applications. Visit the OGC website at http://www.opengeospatial.org.

Candidate Submission: Tue, 2004-08-10 17:00
Close request period: Thu, 2006-08-10 17:00
TC and PC vote to issue request: Thu, 2006-08-10 17:00
Begin request period: Thu, 2006-08-10 17:00
 

OGC Requests: 

OGC Calls for Industry Input on multi-INT Decision Fusion

Status: 
Please note: This Request is scheduled to close on 25 June 2010.
Description: 

The Open Geospatial Consortium (OGC®) has issued a Request for Information (RFI) to solicit industry input into the second phase of a Fusion Standards Study. Phase 2 of the study focuses on Decision Fusion. Input from the RFI will influence planning for the OGC Web Services, Phase 8 (OWS-8) Testbed. OGC also seeks to establish alliances with other Standards Development Organizations (SDOs) having standards work relevant to fusion.

Decision Fusion, as described in the RFI, provides analysts an environment of interoperable services for situation assessment, impact assessment and decision support, based on information from multiple sensors and databases, e.g., multi-INT sources. The study includes recent advances such as social networking for decision fusion. Though the focus of the study is on military intelligence (“INT”), decision fusion is equally relevant to business intelligence, urban planning, and many other domains.

This RFI is based on requirements and contributions from OGC Member organizations – in particular the National Geospatial-intelligence Agency (NGA) – and industry recommendations from Phase 1 of the Fusion Standards Study.

The RFI contains a review of requirements and existing standards for decision fusion in several domains. Responses to the RFI will be reviewed during a workshop in July 2010.

Responses to the RFI are requested by June 11, 2010 [extended to 25 June]. The RFI includes instructions for how organizations can respond. Please contact George Percivall at gpercivall [at] opengeospatial.org with any questions.

OGC testbeds, pilot projects and interoperability experiments are part of OGC's Interoperability Program, a global, hands-on 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.

OGC Requests: 

The OGC requests comment on Coordinate Reference System Extension to Web Coverage Service Interface Standard

Status: 
Please note: This Request is closed as of 5 May 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: 
Sun, 05/05/2013 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) announced a call for public comment on the OGC Web Coverage Service (WCS) Coordinate Reference System (CRS) Extension Standard.

WCS defines an open standard interface to easily access multi-dimensional, spatio-temporal coverages, such as sensor data, satellite imagery, image time series, simulation data, point clouds, and meshes.

The OGC WCS CRS Extension defines an extension to the WCS Core that enables requests to specify that coverages be returned in one of a number of different Coordinate Reference Systems. While the WCS Core defines access only in the coverage’s Native CRS (i.e., the one in which the coverage is stored on the server), the WCS CRS Extension defines how to request and obtain a coverage in a CRS different from the Native CRS. This flexibility is important, for example, in exchanging data between different environments.

The OGC WCS CRS Extension is free and 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 5 May 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 3.1.1 CRS support 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 CRS support 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 09:00
Close request period: Fri, 2005-11-11 09:00
TC and PC vote to issue request: Thu, 2005-12-08 09:00
Begin request period: Sat, 2006-01-07 09:00
 

Downloads: 


This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for supporting other profiles for encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate Operations. This profile can be used without a GML Application Schema, and such use is assumed in this document.
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: 

Executive Director – Marketing and Communications

Status: 
Please note: This Request will remain open until the position is filled.
Description: 

The OGC seeks to hire an Executive Director for Marketing and Communications, This full time position is responsible for the planning and execution of a broad range of marketing, communications and education program activities to raise awareness and increase application of OGC standards by technology providers and users worldwide. These activities also encourage participation in OGC programs through membership growth and direct sponsorship of / participation in OGC programs.

Reporting to the President of OGC and working with OGC staff, board, membership and partner organizations, the Executive Director for Marketing and Communications (EDMC) is responsible for planning, budgeting and executing corporate programs designed to promote adoption of OGC standards by developers and users worldwide and to encourage participation in OGC membership and collaborative testbed and related program activities.

As a key member of OGC senior staff, the EDMC will have overall responsibility for ensuring that OGC marketing & communications activities effectively address both technical professionals and decision-makers at program management and policy levels, emphasizing the value and benefits of OGC's consensus standards process to encourage membership retention and growth, investment and participation in Interoperability Program initiatives, use of OGC's compliance testing and certification resources, and uptake of OGC standards within and across communities of interest.

The EDMC will develop and implement a comprehensive outreach and public relations strategy to address industry sectors and domains of interest identified by the OGC Business Plan. EDMC responsibilities include directing conference, workshop, and seminar activities, as well as creation and distribution of press releases, placement of articles and preparation of educational briefings. The EDMC will also direct OGC Technology Office staff responsible for development, operation and maintenance of all OGC public and member related web service support, including delivery of member portal, net-meeting and related collaborative services.

Core knowledge, skills, and abilities:

Essential:

• Demonstrated experience / skill in public speaking, written communications
• Prior experience in marketing, communication campaign development
• Excellent program / project management and budgeting skills
• Understanding of the geospatial and location based services marketplace
• Familiarity with IT, Web 2.0, and social networking concepts
• Familiarity with benefits of applying standards
• Ability to work effectively with others in a virtual work environment
• Ability to adapt work schedule to accommodate international communications when necessary
• Ability to travel nationally and internationally 12-16 weeks per year

Desirable:

• Experience in developing training materials/coursework
• Previous supervisory experience
• Web design experience

Education:

Undergraduate or higher degree, preferably with concentration in one or more of the following areas: geomatics, information technology, communications and marketing

Work Location:

OGC offers a flexible work environment, emphasizing work from home arrangements. Employee location in Europe or N. America near major airport hub is preferred due to travel requirements.

Travel:

This position requires frequent national and international travel, with up to 16 weeks of travel per year.

Salary:

Negotiable.

Benefits:

OGC offers a generous benefits package. Contact us for details.

Submit: 

Interested parties should send resume, CV and/or intent of interest to:   employment at opengeospatial dot org

OGC Requests: 

The OGC seeks comment on GML Coverages GeoTIFF extension and WCS 2.0 GeoTIFF 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.
Closing Date: 
Thu, 11/29/2012 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks comment on a GeoTIFF extension to the OGC GML Coverages (GMLCOV) 1.0 Standard and on a GeoTIFF extension to the OGC Web Coverage Service (WCS) 2.0 Standard, based on the former.

The OGC Geography Markup Language (GML) Encoding Standard is a widely used XML encoding for geospatial data of all types. OGC "coverages", which can be encoded in GML, associate positions within a bounded space to feature attribute values. Examples of these geospatial coverages include Earth images, referenced and non-referenced rasters, curvilinear grids, and point clouds.

The OGC GML 3.2.1 Application Schema – Coverages (GMLCOV), based on OGC Abstract Topic 6 (which is identical to ISO 19123), provides a unified method for encoding OGC coverages in GML, the OGC Sensor Web Enablement (SWE) Common Standard, and the OGC Web Coverage Service (WCS) Interface Standard. As GMLCOV is independent of a particular service definition, it allows coverage data to be exchanged through different types of services that implement these OGC standards.

To provide maximum flexibility in sharing coverage data, the GML Coverages GeoTIFF extension provides a way to encode coverages that are represented in encoding formats other than GML, such as GeoTIFF. The WCS 2.0 GeoTIFF extension binds the former extension to WCS 2.0 to allow usage of GeoTIFF encoded coverages with WCS. The OGC seeks public comment on the OGC documents describing the candidate GMLCOV and WCS extension standards for encoding GeoTIFF data in GMLCOV and using them with WCS. These documents are free and 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: 

OpenGIS® Sensor Planning Service (SPS): 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 Planning Service (SPS). 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 OpenGIS® Sensor Planning Service (SPS). Documentation of this draft specification can be downloaded here:

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

 

Downloads: 

This OpenGIS® document specifies interfaces for requesting information describing the capabilities of a Sensor Planning Service, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task.
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