: Public <<FeatureType>> Class
Created: 10/01/2008 3:19:52 PM
Modified: 12/05/2015 2:08:38 PM
Project:
Advanced:
A large number of direct in-situ hydrological observations are performed by a sensor or sensor system. Common types of sensors include rain gauges, level gauges, quality sensors such as temperature, turbidity etc. <br /></p><p>Manual procedures may be also used to make measurements at a particular sampling point. These may be ad-hoc visits to particular point that may be of interest, or continued visits to a well identified sampling point. <br /></p><p>Procedures that generate derived or synthetic results also exist, such as those produced by algorithms or simulations. Algorithms are commonly implemented in hydrological software to process data sets for reporting or other purposes. Examples include:<br /></p><p>- Temporal interpolation or aggregation;<br /></p><p>- Spatial interpolation;<br /></p><p>- Quality assurance related tasks such as automatic spike removal or gap filling;<br /></p><p>- Derivation of new observed phenomena such as calculation of volume from stage, discharge (flow) from stage etc.<br /></p>
Attribute
Public TM_PeriodDuration
  aggregationDuration
Details:
sequenceNumber=3
Notes: If the process involves temporal aggregation of a result set, the time duration over which data has been aggregated should be expressed here. E.g. hourly, daily aggregates.
Public CD_VerticalDatum
  verticalDatum
Details:
sequenceNumber=10
Notes: Specifies the datum that is used as the zero point for height-related measurements.
Public GenericName
  input
Details:
sequenceNumber=40
Notes: A list of the inputs used in the process. This may be a list of references to the data sets used (e.g. model input series) or a input array to an algorithm.
Public CharacterString
  comment
Details:
sequenceNumber=15
Notes: Comments specific to the process from the operator.
Public NamedValue
  parameter
Details:
sequenceNumber=60
Notes: A defintion of the type of process used in the observation. This may be a Sensor, ManualMethod, Algorithm or Simulation (including models).
Public GenericName
  processReference
Details:
sequenceNumber=19
Notes: Reference to an external process definition.
Public ProcessTypeCode
  processType
Details:
sequenceNumber=1
Notes: A defintion of the type of process used in the observation. This may be a Sensor, ManualMethod, Algorithm or Simulation (including models).
Element Source Role Target Role
«FeatureType» OM_Process
Class  
Name:  
 
Name: originatingProcess
Used to identify a process that is a source to this process. For example an earlier processing step.
Details:
 
«datatype» CI_ResponsibleParty
Class  
Name:  
 
Name: operator
Describes the party responsible for performing the process. E.g. the person performing the method or operating the sensor.
Details:
 
Element Source Role Target Role
«FeatureType» TimeseriesObservation
Class  
Name: generatedObservation
In this context, any generatedObservation shall be a TimeseriesObservation
Name: procedure
The procedure shall be an ObservationProcess or a process derived from SensorML AbstractProcess
Details:
 
Tag Value
byValuePropertyType false
Details:
Values: true,false
Default: false
Description: enforce the 'by value' property pattern without xl
isCollection false
Details:
Values: true,false
Default: false
Description: attribute group gml:AggregationAttributeGroup is a
noPropertyType false
Details:
Values: true,false
Default: false
Description: suppress automatic creation of *PropertyType compl
Object Type Connection Direction Notes
OM_Process Class Generalization To  
«FeatureType» ObservationProcess Class Realization From