Matches in LOV for { ?s ?p ?o. }
- observedProperty isDefinedBy observation.
- observedProperty label "observed property".
- observedProperty definition "The association Phenomenon shall link the OM_Observation to the GF_PropertyType for which the OM_Observation:result (7.2.2.9) provides an estimate of its value. The property type has the role observedProperty with respect to the observation.\n\nThe observed property shall be a phenomenon associated with the feature-of-interest.\n\nAn observed property may be, 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.\n\nAn instance of GF_PropertyType shall describe a property that is either assignable or observable (7.1.2), such as “temperature”, “height”, “colour”, “material”. A property type may be an operation or function such as a spatiotemporal coverage. Property-type definitions may be organized into a hierarchy or ontology and managed in a register and catalogued to support discovery functions. The observed property supports semantic or thematic classification of observations, which is useful for discovery and data fusion.\n\nNOTE In general, the value of a specific observedProperty can be associated with different feature types in different observations, thus allowing the results of observations made in different projects or campaigns, and even from different disciplines, to be combined when required. A property-type register used in observations is most useful if each property type is not tied to a single feature type, or if equivalence relationships between similar property types from different feature types are provided.".
- parameter type ObjectProperty.
- parameter comment "observation-specific parameter not accommodated by the standard observation properties. Often used to record environmental parameters".
- parameter domain AnyFeature.
- parameter isDefinedBy observation.
- parameter label "parameter".
- parameter range NamedValue.
- parameter definition "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 (7.2.2.7) or to the observation procedure (7.2.2.10). To avoid ambiguity, there shall be no more than one parameter with the same name.\n\nNOTE Parameters that are tightly bound to the procedure can be recorded as part of the procedure description.\n\nIn some contexts, the Observation::procedure (7.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.\n\nEXAMPLE A time sequence of observations of water quality in a well might be made at variable depths within the well. While these can 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\nobservation (Figure 3). The sampling depth is of secondary interest compared to the temporal variation of water quality at the site.".
- phenomenonTime type ObjectProperty.
- phenomenonTime comment "time at which the estimate of the property that is the result of the observation is associated with the feature of interest".
- phenomenonTime domain AnyFeature.
- phenomenonTime isDefinedBy observation.
- phenomenonTime label "phenomenon time".
- phenomenonTime range Object.
- phenomenonTime definition "The attribute phenomenonTime:TM_Object shall describe the time that the result (7.2.2.9) applies to the property of the feature-of-interest (7.2.2.7). This is often the time of interaction by a sampling procedure (9.1.3) or observation procedure (7.2.2.10) with a real-world feature.\n\nNOTE The phenomenonTime is the temporal parameter normally used in geospatial analysis of the result.\n\nIf the observedProperty of an observation is ‘occurrence time’ then the result should be the same as the phenomenonTime.".
- procedure type ObjectProperty.
- procedure comment "procedure used in making observation. Typically a sensor or sensor-system, algorithm, computational procedure.".
- procedure domain AnyFeature.
- procedure isDefinedBy observation.
- procedure label "observation procedure".
- procedure range Process.
- procedure definition "The association ProcessUsed shall link the OM_Observation to the OM_Process (7.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.\n\nThe OM_Process shall be suitable for the observed property. As a corollary, details of the observed property are constrained by the procedure used.\n\nEXAMPLE Observed radiance wavelength is determined by the response characteristics of the sensor.\n\nA description of the observation procedure provides or implies an indication of the reliability or quality of the observation result.".
- relatedObservation type ObjectProperty.
- relatedObservation comment "related observation".
- relatedObservation domain Thing.
- relatedObservation isDefinedBy observation.
- relatedObservation label "related observation".
- relatedObservation range Observation.
- result type Property.
- result comment "estimate of the value of the observed property".
- result domain AnyFeature.
- result isDefinedBy observation.
- result label "observation result".
- result definition "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.\n\nNOTE 1 OGC SWE Common [20] provides a model suitable for describing many kinds of observation results.\n\nThe 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 (7.2.2.8) is a spatial operation or function, the type of the result may be a coverage.\n\nNOTE 2 In some contexts, particularly in earth and environmental sciences, the term “observation” is used to refer to the result itself.".
- resultQuality type ObjectProperty.
- resultQuality comment "assessment of the quality of the observation result. The value should be specific to this observation instance, in addition to any quality that is inferred from the observation procedure used".
- resultQuality domain AnyFeature.
- resultQuality isDefinedBy observation.
- resultQuality label "result quality".
- resultQuality range Element.
- resultQuality definition "the attributes resultQuality:DQ_Element shall describe the quality of the result (7.2.2.9). This instance-specific description complements the description of the observation procedure (7.2.2.10), which provides information concerning the quality of all observations using this procedure. The quality of a result may be assessed following the procedures in ISO 19157. Multiple measures may be provided.".
- resultTime type ObjectProperty.
- resultTime comment "time at which the result became available, after all processing steps were completed".
- resultTime domain AnyFeature.
- resultTime isDefinedBy observation.
- resultTime label "result time".
- resultTime range Instant.
- resultTime definition "The attribute resultTime:TM_Instant shall describe the time when the result became available, typically when the procedure (7.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.\n\nEXAMPLE 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.\n\nEXAMPLE 2 The resultTime also supports disambiguation of repeat measurements made of the same property of a feature using the same procedure.\n\nEXAMPLE 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.\n\nEXAMPLE 4 Simulations can 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.".
- role type ObjectProperty.
- role comment "role of related observation with respect to the observation of interest".
- role domain ObservationContext.
- role isDefinedBy observation.
- role label "role".
- validTime type ObjectProperty.
- validTime comment "time during which the observation result is recommended for use. Most often used in relation to forecasts, but may be used any time the observation procedure (including inputs) is liable to modification. ".
- validTime domain AnyFeature.
- validTime isDefinedBy observation.
- validTime label "valid time".
- validTime range Period.
- validTime definition "the attribute validTime:TM_Period shall describe the time period during which the result is intended to be used.\n\nNOTE This attribute is commonly required in forecasting applications.".
- value type Property.
- value comment "value of named value".
- value domain NamedValue.
- value isDefinedBy observation.
- value label "named value value".
- sampling creator "Simon Jonathan David COX\nCSIRO".
- sampling description "An OWL representation of the Sampling Features Schema described in clauses 8-10 of ISO 19156:2011 Geographic Information - Observations and Measurements".
- sampling source "ISO 19156:2011".
- sampling title "OWL representation of ISO 19156 Sampling Features model".
- sampling created "2012-01-19T00:00:00".
- sampling creator 102311753698482536245.
- sampling description "An OWL representation of the Sampling Features Schema described in clauses 8-10 of ISO 19156:2011 Geographic Information - Observations and Measurements.".
- sampling hasPart Location.
- sampling hasPart NotSamplingFeature.
- sampling hasPart PreparationStep.
- sampling hasPart Process.
- sampling hasPart SamplingCurve.
- sampling hasPart SamplingFeature.
- sampling hasPart SamplingFeatureCollection.
- sampling hasPart SamplingFeatureComplex.
- sampling hasPart SamplingPoint.
- sampling hasPart SamplingSolid.
- sampling hasPart SamplingSurface.
- sampling hasPart SpatialSamplingFeature.
- sampling hasPart Specimen.
- sampling hasPart currentLocation.
- sampling hasPart hostedProcedure.
- sampling hasPart lineage.
- sampling hasPart materialClass.
- sampling hasPart member.
- sampling hasPart parameter.
- sampling hasPart positionalAccuracy.
- sampling hasPart preparationStep.
- sampling hasPart processOperator.
- sampling hasPart processingDetails.
- sampling hasPart relatedObservation.
- sampling hasPart relatedSamplingFeature.
- sampling hasPart role.