BAGIS-P screens

BAGIS-P Main Menu

Data manager (public)

• 1. All windows should be non-resizable; Set FormBorderStyle to "FixedSingle"

Data source editor

Select data source

Clip data source(s)

This dialog is brought up by clicking on the "Clip Selected Layer(s) to AOI" button on the Data Manager dialog.

Profile Builder (Public)

1. When Edit Method button is clicked, the Method Editor window appears, with the "Current Method" selected in the left list and the model's information filled on the right text fields.

Add method to profile

Method editor (with data bin parameter)

Select a model

Local Profile Builder

• 1. Profile names and method names must be unique. Methods of the same name are assumed to be identical.

Select profile to import

Local Data Manager

Data Units (AOI level)

The data units screen will only display of an AOI is selected and the data units aren't defined for its filled_dem, slope, or annual Prism layers. The comboBoxes will only display for the missing units so 1 - 3 comboBoxes may be displayed on this form.

Parameter Viewer

The parameter headings are the same as the field name on the parameter table.

Parameter Export Dialog

This dialog allows users to specify the output parameter file (in OMS tabular parameter file format) and select a predefined template. See this page for more information on the OMS parameter file format.

Edit Parameters

This is the screen that pops when you click the Edit Template screen. Parameter values can be modified on this screen and new parameters can be added to the bottom of the grid. Values are validated to be numeric. To edit or view a table, click on the Table link. The dimension column indicates that a parameter is a dimension. When checked, it indicates the parameter is a value that defines the dimension of other parameters. This column is read-only.

The descriptions come from the parameter_descriptions.txt file that is distributed with BAGIS-P and stored in a user's BAGIS folder. A current copy of this file is attached at the bottom of this web page.

Edit table

SubAOI ID Tool

This tool allows users to generate subAOI IDs for each HRU zones on AOIs that have subAOI defined (in BAGIS). In hydrological modeling, the subAOIs are usually calibrated separately. If an HRU zone falls within an subAOI, then it's very likely that it's parameters generated in BAGIS-P will not be used in the model. Instead, the subAOI provides the parameters to the model. The specific processes of the tool include:

1. GUI for users to select the subAOIs residing in an AOI. A subAOI can be identified as any AOI that is nested under the selected parent AOI. The selected subAOIs form an subAOI_ID layer. Users can select different combinations of subAOIs to create different subAOI_ID layers.

Users may generate the subAOI Id's without applying them to a hru/parameter profile. The subAOI_ID raster is independent from the parameterization. The subAOI ID tool and the treeline tool are menu sub-items under the AOI Parameterization menu. The subAOI ID tool is associated with a checkbox "Add subAOI ID to parameter file." There is a textbox showing which subAOI_ID layer is used and how many subAOIs are in the AOI. If there are no subAOI ID layers, the checkbox is disabled until users use the subAOI tool to create an subAOI_ID raster.

2. Use a subAOI_ID layer to generate subAOI IDs for each HRU zones when a parameter profile had been applied to an HRU. The IDs are sequential numbers ordered from upstream (1) to downstream direction. Flow accumulation numbers at the pourpoints of the subAOIs are used to determine the ID sequence. The order is irrelevant among subAOIs when they are not nested. The Id's, gauge numbers, and subAOI names will be appended to the attribute table of the subAOI ID layer. (See step 3) Gauge numbers are based on the site IDs of the USGS National Water Information System. The information was propagated to the AOI during AOI creation and stored in the awdb_id attribute field of the pourpoint layer in the aoi.gdb of the AOI. ONLY list gauge numbers if they are present on the attribute table. SubAOI's may not have gauges and are independent from the parent AOI's. There is no inheritance.

