SensorThings Entity | Description | Water Use Data for NM Example: CKAN Dataset |
---|
...
Notes from Emily:
I think it would be very useful to have a meeting to discuss this (could be at the Data Lead meetings next week). There are several conversations happening which is great, but it would be good to be in communication with each other and get organized. Then we can figure out how Julie can help and who should be in the meeting with Julie.
We created a process for the Use Case. I think we're exploring if this is Use Case we want to implement now. If it is, then I think we should follow the process, which starts by identifying the team and having a meeting. Are we almost there?? I think so.
Julie would absolutely be the best person to explain the limitations of the data and the query results.
...
Metadata | Location | A unique coordinate or area on the surface of the earth | CN=county code; COUNTY RVB=river basin; GWB=ground water basin (also have state-level values) Are lat/lon captured within data? or require merging with another dataset? |
Thing | Some real-world entity with which one or more Sensors are associated | (Analogous to Location?) | |
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) | 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/) | ac-ft; gallons; % | |
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) | Data Synthesis Some data collected from WATERS/meters; are efficiency/acreage values provided within WATERS? Additional details about how data is collected? | |
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/) | GPCD=gallons per capita per day; WSW=withdrawal, surface water; (ac-ft) WGW=withdrawal, ground water; (ac-ft) TW = withdrawal, total (ac-ft) MSW= percent of surface water withdrawals measured; MGW=percent of groundwater withdrawals measured; MTW=percent of total withdrawals that were measured TFSW=total farm withdrawal, surface water CLSW=surface water conveyance losses from stream or reservoir to farm headgate TPWSW=total project withdrawals, ssurface water TPWGW=total project withdrawals, ground water. | |
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. | Population (number of people or %) For Livestock: User (e.g., Cattle, Chickens, etc.) For Reservoir: CAPACITY=total storage capacity (acre-feet); SAS=surface area at spillway elevation; SAA=surface area, average; EGR=gross evaporation rate in feet/year; R=rainfall in feet/year; ENR=net evaporation rate in feet/year For Power: User (e.g., PNM, Xcel, …), Power Generated (units? kWh?) For Domestic: WEC = water exchange code For Tables: Category (PWS, Domestic, …) For Table 7: WWC = water withdrawal code; WEC = water exchange code For Table 8: T=type of irrigation system, i.e., drip (D), flood (F), or sprinkler (S); ASWO=acreage irrigated with surface water only; AGWO=acreage irrigated with ground water only; ASWC=surface water component of acreage irrigated with combined water, i.e., both surface and ground water; AGWC=ground water component of acreage irrigated with combined water; TAI=total acreage irrigated; For Table 12: T=type of irrigation system, i.e., drip (D), flood (F), or sprinkler (S); CIRSW=consumptive irrigation requirement for acreage irrigated with surface water (units: ac-ft?); CIRGW=consumptive irrigation requirement for acreage irrigated with ground water (units: ac-ft?); ASWO=acreage irrigated with surface water only; AGWO=acreage irrigated with ground water only; ASWC=surface water component of acreage irrigated with combined water, i.e., both surface and ground water; AGWC=ground water component of acreage irrigated with combined water; TAI=total acreage irrigated; EF=on-farm irrigation efficiency (units: fraction/dim-less?); EC=off-farm conveyance efficiency (units: fraction/dim-less?); Ep=project efficiency (units: fraction/dim-less?); | |
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 | Volume or Rate (For Table 1, Pop is the observation - how to best reconcile info within different tables, or do we have a separate data feed for each table?) (For Tables 9-11 - acreage is the observation…would we include this as a sep stream or more as metadata?) |
Observation/result | The actual measured value, with valid values defined in observationType and units defined in unitsOfMeasurement, both provided by Datastream | GPCD (10) Pop (1,916) WSW (4.29) WGW (17.17) TW (284,157) MSW (93.24%) MGW (82.97%) MTW (85.38%) TFSW (9395) CLSW (5632) TPWSW (15027) TPWGW (67684) | |
Observation/phenomenonTime | The date+time (or interval) in ISO 8601 format (YYYY-MM-DDT:HH:MM:SS-Z) when the observation occured | 2015 | |
OPTIONAL: Observation/resultTime | The date+time that the result was generated. May be the same as phenomenonTime | How many years after 2015 was the report generated? 2018? | |
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) | 2010-2015 - reflecting the 5 years prior? As of end of 2015 - inclusive? | |
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. | Diversion and meter data requires QAQC to remove duplicates and irrelevant entries Some entries (e.g., Table 12) contains N/A=not applicable, no acreage was reported; - - =due to report format efficiency not provided. |
Resources:
Notes from meeting with Julie:
View file | ||
---|---|---|
|
CKAN Dataset: https://newmexicowaterdata.org/dataset/water-use
Opportunities for data improvements (based on disc with J. Valdez):
One of the biggest issues is that names of the PWS in WATERs and SDWIS are not the same . Using - using the same names in both databases for all of the water systems would be a huge improvement.
the process of getting the meter readings is multilayered and can be difficult
Julie asks the Waters Bureau to run a query for all of the diversion data for the year but only needs the public water suppliers meter readings
the reason for the broad ask is bc the PWS records are not consistently all labeled as PWS. Some have other labels and she would miss them if the query were just for PWS.
the query results show each diversion within 1 PWS separately. Julie needs to add all of the diversions together for a total of diversions for the PWS.
there are duplicates in the query results. She needs to remove the duplicates.
there are other sector meter readings (e.g. ag diversions) that she needs to remove
she needs to QAQC some meter readings
Previous Meeting Notes from meeting with Julie:
View file | ||
---|---|---|
|
Example data table of water data available containing potentially sensitive info is also available (see email)
...
basin
...
Basin
...
Ground Water Basin
...
nbr
...
number
...
Permit Number
...
suffix
...
suffix
...
...
sub_basin
...
Sub basin
...
Further identifies the basin that well is located (Example well located in the Rio Grande Basin located in the Middle Rio Grande area)
...
sum_rec_nbr
...
Sum record number
...
...
pod_basin
...
pod basin
...
Basin of POD Diversion
...
pod_nbr
...
pod number
...
POD is sometimes has a different number. I don't know why. This is a water rights question.
...
pod_suffix
...
pod suffix
...
If more than on well is assigned to a permit this identifies which well it is
...
pod_rec_nbr
...
pod record number
...
...
own_lname
...
owner last name
...
...
own_fname
...
owner first name
...
...
use
...
Use
...
Use permit was issued for (example Ag, Commercial, Subdivision, etc)
...
tws
...
township
...
PLSS location data of well
...
rng
...
range
...
PLSS location data of well
...
sec
...
section
...
PLSS location data of well
...
qtr_4th
...
quarter
...
PLSS location data of well
...
qtr_16th
...
quarter
...
PLSS location data of well
...
qtr_64th
...
quarter
...
PLSS location data of well
...
utm_zone
...
UTM Zone
...
PLSS location data of well
...
easting
...
Easting
...
X Y coordinates
...
northing
...
Northing
...
X Y coordinates
...
mtr_rec_nbr
...
Meter Record number
...
acct_year
...
Accounting year
...
ytd_mtr_amt
...
Year to date meter amount
...
own_end_date
...
Owner end date
...
Water use includes measurements of volumes (are they all (ac-ft/year)?
...