Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Sub-pages contain specific crosswalks when multiple agencies collect similar data. Datasets in this category include:

  • groundwater levels (Feet, below ground surface)

  • produced water generation/injections

  • streamflow (CFS) instantaneous

    • USGS: prior to 2007, used daily values. Nowadays, it’s at 15-minute intervals

  • lake/reservoir levels (Feet),

  • Reservoir volume (acre-feet) accompanied by area-capacity table

  • Soil moisture (volumetric water content)

  • Precipitation (inches)

  • evapotranspiration (percent of precipitation)

Table 1: The STA data model definitions and example mappings to NM agency datasets

SensorThings Entity

Description

Groundwater Levels

Example: NMBGMR Groundwater Level Well

Diversion Volumes

Example: NMOSE Water - Points of Diversion

Instantaneous streamflow measurements

Example: USGS Gage Data and OSE Real-Time Measurement Data

Lake/Reservoir Levels

Example:

Produced water generation/injections

Example: XX

Metadata

Location

A unique coordinate or area on the surface of the earth

Location in latitude and longitude or UTM easting and Northing (UTM Zone 13, NAD83)

Location in easting and northing (UTM NAD83 in meters)

Location in latitude and longitude (USGS - publicly also represented as deg-min-sec)

OSE data is in UTM Zone 13, NAD83

(OSE location data is within GIS dataset, need to link to IDs below - not publicly displayed due to security concerns - vandalism)

Thing

Some real-world entity with which one or more Sensors are associated

Well Point ID WL-0150

(Thing/Property - Well Use (e.g., pumping well))

(Thing/Property - Well Status (permitted, active, capped, plugged, etc.))could see another use case focused on Well Status as the observed property

Point of Diversion POD Number A 00008 AS

USGS 08324000

OSE website has string IDs: “Citizens/BID” - associated numerical unique identifiers are available on the back end

Datastream

A collection of Observations about an ObservedProperty produced by a Sensor associated with a Thing

Time series, Hydrograph

Meter Readings (Quarterly)

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)

Measurement

Measurement

Measurement

Datastream/unitOfMeasurement

A three-item definition of the unit of measurement, including its name, symbol, and link to the definition (preferably to one provided in an established ontology such as http://unitsofmeasure.org/ucum.html or http://qudt.org/)

feet (e.g. http://qudt.org/vocab/unit/FT)

Acre-Feet (e.g. http://qudt.org/vocab/unit/AC-FT)

cfs (cubic feet/sec) - discharge

feet - gage height

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. If applicable, a specific instance (e.g. a sensor model and serial number)

Steel-tape measurement; Continuous acoustic sounder; e-probe; pressure transducer; airline

MCCROMETER Diversion Meter-Meter Number 17147

continuous: pressure transducer; shaft encoders; radar; bubbler;

(radios/satellites for communication of data from field to HQ at OSE)

manual/field measurements - might be taken at a continuous site or different type of study

ObservedProperty

The raw or processed phenomenon (quantitative or qualitative) being measured for the Datastream. Preferably including a link to a definition provided by an established ontology or controlled vocabulary such as the ODM2 Controlled Vocabularies or http://qudt.org/)

Depth to Water Below Ground Surface (BGS)

Mtr Amount

Discharge

Gage Height (“staff plates” might be field checks)

OPTIONAL: FeatureOfInterest

The real-world feature that the Observations are about. This may or many not be different from the Location where the Thing on which the Sensor is mounted. Can include a JSON-formatted point location or a polygon or collections thereof.

Formation (e.g. https://maps.nmt.edu/maps/data/hydrograph/formation_lu)

Water Right (set of relevant points of diversion)

Purpose/decisions that are informed by streamflow measurements (e.g., apportionment to water users)

River/Acequia name associated with measurement location

(verify with Brian G. about different categories)

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/Parameter - Missing value code (e.g., if well is dry))

(observation/Parameter - Is well recovering?)

Meter Reading

Flow Measurement

Observation/result

The actual measured value, with valid values defined in observationType and units defined in unitsOfMeasurement, both provided by Datastream

Depth (e.g. 337.08)

Mtr Amount (e.g. 107.948)

Discharge (e.g., 17.9)

Gage Height (e.g., 2.38)

(value read is sometimes transformed prior to display, e.g., pressures to height)

Observation/phenomenonTime

The date+time (or interval) in ISO 8601 format (YYYY-MM-DDT:HH:MM:SS-Z) when the observation occured

2019-01-31 00:00:00

1/20/2017-04/05/2017 (Quarterly period for which volume was measured)

2020-02-09 18:15 (15-minute intervals)

(discrete measurement at the end of the 15-minute interval)

OPTIONAL: Observation/resultTime

The date+time that the result was generated. May be the same as phenomenonTime

04/05/2017 (date of meter reading)

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)

OPTIONAL: Observation/resultQuality

A description of the result Quality. Will vary according to agency practice. Can use ODM2 controlled vocabulary for data quality types as a guide.

Precision (e.g. “within two hundredths of a foot”)

Precision (e.g., 1/10 for discharge and 1/100 for gage height)

Tagged Provisional vs. Approved for data. Pre-data quality check for USGS = Provisional (usually turned around within a target of 150 days).

verify with Brian G. re: (data quality) flags for OSE.

  • No labels