Table of Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
...
The STA data model is based on the Observations and Measurements data model of the OGC, which itself underlies many environmental science data systems that integrate data from many independent organizations. Examples include the CUAHSI HydroClient that provides centralized access to global streamgage, monitoring well, and meteorlogical meteorological networks; and the National Groundwater Monitoring Network that provides centralized access to standardized high-frequency groundwater level and quality data from federal, state, and local agencies. The STA data model provides a unifying metadata standard and data structure standard that can model any data generated about point or polygonal locations on earth. It is important to be bale to map agency data to this data model in order to structure each agency’s data in a compatible format and to provide a seamless data request experience to users. The STA data model shown in Figure 2 below, and full specified in this OGC Specification.
...
SensorThings Entity | Description | Example: NMBGMR Aquifer Monitoring Well | NMED Drinking Water Quality Monitoring | NMOSE Water Withdrawal Monitoring | ||
|---|---|---|---|---|---|---|
Metadata | Location | A unique coordinate or area on the surface of the earth | Location in latitude and longitude | Street Address (with associated latitude and longitude) | Location in easting and northing | |
Thing | Some real-world thing with which one or more Sensors are associated | Well | Sampling Point | |||
Datastream | A collection of Observations about an ObservedProperty produced by a Sensor associated with a Thing | Time series, Hydrograph | ||||
Datastream/observationType | The type of observation, codified in the Observations and Measurements data standard. Types include Categorical (defined text), Count (integer), Measurement (continuous number), Observation (free text), and TruthObservation (True/False) | continuous number (Measurement) | ||||
Datastream/unitOfMeasurement | A three-item definition of the unit of measurement, including its name, symbol, and link to the definition. | meters | ||||
Sensor | The procedure used to provide a Datastream. Can be a particular data recording device model, or a defined procedure followed by a human observer. | Diver, Wellintel, Steel tape | ||||
ObservedProperty | The raw or processed phenomenon (quantitative or qualitative) being measured for the Datastream. | Water Pressure Head, DepthBelowSurface | ||||
OPTIONAL: FeatureOfInterest | The real-world feature that the Observations are about. This may be different from the Thing on which the Sensor is mounted. Can be a point location or a polygon or collections thereof. | Aquifer (polygon) | Public Water System (head office location or service area boundary) | Water Right (set of relevant points of diversion) | ||
Data | Observation | A single measurement value including the result, time values, and other metadata. Information on the ObservedProperty that was measured by what Sensor is provided by the Datastream these observations are in. Features of Interest are linked for each observation as well. Observations are linked to (collected in) Datastreams | Depth measurement | |||
Observation/result | The actual measured value, with valid values defined in observationType and units defined in unitsOfMeasurement, both provided by Datastream | 3252 | ||||
Observation/phenomenonTime | The date+time (or interval) in ISO 8601 format (YYYY-MM-DDT:HH:MM:SS-Z) when the observation occured | |||||
OPTIONAL: Observation/resultTime | The date+time that the result was generated | |||||
OPTIONAL: Observation/validTime | The date+time interval during which the Observation can be used (often used for provisional values that are replaced by QA/QC’d observations) |
...