CKAN Dataset: https://newmexicowaterdata.org/dataset/water-use
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.
But here's a brief recap of some of the key issues for this example with the Public Water Suppliers (PWS).
One of the biggest issues is that names of the PWS in WATERs and SDWIS are not the same.
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
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 | |
POD=Point of Diversion; well location | ||
...