observation::OM_Observation

: Public <<FeatureType>> Class

Created:	10/4/2004 11:28:43 AM
Modified:	4/11/2013 10:50:20 AM

Project:
Author:
Version:
Phase:
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{1778FD08-66AC-437d-A152-795D9AEBDD90}
Appears In:	Summary diagram: Boreholes, Context Diagram : StratigraphicDateEstimate, Summary diagram : age values, Summary diagram: LaboratoryAnalysis (O&M v2 and SWE v1), Summary diagram: Geochronology, Figure 2: Observation Core, Figure 6: Specialized Observations, Figure 7: Coverage Observation, Overview: Observation, Context diagram: OM_Observation, Context diagram: OM_Process, OM_Measurement, OM_CategoryObservation, OM_CountObservation, OM_TruthObservation, Context diagram: OM_TemporalObservation, Context diagram: OM_GeometryObservation, Context diagram: OM_ComplexObservation, Context diagram: OM_DiscreteCoverageObservation, Summary: Time series observations, Figure 10: sampling vs. domain features, Figure 9: SF_SamplingFeature, Overview: sampling, Context diagram: SF_SamplingFeature, Figure 16: SamplingCoverageObservation, Context diagram: GFI_Feature, MonitoringPointFeatureOfInterest, Context diagram: TimeseriesObservation, Observation metadata, TimeseriesObservation specialisations, AC-MF : Overview, Observation(Informative), CoverageObservation(Informative), EnvironmentalMonitoringFacilities, ObservingCapability and link to OM_Observation, References to Environmental Monitoring Features, Soil: O&M, Observations Pattern - Overview, Observation References, ReferencesToObservation, Process, Gridded Observation Types, GridSeriesObservation, GridObservation, PointObservation, PointTimeSeriesObservation, MultiPointObservation, PointObservationCollection, Trajectory Observation, Profile Observation

An observation is an act that results in the estimation of the value of a feature property, and involves application of a specified procedure, such as a sensor, instrument, algorithm or process chain. The procedure may be applied in-situ, remotely, or ex-situ with respect to the sampling location. Use of a common model allows observation data using different procedures to be combined unambiguously. Observation details are also important for data discovery and for data quality estimation. Observation feature types are defined by the properties that support these applications. An observation is an act associated with a discrete time instant or period through which a number, term or other symbol is assigned to a phenomenon [2]. The result of an observation is an estimate of the value of a property of some feature, so the details of the observation are metadata concerning the value of the feature property. The observation itself is also a feature, since it has properties and identity.

Attributes
Associations To
Associations From
Tagged Values
Constraints
Other Links

Attribute

Public TM_Object
phenomenonTime

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:

sequenceNumber=3

Notes:

The attribute phenomenonTime:TM_Object shall describe the time 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.2) or observation procedure (6.2.2.10) with a real-world feature. NOTE 1 The phenomenon time is the temporal parameter normally used in geospatial analysis of the result. NOTE 2 If the observedProperty of an observation is ‘occurrence time’ then the result should be the same as the phenomenonTime

Public TM_Instant
resultTime

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:

sequenceNumber=4

Notes:

The attribute resultTime:TM_Instant shall describe the time when 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 phenomenonTime. However, there are important cases where they differ. EXAMPLE 1 Where a measurement is made on a specimen in a laboratory, the phenomenonTime is the time the specimen was retrieved from its host, while the resultTime is the time the laboratory procedure was applied. EXAMPLE 2 The resultTime also supports disambiguation of repeat measurements made of the same property of a feature using the same procedure. EXAMPLE 3 Where sensor observation results are post-processed, the resultTime is the post-processing time, while the phenomenonTime is the time of initial interaction with the world. EXAMPLE 4 Simulations may be used to estimate the values for phenomena in the future or past. The phenomenonTime is the time that the result applies to, while the resultTime is the time that the simulation was executed.

Public TM_Period
validTime

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1

sequenceNumber=5

Notes:

If present, the attribute validTime:TM_Period shall describe the time period during which the result is intended to be used. NOTE This attribute is commonly required in forecasting applications.

Public DQ_Element
resultQuality

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:	Range:0 to *

sequenceNumber=10

Notes:

If present, the attributes resultQuality:DQ_Element shall 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).

Public NamedValue
parameter

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:	Range:0 to *

sequenceNumber=7

Notes:

If present, the attributes parameter:NamedValue shall describe 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 identifer, operator, may augment the description of a standard procedure. EXAMPLE A time sequence of observations of water quality in a well may be made at variable depths within the well. While these may be associated with specimens taken from the well at this depth as the features-of-interest, a more common approach is to identify the well itself as the feature-of-interest, and add a “samplingDepth” parameter to the observation (Figure 3). The sampling depth is of secondary interest compared to the temporal variation of water quality at the site.

