BAGIS-P was delivered with a prepackaged databin. The databin is stored as an ArcGIS File Geodatabase (i.e., a .gdb folder). Please see the GIS Data Download page for more information about the databin files.
Use the following information to set up your BAGIS-P data manager.
The parameter methods defined in BAGIS-P use both AOI internal layers (such as DEM, slope, and aspect) and external Data Bin layers (such as % impervious or canopy cover). Hru zone layer is used in all calculations and, thus, no noted in the table. The table below provides a summary of the parameters used in PRMS and their required data bin layers.
BAGIS-P has a tool that calculates the PE(T) and SR based on observed data. The calculated PE and SR values can be written to the nmonth table of the exported eWSF PRMS parameter files. The observed PE and SR data are stored in an ESRI file geodatabase and can be downloaded from the GIS Data Download page.
PE_Obs (Observed Potential Evapotranspiration) is defined as the AOI mean daily PET (inch/day). The PET source data are from the National Weather Service. The NWS derived the PET values from the free water evaporation atlas of Farnsworth et al. (1982). These PET maps were used for calibration and evaluation purposes in this study because these values are available for the entire U.S. and the ability to apply this calibration procedure to numerous basins across the U.S. depends on having a data source for PET. The PET data are provided as GIS rasters with a spatial resolution of 16.5 by 16.5 Km. The unit of the NWS PET values is mm/month. The output unit for PE_Obs is inch/day. The theoretic minimum value for PE_Obs is 0.0001 inch/day. PE_Obs is set to 0.0001 if the observed value is smaller than the theoretic minimum.
SR_Obs (Observed Solar Radiation) is defined as the averaged daily solar radiation, expressed as langleys/day (i.e., calories/sq cm/day), for each month of the year. The measured monthly SR values are available for 217 stations in the U.S. (http://rredc.nrel.gov/solar/old_data/nsrdb/). According to Farnsworth et al. (1982), "a data set of mean monthly SR values at each of the climate station sites (SNOTEL and NWS) in the U.S. was developed. A multiple linear regression (MLR) was developed between measured monthly SR values at the 217 stations and independent variables (climate statistics calculated using climate stations co-located with the measured solar radiation). For each month a separate MLR equation was developed, choosing from the following independent variables: latitude, longitude, elevation, mean precipitation (days > 0˚C), mean precipitation, number of rain days, mean maximum temperature, and the difference between mean maximum and mean minimum temperature. Adjusted R2 values ranged from 0.83-0.98. Mean monthly SR values were calculated at each SNOTEL and NWS climate station site using the monthly MLR equations. As noted earlier in this paper, there is a lack of additional data sources for model calibration and evaluation in nonresearch oriented basins. Mean monthly values of SR are used for calibration and evaluation purposes in this study because these values are available for the entire U.S. and the ability to apply this calibration procedure to numerous basins across the U.S. depends on having a data source for SR in each of these basins." The source data file (solarDAT.oct2004) provided by George contains monthly solar radiation values for 3059 data points. The station number, x, y, coordinates (in Albers Projection coordinates), and station elevation (in meters) are also recorded in the data file. The monthly solar radiation values of the station that is the closest to the centroid of the AOI are extracted from the data file as the SR_Obs values.
The 12 monthly PET rasters and the SR point featureclass are packaged in the PE_SR_Obs_nmonth_Databin.gdb.
The land cover type (COV_TYPE) parameter used in BAGIS-P has 5 categories. They are:
0 = bare ground
1 = grass
2 = shrub
3 = deciduous trees
4 = coniferous trees
Please use the Landfire_SAF-SRM_classes_PRMS_new.xlsx file below to convert the Landfire_evt to cov_type. The keys fields are SAF_SRM from Landfire_evt and cov_type_new for the cov_type output. The cov_type_prms in the lookup table is the original 4 categories used in PRMS. The lookup table was compiled and provided by George Leavesley (2013).
In addition to COV_TYPE that is based on Landfire layer, the following parameters are also based on Landfire. Please refer to the lookup table compiled by Leavesley (2013).
prms-intcp_snow: for assigning values to the snow_intcp parameter. The parameter sets the snow interception storage capacity (inches).
prms-intcp_wrain: for assigning values to the wrain_intcp parameter. The parameter sets the rainfall interception storage capacity (inches) in winter.
prms-intcp_srain: for assigning values to the srain_intcp parameter. The parameter sets the rainfall interception storage capacity (inches) in summer.
rooting depth: for calculating the values for the soil_rechr_max parameter. The parameter sets the soil recharge maximum capacity (inches).
The table below shows a general pattern of INTCP_SNOW, INTCP_WRAIN, INTCP_SRAIN, and ROOT_DEPTH values for differnt COV_TYPE.
Soil dataset uses soil mapping unit identifiers (MUID) as the mapping unit. There are several stand-alone tables that can be joined to the MUID layer using MUID as the key. The soil dataset in the BAGIS databin contains 4 additional attributes in its attribute table. These attributes include depth to bedrock (ROCKDEPH and ROCKDEPL from the comp table) and available water capacity (AWCL and AWCH from the layer table). These attributes are used in the estimation of Soil_Moist_Max and Soil_Rechr_Max parameters. The soil_texture raster is used in the estimation of Soil_Type parameter. There are 3 valid texture values: 1. sands, 2. loams, and 3. clays. Here is a summary of the attributes.
AWCL: lower limit on the estimated water holding capacity in inches of water per inch depth of soil
AWCH: upper limit on the estimated water holding capacity in inches of water per inch depth of soil
ROCKDEPL: low value for the range in the total soil thickness examined (low value of the mean depth to bedrock) in inches
ROCKDEPH: high value for the range in the total soil thickness examined (high value of the mean depth to bedrock) in inches
Texture: 1. sands, 2. loams, and 3. clays (0. others, such as outcrops or areas with poor soil development, 5. water)
STATSGO soil attributes are used for soil moisture estimates in BAGIS-P. The additional attributes are ROCKDEPM (replacing Weasel's ROCKDEPL and ROCKDEPH), AWC_100, AWC_150, and AWC_250 (replacing Weasel's AWCL and AWCH). The definitions of these additional attributes can be found at Penn State University STATSGO website (link).
These attributes are used in the estimate of soil moisture (e.g., soil_moist_max) in BAGIS-P. Soil_moist_max is defined as:
Let soil_depth = MIN (ROCKDEPM, Rooting_Depth),
If (soil_depth <= 100 cm) then
soil_moist_max = soil_depth * AWC_100/100
else if (100 < soil_depth <= 150 cm) then
soil_moist_max = AWC_100 + (soil_depth - 100) * (AWC_150 - AWC_100)/50
else if (soil_depth > 150 cm)
soil_moist_max = AWC_150 + (soil_depth - 150) * (AWC_250 - AWC_150)/100
HSGW (percent of water for each mapunit) is used to set the soil texture pixel value to water (5).
1. Layers that need Unit ID
2. System behaviors:
The system will behave differently depending on if the layer is a custom data layer or a system data layer. A custom data layer is any data layer not stored in surfaces.gdb or prism.gdb.
For custom data layers:
Unit ID tags are created/stored when a layer is defined in the "Data Source Editor" (see notes on the GUI screenshot page). The ID tags are stored in the layer metadata. The tags will record the unit type (temperature, slope, etc.) and the selected unit. Note that custom layers can only be defined in the Public Data Manager.
When adding a layer check to see if another layer already has this unit type. If it does, don't let the layer be added until it matches.
We will build a table in memory of each unit type and is associated measurement unit to check against
When custom layers are clipped to AOI, units tag is appended to the metadata for each layer in paramdata.gdb. The purpose of this is to be able to store the measurement unit with the data layer if the layer is copied from one computer to another.
Slope, Elevation, and Depth are potential issues because we won't know their units until an AOI is selected. Do we want to throw an error during the clipping process if there is a units conflict with these unit types?
For system data layers:
When an AOI is set in the "Local Data Manager", the program checks for the metadata units tag for dem-filled, slope, and prism annual. These are files in the surfaces.gdb and prism.gdb. If any of the tags are missing, prompt for input and update the metadata for the layers. Need an interface for this.
Let the user opt to not define the units. However, they will be reminded every time they access the Local Data Manager
If the model requests sys_units_elevation, it comes from the filled_dem.
For all data layers:
When checking the integrity of a method before it's added to a local profile, check for methods (models) that use sys_units_xxxx parameters (e.g., sys_units_prism_temp). If the unit is missing from the aoi data, warn the user, don't allow the method to be added
Also check for conflicting measurement units for measurement type with elevation, slope, and depth.
This check needs to run when a method is added to a local profile. Also when a public profile is imported to an AOI. Don't allow the profile to be imported until the units data is added or the conflict is resolved
Use this table to determine which parameter name to use to get the desired input unit
3. Metadata XML tag: The units metadata tags will be stored in the metadata xml for each layer.
The XPath to the section where it will be stored is: /metadata/dataIdInfo/searchKeys/keyword
The tag is displayed in the "Tags" section of the ArcMap Item Description if the default Item Description template is used
The format for the tag is BAGIS Tag < Please do not modify: ZUnitCategory|Slope; ZUnit|% Slope; > End Tag. Additional elements may be added to the tag separated by a semi-colon. Name|value pairs are associated with the pipe "|" symbol
4. data_descriptor.xml files
Use suffix to differentiate the files of different layers, e.g., data_descriptor_slope.xml, data_descriptor_dem.xml, etc.
Update BAGIS-H to store prism descriptor as data_descriptor_prism.xml
Attribute fields: timeStamp, fileName, measurementUnit, slopeUnit. The timeStamp records the time when the xml file is created.
Slope notes
Get the parameters from the model needs to send input units, output units.
If input units is slope and input != output
Rename old slope layer and generate new slope layer