SOS - Obligation of observedProperty parameter in GetObservation request - SOS

OGC Doc 08-183

Open Geospatial Consortium

CR-Form-v3

CHANGE REQUEST
SOS CR



08-183



rev

-



Current version: 06-009r6 

 

For HELP on using this form, see bottom of this page or look at the pop-up text over the  symbols.
Proposed change affects:



AS

Imp Spec X

Best Practices Paper

Title:

 Obligation of observedProperty parameter in GetObservation request

Source:

 Oceans IE WG – Luis Bermudez (SURA)

Work item code: 
Category:

Other

Date:  2008-11-07

 C
Use one of the following categories:
F (Critical correction)
A (corresponds to a correction in an earlier
release)
B (Addition of feature),
C (Functional modification of feature)
D (Editorial modification)
Detailed explanations of the above categories can
be found in the TC Policies and Procedures.

Reason for change:

 Simplification of SOS getObservation request, as demonstrated by the Oceans
IE report (08-124).

Summary of change:  Change obligation of observedProperty parameter in GetObservation request
from mandatory to optional and from ‘one or many’ to ‘zero or many’.
Table 4, specifies that the observedProperty is mandatory. It should be optional,
since the ObservationOffering already provides the information of the
observedProperties that could be returned. Furthermore if is not given, the
default behaviour should be to return all the observedProperties advertised in
the getCapabilities response.
Consequences if
not approved:



Clauses affected:

 8.4.2

Other specs
Affected:



Supporting Doc.



Other comments:
Status
Disposition






Other core specifications
Abstract specifications
Best Practices Document



The OGC Technical Committee Policies & Procedures 05-020r3

Last Revision Date: 2 December 2017

Page2