Elevation data is available for the entire nation from the U.S. Geological Survey National Map. 

https://apps.nationalmap.gov/downloader/

For instructions on how to download elevation tiles from the National Map see here.

Hydrographic data is available for download over the entire nation from the U.S. Geological Survey National Map. 

https://apps.nationalmap.gov/downloader/

A network showing how water right and storage deliveries traverse stream and canal systems from points of diversion to place of use. This dataset is maintained by the Utah Division of Water Rights and contains the following individual files:

• Network Nodes

• Measurement Stations

• Network Flowlines

• Network Fields

• NetPaths Table

• PathPoints Table

• NetPathlines Table

https://utahdnr.maps.arcgis.com/home/item.html?id=742b709208934b4a970ec8af34046104 

Annually updated dataset with agricultural and other water-related land use and crop types in Utah. This dataset is maintained by the Utah Division of Water Resources.

https://utahdnr.maps.arcgis.com/ 

A series of tables describing consumptive use of irrigated crops in Utah developed by Hill, 1994. Crop water use was calculated with a calibrated Blaney-Criddle equation at 111 National Weather Station sites across Utah. The folder linked below contains a shapefile (Utah_Table_Locations.shp) with all the stations and the individual tables along with an index file (UT_Table_ConsumptiveUse.xlsx) containing station metadata read by the DRC.

FHS - Shared Drive/Projects/UCRAF Final Deliverables/2.1 Climate Data/Utah ET Tables 

Remotely sensed evaporative demand data that typically consists of a shapefile containing the OpenET ID values along with Earth Engine implementation of Mapping Evapotranspiration at High Resolution with Internalized Calibration (eeMETRIC) evaporation and precipitation time series information. Requires registration through OpenET to access the data via Google Earth Engine.

The DRC reads a derivative comma delimited text file (OpenET_InputCSV_NAME) using a python routine called 'FormatOpenETData_v2.py'. or 'FormatETDemandsData_v3_Duchesne.py' 

https://openetdata.org/ 

ET Demands

The Bureau of Reclamation (Reclamation) has collaborated with the Desert Research Institute and the University of Idaho in the development of a state-of-the-science computerized evapotranspiration (ET) model (ET Demands) derived from OpenET which the DRC can also use to estimate historical and future agricultural irrigation water demands. While point data from ET Demands is downloadable, the spatially distributed version of this dataset must be requested from the Bureau of Reclamation. The advantage of ET Demands over the standard OpenET dataset is that it incorporates estimates of effective precipitation and carryover soil moisture accounting.

The Bureau of Reclamation, in collaboration with the Desert Research Institute and the University of Idaho, developed the ET Demands model—a state-of-the-science, open-source evapotranspiration (ET) modeling tool. This model estimates crop evapotranspiration (ETact) and net irrigation water requirements (NIWR) using the dual crop coefficient method outlined in FAO-56. It incorporates daily weather data, crop-specific growth curves, and a daily soil water balance that accounts for effective precipitation and carryover soil moisture. ​

While OpenET provides satellite-derived ET data, ET Demands offers enhanced capabilities by integrating detailed soil moisture accounting and effective precipitation estimates. This allows for more precise modeling of irrigation demands, particularly under varying climatic conditions. Point data from ET Demands is publicly downloadable, whereas spatially distributed datasets require a formal request to the Bureau of Reclamation.​

In our application, both OpenET and ET Demands datasets are utilized to compute crop consumptive use, leveraging the strengths of each to improve accuracy and reliability in water resource modeling.

The DRC reads a series of four text files that are constructed from an executable program called 'DistanceToFieldsAndCanals.exe'. These files are created from the digital elevation model, and associated flow direction and flow accumulation rasters, plus rasterized water related landuse (WRLU) and flowline files.

• OutFile_CanalToFields.txt

• OutFile_CanalToRiver.txt

• OutFile_Fields.txt

• OutFile_RiversCanals.txt

These files contain information related to elevation, acreage, distances and gradients for individual canals, rivers, and fields in order to compute runoff fluxes within the DRC.

FHS - Shared Drive/Projects/UCRAF Final Deliverables/Runoff Connection Files

NOTE: These "DistanceTo" files should be regenerated whenever the "Water Right Distribution Network" is updated. Go HERE for instructions on generating these files.

Individual water rights are scraped from the Division of Water Rights and then compiled using a python script called '000_WaterRights_CompileData.py'. This generates an Excel file called 'WaterRights_CompiledData_Updated.xlsx' that the DRC reads, along with the individual water rights records scraped from the links in the 'Place of Use' dataset.

The DRC compiles and plots observed diversion flows for comparison with simulated results. Observed flow can be used to calibrate model parameters to improve simulation results and is also useful for establishing local inflows for accounting models like RiverWare©. Observed diversion flows are available at only some select locations. These locations are generally identified in the "Mesurement Stations". There are three python utilities that can assist with collecting this data:

• format_station_ids.py

• download_data.py

• MergingFlowData.py 

The first script identifies headgates that have flow records available. The next one downloads and formats the flow records into individual files. The third script is used to merge records when more recent data becomes available. 

Finally, the comma delimited text file called "Observed_List.csv" is needed as an index to associate individual flow records with the canals from the main canal list (i.e., main diversions points). The text file is located in the directory that contains the individual flow records and is formatted as follows.

Canal_name, Observed_file,
MainCanalName1,CorrespondingFlowRecord1.csv
MainCanalName2,CorrespondingFlowRecord2.csv
.
.
.
MainCanalNameN,CorrespondingFlowRecordN.csv

Note: If a main canal does not have a corresponding flow record, simply enter a comma in its place. The Observed_List.csv file is needed to run the DRC, but it does not necessarily have to be populated with canal names and corresponding flow records to successfully execute the DRC. Missing canals simply won't have any observed values in the output files.