1. Coverage vs. Observations
A Question of Perspective

2. It‘s long and hairy – must be an observation
It‘s wide and full of stuff – must be a coverage
I think we‘re up against a wall!

3. Coverage vs Observations
Each model is consistent on its own. When they are linked, redundancies pertaining to domain and range occur
Each model has deficits:
O&M: Non-hierarchical sampling strategies as required for classification or other gridding of the domain
Coverage Model: Procedural information, sensor information, the HOW

4. Basic O&M Observation Domain Range Observation Process Property Domain
+featureOfInterest
+result
ProcessUsed
Phenomenon
+observedProperty
+procedure
Process
Property

5. Basic Coverage Domain Range Coverage RangeType Metadata +domainSet
+rangeSet
+rangeType
+metadata
RangeType
Metadata

6. Observation w/ Coverage
Domain
Domain
Range
Range
Observation
+featureOfInterest
ProcessUsed
Phenomenon
+observedProperty
+procedure
Process
Property
+result
Coverage
+domainSet
+rangeSet
+rangeType
+metadata
RangeType
Metadata

7. Coverage w/ Observation
Domain
Range
Coverage
+domainSet
+rangeSet
+rangeType
RangeType
+metadata
Domain
Range
Observation
+featureOfInterest
+result
ProcessUsed
Phenomenon
+observedProperty
+procedure
Process
Property

8. Bits to be Mapped Cov I
CoverageFunction - describes the mapping function from the domain to the range of the coverage
Is this generally provided, or devolved to the default axis order and logical sequence within axes?
Missing in O&M
Envelope
Correspondence sampledFeature?

9. Bits to be Mapped Cov II RangeType dataRecord interpolationRestriction
Data Type SWE Common :: DataRecord
provided within result in observation
interpolationRestriction
can‘t currently find in obs

10. Bits to be Mapped Cov III
Metadata – Coverage sometimes utilizes O&M Observation

11. Bits to be Mapped Obs
Observed Property
Procedure

12. What to do?

13. Kathi Schleidt Kathi@DataCove. eu DataCove e. U
Kathi Schleidt DataCove e.U. Robert Hamerling Gasse 1/ Vienna, Austria