ArcGIS Pro is not required to run the DRC, but it is the preferred platform due its geospatial capabilities and integration with Python via the ArcPy package. Because of this, ArcGIS Pro provides the most user-friendly setup option.

Once you acquire all the external data, the GIS datasets must be processed and staged to make the information available to the DRC. An ArcToolbox is provided to make this simple and straightforward for ArcGIS Pro users. The following steps are required: 

Contents

Note, it is possible to perform all the necessary functions outside of an ArcGIS environment, however, the process is more involved and requires a standalone Python environment.

Populate the Geodatabase

This step provides instructions on how to populate the geodatabase with feature layers used by the DRC. 

Load GIS Layers

Begin by loading the raw geospatial datasets acquired from the USGS and State of Utah into an ArcGIS Pro Map Window.

The raw data includes the following datasets (names may vary):

• HUC.shp

• Measurement Stations

• NetNodes.shp

• Net Flowlines.shp

• NetFields.shp

• Water_Related_Land_Use_Statewide_2023_Features.shp

• OpenET_Utah.shp

Note, the data does not have to to be loaded in order to populate the geodatabase. Data is loaded here to illustrate the transformations that take place during this step. Also note, the Measurement Stations are not used. These are included only because they will assist the user in identifying historical flow records.

Before proceeding, it's necessary to open the HUC shapefile and select the hydrologic unit(s) associated with the specific area of interest in order to export these polygons to represent the basin boundary. This subset defines the extent of the DRC model and trims the data to the selected region. 

To create the basin boundary file, select the HUC polygon either by name, HUC number, or by location. Then right click on the layer in the Content Pane —>Select Data in the popup menu —>Select Export Features and specify a name and location for the output file. This should be saved a shapefile as it will be used later when populating the geodatabase. 

This HUC boundary file may need to be modified to include components of the irrigation system that fall outside this HUC boundary. Hydrologic boundaries represent natural flow divides. There could be relevant fields, canals, and pipelines that extend beyond the natural divide. There could also be areas that are not relevant encompassed by the HUC boundary. In that case, it may be possible to reduce the area before running the 'Populate Geodatabase' tool.

Process the GIS Layers To a GeoDatabase

Expand the UCRAF toolbox and double click on the 'Populate Geodatabase' tool in the 'DRC Setup' tool.

The geoprocessing tool should open. Next, specify the directory where you wish to create the GeoDatabase. This GeoDatabase will hold the clipped and pre-process layers that the DRC will read. Give the GeoDatabase a descriptive name.

Once the boundary is defined, it's time to populate the geodatabase that is read by the DRC. This is done using the 'Populate Geodatabase' tool. Double click on the tool in the Project tab of the Catalog Pane.

In the Geoprocessing Pane, select the folder icon next to each input parameter box and navigate to the appropriate file. 

The final five boxes already have default names assigned. These represent the feature layers created by running the tool. Give these layers descriptive names, avoiding any spaces and special characters, or use the default names listed to ensure compatibility with the DRC.

Once the file paths/filenames are all specified, hit the 'Run' button and wait for the tool to finish running. This creates a GeoDatabase in the specified directory. The GeoDatabase contains several coded value domains that will be imposed on certain fields

The geodatabase is now populated with the GIS files needed to run the DRC. The newly created feature layers should've also been added to the map. If not, navigate to the specified location for the newly crated GeoDatabase in the Catalog Pane and add them to the map as shown below.

Note, the 'Diversions' feature layer should be checked carefully to ensure that all the relevant diversions are identified. The ArcTool algorithmically searches for diversion points off of the natural river system in order to generate the main canal list. Some manual editing is inevitable due to irregularities where the flowline endpoints do not precisely coincide. In addition to supplying the main canal list, this 'Diversions' layer is used to aggregate diversion flows into accounting models like RiverWare©.