Namespace: |
|
Content: |
|
Defined: |
globally in observation.xsd; see XML source |
Includes: |
definition of 1 element |
Used: |
at 1 location |
XML Representation Summary |
||||||
<... |
||||||
|
||||||
> |
||||||
</...> |
Type Derivation Tree
gml:AbstractGMLType (extension)
![]() |
<annotation>
<documentation>
</annotation>
Generic observation, whose result is anyType The following properties
</documentation>
are inherited from AbstractFeatureType: <!-- from AbstractGMLType
<element ref="gml:metaDataProperty" minOccurs="0" maxOccurs="unbounded"/> <element ref="gml:description" minOccurs="0"/> <element ref="gml:name" minOccurs="0" maxOccurs="unbounded"/> --> <!-- from AbstractFeatureType
<element ref="gml:boundedBy" minOccurs="0"/> --> <complexContent>
</complexContent>
</complexType>
|
Type: |
ID, predefined
|
Use: |
required |
Defined: |
by reference within gml:AbstractGMLType complexType |
Type: |
gml:BoundingShapeType, complex content
|
Nillable: |
(can be declared as nil using xsi:nil attribute in instance XML documents) |
Defined: |
by reference within gml:AbstractFeatureType complexType |
Type: |
gml:StringOrRefType, simple content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:ReferenceType, empty content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:CodeWithAuthorityType, simple content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:LocationPropertyType, complex content
|
Subst.Gr: |
may be substituted with 1 element |
Defined: |
by reference within gml:AbstractFeatureType complexType |
Type: |
gml:MetaDataPropertyType, complex content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:CodeType, simple content
|
Defined: |
by reference within gml:StandardObjectProperties group |
Type: |
gml:FeaturePropertyType, complex content |
Nillable: |
(can be declared as nil using xsi:nil attribute in instance XML documents) |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<documentation>
</annotation>
The association Domain shall link the OM_Observation to the
</documentation>
GFI_Feature (C.2.1) that is the subject of the observation and carries the observed property. This feature has the role featureOfInterest with respect to the observation. This feature is the real-world object whose properties are under observation, or is a feature intended to sample the real-world object, as described in Clause 8 of this International Standard. An observation instance serves as a propertyValueProvider for its feature of interest. </element>
|
Type: |
gmd:MD_Metadata_PropertyType, complex content |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<documentation>
</annotation>
If present, the association Metadata shall link the
</documentation>
OM_Observation to descriptive metadata. </element>
|
Type: |
gml:ReferenceType, empty content |
Nillable: |
(can be declared as nil using xsi:nil attribute in instance XML documents) |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<appinfo>
</annotation>
<gml:targetElement>xs:anyType</gml:targetElement>
</appinfo>
<documentation>
The association Phenomenon shall link the OM_Observation to the
</documentation>
GFI_PropertyType (C.2.2) for which the OM_Observation:result (6.2.2.9) provides an estimate of its value. The property type has the role observedProperty with respect to the observation. The observed property shall be a phenomenon associated with the type of the featureOfInterest. NOTE An observed property may, but need not be modelled as a property (in the sense of the General Feature Model) in a formal application schema that defines the type of the feature of interest The observed property supports semantic or thematic classification of observations, which is useful for discovery and data fusion. </element>
|
Type: |
om:NamedValuePropertyType, complex content |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<documentation>
</annotation>
If present, the attributes parameter:NamedValue shall describe
</documentation>
an arbitrary event-specific parameter. This might be an environmental parameter, an instrument setting or input, or an event-specific sampling parameter that is not tightly bound to either the feature-of-interest (6.2.2.7) or to the observation procedure (6.2.2.10). To avoid ambiguity, there shall be no more than one parameter with the same name. NOTE Parameters that are tightly bound to the procedure may be recorded as part of the procedure description. In some contexts the Observation::procedure (6.2.2.10) is a generic or standard procedure, rather than an event-specific process. In this context, parameters bound to the observation act, such as instrument settings, calibrations or inputs, local position, detection limits, asset identifier, operator, may augment the description of a standard procedure. </element>
|
Type: |
om:TimeObjectPropertyType, complex content |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<documentation>
</annotation>
The attribute phenomenonTime:TM_Object shall describe the time
</documentation>
that the result (6.2.2.9) applies to the property of the feature-of-interest (6.2.2.7). This is often the time of interaction by a sampling procedure (8.1.3) or observation procedure (6.2.2.10) with a real-world feature. </element>
|
Type: |
om:OM_ProcessPropertyType, complex content |
Nillable: |
(can be declared as nil using xsi:nil attribute in instance XML documents) |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<documentation>
</annotation>
The association ProcessUsed shall link the OM_Observation to the
</documentation>
OM_Process (6.2.3) used to generate the result. The process has the role procedure with respect to the observation. A process might be responsible for more than one generatedObservation. </element>
|
Type: |
om:ObservationContextPropertyType, complex content |
Defined: |
locally within om:OM_CommonProperties group |
<element maxOccurs="unbounded" minOccurs="0" name="relatedObservation" type="om:ObservationContextPropertyType">
<annotation>
<documentation>
</annotation>
Some observations depend on other observations to provide
</documentation>
context which is important, sometimes essential, in understanding the result. These dependencies are stronger than mere spatiotemporal coincidences, requiring explicit representation. If present, the association class ObservationContext (Figure 2) shall link a OM_Observation to another OM_Observation, with the role name relatedObservation for the target. </element>
|
Type: |
anyType, any content
|
Defined: |
by reference within (this) om:OM_ObservationType complexType |
Type: |
gmd:DQ_Element_PropertyType, complex content |
Defined: |
locally within om:OM_CommonProperties group |
<element maxOccurs="unbounded" minOccurs="0" name="resultQuality" type="gmd:DQ_Element_PropertyType">
<annotation>
<documentation>
</annotation>
If present, the attributes resultQuality:DQ_Element shall
</documentation>
describe the quality of the result (6.2.2.9). This instance-specific description complements the description of the observation procedure (6.2.2.10), which provides information concerning the quality of all observations using this procedure. Quality of a result may be assessed following the procedures in ISO 19114:2003. Multiple measures may be provided (ISO/TS 19138:2006). </element>
|
Type: |
gml:TimeInstantPropertyType, complex content |
Block: |
"#all" (blocks all substitutions of this element or its type) |
Defined: |
locally within om:OM_CommonProperties group |
<!-- om:resultTime is used in schematron-based validaty tests, so must not be changed -->
<annotation>
<documentation>
</annotation>
The attribute resultTime:TM_Instant shall describe the time when
</documentation>
the result became available, typically when the procedure (6.2.2.10) associated with the observation was completed For some observations this is identical to the samplingTime. However, there are important cases where they differ. </element>
|
Type: |
gml:ReferenceType, empty content |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<documentation>
</annotation>
If present, the sub-element 'type' shall indicate the class of
</documentation>
observation. A register of type identifiers corresponding with the observation types in ISO 19156, which distinguishes types on the basis of the type of the result, is provided by OGC at http://www.opengis.net/def/observationType/OGC-OM/2.0/ </element>
|
Type: |
gml:TimePeriodPropertyType, complex content |
Defined: |
locally within om:OM_CommonProperties group |
<annotation>
<documentation>
</annotation>
If present, the attribute validTime:TM_Period shall describe the
</documentation>
time period during which the result is intended to be used. </element>
|
This XML schema documentation has been generated with DocFlex/XML 1.11 using DocFlex/XML XSDDoc 2.8.3 template set.
DocFlex/XML is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from
any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually
using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML,
single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only.
And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool,
you will also make an important investment in its future development, the results of which you could enjoy later by yourself.
Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/
|