Water Levels

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 latitude and longitude (should be the center of reservoir)

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

“LocationId” : 267

"Name": "Avalon Reservoir and Dam"

(focused on “Monitoring” data for catalog records; may also have modeling data for certain locations)

Datastream

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

Time series, Hydrograph

Item

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

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 UCUM Specification or http://qudt.org/)

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

Storage - af

Elevation - ft

inflow/outflow - cfs

Area - acres

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

sensors on the ground

bubbler system

SDR

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)

“Parameter Name”

Inflow

Outflow

Levels

(sediment data, etc. not in RISE)

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 )

Reservoir purposes can vary (recreation, …)

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?)

Inflow

Outflow

Levels

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

Depth (e.g. 337.08)

Inflow (e.g., 5 cfs)

Outflow (e.g., 3 cfs)

Levels (e.g., 19.81 ft)

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

“2021-02-01 07:00:00” (daily data pushed to RISE)

if needed, 15-min, instantaneous data also available through BoR’s hydrological dtb.

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

Elevation and storage are midnight readings

Inflow/Outflow are averaged over the preceding day

The date+time interval during which the Observation can be used (often used for provisional values that are replaced by QA/QC’d observations)

Data is sometimes fixed retroactively if any errors are observed during modeling stage but are not marked with QC flags

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”)

• elevation goes to hundredths

• storage goes to integer

• inflow/outflow goes to integer (nearest cfs)

Column

Description

Agency Cd

Agency Cd

Site No

Site No

Time

24-hr format (HH:MM:SS); assume measurements made in daytime

TimeZone

MDT vs. MST (worth capturing for AZ nuances); store internally as UTC

Date

Date (YYYY-MM-DD)

Depth to Water Below Land Surface in ft

Depth to Water Below Land Surface in ft (2 decimal places)

Measuring point height (relative to land surface)

Measuring point height in ft (relative to land surface)

Accuracy Value

Accuracy Value. Depends on the interpretation made – details need to be captured within metadata.

Water level in feet relative to NAVD88

Water level in feet relative to NAVD88 (transformation done at the central platform)

Observation Method

Observation Method

Level Status

Was the well Pumping? Was there an obstruction? Was the well recovering? etc.

Recommended Standard (NGWMN)

USGS

NMBGMR

ABQ

OSE

Agency Cd

agency_cd

Calculate in crosswalk

Calculate in crosswalk

Calculate in crosswalk

Site No

site_no

PointID, OSEWellID

sys_loc_code, facility_id

 OSE Well #

Time

lev_tm

TimeMeasured

Time

Date

lev_dt

DateMeasured

measurement_date

Date

Depth to Water Below Land Surface in ft

lev_va

DepthToWaterBGS

water_level

Depth to Water (feet below ground surface)

Accuracy Value

lev_acy_cd

Need

Water level in feet relative to NAVD88

Calculate in crosswalk

Calculate in crosswalk

Calculate in crosswalk

Calculate in crosswalk

Observation Method

lev_meth_cd

MeasurementMethod

measurement_method