Interface Observation

    • Method Detail

      • getName

        Identifier getName()
        The name of the observation as an urn.
      • getDefinition

        String getDefinition()
        A description of the observation.
      • getProcedureParameter

        @UML(identifier="parameter",
             obligation=OPTIONAL,
             specification=OGC_07022)
        Object getProcedureParameter()
        An Observation parameter is a general event-specific parameter. This will typically be used to record environmental parameters, or event-specific sampling parameters that are not tightly bound to either the feature-of-interest or the procedure. NOTE: Parameters that are tightly bound to the procedure should be recorded as part of the procedure description. For example, the SensorML model associates parameters with specific process elements or stages. NOTE: The semantics of the parameter must be provided as part of its value. In some applications it is convenient to use a generic or standard procedure, or feature-of-interest, rather than define an event-specific process or feature. In this context, event-specific parameters are bound to the Observation act.
      • getFeatureOfInterest

        @UML(identifier="featureOfInterest",
             obligation=MANDATORY,
             specification=OGC_07022)
        AnyFeature getFeatureOfInterest()
        The featureOfInterest is a feature of any type (ISO 19109, ISO 19101), which is a representation of the observation target, being the real-world object regarding which the observation is made. such as a specimen, station, tract, mountain, pixel, etc. The spatial properties (location) of this feature of interest are typically of most interest for spatial analysis of the observation result.
      • getObservedProperty

        @UML(identifier="observedProperty",
             obligation=MANDATORY,
             specification=OGC_07022)
        Phenomenon getObservedProperty()
        Property-type or phenomenon for which the observation result provides an estimate of its value. for example "wavelength", "grass-species", "power", "intensity in the waveband x-y", etc. It must be a property associated with the type of the feature of interest. This feature-property that provides the (semantic) type of the observation. The description of the phenomenon may be quite specific and constrained. The description of the property-type may be presented using various alternative encodings. If shown inline, the swe:Phenomenon schema is required. If provided using another encoding (e.g. OWL or SWEET) then the description must be in a remote repository and xlink reference used.
      • getResult

        @UML(identifier="result",
             obligation=MANDATORY,
             specification=OGC_07022)
        Object getResult()
        The result contains the value generated by the procedure. The type of the observation result must be consistent with the observed property, and the scale or scope for the value must be consistent with the quantity or category type. Application profiles may choose to constrain the type of the result. an xsi:type attribute may appear in the instance to indicate the type of the result
      • getProcedure

        @UML(identifier="procedure",
             obligation=MANDATORY,
             specification=OGC_07022)
        Process getProcedure()
        The procedure is the description of a process used to generate the result. It must be suitable for the observed property. NOTE: At this level we do not distinguish between sensor-observations, estimations made by an observer, or algorithms, simulations, computations and complex processing chains.