BAGIS-P Download

Use the links below to access the latest version of BAGIS-P addin and supporting files

• BAGIS-P ESRI addin (.esriaddin) - ftp://basins.geog.pdx.edu/BAGIS/BAGIS_addins/

• BAGIS-P Profile definition file (.xml) and OMS-PRMS template parameter file (.csv) - ftp://basins.geog.pdx.edu/BAGIS/BAGIS-P%20Models/profiles/

• BAGIS-P ArcGIS 10.2 or later method toolboxes (.tbx) and method definition files (.xml) - ftp://basins.geog.pdx.edu/BAGIS/BAGIS-P%20Models/methods/

Quick Installation Guide

Please uninstall previous beta versions of BAGIS-H and BAGIS-P add-ins before the installation. BAGIS-P is delivered as an ArcMap add-in. Users can install the add-in by double-clicking the add-in file on a computer with valid ArcGIS 10.x license. The installation does not require the modification of any system registries. It can be done with a regular user account on Windows operating systems.

System Requirements

• 1. Windows operating systems with valid ArcGIS 10.x and Spatial Analyst extension.

  2. The BAGIS-P add-in file (BAGIS_P_BXXX.esriAddIn).

  3. The BAGIS-P models in ArcGIS toolbox (.tbx) file format and predefined profiles and methods files in xml format. The files can be downloaded from PSU CSAR ftp server.

  4. The Data_Bin GIS layers that are used in the BAGIS-P models. If you plan to generate parameters that are only based on BAGIS AOI internal layers (such as DEM, slope, aspect, flow accumulation, etc), then you do not need the data bin GIS layers. Such examples of the layers in the data bin are Landfire evt, Landfire cc, PRISM temperature, NLCD land-use/land-cover data, etc. Please see this page for a complete list of data bin layers that are compiled for USDA-NRCS NWCC.

1. BAGIS-generated AOI with predefined HRU zones

2. For OMS-PRMS users, an OMS parameter file template to be used during parameters export

Preparations and Installation

• 1. Due to a bug in ArcGIS 10's ModelBuilder editor, it's highly recommended that you create a "BAGIS" local environmental variable and set it to a file folder that is different from the folders specified by the TEMP or TMP environmental variables. Usually the TEMP or TMP folder is set to "%USERPROFILE%\AppData\Local\Temp." You can set your BAGIS folder to, for example, "C:\BAGIS". Make sure the folder exists and you have read/write privileges on it. Please refer to Microsoft Windows manuals if you have questions on how to create an environmental variable.

  2. Double click BAGIS-P add-in file to install it. Once you have installed BAGIS-P, you can find the BAGIS-P toolbar from the ArcMap's toolbar menu.

  3. Copy the BAGIS setting files (including all the .xml, .tbx, and .txt files) file to your BAGIS folder (i.e., the folder path defined by the BAGIS environmental variable). If your BAGIS environmental variable is set to "C:\BAGIS", then you should have the BAGIS subfolder under C:\BAGIS (i.e., C:\BAGIS\BAGIS). In it you should also find the methods and profiles folders and a settings.xml.

  4. In the methods folder you can find 6 ArcGIS toolboxes. Each time you get a new toolbox (or a set of new toolboxes), please open the toolbox in ArcCatalog (or ArcMap Catalog) and verify that there is no red error cross associated with any of the models in the box(es). The red x indicates that a model is broken. The image below shows an example of 3 broken models in the bagis_p_climate_methods.tbx toolbox. When you notice the presence of broken models, please right-click the model, and select Edit to open the model, then Save the model and exit ModelBuilder. The format of ArcGIS Toolbox files (.tbx) changes overtime. Toolboxes created in later ArcGIS version (e.g., 10.2) are not backward compatible with ArcGIS 10.0. The toolbox files delivered are stored separately in 10.0 and 10.2 formats. If you use the 10.0 toolbox files in ArcGIS 10.2, you might notice the broken tools in them. Please use the toolbox version that matches the ArcGIS version.

