Search NASA⌕ Search

Engineering topics

Lammers, Richard

Publications and source records attributed to Lammers, Richard.

Harmonized Database of Western U.S. Water Rights (HarDWR)

From Lisk et al. (2024): "In the arid and semi-arid western U.S., access to water is regulated through a legal system of water rights. Individuals, companies, organizations, municipalities, and tribal entities have documents that declare their water rights. State water regulatory agencies collate and maintain these records, which can be used in legal disputes over access to water. While these records are publicly available data in all western U.S. states, the data have not yet been readily available in digital form from all states. Furthermore, there are many differences in data format, terminology, and definitions between state water regulatory agencies. Here, we have collected water rights data from 11 western U.S. state agencies, harmonized terminology and use definitions, formatted them consistently, and tied them to a western U.S.-wide shapefile of water administrative boundaries. We demonstrate how these data enable consistent regional-scale western U.S. hydrologic and economic modeling."

Economics↗

HarDWR - Harmonized Water Rights Records

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Recalculated based on data sourced from WestDAAT - Changed using a Site ID column to identify unique records to using aa combination of Site ID and Allocation ID - Removed the Water Management Area (WMA) column from the harmonized records. The replacement is a separate file which stores the relationship between allocations and WMAs. This allows for allocations to contribute to water right amounts to multiple WMAs during the subsequent cumulative process. - Added a column describing a water rights legal status - Added "Unspecified" was a water source category - Added an acre-foot (AF) column - Added a column for the classification of the right's owner v1.02 - Added a .RData file to the dataset as a convenience for anyone exploring our code. This is an internal file, and the one referenced in analysis scripts as the data objects are already in R data objects. v1.01 - Updated the names of each file with an ID number less than 3 digits to include leading 0s v1.0 - Initial public release Description Here we present an updated database of Western U.S. water right records. This database provides consistent unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of seven broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of inter-sectoral water allocation changes though water markets (Grogan et al., *in review*). Specifically, the data were formatted for use as input to a process-based hydrologic model, Water Balance Model (WBM), with a water rights module (Grogan et al., *in review*). While this specific study motivated the development of the database presented here, water management in the U.S. West is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al., 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. West. We produced the water rights database presented here in four main steps: (1) data collection, (2) data quality control, (3) data harmonization, and (4) generation of cumulative water rights curves. Each of steps (1)-(3) had to be completed in order to produce (4), the final product that was used in the modeling exercise in Grogan et al. (*in review*). All data in each step is associated with a spatial unit called a Water Management Area (WMA), which is the unit of water right administration utilized by the state in which the right came from. Steps (2) and (3) required use to make assumptions and interpretation, and to remove records from the raw data collection. We describe each of these assumptions and interpretations below so that other researchers can choose to implement alternative assumptions an interpretation as fits their research aims. Motivation for Changing Data Sources The most significant change has been a switch from collecting the raw water rights directly from each state to using the water rights records presented in WestDAAT, a product of the Water Data Exchange (WaDE) Program under the Western States Water Council (WSWC). One of the main reasons for this is that each state of interest is a member of the WSWC, meaning that WaDE is partially funded by these states, as well as many universities. As WestDAAT is also a database with consistent categorization, it has allowed us to spend less time on data collection and quality control and more time on answering research questions. This has included records from water right sources we had previously not known about when creating v1.0 of this database. The only major downside to utilizing the WestDAAT records as our raw data is that further updates are tied to when WestDAAT is updated, as some states update their public water right records daily. However, as our focus is on cumulative water amounts at the regional scale, it is unlikely most records updates would have a significant effect on our results. The structure of WestDAAT led to several important changes to how HarWR is formatted. The most significant change is that WaDE has calculated a field known as `SiteUUID`, which is a unique identifier for the Point of Diversion (POD), or where the water is drawn from. This separate from `AllocationNativeID`, which is the identifier for the allocation of water, or the amount of water associated with the water right. It should be noted that it is possible for a single site to have multiple allocations associated with it and for an allocation to be able to be extracted from multiple sites. The site-allocation structure has allowed us to adapt a more consistent, and hopefully more realistic, approach in organizing the water right records than we had with HarDWR v1.0. This was incredibly helpful as the raw data from many states had multiple water uses within a single field within a single row of their raw data, and it was not always clear if the first water use was the most important, or simply first alphabetically. WestDAAT has already addressed this data quality issue. Furthermore, with v1.0, when there were multiple records with the same water right ID, we selected the largest volume or flow amount and disregarded the rest. As WestDAAT was already a common structure for disparate data formats, we were better able to identify sites with multiple allocations and, perhaps more importantly, allocations with multiple sites. This is particularly helpful when an allocation has sites which cross WMA boundaries, instead of just assigning the full water amount to a single WMA we are now able to divide the amount of water between the number of relevant WMAs. As it is now possible to identify allocations with water used in multiple WMAs, it is no longer practical to store this information within a single column. Instead the stAllocationToWMATab.csv file was created, which is an allocation by WMA matrix containing the percent Place of Use area overlap with each WMA. We then use this percentage to divide the allocation's flow amount between the given WMAs during the cumulation process to hopefully provide more realistic totals of water use in each area. However, not every state provides areas of water use, so like HarDWR v1.0, a hierarchical decision tree was used to assign each allocation to a WMA. First, if a WMA could be identified based on the allocation ID, then that WMA was used; typically, when available, this applied to the entire state and no further steps were needed. Second was the spatial analysis of Place of Use to WMAs. Third was a spatial analysis of the POD locations to WMAs, with the assumption that allocation's POD is within the WMA it should belong to; if an allocation still had multiple WMAs based on its POD locations, then the allocation's flow amount would be divided equally between all WMAs. The fourth, and final, process was to include water allocations which spatially fell outside of the state WMA boundaries. This could be due to several reasons, such as coordinate errors / imprecision in the POD location, imprecision in the WMA boundaries, or rights attached with features, such as a reservoir, which crosses state boundaries. To include these records, we decided for any POD which was within one kilometer of the state's edge would be assigned to the nearest WMA. Other Changes WestDAAT has Allowed In addition to a more nuanced and consistent method of assigning water right's data to WMAs, there are other benefits gained from using the WestDAAT dataset. Among those is a consistent categorization of a water right's legal status. In HarDWR v1.0, legal status was effectively ignored, which led to many valid concerns about the quality of the database related to the amounts of water the rights allowed to be claimed. The main issue was that rights with legal status' such as "application withdrawn", "non-active", or "cancelled" were included within HarDWR v1.0. These, and other water rights status' which were deemed to not be in use have been removed from this version of the database. Another major change has been the addition of the "unspecified water source category. This is water that can come from either surface water or groundwater, or the source of which is unknown. The addition of this source category brings the total number of categories to three. Due to reviewer feedback, we decided to add the acre-foot (AF) column so that the data may be more applicable to a wider audience. We added the ownerClassification column so that the data may be more applicable to a wider audience. File Descriptions The dataset is a series of various files organized by state sub-directories. In addition, each file begins with the state's name, in case the file is separate from its sub-directory for some reason. After the state name is the text which describes the contents of the file. Here is each file described in detail. Note that st is a placeholder for the state's name. stFullRecords_HarmonizedRights.csv: A file of the complete water records for each state. The column headers for each of this type of file are: state - The name of the state to which the allocations belong to. FIPS - The two digit numeric state ID code. siteID - The site location ID for POD locations. A site may have multiple allocations, which are the actual amount of water which can be drawn. In a simplified hypothetical, a farm stead may have an allocation for "irrigation" and an allocation for "domestic" water use, but the water is drawn from the same pumping equipment. It should be noted that many of the site ID appear to have been added by WaDE, and therefore may not be recognized by a given state's water rights database. allocationID - The allocation ID for the water right. For most states this is the water right ID, and what is recommended to use should a right be looked up on a given state's water rights database. The water amounts associated with these IDs tend to be finer scaled than those associated with siteID. It should be noted that some allocations may be extracted from multiple sites, particularly for larger Places of Use. ownerClassification - A classification of the types of owners for water rights. The most common is `Private` which incorporates a wide range of entities. Several classifications would be grouped into a government category, most of which are for the U.S. Federal Government. These allocations could be listed as "Federal", "United States of America", or as the names of any number of federal agencies. The last major grouping of entities is for "Native American"s. priorityDate - The date we use as the water right priority date for our modeling analysis. This is the legal priority date when it is available. However, for some rights, specifically from California and New Mexico, we used a pseudo priority date (e.g. well completion date or start of well drilling date) when a legal priority date was not available. The most questionable dates come from New Mexico, where the only date associated with certain water right records was the date the allocation was recorded in the database. As the allocation record creation tended to be within a few months of the filing of the application of the water right, from manually double checking the water rights, and our analysis focuses on aggregating water rights on the timescale of years, we determined it was acceptable to use such dates to include as many records as possible. primaryBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories WestDAAT. This column is the original WaDE category for the primary water use at the PoD site. allocationBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories for WestDAAT. This column is the original WaDE category