3. A subaoi.gdb is created to store the raster subAOI_ID layers representing the subAOI ID for each AOI. The subAOI ID values represent the unique sequential numbers described in step 2. HRU zones not in any subAOI have a subAOI ID of "0." The subAOI ID values are appended (zonalmajority) to a parameter table only when a parameters table exists in the param.gdb geodatabase for the selected hru/profile combination. (that is, the user must have applied the selected profile to the selected HRU.

The selected subAOIs are "combined" to form a new raster. The max flow accumulation values are extracted for each subAOI prior to creating the combined raster. The zones are then recoded to new values based on the ascending order of the max flow accumulation values. In the case of nested AOI's, the lowest flow accumulation value is used. If an AOI has, say, 5 subAOIs, users might select 3 to create a subAOIID raster and later select all 5 create another subAOIID raster.

Sample of attribute table for subAOIid raster (these subAOI's do not have gauge numbers).:

OBJECTID, VALUE, COUNT, SUB_AOI_ID,NAME,GAUGE_NUMBER

1,1,100000,2,subaoi2_12142012,

2,2,200000,3,subaoi3_12142012,

3,4,150000,1,subaoi1_12142012,

We use the majority rule to determine the subAOIID. In theory, no HRU zones should be divided into different subAOIs. However, this might happen if users don't use the contributing area rule in HRU delineation. BAGIS-H has the tool (stamp?) to fix this problem. George and Dave are fully aware of this problem.

4. Allow unlimited number of subAOI-ID to be created. The user must have the functions to manage (i.e., add, delete, or rename) the subAOI_ID layers. (Note: subAOIs can only be created and managed in BAGIS, not in this tool.)

5. Users first need to select an AOI, then create at least one subAOI set (in BAGIS), create at least one subAOI_ID layer, and finally, select an HRU parameter table for the subAOI_ID values to be propagated to. If the parameters for a subAOI need to be generated, then users will select the subAOI as an AOI in BAGIS-P. For a large watershed (e.g., the Columbia River), it's possible that the subAOIs can have subAOIs (i.e., sub-subAOIs). We only need to generate the subAOIID for the AOI and its immediate subAOIs.

Timberline (Snowmelt Depletion Curve Determination) Tool

This tool allows users to specify a timberline elevation for a HRU layer in the AOI interactively. When initiated, the filled DEM and the HRU zone boundaries are available for users to collect elevation points and save the values to HRU zones. Users have the option to add a background landcover map (or satellite image) or a user-specified layer (e.g., Landfire vegetation layer) (.lyr layer file) to the map for easier identification of timberline location.

This tool saves the timberline elevation values in the attribute table of the vector HRU featureclass (grid_zones_v). The timberline elevation will be recorded only in the attribute table of this featureclass (but will not be added to the exported OMS parameter files). A timberline elevation value of 0 indicates that the HRU is a regular HRU (not above timberline). Though the tool can display the timberline elevation values either in meters or in feet, the elevation unit of the stored values is the same as the (filled) DEM of the AOI.

The actual calculation of the Snowmelt Depletion Curve (hru_deplcrv) is done by parameter models built in ArcGIS ModelBuilder. Users can either use the timberline elevation extracted in this tool or the landfire vegetation layer to set the values of hru_deplcrv. If the area of an HRU is more then 50% above timberline elevation or not covered by canopy vegetation (based on the attached spreadsheet - Landfire_SAF-SRM_classes_PRMS_new.xlsx provided by George Leavesley), then the hru_deplcrv is set to 2, otherwise 1. BAGIS-P has two models for assigning hru_deplcrv values, hru_deplcrv_treeline that uses the treeline information generated in this tool and hru_deplcrv_landcover that uses the LandFire landcover data to identify canopy tree cover.

There are two modes for specifying (updating) timberline elevation values of the HRU zones. The first one is by clicking on a location within an HRU zone. The tool retrieves the elevation from the DEM and the HRU ID from the HRU layer and uses the information to set the timberline elevation for the matching HRU ID in the data grid. The second mode is for setting a user-specified elevation value for any selected HRU zones. Users must select one or several HRU zones from the data grid, key in an elevation value, and then check the "Set Selected HRU values to user-specified values" option.