Administrator Interface

To prevent confusion and to maintain system consistency, many BAGIS-P administrator functions are disabled. Users must enter the administrator interface to access these functions. To access this interface, please contact Geoffrey. Administrator Interface password: NWCC_PSU

Updating the BAGIS-P settings (methods, profiles, and data)

BAGIS-P methods refer to models created in ArcGIS ModelBuilder and stored in ArcToolboxes (.tbx). These standalone models are registered to and managed by BAGIS-P using the xml files created by the Method Editor. Each method generally is used to estimate the value of one PRMS parameter.

BAGIS-P profiles are collections of methods that are used together as a group. A method can be used in multiple profiles. A profile can contain many methods. The profiles are stored in the profiles folder as .xml files. The xml files are created and managed in Profile Builder.

External data used in BAGIS methods are compiled into the BAGIS Databin. The databin is delivered as ArcGIS File Geodatabase (.gdb). The layers in the File GDB are registered to the BAGIS-P using the settings.xml file created by the Data Manager.

BAGIS-P keeps track of one set of ModelBuilder models (i.e., .tbx files) that are stored in the BAGIS folder (under the methods subfolder). However, two sets of profiles, methods, and data definitions are managed by BAGIS-P. One set is for Global/Public use; the other set is for AOI/Local use. This design allows users to use different sets of methods, models, and data layers for different AOIs. The public profile .xml files are saved in the [BAGIS folder]\BAGIS\profiles folder; the public method .xml files are saved in the [BAGIS folder]\BAGIS\methods; the public data definition xml file (settings.xml) is [BAGIS folder]\settings.xml (see image below).

The AOI/local set of profiles, methods, and data definition files can be found at [AOI folder]\param folder (see image below). If you have used an AOI in the beta-testing of BAGIS-P, then it's recommended that you delete the AOI's param folder before executing BAGIS-P.

Updating Public Settings

• Updating Public Methods: Copy the new .xml files and .tbx files to the methods folder of your BAGIS folder. Users can either redefine new methods individually by selecting the models from the tbx containers or use the "Reset toolbox path(s)" function of the "Method Editor (Public)" to connect updated models (.tbx) and their definition files (.xml). The "Verify" function of the "Profile Builder (Public)" can detect any broken links between the xml files and their associated models stored in the tbx files.

• Updating Public Profiles: Copy the new profile xml files to the profiles folder of your BAGIS folder. Use the "Verify" function of the "Profile Builder (Public)" to check that the methods associated with the profile are defined correctly. If not, activate the Admin interface, then delete the methods that failed the verification and add the correct methods back to the profile.

• Updating Public Data: Open the public Data Manager to see if any data entry is labeled as invalid. If yes, then use the Edit function to reconnect the entry to its correct data source.

Updating Local Settings

• Updating Local Methods: The local methods do not have their own tbx models. The best way to update local methods is to delete the param folder entirely and prepare the AOI for BAGIS-P execution from scratch. Alternatively, users can use BAGIS-P admin interface to delete a profile and then reimport the profile from the public (global) profile folder. Select to overwrite all existing model definition files when prompted.

• Updating Local Profiles:

• Updating Local Data

BAGIS-P Execution

Figure 1. BAGIS-P Workflow.

Figure 1 illustrates several BAGIS-P execution steps. Depending on the stages of and user's role in the process, there could be different BAGIS-P usage scenarios. Some scenarios include:

• • Standard user with predefined profiles and data (begin with the Profile Builder on the AOI Parameterization menu - Step 4 in Figure 1)

  • Administrator creating new methods/profiles (begin with Profile Builder on the BAGIS-P menu - Step 2 in Figure 1)

  • General user with custom methods and/or data (begin with Data Manager on the AOI Parameterization menu - Step 1 in Figure 1)