EO Metadata EO Coverage .1 Overview
8
Copyright © 2014 Open Geospatial Consortium
NOTE Throughout this standard,
eop:
and
EOP::
can be substituted by
opt:
and
OPT::
or
sar:
and
SAR::
, respectively, as in [OGC 10-157r3]
opt
and
sar
are in the substitution group of
eop
.
Figure 3 — UML Lineage class diagram
NOTE The
lineage
records are supposed to describe the history of processing steps that has led to the coverage on hand. As at the time of this writing there is no canonical format for such histories available
in OGC, for the purpose of this specification no assumption is made about the contents of a
lineage
record, except that GetCoverage appends its request verbatim as an additional record see Requirement 46.
The footprint of an EO Coverage, which contains one or more bounding polygons to describe the region of valid data more accurately than the EO Coverage’s bounding box, is mandatory
as opposed to [OGC 10-157r3].
Requirement 2 reqeowcsfootprint-in-eo-metadata: The
EOWCS::EOMetadata
element of
EOWCS::ReferenceableEOCoverage
and
EOWCS::RectifiedEOCoverage
instances shall contain an
eop:EarthObservat- ionom:featureOfInteresteop:Footprint
element.
NOTE As per [OGC 10-157r3], the footprint is always given in WGS84.
6.3 EO Coverage 6.3.1 Overview
An EO Coverage is a coverage as defined in the GML Application Schema for Coverages [OGC 09-146r2]. EO Coverages appear in two variants:
Rectified EO Coverages are derived from Rectified Grid Coverage as defined in [OGC 09-146r2];
Referenceable EO Coverages are derived from Referenceable Grid Coverage as de- fined in [OGC 09-146r2].
Requirement 3 reqeowcseo-coverage-structure:
EOWCS::ReferenceableEOCoverage
and
EOWCS::RectifiedEOCoverage
in-
stances shall conform to Figure 2, Figure 3, and the XML schema being part of this standard.