Water Use By Categories Report Source Data
Purpose
The purpose of this document is to identify and detail the source data that is used in compiling the Water Use By Categories report as well as document the manner in which they are aggregated to form the final report.
Report Sources
The following subsections describe report sources that collectively compose the report and the relevant data elements captured.
OSE / Waters DB
Julie initially requests a report from Waters DB admin that specifies all public water systems as identified by their Use Code
. The use codes that are used as filter constraints (as reported by Julie) to indicate a Public Water System are as follows:
MDWCA (community type)
MOB (mobile home park)
MUN (municipal)
SAN (sanitary use)
SUB (subdivision)
UTL (public utility)
PMH (well permitted for multiple households)
Report Output Data Elements
Data Element | Short Decription | Long Description |
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 |
|
NMED / SDWIS
After Julie receives an initial spreadsheet from OSE/WatersDB, she requests a report of all PWS from NMED/SDWIS system. NMED requires all PWS to report their water quality data approximately every three years. This is an opporunity to collect water meter data from PWS that may not be present or current in OSE/Waters DB. In cases where meter data exists in both, a judgement call is made as to which values to include in final report.
Correlation between OSE/WatersDB and NMED/SDWIS records is done through matching
System Name
(as labeled in the NMED/SDWIS report) and Owner Last Name (labels own_lname) in OSE/Waters DB.estimated that 30-40% strict comparison matches do not match.
My own exact match between the two fields yields only 68 matches
Fields of interest in NMED/SDWIS report are:
System Name
Facility Name
Water Type
Active/inactive
Use - helpful in deciding whether to include on master list (or not)
Population
Use - to verify how many systems
City
Use - to verify Location
Report Output Data Elements
Data Element | Short Description | Long Description |
---|---|---|
NUMBER0 |
|
|
System_Name |
|
|
TINWSYS_LOCAL_NAME |
|
|
OWNER_TYPE_CODE |
|
|
ST_ASGN_IDENT_CD |
|
|
Facility_Name |
|
|
TINWSF_LOCAL_NAME |
|
|
Facility_Type |
|
|
WATER_TYPE_CODE |
|
|
AVAILABILITY_CODE |
|
|
LATITUDE_MEASURE |
|
|
LONGITUDE_MEASURE |
|
|
HORIZ_REF_DATUM_CD |
|
|
DATA_COLLECTION_DT |
|
|
TINWSF_IS_NUMBER |
|
|
TINWSYS_IS_NUMBER |
|
|
TINWSF_ACTIVITY_STATUS_CD |
|
|
D_POPULATION_COUNT |
|
|
D_PRIN_CNTY_SVD_NM |
|
|
Admin Contact |
|
|
ADDR_LINE_TWO_TXT |
|
|
ADDRESS_CITY_NAME |
|
|
ADDRESS_STATE_CODE |
|
|
ADDRESS_ZIP_CODE |
|
|