Economics↗

HarDWR - Harmonized Water Rights Records

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. Here we present a new dataset of western U.S. water rights records. This dataset provides consistent unique identifiers for each spatial unit of water management across the domain, unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of 7 broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of intersectoral water allocation changes through water markets (Grogan et al., in review). Specifically, the data were formatted for use as input to a process-based hydrologic model, WBM, with a water rights module (Grogan et al., in review). While this specific study motivated the development of the database presented here, U.S. west water management is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al, 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. west. The raw downloaded data for each state is described in Lisk et al. (in review), as well as here. The dataset is a series of various files organized by state sub-directories. The first two characters of each file name is the abbreviation for the state the in which the file contains data for. After the abbreviation is the text which describes the contents of the file. Here is each file type described in detail: XXFullHarmonizedRights.csv: A file of the combined groundwater and surface water records for each state. Essentially, this file is the merging of XXGroundwaterHarmonizedRights.csv and XXSurfaceWaterHarmonizedRights.csv by state. The column headers for each of this type of file are: state - The name of the state the data comes from. FIPS - The two-digit numeric state ID code. waterRightID - The unique identifying ID of the water right, the same identifier as its state uses. priorityDate - The priority date associated with the right. origWaterUse - The original stated water use(s) from the state. waterUse - The water use category under the unified use categories established here. source - Whether the right is for surface water or groundwater. basinNum - The alpha-numeric identifier of the WMA the record belongs to. CFS - The maximum flow of the allocation in cubic feet per second (ft3s-1). Arizona is unique among the states, as its surface and groundwater resources are managed with two different sets of boundaries. So, for Arizona, the basinNum column is missing and instead there are two columns: surBasinNum - The alpha-numeric identifier of the surface water WMA the record belongs to. grdBasinNum - The alpha-numeric identifier of the groundwater WMA the record belongs to. XXStatePOD.shp: A shapefile which identifies the location of the Points of Diversion for the state's water rights. It should be noted that not all water right records in XXFullHarmonizedRights.csv have coordinates, and therefore may be missing from this file. XXStatePOU.shp: A shapefile which contains the area(s) in which each water right is claimed to be used. Currently, only Idaho and Washington provided valid data to include within this file. XXGroundwaterHarmonizedRights.csv: A file which contains only harmonized groundwater rights collected from each state. See XXFullHarmonizedRights.csv for more details on how the data is formatted. XXSurfaceWaterHarmonizedRights.csv: A file which contains only harmonized surface water rights collected from each state. See XXFullHarmonizedRights.csv for more details on how the data is formatted. Additionally, one file, stateWMALabels.csv, is not stored within a sub-directory. While we have referred to the spatial boundaries that each state uses to manage its water resources as WMAs, this term is not shared across all states. This file lists the proper name for each boundary set, by state. For those whom may be interested in exploring our code more in depth, we are also making available an internal data file for convenience. The file is in .RData format and contains everything described above as well as some minor additional objects used within the code calculating the cumulative curves. For completeness, here is a detailed description of the various objects which can be found within the .RData file: states: A character vector containing the state names for those states in which data was collected for. More importantly, the index of the state name is also the index in which that state's data can be found in the various following list objects. For example, if California is the third index in this object, the data for California will also be in the third index for each accompanying list. rightsByState_ground: A list of data frames with the cleaned ground water rights collected from each state. This object holds the the data that is exported to created the xxGroundwaterHarmonizedRights.csv files. rightsByState_surface: A list of data frames with the cleaned surface water rights collected from each state. This object holds the the data that is exported to created the xxSurfaceWaterHarmonizedRights.csv files. fullRightsRecs: A list of the combined groundwater and surface water records for each state. This object holds the the data that is exported to created the xxFullHarmonizedRights.csv files. projProj: The spatial projection used for map creation in the beginning of the project. Specifically, the World Geodetic System (WGS84) as a coordinate reference system (CRS) string in PROJ.4 format. wmaStateLabel: The name and/or abbreviation for what each state legally calls their WMAs. h2oUseByState: A list of spatial polygon data frames which contain the area(s) in which each water right is claimed to be used. It should be noted that not all water right records have a listed area(s) of use in this object. Currently, only Idaho and Washington provided valid data to be included in this object. h2oDivByState: A list of spatial points data frames which identifies the location of the Point of Diversion for the state's water rights. It should be noted that not all water right records have a listed Point of Diversion in this object. spatialWMAByState: A list of spatial polygon data frames which contain the spatial WMA boundaries for each state. The only data contained within the table are identifiers for each polygon. It is worth reiterating that Arizona is the only state in which the surface and groundwater WMA boundaries are not the same. wmaIDByState: A list which contains the unique ID values of the WMAs for each state. plottingDim: A character vector used to inform mapping functions for internal map making. Each state is classified as either "tall" or "wide", to maximize space on a typical 8x11 page. The code related to the creation of this dataset can be viewed within HarDWR GitHub Repository/dataHarmonization.

