SOS change request - KVP Encoding for Core Operations
OGC Doc 08-17306-112
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
SOS CR 08-173?
rev
-
Current version:
1.0.0
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
Other
Title:
SensorOfferings instead of ObservationOffering in GetCapabilities responseKVP
Encoding for Core operations
Source:
Institute for Geoinformatics, University of Muenster
Work item code:
Category:
Date: 2008-10-301-05
B
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:
Currently, no relationships between sensor, featureOfInterest and
observedProperties could be expressed in the context section of the SOS
Capabilities document.A KVP encoding for the requests of the SOS core
operations simplifies the communication between clients and the SOS. Chapter
is mentioned in clause 8.1 of current IS, but not contained in specification.
Summary of change: Instead of grouping the offered observations into ObservationOfferings, we
propose to create a SensorOffering for each sensor which contains the observed
featureOfInterests as well as the observedProperties of each featureOfInterest.
Additionally, the time period, for which observations produced by the sensor are
available , should be contained in the SensorOffering.A KVP encoding for the
requests of the core operations is proposed.
Consequences if
not approved:
No relationship could be expressed between sensor, featureOfInterest and
observedProperties. This could lead to inconsistent queries of clients to the SOS.
Clauses affected:
4.4 Observation Offering11 KVP encoding
Other specs
Affected:
Supporting Doc.
Other comments:
Other core specifications
Abstract specifications
Best Practices Document
The OGC Technical Committee Policies & Procedures 05-020r3
Status
Disposition
4.4
Observation Offering
An observation offering is a logical grouping of observations offered by a service that are
related in some way. The parameters that constrain the offering should be defined in such
as way that the offering is “dense” in the sense that requests for observations that are
within the specified parameters should be unlikely to result in an empty set.
Last Revision Date: 2 December 2017
Page2
Open Geospatial Consortium
CR-Form-v3
CHANGE REQUEST
SOS CR 08-173?
rev
-
Current version:
1.0.0
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
Other
Title:
SensorOfferings instead of ObservationOffering in GetCapabilities responseKVP
Encoding for Core operations
Source:
Institute for Geoinformatics, University of Muenster
Work item code:
Category:
Date: 2008-10-301-05
B
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:
Currently, no relationships between sensor, featureOfInterest and
observedProperties could be expressed in the context section of the SOS
Capabilities document.A KVP encoding for the requests of the SOS core
operations simplifies the communication between clients and the SOS. Chapter
is mentioned in clause 8.1 of current IS, but not contained in specification.
Summary of change: Instead of grouping the offered observations into ObservationOfferings, we
propose to create a SensorOffering for each sensor which contains the observed
featureOfInterests as well as the observedProperties of each featureOfInterest.
Additionally, the time period, for which observations produced by the sensor are
available , should be contained in the SensorOffering.A KVP encoding for the
requests of the core operations is proposed.
Consequences if
not approved:
No relationship could be expressed between sensor, featureOfInterest and
observedProperties. This could lead to inconsistent queries of clients to the SOS.
Clauses affected:
4.4 Observation Offering11 KVP encoding
Other specs
Affected:
Supporting Doc.
Other comments:
Other core specifications
Abstract specifications
Best Practices Document
The OGC Technical Committee Policies & Procedures 05-020r3
Status
Disposition
4.4
Observation Offering
An observation offering is a logical grouping of observations offered by a service that are
related in some way. The parameters that constrain the offering should be defined in such
as way that the offering is “dense” in the sense that requests for observations that are
within the specified parameters should be unlikely to result in an empty set.
Last Revision Date: 2 December 2017
Page2