-- Definition -- Chronological list of surveys undertaken to better define the potential of a mineral occurrence

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\EarthResourceML\EarthResource\MineralOccurrence

WaterML2.0 defines a generic collection feature type, Collection, to allow the grouping of observations and/or sampling features with metadata to describe the nature of the collection. Such collections are required in a number of data exchange scenarios; whether the underlying transport technology is web services, FTP or other technologies.

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Collection

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Timeseries Observation

A WaterMonitoringObservation is defined as a specialisation of the O&M OM_TimeSeriesObservation class as shown in Figure 4. This specialisation allows for more specific use of O&M to be defined according to the commonalities of in-situ hydrological observations. The following requirements are defined for this specialisation of OM_Observation: Req 1 A WaterMonitoringObservation shall have a result of type Timeseries, as defined in section 10 of this standard. Req 2 A WaterMonitoringObservation shall have a featureOfInterest of type SF_SpatialSamplingFeature, as defined by ISO19156, which includes WaterSamplingPoint defined in section 8.3 of this standard. Req 3 A WaterMonitoringObservation shall have a procedure property of type WaterObservationProcess, as defined in section 8.11 of this standard. Req 4 A WaterMonitoringObservation shall have a metadata property of type ObservationMetadata, as defined in section 8.2.8 of this standard. Req 5 A WaterMonitoringObservation shall have an observedProperty of type GFI_PropertyType, as described in ISO19156.

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Timeseries Observation

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Timeseries Observation

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Categorical Timeseries (Domain Range) Observation

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Measurement Timeseries (Domain Range) Observation

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Categorical Timeseries (TVP) Observation

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Measurement Timeseries (TVP) Observation

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Timeseries (Domain Range)

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Timeseries (Domain Range)

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Categorical (Domain Range) Timeseries

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Interleaved (TVP) Timeseries

A (point) location where water flow or properties are reported, such as a stream gauge, rainfall gauge, or water quality monitoring site. The primary specialization from the generic SamplingPoint is that the domain of the relatedObservation property is a WaterMonitoringObservation

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Monitoring Point

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. 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. 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: - Temporal interpolation or aggregation; - Spatial interpolation; - Quality assurance related tasks such as automatic spike removal or gap filling; - Derivation of new observed phenomena such as calculation of volume from stage, discharge (flow) from stage etc.

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\OGC\WaterML2.0\Procedures

A MappedFeature is part of a geological interpretation. It provides a link between a notional feature (description package) and one spatial representation of it, or part of it. (Exposures, Surface Traces and Intercepts, etc) * the specific bounded occurrence, such as an outcrop or map polygon * the Mapped Feature carries a geometry or shape - the association with a Geologic Feature (legend item) provides specification of all the other descriptors - the association with a Sampling Feature provides the context and dimensionality A Mapped Feature is always associated with some sampling feature - e.g. a mapping surface, a section, a Borehole (see BoreHolesAndObservation) etc. As noted on the diagram, if the associated sampling feature is a Borehole, then the shape associated with the MappedFeature will usually be either a point or an interval. This reconciles the 2-D ("map", section) and 1-D (borehole, traverse) viewpoints in a common abstraction.

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\GeoSciML\GeoSciML-Core\GeologicFeature

The abstract GeologicFeature class represents a conceptual feature that is hypothesized to exist coherently in the world. * this corresponds with a "legend item" from a traditional geologic map * while the bounding coordinates of a Geologic Feature may be described, its shape is not. The implemented Geologic Feature instance acts as the "description package" * the description package is classified according to its purpose as an Instance, TypicalNorm, or DefiningNorm.

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\GeoSciML\GeoSciML-Core\GeologicFeature

The GeologicFeatureRelation class is a concrete subtype of the abstract GeologicRelation class that is used to define relationships between geologic features, ie. structure-structure, unit-unit, and structure-unit relationships. Relationships are always binary and directional. There is always a single source and a single target. The relationship is always defined from the perspective of the Source and is generally an active verb. Example: a Source may point to an intrusive igneous rock body. In this case, the Target would point to the appropriate host rock body and the relationship attribute would be 'intrudes'. Other appropriate relationship attributes might include: overlies, offsets, crosscuts, folds, etc. Two or more GeologicFeatures are associated in a GeologicFeatureRelation; each has a role in the relationship. Examples of geological roles include "overlies", "is overlain by", "is younger", "is older", "intrudes", "is intruded by", and so forth. In a relationship where an igneous unit intrudes a sedimentary unit, the geological relationship is "intrudes", the intruded sedimentary unit has the role "host", and the igneous unit has the role "intrusion".

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\GeoSciML\GeoSciML-Core\GeologicFeature

Operationally, the GeologicUnit element is a container used to associate geologic properties with some mapped occurrence (through GeologicFeature.occurrence -> MappedFeature link), or with a geologic unit ControlledConcept in a vocabulary (through the GeologicUnit.classifier ->ControlledConcept link). Conceptually, may represent a body of material in the Earth whose complete and precise extent is inferred to exist (NADM GeologicUnit, Stratigraphic unit in sense of NACSN or Intnl Stratigraphic Code), or a classifier used to characterize parts of the Earth (e.g. lithologic map unit like 'granitic rock' or 'alluvial deposit', surficial units like 'till' or 'old alluvium'). Spatial properties are only available through association with a MappedFeature. Includes both formal units (i.e. formally adopted and named in the official lexicon) and informal units (i.e. named but not promoted to the lexicon) and unnamed units (i.e. recognisable and described and delineable in the field but not otherwise formalised). Will be made Abstract when a complete (enough) set of specialized subtypes is defined.

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\GeoSciML\GeoSciML-Core\GeologicUnit

An identifiable event during which one or more geological processes act to modify geological entities. A GeologicEvent must have a specified GeologicAge and may have specified environments and processes. An example might be a cratonic uplift event during which erosion, sedimentation, and volcanism all take place. Geological history is an ordered aggregation of Geological Event objects, each of which may have an associated Geological Age, Geological Environment, and one or more Geological Process objects. Genesis typically pertains to some geological phenomenon (Geological Structure, Earth Material, Geological Unit, Fossil, etc.) In GeoSciML 2.0 this ordering cannot be specified. A GeologicEvent must have a specified eventAge (numericAgeDate, olderNamedAge, or youngerNamedAge), at least one eventProcess, and may have specified eventEnvironments. An example might be a cratonic uplift event during which erosion, sedimentation, and volcanism all take place. Traditionally, geologists have described the age of a feature without explicitly specifying the event or processes the age related to. The GeologicEvent package allows for explicitly linking the three, without mandating it. The eventAge attribute is the age of a particular geological event or feature expressed in terms of years before present (absolute age), referred to the geological time scale, or by comparison with other geological events or features (relative age). An eventAge can represent an instant in time, an interval of time, or any combination of multiple instants or intervals. Specifications of age in years before present are based on determination of time durations based on interpretation of isotopic analyses of EarthMaterial (some other methods are used for geologically young materials). Ages referred to geological time scales are essentially based on correlation of a geological unit with a standard chronostratigraphic unit that serves as a reference. Relative ages are based on relationships between geological units such as superposition, intruded by, cross-cuts, or "contains inclusions of".

Spesifikasjon:
Inspire Consolidated UML Model\Foundation Schemas\GeoSciML\GeoSciML-Core\GeologicAge