Economics↗

HarDWR - Harmonized Water Rights Records

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. Here we present a new dataset of western U.S. water rights records. This dataset provides consistent unique identifiers for each spatial unit of water management across the domain, unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of 7 broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of intersectoral water allocation changes through water markets (Grogan et al., in review). Specifically, the data were formatted for use as input to a process-based hydrologic model, WBM, with a water rights module (Grogan et al., in review). While this specific study motivated the development of the database presented here, U.S. west water management is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al, 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. west. The raw downloaded data for each state is described in Lisk et al. (in review), as well as here. The dataset is a series of various files organized by state sub-directories. The first two characters of each file name is the abbreviation for the state the in which the file contains data for. After the abbreviation is the text which describes the contents of the file. Here is each file type described in detail: XXFullHarmonizedRights.csv: A file of the combined groundwater and surface water records for each state. Essentially, this file is the merging of XXGroundwaterHarmonizedRights.csv and XXSurfaceWaterHarmonizedRights.csv by state. The column headers for each of this type of file are: state - The name of the state the data comes from. FIPS - The two digit numeric state ID code. waterRightID - The unique identifying ID of the water right, the same identifier as its state uses. priorityDate - The priority date associated with the right. origWaterUse - The original stated water use from the state. waterUse - The water use category under the unified use categories established here. source - Whether the right is for surface water or groundwater. basinNum - The alpha-numeric identifier of the WMA the record belongs to. CFS - The maximum flow of the allocation in cubic feet per second (ft3s-1). Arizona is unique among the states, as its surface and groundwater resources are managed with two different sets of boundaries. So, for Arizona, the basinNum column is missing and instead there are two columns: surBasinNum - The alpha-numeric identifier of the surface water WMA the record belongs to. grdBasinNum - The alpha-numeric identifier of the groundwater WMA the record belongs to. XXStatePOD.shp: A shapefile which identifies the location of the Points of Diversion for the state's water rights. It should be noted that not all water right records in XXFullHarmonizedRights.csv have coordinates, and therefore may be missing from this file. XXStatePOU.shp: A shapefile which contains the area(s) in which each water right is claimed to be used. Currently, only Idaho and Washington provided valid data to included within this file. XXGroundwaterHarmonizedRights.csv: A file which contains only harmonized groundwater rights collected from each state. See XXFullHarmonizedRights.csv for more details on how the data is formatted. XXSurfaceWaterHarmonizedRights.csv: A file which contains only harmonized surface water rights collected from each state. See XXFullHarmonizedRights.csv for more details on how the data is formatted. Additionally, one file, stateWMALabels.csv, is not stored within a sub-directory. While we have referred to the spatial boundaries that each state uses to manage its water resources as WMAs, this term is not shared across all states. This file lists the proper name for each boundary set, by state.