Element	Source Role	Target Role
«FeatureType» OM_Observation Class	Name:	Name: relatedObservation Some observations depend on other observations to provide context which is important, sometimes essential, in understanding the result. These dependencies are stronger than mere spatio-temporal coincidences, requiring explicit representation. If present, the association class class ObservationContext (Figure 2) shall link a OM_Observation to another OM_Observation, with the role name relatedObservation for the target. It shall support one attribute. EXAMPLES Some examples include the conditions associated with experimental replicates (e.g., experimental plots and treatments used), biotic factors (e.g., ecological community), interactions among features (e.g., predator-prey), or other temporary relationships occurring at the time of observation that are are not inherent to the observed features themselves (i.e., they change over time), or the related observation may provide input to a process that generates a new result. This association complements the Intention association which describes relationships between a sampling feature and domain features.
Details:
«FeatureType» OM_Process Class	Name: generatedObservation Many Observations may be generated by a procedure, except if the Process is instance-specific, where the time of application is bound into the description of the Process.	Name: procedure The association ProcessUsed shall link the OM_Observation to the 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. The OM_Process shall be suitable for the observed property. As a corollary, details of the observed property are constrained by the procedure used. EXAMPLE Observed radiance wavelength is determined by the response characteristics of the sensor. A description of the observation procedure provides or implies an indication of the reliability or quality of the observation result.
Details: The association <i>ProcessUsed</i> shall link the OM_Observation to the OM_Process (6.2.3) used to generate the result. The process has the role <i>procedure</i> with respect to the observation. A process might be responsible for more than one <i>generatedObservation</i>. <br /></p><p>The OM_Process shall be suitable for the observed property. As a corollary, details of the observed property are constrained by the procedure used. <br /></p><p>EXAMPLE Observed radiance wavelength is determined by the response characteristics of the sensor. <br /></p><p>A description of the observation procedure provides or implies an indication of the reliability or quality of the observation result. observation result. <br /></p>
«FeatureType» GFI_Feature Class	Name: propertyValueProvider Pointer to an observation that provides an estimate of a property value	Name: featureOfInterest The association Domain shall link the OM_Observation to the GFI_Feature (B.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 standard. An observation instance serves as a propertyValueProvider for its feature of interest.
Details: The association <i>Domain</i><b> </b>shall link the OM_Observation to the GFI_Feature (B.2.1) that is the subject of the observation and carries the observed property. This feature has the role <i>featureOfInterest</i> 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 standard. An observation instance serves as a <i>propertyValueProvider</i> for its feature of interest.
MD_Metadata Class	Name:	Name: metadata If present, the association Metadata shall link the OM_Observation to descriptive metadata.
Details: If present, the association <i>Metadata</i> shall link the OM_Observation to descriptive metadata.
«MetaClass» GF_PropertyType Class	Name:	Name: observedProperty The association Phenomenon shall link the OM_Observation to the GFI_PropertyType (B.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.
Details: The association <i>Phenomenon</i> shall link the OM_Observation to the GFI_PropertyType (B.2.2) for which the OM_Observation:result (6.2.2.9) provides an estimate of its value. The property type has the role <i>observedProperty</i> with respect to the observation. <br /></p><p>The observed property shall be a phenomenon associated with the type of the featureOfInterest. <br /></p><p>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<br /></p><p>The observed property supports semantic or thematic classification of observations, which is useful for discovery and data fusion.<br /></p>

Element	Source Role	Target Role
«featureType» SoilDerivedObject Class	Name:	Name: soilDerivedObjectObservation -- Name -- soil derived object observation -- Definition -- Observation of a soil property for characterizing the soil derived object.
Details:
«featureType» SoilSite Class	Name:	Name: soilSiteObservation -- Name -- soil site observation -- Definition -- Observation of a soil property for characterizing the soil site.
Details:
«FeatureType» OM_Observation Class	Name:	Name: relatedObservation Some observations depend on other observations to provide context which is important, sometimes essential, in understanding the result. These dependencies are stronger than mere spatio-temporal coincidences, requiring explicit representation. If present, the association class class ObservationContext (Figure 2) shall link a OM_Observation to another OM_Observation, with the role name relatedObservation for the target. It shall support one attribute. EXAMPLES Some examples include the conditions associated with experimental replicates (e.g., experimental plots and treatments used), biotic factors (e.g., ecological community), interactions among features (e.g., predator-prey), or other temporary relationships occurring at the time of observation that are are not inherent to the observed features themselves (i.e., they change over time), or the related observation may provide input to a process that generates a new result. This association complements the Intention association which describes relationships between a sampling feature and domain features.
Details:
«featureType» AbstractMonitoringFeature Class	Name:	Name: hasObservation -- Definition -- Observation of emissions, of the state of environmental media and of other ecosystem parameters (biodiversity, ecological conditions of vegetation, etc.) by or on behalf of public authorities at this AbstractMonitoringFeature.
Details:
«FeatureType» SF_SamplingFeature Class	Name:	Name: relatedObservation Sampling features are distinctive compared with other features from application domains by having navigable associations to observations. If present, the association Design shall link the SF_SamplingFeature to an OM_Observation that was made utilizing the sampling feature, and the description of the sampling feature provides an intrinsic element of the observation protocol, along with the observation procedure (6.2.2.10) and the decomposition of the domain geometry in the case of a coverage-valued result (7.3.1). The OM_Observation has the role relatedObservation with respect to the sampling feature. Multiple observations may be made on a single sampling feature. This association complements the Domain association owned by OM_Observation. The featureOfInterest of a relatedObservation shall be the SF_SamplingFeature (modelled as a UML constraint).
Details: Sampling features are distinctive compared with other features from application domains by having navigable associations<b> </b>to observations. If present, the association <i>Design </i>shall link the SF_SamplingFeature to an OM_Observation that was made utilizing the sampling feature, and the description of the sampling feature provides an intrinsic element of the observation protocol, along with the observation procedure (6.2.2.10) and the decomposition of the domain geometry in the case of a coverage-valued result (7.3.1). The OM_Observation has the role <i>relatedObservation </i>with respect to the sampling feature. Multiple observations may be made on a single sampling feature. <br /></p><p>This association complements the Domain association owned by OM_Observation. The featureOfInterest of a relatedObservation shall be the SF_SamplingFeature (modelled as a UML constraint). relatedObservation shall be the SF_SamplingFeature. <br /></p>
«featureType» ProfileElement Class	Name:	Name: profileElementObservation -- Name -- profile element observation -- Definition -- Observation of a soil property for characterizing the profile element (layer or horizon).
Details:
«featureType» SoilProfile Class	Name:	Name: soilProfileObservation -- Name -- soil profile observation -- Definition -- Observation of a soil property for characterizing the soil profile.
Details:
«Type» Any Class	Name: result The association Range shall link the OM_Observation to the value generated by the procedure.The value has the role result with respect to the observation. The type of the result is shown as Any, since it may represent the value of any feature property. NOTE OGC SWE Common provides a model suitable for describing many kinds of observation results. The type of the observation result shall be consistent with the observed property, and the scale or scope for the value shall be consistent with the quantity or category type. If the observed property (6.2.2.8) is a spatial operation or function, the type of the result may be a coverage, NOTE In some contexts, particularly in earth and environmental sciences, the term “observation” is used to refer to the result itself.	Name:
Details: The association <i>Range</i> shall link the OM_Observation to the value generated by the procedure.The value has the role <i>result </i>with respect to the observation. The type of the result is shown as Any, since it may represent the value of any feature property. <br /></p><p>NOTE OGC SWE Common provides a model suitable for describing many kinds of observation results. <br /></p><p>The type of the observation result shall be consistent with the observed property, and the scale or scope for the value shall be consistent with the quantity or category type. If the observed property (6.2.2.8) is a spatial operation or function, the type of the result may be a coverage, <br /></p><p>NOTE In some contexts, particularly in earth and environmental sciences, the term “observation” is used to refer to the <i>result </i>itself. <br /></p>
«DataType» StratigraphicDateEstimate Class	Name:	Name: observationalBasis Descriptions of the age determination acts which support this date estimate
Details:

Tag	Value
byValuePropertyType	false
Details: Values: true,false Default: false Description: enforce the 'by value' property pattern without xl
byValuePropertyType	false
Details: Values: true \| false Default: false Description: enforce the 'by value' property pattern without xlinks
hasXmlLang	false
Details: Values: true \| false Default: false Description: axml attribute xml:lang shall be generated for the type representing the class
isCollection	false
Details: Values: true,false Default: false Description: attribute group gml:AggregationAttributeGroup is a
isCollection	false
Details: Values: true \| false Default: false Description: attribute group gml:AggregationAttributeGroup is added to the complex type of the feature type
noPropertyType	false
Details: Values: true,false Default: false Description: suppress automatic creation of *PropertyType compl
noPropertyType	false
Details: Values: true \| false Default: false Description: suppress automatic creation of *PropertyType complexType

Constraint	Type	Status
observedProperty shall be a phenomenon associated with the feature of interest	Invariant	Approved
Details:
procedure shall be suitable for observedProperty	Invariant	Approved
Details:
result type shall be suitable for observedProperty	Invariant	Approved
Details:
a parameter.name shall not appear more than once	Invariant	Approved
Details:

Object	Type	Connection	Notes
«FeatureType» OM_TemporalObservation	Class	Generalization
«FeatureType» OM_TruthObservation	Class	Generalization
«FeatureType» OM_CategoryObservation	Class	Generalization
«FeatureType» OM_CountObservation	Class	Generalization
«FeatureType» OM_DiscreteCoverageObservation	Class	Generalization
«FeatureType» OM_Observation	Class	Class
«FeatureType» OM_Measurement	Class	Generalization
«FeatureType» OM_GeometryObservation	Class	Generalization
«FeatureType» OM_ComplexObservation	Class	Generalization
«Type» Any	Class	Strong	The association Range shall link the OM_Observation to the value generated by the procedure.The value has the role result with respect to the observation. The type of the result is shown as Any, since it may represent the value of any feature property. NOTE OGC SWE Common provides a model suitable for describing many kinds of observation results. The type of the observation result shall be consistent with the observed property, and the scale or scope for the value shall be consistent with the quantity or category type. If the observed property (6.2.2.8) is a spatial operation or function, the type of the result may be a coverage, NOTE In some contexts, particularly in earth and environmental sciences, the term “observation” is used to refer to the result itself.
«metaclass» GF_FeatureType	Class	Dependency