Copyright © 2012 Open Geospatial Consortium
13 opt:EarthObservationResultType element which extends and acts as a substitution for
eop: EarthObservationResultType:
opt :EarthObservation
[ …]
om :result
opt :EarthObservationResult gml:id=eop_2
[ …]
opt :cloudCoverPercentage uom= 30
opt :cloudCoverPercentage
[ …]
opt : EarthObservationResult
om :result
[ …]
opt : EarthObservation
7.4.2.2 Mission specific extended namespace
Mission specific extended namespace Sentinel-1 for example contains : - sen1 words;
- a sen1:EarthObservation element that inherits from sar:EarthObservation. This inheritance is an XML schema extension to avoid restriction problems with no
element added because all elements fit inside one of the Observation property metadata, procedure, phenomenonTime, result or featureOfInterest ;
- one or more extensions of existing sar properties. These rules are close to those described in the thematic extended namespace. However,
the property extension approach leads to a drawback in the mission specific case. Indeed, from a client point of view, an “eop” enabled reader must encounter well-known
structures under “eop” properties. This may not be a problem for “eop” and thematics schemas since they are completely described in this document i.e. structure can be “hard
coded”. However, a mission specific schema shall follow the rules described in this document but
the content of this schema is not in the scope of this document. Thus a generic “eop” enabled reader should be able to process complex schema inheritance mechanisms to
“understand” mission specific data. To avoid this drawback, we introduce an attribute eop:type at the eop level. This
attribute is required for properties that extend one of eop or its thematic properties. This attribute is expected to contain the name of the property it extends directly. This
mechanism is comparable to the ISO19139 gco:isoType.
7.4.3 Units of measure
Each non-angle property concerned by a unit of measure shall use the existing GML type
gml:MeasureType.