Economics↗

HarDWR - Cumulative Water Rights Curves

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. This product is the dataset used as input to the WBM model (Grogan et al., in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (submission pending). This database contains 1,744 individual .csv files, two for each Water Management Area (WMA; see here) in the 11-state region. File naming convention: WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either S for surface water rights, or G for groundwater rights. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the ### unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al., in review) The code related to the creation of this dataset can be viewed within HarDWR GitHub Repository/dataCumulationCurves.

Economics↗

Data for Grogan et al. "Bringing Hydrologic Realism to Water Markets"

This data set provides model output and post-processing files required to reproduce the results, tables, and figures in the paper "Bringing Hydrologic Realism to Water Markets" by Grogan et al. (in review). Other input data used in this study includes: Lisk, M., Grogan, D., Zuidema, S., Caccese, R., Peklak, D., Zheng, J., Fisher-Vanden, K., Lammers, R., Olmstead, S., & Fowler, L. (2023). Harmonized Database of Western U.S. Water Rights (HarDWR) (Version v1) [Data set]. MSD-LIVE Data Repository. https://doi.org/10.57931/2205619 Two models were used in this study: (1) The University of New Hampshire Water Balance Model WBM, and (2) a Water Market Model. Market model code and model output post-processing code that make use of these data can be found here Model output files are: 1. WBM output files: scenario[x]_wbm_output.zip Where [x] is one of 1, 2, 2a, 3, and 3a Each zipped directory contains 7 gridded NetCDF files, each reporting the 10-year annual average value of a given variable, in units of average mm/day: File Name: wbm_indUseGross_yc.nc; Description: Water withdrawals by industry (part of the urban sector) File Name: wbm_domUseGross_yc.nc; Description: Water withdrawals by the domestic sector (part of the urban sector) File Name: wbm_irrigationGross_yc.nc; Description: Water withdrawals for agriculture File Name: wbm_irrigationExtra_yc.nc; Description: Water withdrawals from unsustainable groundwater for agriculture File Name: wbm_indUseEvap_yc.nc; Description: Consumptive water use by industry File Name: wbm_domUseEvap_yc.nc; Description: Consumptive water use by the domestic sector File Name: wbm_irrigationNet_yc.nc; Description: Consumptive water use by agriculture The file full_cell_area.nc gives the area of each grid cell in km2, which is used for converting water depth to water volume. 2. Water market model output & post processing output Folder: marketTrdSummaries/ Description: Files in this folder are used as input to code 1_WelfareCalculation_actual_trades.R. They summarize historical water right trade transactions in each state. File Name: welfare_gain_by_state_sector.csv; Description: Welfare gains by state and sector, as shown in Figure 3F. Used in code Figure3.R and produced (as a .xlsx file) by code 2_DemandCurves_simulated_trades.R File Name: welfare_data_actual.rdata; Description: welfare gains by WMA from actual historical trades, as shown in Figure 3A. This data is the output of code 1_WelfareCalculation_actual_trades.R File Name: welfare_summary_simulated.xlsx; Description: Welfare gains by state as simulated by the market model in Scenario 1. Produced by code 2_DemandCurves_simulated_trades.R, and used in code 4_WelfareCalculation.R. File Name: welfare_summary_cutoffs.xlsx; Description: Welfare gains by state as simulated by the market model in Scenario 2. Produced by code 3_DemandCurves_simulated_trades_cutoffs.R, and used in code 4_WelfareCalculation.R. File Name: welfare_summary_cutoffs_SGMS.xlsx; Description: Welfare gains by state as simulated by the market model in Scenario 2a. Produced by code 3_DemandCurves_simulated_trades_cutoffs.R, and used in code 4_WelfareCalculation.R. File Name: welfare_data_actual.rdata; Description: Spatial data, actual historical welfare gains by WMA as shown in Figure 3A. Produced by code 4_WelfareCalculation.R and used by code Figure3.R. File Name: welfare_data_simulated.rdata; Description: Spatial data, simulated Scenario 1 welfare gains by WMA as shown in Figure 3B. Produced by code 4_WelfareCalculation.R and used by code Figure3.R. File Name: welfare_data_simulated_cutoffs.rdata; Description: Spatial data, simulated Scenario 2 welfare gains by WMA. Produced by code 4_WelfareCalculation.R and used by code Figure3.R. File Name: welfare_data_simulated_cutoffs_SGMA.rdata; Description: Spatial data, simulated Scenario 2a welfare gains by WMA. Produced by code 4_WelfareCalculation.R and used by code Figure3.R. Additional files are provided for efficient reproduction of tables and figures. These include: File Name: wma_thresold_dates_Scenario2(a).csv; Description: Wet vs. paper right threshold dates for each WMA. Shown in Figure 2A,B. Produced and used by code calculate_thresolds_Figure2.R File Name: WWRTradeBounds (directory); Description: Trade boundary shapefile required to reproduce Figure 3A-D. Used in code Figure3.R File Name: welfare_region_totals.csv; Description: Welfare gains for the entire study region, as shown in Figure 3E. Used in code Figure3.R File Name: Welfare_gain_by_state_sector.csv; Description: Welfare gains by state and sector, as shown in Figure 3F. Used in code Figure3.R and produced (as a .xlsx file) by code 2_DemandCurves_simulated_trades.R File Name: WECC_MERIT_5min_v3b_mask.nc; Description: Gridded file that identified which land grid cells are in the WBM model domain, used for processing in code Figure4.py File Name: Table_1.csv; Description: All data in Table 1, reproducible from WBM output files using code table_1.R

Economics↗

MERIT-Plus Dataset: Delineation of endorheic basins in 5 and 15 min upscaled river networks

Endorheic drainage basins, those inland basins not connected directly to ocean, are essential for hydrological modeling of global and regional water balances, land surface water storage, gravity anomalies, sea level rise, etc. Within many hydrological model frameworks, river basins are defined by digital river networks through their flow direction and connectivity datasets. Here we present an improvement to gridded flow direction data and its derivatives produced from upscaled global 5 and 15 arc minute MERIT networks. We explicitly label endorheic and exorheic drainage basins and alter the delineation of endorheic basins by merging small inland watersheds to the adjacent host basins. The resulting datasets have a significantly reduced number of endorheic basins while preserving the total land portion of those basins since most of the merged catchments were inside other larger endorheic areas. We developed and present here the endorheic basin delineation method. This method performs an analysis of the contributing river and basin geometry relative to the location of the flow end point (i.e. potential endorheic lake), proximity of the latter to the drainage basin boundary and the elevation difference between the basin's lowest point and potential spillover location at the basin boundary. The new digital river network was validated using the University of New Hampshire Water Balance Model by comparing the water balance of endorheic inland depressions with modeled accumulation of water in their inland lakes based on the observed historical climate drivers used by WBM.

Earth Systems↗

MERIT-Plus Dataset: Delineation of endorheic basins in 5 and 15 min upscaled river networks

Endorheic drainage basins, those inland basins not connected directly to ocean, are essential for hydrological modeling of global and regional water balances, land surface water storage, gravity anomalies, sea level rise, etc. Within many hydrological model frameworks, river basins are defined by digital river networks through their flow direction and connectivity datasets. Here we present an improvement to gridded flow direction data and its derivatives produced from upscaled global 5 and 15 arc minute MERIT networks. We explicitly label endorheic and exorheic drainage basins and alter the delineation of endorheic basins by merging small inland watersheds to the adjacent host basins. The resulting datasets have a significantly reduced number of endorheic basins while preserving the total land portion of those basins since most of the merged catchments were inside other larger endorheic areas. We developed and present here the endorheic basin delineation method. This method performs an analysis of the contributing river and basin geometry relative to the location of the flow end point (i.e. potential endorheic lake), proximity of the latter to the drainage basin boundary and the elevation difference between the basin's lowest point and potential spillover location at the basin boundary. The new digital river network was validated using the University of New Hampshire Water Balance Model by comparing the water balance of endorheic inland depressions with modeled accumulation of water in their inland lakes based on the observed historical climate drivers used by WBM.

Earth Systems↗

HarDWR - Water Management Area (WMA) Shapefiles

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. Borders of all Water Management Areas (WMAs) across the 11 Western-most states of the continental United States are available filtered through a single source. The legal name for this set of boundaries varies state-by-state. The data is provided as two compressed shapefiles. One, stateWMAs, contains data for all 11 states. For 10 of those states, Arizona being the exception, the polygons represent the legal management boundaries used by those states to manage their surface and groundwater resources respectively. Arizona is unique among this collection of states in that surface and groundwater resources are managed using two separate sets of boundaries. During our followup analysis, due to technical reasons we decided to focus on one set of boundaries, those for surface water. Due to this, the Arizona surface WMAs are included within stateWMAs. The Arizona groundwater WMAs are provided as the second file azGroundWMAs as a companion to the first file for completeness and general reference, although the boundaries were no longer referenced in the analysis (Grogan et al., in review) past a certain point. The columns for both shapefiles are: basinNum: the state provided unique numerical ID basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID

Economics↗

HarDWR - Harmonized Water Rights Records

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. Here we present a new dataset of western U.S. water rights records. This dataset provides consistent unique identifiers for each spatial unit of water management across the domain, unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of 7 broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of intersectoral water allocation changes through water markets (Grogan et al., in review). Specifically, the data were formatted for use as input to a process-based hydrologic model, WBM, with a water rights module (Grogan et al., in review). While this specific study motivated the development of the database presented here, U.S. west water management is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al, 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. west. The raw downloaded data for each state is described in Lisk et al. (in review), as well as here. The dataset is a collection of objects stored within an RDate file, stateWaterRightsHarmonized.RData. Each object either describes how one should interact with the other objects, or contains the harmonized water rights data. Here is each object described in detail: states: A character vector containing the state names for those states in which data was collected for. More importantly, the index of the state name is also the index in which that state's data can be found in the various following list objects. For example, if California is the third index in this object, the data for California will also be in the third index for each accompanying list. rightsByState_ground: A list of data frames with the cleaned ground water rights collected from each state. The column headers for each data frame are: waterRightID - The unique identifying ID of the water right, the same identifier as its state uses. basinNum - The alpha-numeric identifier of the WMA the record belongs to. priorityDate - The priority date associated with the right. allocatedFlow - The maximum flow of the allocation in cubic feet per second (ft3s-1). source - Whether the right is for surface water or groundwater. origWaterUse - The original stated water use from the state. waterUse - The water use category under the unified use categories established here. rightsByState_surface: A list of the cleaned surface water rights collected from each state. See rightsByState_ground for more details on how the data is formatted. fullRightsRecs: A list of the combined groundwater and surface water records for each state. Essentially, these lists are the merging of rightsByState_ground and rightsByState_surface by state. See rightsByState_ground for more details on how the data is formatted. projProj: The spatial projection used for map creation in the beginning of the project. Specifically, the World Geodetic System (WGS84) as a coordinate reference system (CRS) string in PROJ.4 format. wmaStateLabel: The name and/or abbreviation for what each state legally calls their WMAs. h2oUseByState: A list of spatial polygon data frames which contain the area(s) in which each water right is claimed to be used. It should be noted that not all water right records have a listed area(s) of use in this object. Currently, only Idaho and Washington provided valid data to be included in this object. h2oDivByState: A list of spatial points data frames which identifies the location of the Point of Diversion for the state's water rights. It should be noted that not all water right records have a listed Point of Diversion in this object. spatialWMAByState: A list of spatial polygon data frames which contain the spatial WMA boundaries for each state. The only data contained within the table are identifiers for each polygon. It is worth reiterating that Arizona is the only state in which the surface and groundwater WMA boundaries are not the same. wmaIDByState: A list which contains the unique ID values of the WMAs for each state. plottingDim: A character vector used to inform mapping functions for internal map making. Each state is classified as either "tall" or "wide", to maximize space on a typical 8x11 page.

Economics↗

HarDWR - Raw Water Rights Records

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. In order to hold a water right in the western United States, an entity, (e.g., an individual, corporation, municipality, sovereign government, or non-profit) must register a physical document with the state's water regulatory agency. State water agencies each maintain their own database containing all registered water right documents within the state, along with relevant metadata such as the point of diversion and place of use of the water. All western U.S. states have digitized their individual water rights databases, along with the geospatial data describing the spatial units where water rights are managed. Each state maintains and provides their own water rights data in accordance with individual state regulations and standards. We collected water rights databases from 11 western United States states either by downloading them from publicly accessible web portals, or by contacting state water management representatives; detailed descriptions of where and when the data was collected is provided in the README.txt, as well as Lisk et al.(in review). This collection of data are those raw water rights. Each state formats their data differently, meaning that file types, field availability, and names vary from state to state. Note, the data provided here reflects the state of the water rights databases at the time we collected the data; updates have likely occurred in many states. Some pieces of information are common among all states. These are: priority date, volume or flow of water allowed by the right, stated water use of the right, and some means of identifying the geography and source of the water pertaining to the right - typically the coordinates of the Point of Diversion (PoD) of a waterbody or well. Arizona regulates water in a different way than the other 10 states. Outside of some relatively small critical agricultural areas called Active Management Areas (AMAs), Arizona does not maintain any water rights. However, the state does require registration of surface and groundwater pumping devices, which includes disclosing the mechanical specifics of the devices. We used these records as a proxy for water rights. Each state, and their respective water right authorities, have made their water right records available for non-commercial reference uses. In addition, the states make no guarantees as to the completeness, accuracy, or timeliness of their respective databases, let alone the modifications which we, the authors of this paper, have made to the collected records. None of the states should be held liable for using this data outside of its intended use. In addition, the following states have requested specifically worded disclaimers to be included with their data. Colorado: "The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk." Montana: "The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time." Oregon: "This product is for informational purposes and may not have been prepared for, or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information." The available data is provided as a series of compressed files, which each containing the full data collected from each state. Some of the files have been renamed, to more easily know which state the data belongs to. The file renaming was also required as some files from different states had the same name. In other cases, the data for a state has been placed in a folder indicating which state it belongs to - as the state organized its data by selected subregions. Below is a brief description of the format of the collected data from each state. ArizonaRights_StatementOfClaimants: A folder containing a database of interconnected CSV files. The soc_erd.pdf file contains a visual flowchart of how the various files are connected, beginning with SOC_MAIN.csv in the center of the page. ArizonaRights_SurfaceWaterRightsData: A folder containing a database of a single Shapefile and 10 associated CSVs. SurfaceWater.pdf contains a visual flowchart of how the various files are connected, beginning with ADWR_SW_APPL_REGRY.csv. ArizonaRights_Well55Registry: A folder containing a database of a single Shapefile and 59 associated CSVs. Wells55.pdf contains a visual flowchart of how the various files are connected, beginning with WellRegistry.shp. CaliforniaRights_eWRIMS_directDatabase: A folder containing a collection of four "series" Microsoft Excel files, as either XLS or XLSX. The four "series": byCounty, byEntity (what type of legal entity holds the right), byUse (stated water use), and byWatershed, are various methods by which the California water rights are organized within the state's database. However, it was observed that by only collecting a single series, not all water rights were being provided. So, essentially, the majority of records within each "series" are copies of each other, with each "series" containing some unique records. ColoradoRights_NetAmounts: A folder containing 78 CSV files, with one file per Colorado Water District. IdahoRights_PointOfDiversion: A Shapefile containing the Points of Diversion for the entire state of Idaho. IdahoRights_PlaceOfUse: A Shapefile containing the Place of Use polygons for the entire state of Idaho. MontanaRights_WaterRights: A Geodatabase file containing the Points of Diversion and Places of Use for the entire state of Montana. The name of the Points of Diversion Feature Layer within the Geodatabase is "WRDIV", and the name of the Places of Use Feature Layer is "WRPOU". NevadaRights_POD_Sites: A Shapefile containing the Points of Diversion for the entire state of Nevada. NewMexicoRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of New Mexico. OregonRights_state_shp: A folder containing 36 Shapefiles and are split between "pod" (Point of Diversion) and "pou" (Place of Use) for each water management basin within Oregon. In other words, each basin has one "pod" file and one "pou" file. The "pod" files are point shapes, and the "pou" files are polygons. UtahRights_Points_of_Diversion: A Shapefile containing the Points of Diversion for the entire state of Utah. WashingtonRights_WaterDiversions_ECY_NHD: A Geodatabase file containing both the Points of Diversion for the entire state of Washington. The name of the Feature Layer within the Geodatabase is "WaterDiversions_ECY_NHD". WyomingRights: A folder containing four subdirectories, one for each Wyoming Water Division. Each Division directory includes a varying number of subdirectories for each Wyoming Water District. Each District folder contains two copies of the Point of Diversion records for that area, with one copying being in CSV and one copy in Microsoft Excel XLS format.

Lisk, Matthew↗

HarDWR - Cumulative Water Rights Curves

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. This product is the dataset used as input to the WBM model (Grogan et al., in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (submission pending). This database contains 1,744 individual .csv files, two for each Water Management Area (WMA; see here) in the 11-state region. File naming convention: WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either S for surface water rights, or G for groundwater rights. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the ### unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al., in review)

Economics↗

Harmonized Database of Western U.S. Water Rights (HarDWR)

From Lisk et al. (in review): "In the arid and semi-arid western U.S., access to water is regulated through a legal system of water rights. Individuals, companies, organizations, municipalities, and tribal entities have documents that declare their water rights. State water regulatory agencies collate and maintain these records, which can be used in legal disputes over access to water. While these records are publicly available data in all western U.S. states, the data have not yet been readily available in digital form from all states. Furthermore, there are many differences in data format, terminology, and definitions between state water regulatory agencies. Here, we have collected water rights data from 11 western U.S. state agencies, harmonized terminology and use definitions, formatted them consistently, and tied them to a western U.S.-wide shapefile of water administrative boundaries. We demonstrate how these data enable consistent regional-scale western U.S. hydrologic and economic modeling."

Economics↗

MERIT-Plus Dataset: Delineation of endorheic basins in 5 and 15 min upscaled river networks

Endorheic drainage basins, those inland basins not connected directly to ocean, are essential for hydrological modeling of global and regional water balances, land surface water storage, gravity anomalies, sea level rise, etc. Within many hydrological model frameworks, river basins are defined by digital river networks through their flow direction and connectivity datasets. Here we present an improvement to gridded flow direction data and its derivatives produced from upscaled global 5 and 15 arc minute MERIT networks. We explicitly label endorheic and exorheic drainage basins and alter the delineation of endorheic basins by merging small inland watersheds to the adjacent host basins. The resulting datasets have a significantly reduced number of endorheic basins while preserving the total land portion of those basins since most of the merged catchments were inside other larger endorheic areas. We developed and present here the endorheic basin delineation method. This method performs an analysis of the contributing river and basin geometry relative to the location of the flow end point (i.e. potential endorheic lake), proximity of the latter to the drainage basin boundary and the elevation difference between the basin's lowest point and potential spillover location at the basin boundary. The new digital river network was validated using the University of New Hampshire Water Balance Model by comparing the water balance of endorheic inland depressions with modeled accumulation of water in their inland lakes based on the observed historical climate drivers used by WBM.

Earth Systems↗

Local, regional, and global adaptations to a compound pandemic-weather stress event

Global food security can be threatened by short-term extreme events that negatively impact food production, food purchasing power, and agricultural economic activity. At the same time, environmental pollutants like greenhouse gases (GHGs) can be reduced due to the same short-term extreme stressors. Stress events include pandemics like COVID-19 and widespread droughts like those experienced in 2015. Here we consider the question: what if COVID-19 had co-occurred with a 2015-like drought year? Using a coupled biophysical-economic modeling framework, we evaluate how this compound stress would alter both agricultural sector GHG emissions and change the number of undernourished people worldwide. We further consider three interdependent adaptation options: local water use for crop production, regional shifts in cropland area, and global trade of agricultural products. We find that GHG emissions decline due to reduced economic activity in the agricultural sector, but this is paired with large increases in undernourished populations in developing nations. Local and regional adaptations that make use of natural resources enable global-scale reductions in impacted populations via increased global trade.

54 ENVIRONMENTAL SCIENCES↗

MERIT-Plus Dataset: Delineation of endorheic basins in 5 and 15 min upscaled river networks

Endorheic drainage basins, those inland basins not connected directly to ocean, are essential for hydrological modeling of global and regional water balances, land surface water storage, gravity anomalies, sea level rise, etc. Within many hydrological model frameworks, river basins are defined by digital river networks through their flow direction and connectivity datasets. Here we present an improvement to gridded flow direction data and its derivatives produced from upscaled global 5 and 15 arc minute MERIT networks. We explicitly label endorheic and exorheic drainage basins and alter the delineation of endorheic basins by merging small inland watersheds to the adjacent host basins. The resulting datasets have a significantly reduced number of endorheic basins while preserving the total land portion of those basins since most of the merged catchments were inside other larger endorheic areas. We developed and present here the endorheic basin delineation method. This method performs an analysis of the contributing river and basin geometry relative to the location of the flow end point (i.e. potential endorheic lake), proximity of the latter to the drainage basin boundary and the elevation difference between the basin's lowest point and potential spillover location at the basin boundary. The new digital river network was validated using the University of New Hampshire Water Balance Model by comparing the water balance of endorheic inland depressions with modeled accumulation of water in their inland lakes based on the observed historical climate drivers used by WBM.

Earth Systems↗

C3F: Collaborative Container-based Model Coupling Framework

Solving complex real-world grand challenge problems requires in-depth collaboration of researchers from multiple disciplines. Such collaboration often involves harnessing multiscale and multi-dimensional data and combining models from different fields to simulate systems. However, the progress on this front has been limited mainly due to significant gaps in domain knowledge and tools that are typically employed in silos of the domains. Researchers from different fields face considerable barriers to understanding and reusing each other’s data/models in order to collaborate effectively. For example, in solving the global sustainability problems, researchers from hydrology, climate science, agriculture, and economics need to run their respective models to study different components of the global and local food, energy and water systems while, at the same time, need to interact with other researchers and integrate the results of one model with another. Developing this kind of model coupling workflow calls for (1) a large amount of data being processed and exchanged across domains and organizations, (2) identifying and processing the output of one model to make it ready for integration into another model, (3) controlling the workflow dynamically so that it runs until a certain convergence condition or other criteria is met, and (4) close collaboration among the modelers to explore, tune, and test the configuration and data transformation needed to link the models. We have developed C3F, a flexible collaborative model coupling framework to help researchers accelerate their model integration and linking efforts by leveraging advanced cyberinfrastructure such as high-performance computing and virtual containers. In this paper, we describe our experience and lessons learned in developing this cyberinfrastructure solution to support the linking of Water Balance Model (WBM) and SIMPLE-G agricultural economic model in an NSF funded INFEWS project and a DOE-funded Program on Coupled Human and Earth Systems (PCHES) to study the implications of groundwater scarcity for food-energy-water systems. The C3F model coupling framework can be extended to facilitate other model linkages as well.

containerization↗

A Regional, Integrated Monitoring System for the Hydrology of the Pan-Arctic Land Mass

Work under this NASA contract developed a system for monitoring and historical analysis of the major components of the pan-Arctic terrestrial water cycle. It is known as Arctic-RIMS (Regional Integrated Hydrological Monitoring System for the Pan-Arctic Landmass). The system uses products from EOS-era satellites, numerical weather prediction models, station records and other data sets in conjunction with an atmosphere-land surface water budgeting scheme. The intent was to compile operational (at 1-2 month time lags) gridded fields of precipitation (P), evapotranspiration (ET), P-ET, soil moisture, soil freeze/thaw state, active layer thickness, snow extent and its water equivalent, soil water storage, runoff and simulated discharge along with estimates of non-closure in the water budget. Using "baseline" water budgeting schemes in conjunction with atmospheric reanalyses and pre-EOS satellite data, water budget fields were conjunction with atmospheric reanalyses and pre-EOS satellite data, water budget fields were compiled to provide historical time series. The goals as outlined in the original proposal can be summarized as follows: 1) Use EOS data to compile hydrologic products for the pan-Arctic terrestrial regions including snowcover/snow water equivalent (SSM/A MODIS, AMSR) and near-surface freeze/thaw dynamics (Sea Winds on QuikSCAT and ADEOS I4 SSMI and AMSR). 2) Implement Arctic-RIMS to use EOS data streams, allied fields and hydrologic models to produce allied outputs that fully characterize pan-Arctic terrestrial and aerological water budgets. 3) Compile hydrologically-based historical products providing a long-term baseline of spatial and temporal variability in the water cycle.

Serreze, Mark↗