Tahoe Stormwater and BMP Performance Database
Monitoring and Reporting Guidance Document
APPENDICES
October 5, 2010
Tahoe Stormwater and BMP Performance Database: Monitoring and Reporting Guidance Document
LIST OF APPENDICES
Appendix A Database User’s Guide
Appendix B Database Structure & Specifications
Appendix C Treatment BMP Design Parameters
Appendix D Monitoring and Analytical QA/QC
October 5, 2010
Appendix A
Tahoe Stormwater and BMP Performance Database
Database User’s Guide
October 5, 2010
Table of Contents
1
Introduction ..................................................................................................................................................................... 1
1.1
1.2
2
Quick Start Guide ........................................................................................................................................................... 2
2.1
2.2
2.3
2.4
3
Purpose of the Application ............................................................................................................................... 1
Application Overview ......................................................................................................................................... 1
System Requirements......................................................................................................................................... 2
Verify Installation and Connection to Remote Database ..................................................................... 3
Quick Tour ............................................................................................................................................................... 3
Getting Help ............................................................................................................................................................ 8
In‐Depth Guide to Using Tahoe BMP‐DB ............................................................................................................. 9
3.1
Submitting Data to the Tahoe Stormwater and BMP Performance Database............................. 9
3.2
Creating or Accessing a BMP Site ................................................................................................................ 10
3.2.1
Site Information ........................................................................................................................................ 11
3.2.2
Site Contact Info ........................................................................................................................................ 12
3.2.3
Site Inlets...................................................................................................................................................... 13
3.2.4
Site Outlets .................................................................................................................................................. 15
3.2.5
Other Locations ......................................................................................................................................... 16
3.3
Creating or Accessing a Stormwater Site ................................................................................................. 17
3.3.1
Site Information ........................................................................................................................................ 18
3.3.2
Site Contact Info ........................................................................................................................................ 19
3.3.3
Site Inlets...................................................................................................................................................... 20
3.3.4
Site Outlets .................................................................................................................................................. 21
3.3.5
Other Locations ......................................................................................................................................... 22
3.4
Monitoring Locations and Data .................................................................................................................... 24
3.4.1
Monitoring Location Information ...................................................................................................... 24
3.4.2
Runoff and Monitoring Events ............................................................................................................ 25
3.4.3
Discrete Samples ....................................................................................................................................... 29
3.4.4
Meteorologic Data .................................................................................................................................... 31
3.5
Ancillary BMP Information ............................................................................................................................ 32
3.5.1
Cost and Maintenance Data .................................................................................................................. 32
3.5.2
Documents and Design Information ................................................................................................. 35
3.6
Querying Raw Data ............................................................................................................................................ 37
3.7
Accessing Statistical Summary Reports .................................................................................................... 39
October 5, 2010
Appendix A – Database User’s Guide
1 Introduction
The Tahoe Stormwater and BMP Performance Database (Tahoe BMP‐DB) is a repository for storm water
quality data, BMP performance data, and BMP design and maintenance information. The database
resulted from a joint effort between researchers and consultants at the Desert Research Institute (DRI),
Geosyntec Consultants, Inc., Northwest Hydraulic Consultants, Inc. (nhc), 2NDNATURE, LLC, and the
University of California. It was developed through a grant with the USDA Forest Service Pacific
Southwest Research Station using funds provided by the Bureau of Land Management through the sale
of public lands as authorized by the Southern Nevada Public Land Management Act.
Figure 1: Tahoe BMP‐DB Application Icon
1.1 Purpose of the Application
The goal of the Tahoe Stormwater BMP Database (Tahoe BMP‐DB) is to provide a central repository for
housing design, monitoring, and performance data for stormwater best management practices (BMPs)
from around the Lake Tahoe area. The information stored in the database will be used to track BMP
performance with the eventual goal of linking performance to BMP design and maintenance practices.
1.2 Application Overview
The Tahoe BMP‐DB desktop application is a local interface to an online database that provides users
with a clean, simple and efficient means of interacting with the underlying data. Conceptually, the Tahoe
BMP‐DB application can be thought of as consisting of two major components, a desktop application
and a backend database (as shown in Figure 2).
Figure 2: Tahoe BMP‐DB Database Application Overview
Internet
Tahoe BMP
Database
Desktop
application
October 5, 2010
Page A‐1
Appendix A – Database User’s Guide
2 Quick Start Guide
The Tahoe BMP‐DB is simple to use and easy to install. The instructions contained in this section of the
manual will walk you through installing the application and running it for the first time. The total
estimated time needed to install and begin using the application is less than 5 minutes. Please note that
the current version of the database is available only for IBM compatible personal computers running
Windows. However, the application can be installed and used on some Apple Macintosh or Linux / Unix
computers when running a Windows PC emulator program. To get the Tahoe BMP‐DB installed and
ready to use on your Windows PC, follow these steps:
1. Step 1: Check that your Windows PC meets the system
requirements (see section 2.1: System Requirements )
2. Step 2: Install Tahoe BMP‐DB from the executable on the Lake
Tahoe BMP Database Installation CD (or other trustworthy
source). The installation program will first un‐install any
previous version of the application that may exist on your
computer prior to installing the current version.
3. Step 3: Verify your installation by checking that the
application can successfully connect to the remote database
(see Section 2.2: Verify Installation).
2.1 System Requirements
For best results, use a system that meets or exceeds the following specifications:
Supported Operating Systems:
Windows 7
Windows Vista
Windows XP
Other Software Requirements:
No other software is required; however the installation program might download and install additional
system components from Microsoft to update your system prior to installation if needed. The
application connects to a database that resides on a remote server. Therefore, the application will not
be functional if an internet connection is not available or when the remote server is offline. As of this
writing, the remote server is running Windows 2003 Server and Microsoft SQL Server 2005.
October 5, 2010
Page A‐2
Appendix A – Database User’s Guide
Hardware Requirements:
Processor:
400 MHz Pentium processor or equivalent (Minimum);
1 GHz Pentium processor or equivalent (Recommended)
Ram:
128 MB (Minimum)
512 MB (Recommended)
Hard Disk:
A minimum of 2.35 MB of available space is required
Internet Connection:
An internet connection is needed to run the application. For best results use a broadband
connection.
CD or DVD Drive:
Required only if installing from a CD or other optical media
Display:
800 x 600, 256 colors (Minimum)
1024 x 768 high color, 32 bit (Recommended)
2.2 Verify Installation and Connection to Remote Database
After successfully installing the application by following the steps outlined above, verify your installation
by simply clicking the desktop shortcut or using the Windows start menu by clicking on Start > Programs
> Tahoe Stormwater and BMP Performance Database > Tahoe BMP‐DB to launch the application. The
Tahoe BMP‐DB application is successfully launched if Form 1.0 “Tahoe Stormwater and BMP
Performance Database” is displayed (Figure 3).
Refer to Section 2.4 Getting Help if you are unable to connect to the remote database after you have
successfully installed the application. You may have to check with your System Administrator to ensure
that your local firewall and network administration policies are not interfering with your connection to
the remote database.
2.3 Quick Tour
Congratulations on successfully installing the Tahoe BMP‐DB. This section will quickly get you started on
being productive with the application; however for detailed guidance on how to use the database refer
to Section 3, In‐Depth Guide to Using Tahoe BMP‐DB.
The application allows the user to upload data, edit and export previously entered records, query water
quality data, and access BMP performance summary reports.
October 5, 2010
Page A‐3
Appendix A – Database User’s Guide
Data Entry and Retrieval – The application provides forms for data entry and individual record retrieval.
Some of the forms allow users to import text files as a mechanism to facilitate bulk submittal of data. To
enter data, start the application by clicking on the desktop shortcut or navigating to the program via the
Start Menu. The control form, Form 1.0 “Tahoe Stormwater and BMP Performance Database” is
displayed (Figure 3). Two main categories of data can be entered in to the database, data pertaining to
BMP sites and data pertaining to Stormwater sites (monitoring locations without associated BMPs),
refer to Section 3 for a detailed description of the two categories of data. Use the “Site Type” drop down
to access data entry forms for either a storm water site or a BMP site. After the site type selection is
made the “Current Site” drop down will be populated with a list of available sites from the database in
the same category as the site type you have selected. Edit one of the existing entries in the database by
selecting a site in the “Current Site” drop down or create a new site by clicking on the “Create New Site”
button to load a series of data entry forms.
The list of data entry forms along with a brief description of each form is provided in Table 1 as follows.
Table 1: Data Entry Forms
Code
Form 1.0
Form Title and Screen Shot
Tahoe Stormwater and BMP Performance Database
Description
Data entry begins on Form 1.0 which is the first
form presented after launching the application.
The user first selects a site type (BMP or
Stormwater). The user can then create a new site
by clicking on the “Create Site” button or edit an
existing site by selecting it from the “Current Site”
drop down.
The buttons on the “Database Management”
portion of the form become active when an
existing site is selected or a new site is created. The
four buttons which load specific data forms
become labeled as follows:
A.
B.
C.
D.
General Site Information (Button A)
Monitoring Locations and Data (Button B)
Cost and Maintenance Data (Button C)
Documents and Design Information
(Button D)
The buttons on the “Data Retrieval” portion of the
form also become active when an existing site is
selected or a new site is created. Two buttons are
available to retrieve data:
A.
B.
October 5, 2010
Query Raw Data
Query Data Summaries
Page A‐4
Appendix A – Database User’s Guide
Form A is presented to the user after a user selects
a site type and then clicks the “Create New Site”
button or the user selects a site type, next select an
existing site from the “Current Site” drop down,
and then clicks on Button A (General Site
Information) on Form 1.0 above.
Form A
General Site Information
Form A allows users to submit all the information
that is relevant to a BMP site and its associated
drainage area. The forms consist of multiple tabs
listed as follows:
A1.
A2.
A3.
A4.
A5.
Site info
Site Contact info
Site Inlets
Site Outlets
Other Locations
It is recommended that users progress through the
tabs sequentially. Make sure to click the relevant
“Submit” button on each form whenever data are
entered prior to proceeding to the next tab. After
data on all tabs have been entered and submitted,
check the “Confirm data have been submitted”
check box and click the “Done” button to save the
data and exit this form. Note that required fields
on all forms are presented with a light yellow
background. Entering non numeric information in
numeric fields produces a warning and the
background color of the field in question turns
red. Gray fields are fixed and cannot be edited
and white fields are optional.
October 5, 2010
Page A‐5
Appendix A – Database User’s Guide
Form B
Monitoring Location and Data
Form B is launched after clicking on Button B from
Form 1.0. This form allows users to submit
information relevant to a monitoring location and
allows entry of data collected at that location. The
form consists of multiple tabs listed as follows:
B1.
B2.
B3.
B4.
New Location Info
Runoff and Monitoring Events
Discrete Samples
Meteorological Data
Again, it is recommended that users progress
through the tabs sequentially. Make sure to click
the relevant “Submit” button on each form
whenever data are entered prior to proceeding to
the next tab. After data on all tabs have been
entered, check the “Confirm data have been
submitted” check box and click the “Done” button
to save data and exit this form.
Form C
Cost and Maintenance Data
Form C is launched after clicking on Button C of
Form 1.0. This form allows users to submit all the
cost and maintenance data associated with a BMP.
The forms consists of two tabs labeled as follows:
C1. Cost Data
C2. Maintenance Data
Make sure to click the relevant “Submit” button on
each form whenever data are entered prior to
proceeding to the next tab. After data on both
tabs have been entered, check the “Confirm data
have been submitted” check box and click the
“Done” button to save the data and exit this form.
October 5, 2010
Page A‐6
Appendix A – Database User’s Guide
Form D
Documents and Design Information
Form D is launched after clicking on Button D of
Form 1.0 This form allows users to provide
information about available documents and files
(drawings, photos, etc) associated with a BMP as
well as sizing and design parameters. Contact
information is saved for all document records, so
specific documents may be requested. Form D
consists of two tabs labeled as follows:
D1. Site Documents
D2. Design Specifications
Make sure to click the relevant “Submit” button on
each form whenever data are entered prior to
proceeding to the next tab. After data on both
tabs have been entered, check the “Confirm data
have been submitted” check box and click the
“Done” button to save data and exit this form.
Data Retrieval – To query data and to access data summary reports, start the application (if not already
started) by clicking on the desktop shortcut or via the start menu. Again, the control form, Form 1.0
“Tahoe Stormwater and BMP Performance Database” (see Figure 3) pops up. Select the appropriate site
type in the “Site Type” drop down and an existing site in the “Current Site” drop down. This enables the
button on the form. Click on the “Query Raw Data” button to proceed. The user is presented with a
form that allows one to retrieve the required data. A brief description of the data retrieval workflow is
provided in Table 2 as follows.
October 5, 2010
Page A‐7
Appendix A – Database User’s Guide
Table 2: Data Retrieval Forms
Code
Form 1.0
Form Title and Screen Shot
Tahoe Stormwater and BMP Performance Database
Form 1.1
Description
Data retrieval begins on Form 1.0 which is the first
form presented to the user after launching the
application. This form presents five buttons that allow
users to launch other forms. Click the “Query Raw
Data” button to load Form 1.1 for data retrieval.
Form 1.1 is launched after clicking on the “Query Raw
Data” Button on Form 1.0. A user interface is
provided that allows users to query the database by
data type and time range, as well as BMP type
(applicable to BMP sites only), site name, and TRPA
watershed. After all available filters have been
applied click the “Preview SQL Statement” button.
The SQL statement is generated and displayed in the
“SQL Query Preview” box. To execute the query and
populate the data grid click the “Submit SQL
Statement.” Users who are familiar with SQL
statements and the structure of the tables and fields
in the database can customize this query (see
Section 3.6). The data shown in the data grid may be
exported to a text file by clicking on the “Export
Selected Data” button.
2.4 Getting Help
A PDF version of the Lake Tahoe BMP Database Guidance Document (which contains a copy of this user
guide as Appendix A) can be found in the installation directory under the “Supporting Documents”
folder. Assuming you have installed to the default location, the guidance document can be found at:
C:\Program Files\Tahoe BMP Database\Supporting Documents\Lake Tahoe BMP Database Guidance
document.pdf. Refer to the main document for a deeper understanding of the recommended
monitoring protocols and data formats; use this user guide for information on how to enter data and
retrieve information from the application.
October 5, 2010
Page A‐8
Appendix A – Database User’s Guide
3 In­Depth Guide to Using Tahoe BMP­DB
This section of the guide provides an in‐depth explanation of how to use Tahoe BMP‐DB. For a quick
description of the data entry and data retrieval forms refer to Section 2: Quick Start Guide. After
successfully installing the application, simply click the desktop shortcut or launch the application from
the Windows start menu. Launching the Tahoe BMP‐DB application will bring up Form 1.0, the “Tahoe
Stormwater and BMP Database” introductory window (Figure 3).
Figure 3: Introductory Window of the Tahoe Database Application (Form 1.0)
From the introductory window, users can access all the major components of the Tahoe BMP‐DB
application by simply clicking on one of the six buttons on the form.
3.1 Submitting Data to the Tahoe Stormwater and BMP Performance
Database
The Tahoe BMP‐DB accepts water quality and hydrologic monitoring data associated with BMPs (BMP
Sites), as well as general stormwater data not associated with any BMP (Stormwater Sites). Several
monitoring locations and associated datasets may be associated with a single BMP Site (or BMP record),
such as data collected at the inlet or outlet of the BMP. General stormwater data is entered by creating
a Stormwater Site and entering the associated monitoring data. The monitoring data entry procedures
for BMP sites and Stormwater sites are similar as described in Sections 3.2 and 3.3, respectively.
October 5, 2010
Page A‐9
Appendix A – Database User’s Guide
Users enter data into the Tahoe BMP‐DB through a series of data entry forms containing labeled fields,
selection boxes, and drop down menus. Required fields are presented with a light yellow background,
non‐editable fields are gray and optional fields are white. Entering non‐numeric input in numeric fields
results in a validation warning and a light red background is applied to the field in question. Form B also
allows bulk data submittal through the import of specially formatted text files in tab‐delimited (.txt)
format. A user‐friendly Microsoft Excel template file is provided to facilitate simple data entry into the
required text file format. The Microsoft Excel file contains macros that automatically create and
populate the text file with data for bulk upload to the database. The Excel template file included as part
of the installation package for use in generating and populating text files for bulk upload is automatically
copied to the installation directory during the installation of Tahoe BMP‐DB. For example, if you
installed the database to the default installation folder then the bulk upload Excel file will be located at:
C:\Program Files\Tahoe BMP Database\FormB\Tahoe_FormB_templates.xlsm. Follow all instructions in
the Excel file to successfully create the tab‐delimited text file in the required format.
Figure 4: Microsoft Excel Bulk Upload Text File Location in Default Installation Directory
IMPORTANT: Any columns in the data templates for which data is not readily available should be populated with the word
“NULL “to maintain the integrity of the bulk import executed by the Tahoe BMP‐DB application.
3.2 Creating or Accessing a BMP Site
For the purposes of the Tahoe Stormwater and BMP Performance Database, a BMP Site is represented
as a record which stores information for one or more monitored locations associated with a single BMP.
Conversely, a Stormwater Site refers to a single monitored location that does not have a BMP associated
with it (see Section 3.3 Creating or Accessing a Stormwater Site). The information entered for a BMP
Site constitutes a BMP Site Record. To create or edit a BMP Site Record, click the “Create or Edit BMP
Record” button located in the upper left portion of Form 1.0 to bring up the “Monitoring Data and
Information Manager” (Information Manager) shown in Figure 5.
October 5, 2010
Page A‐10
Appendix A – Database User’s Guide
Figure 5: Creating or Accessing a BMP Site Record
Note: As shown in the figure above, when the control form is first loaded and site Type is selected, the “Create New Site”
button becomes active. The other buttons only become active after a new BMP Site is created or an existing BMP Site is
selected. This ensures that data submitted to the database during a session is properly associated with the appropriate BMP
Site.
3.2.1 Site Information
Click the “Create New Site” button to load Form A. Form A presents a tabbed interface with 5 sub‐forms
arranged as tabs. Each tab provides a series of input controls located at the top half with a data grid
displayed at the bottom half. The data grid allows the user to see what data currently exists in the
database and to visually confirm that newly created or edited data have been successfully submitted to
the database. The data displayed in the data grids may be exported by clicking on the button labeled
“Export Data on this Tab.”
Upon loading Form A, the “A1: Site Info” tab is selected by default (Figure 6). The user can begin
entering data for a new BMP Site. Provide information for a new record by typing a new name into the
“Site Name” field. Complete the form by selecting the Treatment BMP type, subtype, and the TRPA
watershed in which it is located, and fill in the remaining fields on the form. Please see the Guidance
Document for a complete discussion on the determination of Treatment BMP type. It is very important
for the user to apply the standard definitions of Treatment BMPs to ensure proper data comparison and
analysis. The number of inlets is intended to identify the number of discrete drainage areas feeding into
the BMP. The number of outlets is intended to identify the primary treatment outlets (e.g., perforated
riser of a dry basin) and the bypass and/or emergency overflow outlets. The coordinates entered on this
form represent the geometric centroid of the BMP and should be entered in decimal degrees to the
highest level of accuracy possible. Coordinates for other locations associated with the BMP such as the
inlet(s) and outlet(s) specified or various other locations of interest will be entered at subsequent tabs
October 5, 2010
Page A‐11
Appendix A – Database User’s Guide
within Form A. After completing all required fields on the form, click the “Submit New Site” button and
the new record will appear in the data grid located on the bottom half of the form.
To edit an existing BMP Site record, the user should select an existing site from the “Current Site” drop
down on the Control Form (Form 1.0), which will load all of the existing data of the selected BMP into
the “Site Info” tab of Form A, as well as the other forms and tabs. At this point, the existing data
contained within the fields on the form can be edited and resubmitted by clicking on the “Submit Edited
Site” button.
Figure 6: BMP Site Information
3.2.2 Site Contact Info
The second tab within Form A is the “A2: Site Contact Info” tab (Figure 7), which is used for providing
information about the agencies, organizations and the people that are associated with a BMP Site
record and specifying their roles as they relate to the site.
Begin by providing entries in the first group box area labeled “1. Create/Select Agency”. To create a new
agency, simply type a new name into the “Current Agency Name” field. Complete the agency
information fields, as available, and then click the “Submit New Agency Info” button and the new agency
will be submitted to the database and appear in the data grid below. To select an existing agency, click
October 5, 2010
Page A‐12
Appendix A – Database User’s Guide
on the “Edit or use existing agency” radio button and then select an existing agency from the drop down
list. The existing information of the selected agency will be loaded into Tab A2, allowing the existing data
to be edited and resubmitted by clicking on the corresponding “Submit Edited Agency” button.
To assign a role to an Agency, select one of the options in the “2. Agency Roles” option group and click
on the “Apply Roles to Agency/Site” button. You can add a contact person to an Agency by providing a
person’s name and email address and clicking on the “Add Person to Current Agency” button.
Figure 7: Site Contact Information
3.2.3 Site Inlets
The third tab of Form A is the “A3: Site Inlets” tab which allows users to submit information on BMP
inlets and their associated drainage areas. Information can only be provided for multiple inlets up to the
number of inlets previously entered on Tab “A1: Site Info.” Inlets must be defined before monitoring
data associated with those locations can be entered into the database in Form B.
Since inlets are implicitly created on Tab A1, users cannot create an inlet on Tab A3; rather, users can
only edit the information for an inlet on Tab A3. To edit an inlet, select the inlet number using the “Inlet
No.” control. Provide inlet coordinates, the total drainage area in acres, percent slope, percent
imperviousness (% IMP), percent directly connected impervious area (%DCIA), and a description of the
October 5, 2010
Page A‐13
Appendix A – Database User’s Guide
inlet, such as the configuration, type, or relevant notes about the drainage area such as the presence of
upstream BMPs. The data grid on the right side of the form should be edited to reflect the land use
breakdown for the drainage area that is tributary to each inlet if such data is available. Failure to provide
information in the land use grid results in a warning. Note that the data are still submitted despite the
land use grid warning. The land use categories shown in the land use grid are adapted from the TRPA
land use shapefile for the Tahoe Basin and cannot be modified. If the drainage areas of two or more
inlets are indistinguishable, then the drainage area characteristics should be evenly split among them as
appropriate. After all of the relevant inlet information has been entered click on “Submit Inlet and
Drainage Area at Site” button. This will submit the new or edited data to the database and the data grid
at the bottom of the form will be updated.
Repeat the process until all the inlets have been populated with the requisite information. With each
Inlet submission the drainage area characteristics are simultaneously submitted and intrinsically linked
to the inlet in the database. As each inlet’s data are submitted, the “Inlet No.” control will be
automatically incremented forward. After data have been submitted for the last inlet, the inlet data
label in the status bar at the bottom of the window changes to read “Inlet Data COMPLETE” indicating to
the user that all the inlets have been addressed. If there is a need to provide information for additional
inlets beyond the number of inlets submitted on Tab A1, then the user must return to Tab A1 and
increase the number of inlets and click “Submit Edited Site.” The user may then return to Tab A3 to
submit data for the newly entered inlet.
October 5, 2010
Page A‐14
Appendix A – Database User’s Guide
Figure 8: Site Inlets and Drainage Areas
3.2.4 Site Outlets
The fourth tab of Form A is the “A4: Site Outlets” tab which allows users to submit information on BMP
outlets (Figure 9). Information can only be provided for multiple outlets up to the number of outlets
entered on Tab “A1: Site Info.” Outlets must be defined before monitoring data associated with these
locations can be entered into the database in Form B.
Since outlets are implicitly created on Tab A1, users cannot create an outlet on Tab A4; rather, users can
only edit the information for an outlet on Tab A4. To edit an outlet, select the outlet number using the
“Outlet No.” control. Provide the outlet coordinates, a description, and the type of outlet (i.e.,
treatment, bypass, or overflow) and click on the “Submit Outlet” button to define a new outlet or to
modify an existing outlet. This button will submit the new or edited data to the database and the data
grid at the bottom of the form will be updated.
Repeat the process until all the outlets have been populated with the requisite information. As each
outlet’s data are submitted, the “Outlet No.” control will be automatically incremented. After data has
been submitted for the last outlet, the outlet data label in the status bar at the bottom of the window
changes to read “Outlet Data COMPLETE” indicating to the user that all the outlets have been
addressed. If there is a need to provide information for additional outlets beyond the number of outlets
October 5, 2010
Page A‐15
Appendix A – Database User’s Guide
originally submitted on Tab A1, then the user must return to Tab A1 and increase the number of outlets
and click “Submit Edited Site”. The user may then return to Tab A4 to submit data for the newly entered
outlet.
Figure 9: Site Outlets
3.2.5 Other Locations
The final tab on Form A is the “A5: Other Locations” tab which is used to track any other locations
relevant to the BMP that are not its centroid, inlets, or outlets. These may include other monitoring
locations (e.g., upgradient monitoring well, weather station, etc.) or other important BMP features, such
as a sediment forebay. The location type includes options for identifying how the location relates to the
BMP. Descriptions should be provided to give additional details of the relevance of the location.
October 5, 2010
Page A‐16
Appendix A – Database User’s Guide
Figure 10: Other Locations
3.3 Creating or Accessing a Stormwater Site
For the purposes of the Tahoe Stormwater and BMP Performance Database, a Stormwater Site is a
single monitored location that does not have a BMP associated with it, while a BMP site represents one
or more monitored locations associated with a single BMP (refer to Section 3.2 Creating or Accessing a
BMP Site). The information entered for a Stormwater Site constitutes a Stormwater Site Record. To
create or edit data related to a Stormwater site, click the “Create or Edit Stormwater Record” button
located in the upper right portion of Form 1.0 will bring up the “Monitoring Data and Information
Manger” (Information Manager) shown in Figure 11.
October 5, 2010
Page A‐17
Appendix A – Database User’s Guide
Figure 11: Monitoring Data and Information Manager
Note: As shown in Figure 11, when control form is first loaded and site type is selected, the “Create New Site” button
becomes active. The other buttons only become active after a new Stormwater Site is created or an existing Stormwater Site
is selected. This ensures that data submitted to the database during a session is properly associated with the appropriate
Stormwater Site.
3.3.1 Site Information
Click the “Create New Site” button to load Form A. Form A presents a tabbed interface with 5 sub‐forms
arranged as tabs. Each tab provides a series of input controls located at the top half with a data grid
displayed at the bottom half. The data grid allows the user to see what data currently exists in the
database and to visually confirm that newly created or edited data have been successfully submitted to
the database. The data displayed in the data grids may be exported by clicking on the button labeled
“Export Data on this Tab”.
Upon loading Form A, the “A1: Site Info” tab is selected by default (Figure 12). The user can begin
entering data for a new Stormwater Site. Provide information for a new record by typing in a new name
into the “Site Name” field. Complete the form by selecting the TRPA watershed in which the site is
located, and fill in the remaining fields on the form. The coordinates entered on this form represent the
coordinates of the primary monitoring location at the site and should be entered in decimal degrees to
the highest level of accuracy possible. Coordinates for other locations of interest associated with the Site
such as a local weather station will be entered on the “A5: Other Locations” tab within Form A. After
completing all required fields on the form, click the “Submit New Site” button and the new record will
appear in the data grid located on the bottom half of the form.
To edit an existing Stormwater Site record, the user should have selected an existing site from the
“Current Site” drop down on the Control Form (Form 1.0), which will load all of the existing data of the
selected Stormwater Site into the “Site Info” tab of Form A as well as the other forms and tabs. At this
October 5, 2010
Page A‐18
Appendix A – Database User’s Guide
point, the existing data contained within the fields on the form can be edited and resubmitted by
clicking on the “Submit Edited Site” button.
Figure 12: Stormwater Site Information
3.3.2 Site Contact Info
The second tab within Form A is the “A2: Site Contact Info” tab (Figure 13), which is used for providing
information about the agencies, organizations and the people that are associated with a Stormwater
Site record and specifying their roles as they relate to the site.
Begin by providing entries in the first group box area labeled “1. Create/Select Agency”. To create a new
agency, simply click on and type a new name into the “Agency” field. Complete the agency information
fields, as available, and then click the “Submit New Agency Info” button and the new record will be
submitted to the database and appear in the data grid below. To select an existing agency, click on the
“Edit or use existing agency” radio button and then select an existing agency from the drop down list.
The existing information of the selected agency will be loaded into Tab A2, allowing the existing data to
be edited and resubmitted by clicking on the corresponding “Submit Edited Agency” button.
October 5, 2010
Page A‐19
Appendix A – Database User’s Guide
To assign a role to an Agency, select one of the options in the “2. Agency Roles” option group and click
on the “Apply Roles to Agency/Site” button. You can add a contact person to an Agency by providing a
person’s name and email address and clicking on the “Add Person to Current Agency” button.
Figure 13: Site Contact Information
3.3.3 Site Inlets
The third tab of Form A is the “A3: Site Inlets” tab which allows users to submit information on the
drainage areas to their Stormwater Site. By default, Stormwater Sites only have a single inlet, so the
entire tributary area should be included in the drainage area information provided on this form. The
fields relevant to the drainage area of a Stormwater Site include: total drainage area in acres, percent
slope, percent imperviousness (% IMP), percent directly connected impervious area (%DCIA), and any
specific notes about the drainage area such as the presence of upstream controls. The data grid on the
right side of the form should be edited to reflect the land use breakdown for the drainage area that is
tributary to each inlet if such data are available. The land use categories are based on the TRPA land use
shapefile for the Tahoe Basin and cannot be modified.
October 5, 2010
Page A‐20
Appendix A – Database User’s Guide
Figure 14: Site Inlets and Drainage Areas
3.3.4 Site Outlets
The fourth tab of Form A is the “A4: Site Outlets” tab. For Stormwater sites, the contents of this tab are
disabled (see Figure 15). The representation of Stormwater sites as discrete monitoring locations allows
all data to be associated with the site using the theoretical “inlet” designation without the need for an
“outlet”.
October 5, 2010
Page A‐21
Appendix A – Database User’s Guide
Figure 15: Site Outlets disabled for Stormwater Sites
3.3.5 Other Locations
The final tab on Form A is the “A5: Other Locations” tab which is used to track any other locations
relevant to the Stormwater Site such as an onsite weather station or other important site features. The
location type includes options for identifying how the location relates to the site. Descriptions should be
provided to give additional details of the relevance of the location.
October 5, 2010
Page A‐22
Appendix A – Database User’s Guide
Figure 16: Other Locations Tab
October 5, 2010
Page A‐23
Appendix A – Database User’s Guide
3.4 Monitoring Locations and Data
For the purposes of the Tahoe Stormwater and BMP Performance Database, monitoring locations are
entities that belong to either a BMP Site record or a Stormwater Site record and have data associated
with those locations. A BMP Site record can have multiple water quality monitoring locations, each with
multiple datasets. A Stormwater Site record generally has a single water quality monitoring location,
but may have other monitoring locations, such as a weather station, associated with it. Before a
monitoring location can be defined, the coordinates and other attributes for that location must be
provided in Form A after creating either a BMP Site record (Section 3.2: Creating or Accessing a BMP
Site) or a Stormwater Site record (Section 3.3:Creating or Accessing a Stormwater Site).
After a BMP or Stormwater Site record has been created and associated location information provided,
click on the “Monitoring Location and Data” button to launch Form B. Form B presents a tabbed
interface with 4 sub‐forms arranged as tabs. Each tab provides a series of input controls located at the
top half with a data grid(s) displayed at the bottom half. The data grid allows the user to see what data
currently exists in the database and to visually confirm that new or edited data have been successfully
submitted to the database. Form B contains the following tabs or sub‐forms:
B1.
B2.
B3.
B4.
Monitoring Location Info
Runoff and Monitoring Events
Discrete Samples
Meteorologic Data
Data collected during a water quality monitoring event is classified as either being a composite or
discrete (grab) sample. Composite sub‐sample, or aliquots, are collected intermittently during a
monitoring event and combined before laboratory analysis (typically using a time‐weighted or volume‐
weighted compositing scheme). Composite data is submitted through “B2: Runoff and Monitoring
Events” tab. Discrete or grab samples are collected at instantaneous points in time and analyzed
individually. Discrete data are submitted through the Tab B3 of Form B, “Discrete Samples.” Water
quality grab samples or flow data collected as a time series record should be submitted as a group of
discrete samples. The common monitoring event number and sequential date and time values will allow
the database to link the individual records as part of the same dataset.
3.4.1 Monitoring Location Information
The first tab (Tab B1) of Form B allows a user to designate an existing location at the site that was
previously created in Tab A1 of Form A as a monitoring location. Only valid locations that have already
been defined in Form A are candidates for designation as monitoring locations. The monitoring location
type that defines where the monitoring is occurring (e.g., flume, monitoring well, weather station, etc.)
must also be provided. A detailed description of the location in the “Description” text box is not
required, but is highly recommended for future reference. Select the “Add New Monitoring Location” to
submit the new location to the database. Or if an existing monitoring location has been edited, select
the “Edit Current Monitoring Location” to submit changes to the location designation. Note that even
though the form displays the existing location name which was previously entered on Form A1, this
October 5, 2010
Page A‐24
Appendix A – Database User’s Guide
information cannot be edited on Tab B1 and can only be changed on Form A1 where it was originally
submitted.
Two data grids are shown on Tab B1. The first one shows all locations that are associated with the
current site and available for conversion into monitoring locations. The second data grid shows the
locations that have been designated as monitoring locations.
Figure 17: Monitoring Location Information
3.4.2 Runoff and Monitoring Events
The second tab (Tab B2) of Form B allows the user to define runoff events and then submit monitoring
data associated with those runoff events (Figure 18). Note: Runoff events must be defined individually
for each monitoring location. Begin in section “1a: Select Monitoring Location” to select a monitoring
location designated on Tab B1. monitoring data can be entered, a runoff event1 must be defined. Runoff
events may be defined in two ways:
1
Note that the more general term Runoff Event is used instead of Storm Event because other runoff events are
permissible. The valid Runoff Event types include: rain, rain‐on‐snow, event snowmelt, non‐event snow melt,
post‐event snowmelt, thunderstorm, baseline, and other.
October 5, 2010
Page A‐25
Appendix A – Database User’s Guide
1. One event at a time by entering the required information in section “2: Individual Runoff Events”
and then selecting “Create New Runoff Event.” Two optional fields are included: storm depth
and monitored volume. The storm depth is the total rainfall depth that occurred during the
sampling period. The monitored volume is the approximate percentage of the event estimated
to be sampled.
2. Several events at once by uploading to the database from a text file by clicking the “Import
Runoff Events from File” button. The text file can be generated using the macro‐enabled Excel
file template provided with the application. For best results, use Excel 2007 or later for editing
the Excel template. Both Excel 2007 and 2003 users should verify that macros are enabled and
that the template file is not opened as a read‐only file. If you get asked for a username and
password they are Tahoe1 and bluelake, respectively. If you have installed the application to
the default location, this template can be found at: C:\Program Files\Tahoe BMP
Database\FormB\Tahoe_FormB_templates.xlsm. Follow all instructions in the Excel file to
successfully create the tab‐delimited runoff event text file in the required format. The general
process for using the Excel template is:
a. The user enters the monitoring dataset into blue‐tabbed (B2a Runoff Event INPUT)
worksheet. Hover the cursor over column headings to identify the required data types.
b. The Excel spreadsheet tool automatically generates the properly formatted dataset for
upload in the green‐tabbed (B2a Runoff Event OUTPUT) worksheet based on the user
inputs. Users do not edit the green‐tabbed worksheets.
c. The user clicks the macro button on the green‐tabbed worksheet to export the data to a
text file.
d. If composite water quality data associated with the runoff events will also be uploaded
to the database either keep the Excel file open for later use (explained below) or save a
copy of it (preferably using a unique name) containing the runoff events data. If using
Excel 2007, save as a Macro‐Enabled Workbook.
3. To upload the text file data to the database, the user clicks the “Import Runoff Events from File”
button on Tab B.2 and navigates to the saved text file.
4. A data preview grid (Figure 19) will pop‐up that displays the data that will be entered into the
database. If the runoff events data were successfully read in from the text file click “Confirm
Data Submission”. If data appear incorrect, click “Cancel Data Submission” and return to the
Excel file template to ensure data were entered correctly then recreate the text file.
Runoff events that have been successfully submitted to the database appear in a grid in the middle of
the form. Uploaded runoff events may be edited one at a time by selecting an event using “1b: Select
Runoff Event to Edit” drop down menu and then editing the fields in the “2: Individual Runoff Events”
section. Once changes have been made to a runoff event, the user must select the “Submit Edits to
Runoff Event” button to commit the changes to the dataset.
Once runoff events are defined, composite water quality data associated with those events can be
uploaded to the database. Composite data can only be uploaded to the database in bulk using the
“Import Composite Data” button. To begin, select a monitoring location in section “1a: Select
October 5, 2010
Page A‐26
Appendix A – Database User’s Guide
Monitoring Location”. Note: you may have to reselect a monitoring location after entering runoff events
data to reactivate the form. The process for uploading composite data is as follows:
1. Click the “Import Runoff Events from File” button to upload composite data associated with
previously defined runoff events. The text file can be generated using the macro‐enabled Excel
file template provided with the application. Follow all instructions in the Excel file to
successfully create the tab‐delimited composite data text file in the required format. The
general process for using the Excel template is:
a. The user enters the monitoring dataset into blue‐tabbed (B2b Composite Data INPUT)
worksheet. Hover the cursor over column headings to identify the required data types.
Unique storm event IDs from the previously entered runoff events are available for drop
down selection in the first column. These IDs are based on the year, month, day, and
hour of the start event. Permissible parameter names are also provided in a drop down
menu for the second column.
b. The Excel spreadsheet tool automatically generates the properly formatted dataset for
upload in the green‐tabbed (B2b Composite Data OUTPUT) worksheet based on the user
inputs. Users do not edit the green‐tabbed worksheets.
c. The user clicks the macro button on the green‐tabbed worksheet to export the data to a
text file.
2. To upload the text file data to the database, the user clicks the “Import Composite Data from
File” button on Tab B.2 and navigates to the saved text file.
3. A data preview grid will pop‐up that displays the data that will be entered into the database. If
the runoff events data were successfully read in from the text file click “Confirm Data
Submission”. If data appear incorrect, click “Cancel Data Submission” and return to the Excel file
template to ensure data were entered correctly then recreate the text file.
After selecting the appropriate text file for upload, a data preview grid (Figure 19) will pop‐up that
displays the data that will be entered into the database. If the composite data were successfully read in
from the text file and appear correct click “Confirm Data Submission.” If data appear incorrect, click
“Cancel Data Submission” and return to the Excel file template to ensure data were entered correctly
and then recreate the text file. The Composite Data grid at the bottom of the form will be populated
with the newly entered data if the upload was successful. Warning: Composite Data successfully
uploaded to the database cannot be modified. Contact the database administrator if you need to delete
an uploaded composite water quality dataset.
October 5, 2010
Page A‐27
Appendix A – Database User’s Guide
Figure 18: Runoff Events and Monitoring Events
Figure 19: Import Data Preview Form.
October 5, 2010
Page A‐28
Appendix A – Database User’s Guide
3.4.3 Discrete Samples
The third tab (Tab B3) of Form B allows the user to submit discrete sample data (Figure 20). The
“Discrete and Time Series Data” group box contains input fields that allow the user to select the
monitoring location where the data were collected and import discrete water quality data or time series
data. To begin, select a previously defined monitoring location from the “Monitoring Location” drop
down menu and then click “Import Discrete or Time Series Data” button to navigate to a formatted data
text file. Discrete sample data and time series data text files can be generated using the macro‐enabled
Excel file template for generating properly formatted tab‐delimited text files for upload to the database.
If you have installed the application to the default location, this template can be found at: C:\Program
Files\Tahoe BMP Database\FormB\Tahoe_FormB_templates.xlsm. The general process for using the
Excel template is:
1. The user enters the monitoring dataset into blue‐tabbed (B3 Discrete Data INPUT) worksheet.
Hover the cursor over column headings to identify the required data types. Permissible
parameter names are also provided in a drop down menu for the second column.
2. The Excel spreadsheet tool automatically generates the properly formatted dataset for upload in
the green‐tabbed (B3 Discrete Data OUTPUT) worksheet based on the user inputs. Users do not
edit the green‐tabbed worksheets.
3. The user clicks the macro button on the green‐tabbed worksheet to export the data to a text
file.
To upload data, click on “Import Discrete or Time Series Data” button. This action will open a file browser
dialog and allow the user to select the tab‐delimited discrete data text file generated as described
above. After selecting the appropriate text file for upload, a data preview screen appears that
summarizes the data from the imported text file (Figure 21). The data may be reviewed and edited prior
to submitting to the database. If the data appear correct, click on the “Confirm Data Submission” button
to commit the data to the database. If data appear incorrect, click “Cancel Data Submission” and return
to the Excel file template to ensure data were entered correctly and then recreate the text file and
repeat the above steps. After confirming the data submission, a preview of the data uploaded will be
shown in the data grid located on the bottom of Tab B3. Warning: Discrete Data successfully uploaded
to the database cannot be modified. Contact the database administrator if you need to delete an
uploaded discrete dataset.
October 5, 2010
Page A‐29
Appendix A – Database User’s Guide
Figure 20: Discrete Sample Data Form
Figure 21: Discrete Data Import Preview Form
October 5, 2010
Page A‐30
Appendix A – Database User’s Guide
3.4.4 Meteorologic Data
The fourth tab (Tab B4) of Form B allows the user to submit meteorologic data (Figure 22) associated
with a previously defined monitoring location. For example, a location defined in Form A, “A5: Other
Locations” may be designated as a monitoring location on Form B1 with the type set to “weather
station.” Once the monitoring location is defined, it can be selected on Form B4 and then
meteorological data associated with that location can be imported using the “Import Meteorological
Data” button. Meteorological data can be generated using the macro‐enabled Excel file template for
generating properly formatted tab‐delimited text files for upload to the database. If you have installed
the application to the default location, this template can be found at: C:\Program Files\Tahoe BMP
Database\FormB\Tahoe_FormB_templates.xlsm. Follow all instructions in the Excel file to successfully
create the tab‐delimited composite data text file in the required format. The general process for using
the Excel template is:
1. The user enters the monitoring dataset into blue‐tabbed (B4 Met Data INPUT) worksheet. Hover
the cursor over column headings to identify the required data types. Permissible parameter
names are also provided in a drop down menu for the second column.
2. The Excel spreadsheet tool automatically generates the properly formatted dataset for upload in
the green‐tabbed (B4 Met Data OUTPUT) worksheet based on the user inputs. Users do not edit
the green‐tabbed worksheets.
3. The user clicks the macro button on the green‐tabbed worksheet to export the data to a text
file.
To upload data, click on the “Import Meteorological Data” button. This action will open a file browser
dialog and allow the user to select the tab‐delimited meteorological data text file generated as
described above. After selecting the appropriate text file for upload, a data preview grid will pop‐up that
displays the data that will be entered into the database. If the meteorological data were successfully
read in from the text file and appear correct click “Confirm Data Submission.” If data appear incorrect,
click “Cancel Data Submission” and return to the Excel file template to ensure data were entered
correctly and then recreate the text file. The grid at the bottom of the form will be populated with the
newly entered data if the upload was successful. A data successfully uploaded to the database is shown
in the data grid located at the bottom half of the form. Warning: meteorological data successfully
uploaded to the database cannot be modified. Contact the database administrator if you need to delete
an uploaded dataset.
October 5, 2010
Page A‐31
Appendix A – Database User’s Guide
Figure 22: Meteorological Data Upload Form
3.5 Ancillary BMP Information
In addition to monitoring data, the Tahoe Stormwater and BMP Performance Database accepts ancillary
BMP information, including cost and maintenance data, design information, and references to relevant
documents. The steps necessary to upload this ancillary BMP information are described below.
3.5.1 Cost and Maintenance Data
Each BMP Site Record may have associated cost and maintenance data. Assuming you have already
created and selected a BMP Site Record and the “C: Cost and Maintenance Data” button on the
database manager (Form 1.0) form is enabled, click on this button to load up Form C. Form C presents a
tabbed interface with 2 sub‐forms or tabs. Each tab provides a series of input controls located at the
top half with a data grid displayed at the bottom half. The data grid allows the user to visually confirm
that new or edited data have been successfully submitted to the database.
Cost Data (Tab C1)
The first tab (Tab C1) of Form C allows the user to store the capital and maintenance costs associated
with the installation and successful operation of stormwater BMPs (Figure 23). To begin entering cost
data for the current BMP shown at the top of the form (recall this was selected on the database
manager form), select an available agency for which the cost data should be attributed to. The “Capital
October 5, 2010
Page A‐32
Appendix A – Database User’s Guide
Costs” group box near the top of the form allows users to enter the engineering design and construction
costs for the current BMP. The current BMP would have been previously selected on the main control
form (Form 1.0) prior to accessing the Cost Data form. The “Intermittent Costs” group box allows users
to enter any irregular costs associated with the BMP, such as repairs that are not associated with regular
maintenance. The “Annual Average Costs” group box contains inputs for specifying annual operation
and maintenance costs as well as monitoring costs. Users must click on the “Submit Cost Data from
Form” button to commit their entries to the database. The grid located at the bottom half of the forms
shows the newly added entries.
To edit existing cost data, select the “Edit Existing” radio button and select a cost batch ID from the drop
down. A cost batch is the batch of data submitted during an initial database submittal event. The ID can
be found in the data grid at the bottom of the form. After the data are edited, select the “Edit Cost Data
on Form” button to submit the edited database.
Figure 23: BMP Cost Records Form
October 5, 2010
Page A‐33
Appendix A – Database User’s Guide
Maintenance Data (Tab C2)
The second tab (Tab C2) of Form C allows the user to document maintenance activities performed at a
BMP site. The date of the maintenance activity, and the type of maintenance selected are entered using
a calendar control and a drop down combo box respectively. Users are encouraged to provide a good
description of the location, the activity as well as the yield (waste material removed) in the “Location
Description,” “Activity Description,” and the “Yield Description” input fields respectively. Users must click
on the “Submit Data from Form” button to commit their entries to the database. The grid located at the
bottom half of the form shows the newly added entries.
To edit existing cost data, select the “Edit Existing” radio button and select a batch record ID from the
drop down. A batch record is the batch of data submitted during an initial database submittal event.
The ID can be found in the data grid at the bottom of the form. After the data are edited, select the
“Edit Data on Form” button to submit the edited database.
October 5, 2010
Page A‐34
Appendix A – Database User’s Guide
Figure 24: BMP Maintenance Data
3.5.2 Documents and Design Information
One of the ultimate goals of the Tahoe Stormwater and BMP Performance Database is to be able to link
BMP performance to design attributes. To that end, the database includes data entry fields specific to
each BMP type for capturing BMP design information. In addition, each BMP site may have files and
documents with detailed information including CAD design files, photographs of construction and
maintenance activities, GIS files, etc. associated with the site. These files and documents associated
with a BMP site can be summarized and referenced in the database. Assuming you have already created
a BMP Site Record (or selected one to edit) and the “Documents and Design Information” button on
October 5, 2010
Page A‐35
Appendix A – Database User’s Guide
“Monitoring Data and Information Manager” is enabled, click on this button to load up Form D. Form D
presents a tabbed interface with 2 sub‐forms or tabs as described below.
Document Upload (Tab D1)
The first tab (Tab D1) of Form D allows the user to upload files associate with a BMP Site (Figure 25). The
user can provide a file name and then classify the file using the “Document Type” and “File Type” drop
down lists. The user is encouraged to provide a detailed description of the contents of the file in the
“File Description” input field. The source agency and the agency contact associated with the file should
also be provided so users may request any of the specific files referenced for the BMP. Users must click
on the “Submit Document Info” button to commit their entry to the database. The grid located at the
bottom half of the forms shows the newly added entry.
Figure 25: Site Documents Reference Form
Design Specifications (Tab D2)
The second tab (Tab D2) of Form D allows the user to submit BMP design information. Relevant physical
attributes and dimensions of structural BMPs currently considered as the most important in terms of
influencing BMP performance are provided in the data grid. Design components and associated
parameters are included in the grid along with a column indicating whether the data are required or not.
Initially the Design Value field contains “NULL” values that the users overwrite with alpha‐numeric
October 5, 2010
Page A‐36
Appendix A – Database User’s Guide
quantities according to the units for each parameter. The user must click the “Submit Design Values”
button to commit changes to the database.
Figure 26: BMP Documents and Design Information (Tab D2: Design Specifications) Form
3.6 Querying Raw Data
Accessing the data stored in the database is a simple process that begins on the main control from
(Form 1.0) with the user first selecting the “Site Type” as either a Stormwater site or a BMP site and
then clicking on the “Query Raw Data” button (see Figure 3). This action launches the “Query Data” form
shown in Figure 27. The type of data to be queried must first be selected along with the start and end
October 5, 2010
Page A‐37
Appendix A – Database User’s Guide
dates. The form also provides a series of filters including “BMP Type”, “Site” name, and “TRPA
Watershed”. The selections made under each of the filters are used to generate a SQL query statement
which is shown in an editable text area. Advanced users can edit the generated SQL query to further
customize the dataset that will be returned from the database. For non‐advanced users, the user
interface simplifies query creation by showing table names as well as table field names and allowing
users to retrieve data from multiple related tables without needing to know the SQL syntax needed to
perform these operations.
After making their selection and optionally editing the generated query, the user clicks the “Submit SQL
Statement” button to submit the query to the database. The results returned from the database are
shown in the data grid which occupies the bottom half of the “Data Retrieval Form.” To export the data
contained in the grid select the “Export Selected Data” button to save a tab‐delimited text file that can
be readily opened in a text editor or a spreadsheet program for analysis.
Figure 27: Data Retrieval Form
October 5, 2010
Page A‐38
Appendix A – Database User’s Guide
3.7 Accessing Statistical Summary Reports
Statistical data summary reports are periodically prepared for studies with adequate data for
informative analyses. These summary reports can be accessed by first selecting first selecting the “Site
Type” as either a Stormwater site or a BMP site and then clicking on the “Download Data Summaries”
button (see Figure 3). This action launches the user’s default web browser and displays the internet
location containing the summary reports.
October 5, 2010
Page A‐39
Appendix B
Tahoe Stormwater and BMP Performance Database
Database Structure and Specifications
October 5, 2010
Table of Contents
1
Introduction ......................................................................................................................................... 1
1.1
2
The Lookups Hierarchy ...................................................................................................................... 1
2.1
2.2
3
Dominant Tables ......................................................................................................................... 1
First‐Level Dependent Tables .................................................................................................... 2
The Agencies Hierarchy ...................................................................................................................... 2
3.1
3.2
4
Tables within the Database ........................................................................................................... 1
Dominant Table ........................................................................................................................... 3
First‐Level Dependent Tables .................................................................................................... 3
The Sites Hierarchy ............................................................................................................................. 3
4.1
4.2
4.3
4.4
4.5
Dominant Table ........................................................................................................................... 4
First‐Level Dependent Tables .................................................................................................... 4
Second‐Level Dependent Tables ................................................................................................ 7
Third ‐Level Dependent Tables .................................................................................................. 8
Database Relationship Diagram ................................................................................................. 9
October 5, 2010
Appendix B ‐ Database Structure and Specifications
1 Introduction
The Tahoe Stormwater and BMP Performance Database is hosted at the corporate headquarters of
Geosyntec Consultants in Boca Raton, FL. The server hardware runs Microsoft SQL Server 2005 and
backups are created nightly with weekly archives stored on physical media.
1.1 Tables within the Database
The Tahoe Database is a relational database comprised of several data tables and a handful of lookup
tables. The lookup tables are generally static in nature and improve performance and maintain relational
integrity of the database by providing a central location to store the large numbers of values that would
otherwise need to be replicated across many records or even tables. In total, there are four lookup
tables (lookup, TRPA, Parameter, and DesignCompPar) and 18 data tables. In a very broad sense, the
structure of the database reveals three main hierarchies of tables: the lookups, agencies, and sites.
While conceptually distinct, the three hierarchies relate to each other via foreign key constraints.
The subsequent sections of this appendix will explicitly outline the structure of the three hierarchies and
their tables. In doing so, the ways in which the hierarchies are interrelated will also be revealed. Users
knowledgeable with the Structured Query Language (SQL), specifically Microsoft’s Transact‐SQL, will be
able to use the database design to customize the stock queries available in the Data Retrieval section of
the application. Additionally, advanced users will be able to create fully‐customized queries from
scratch, selecting and filtering columns from any number of tables.
2 The Lookups Hierarchy
The lookups hierarchy of tables is a collection of four static tables that feed often repeated values into
other tables in the database.
2.1 Dominant Tables
The first dominant table in the Lookups Hierarchy is named lookup. It contains four columns defined
below.
lookup table columns:
• code – integer, primary key
• val1 – text, primary and short display value for the entry
• val2 – text, secondary and longer definition value for the entry
• rel – integer, column that allows this table to relate to itself in queries
Some examples of the values contained in lookup include the types of sites stored in the database, units
of measure, BMP types, and storm event type. In some instances, this table can relate to itself via the rel
column. An example of this would be the lookup values for BMP subtypes, which relate to the lookup
values for BMP types.
October 5, 2010
Page B‐1
Appendix B ‐ Database Structure and Specifications
Another table, TRPA, stores IDs, areas, and the name of each TRPA priority watershed in the Lake Tahoe
Basin. No other tables in the lookup hierarchy depend on it.
TRPA table columns:
• trpaID – integer, sequence, primary key
• trpaName – text, name of the watershed
• priority – integer, the TRPA‐defined priority of the watershed
• acreage – double, total area in acres of the watershed
2.2 First­Level Dependent Tables
There are two first‐level dependent tables in the lookup hierarchy. The first is the Parameter table which
stores information on the monitoring parameters in the database.
Parameter table columns:
• pID – integer, primary key
• pName – text, name of monitored quantity
• pUC – integer, references lookup, defines the units of measure of the parameter
• pGID – integer, references lookup, defines the general category of the parameter
The second first‐level dependent table in the lookup hierarchy, DesignCompPar, houses the various
design components and parameters that comprise various BMP types.
DesignCompPar table columns:
• dcpID – integer, sequence
• dcCode – integer, primary key, references lookup, defines a general design component
• dpCode – integer, primary key, references lookup, defines a specific parameter of a design
component
• btCode – integer, primary key, references lookup, defines the BMP type to which dcCode and
dpCode apply
• req – boolean, defines a design parameter as required or optional
3 The Agencies Hierarchy
The Agencies Hierarchy of the database stores information on the various groups and individuals
involved in the design, construction, and monitoring of BMP and stormwater sites. Additionally,
information regarding an agency’s role at a particular site can be stored.
October 5, 2010
Page B‐2
Appendix B ‐ Database Structure and Specifications
3.1 Dominant Table
The dominant table of this hierarchy is the AgencyInfo table. This is where the most basic information
about an agency is stored.
AgencyInfo table columns:
• agID – integer, sequence, primary key
• agName –text, name of agency
• address – text, street address of agency
• city – text, city where agency is located
• state – text, state where agency is located
• zip – text, zip code where agency is located
• phone – text, phone number of the agency
• url – text, web address of the agency
• descr – text, general description of the agency
3.2 First­Level Dependent Tables
Two first‐level dependent tables complete this hierarchy of the database. They are AgencyRoles and
ContactInfo and relate agencies from the AgencyInfo table to BMP or stormwater sites and to individual
contacts, respectively.
AgencyRoles table columns:
• agID – integer, primary key, references AgencyInfo
• sID – integer, primary key, references SiteInfo
• agCode – integer, primary key, references lookup, defines roles of the agency with respect to
the site
ContactInfo table columns:
• cID – integer, sequence, primary key
• agID – integer, references AgencyInfo
• name – text, name of contact
• email – text, email address of contact
4 The Sites Hierarchy
The final hierarchy of the database, the sites hierarchy, differs from the other two in that it is
considerably larger with 15 tables and much more complex with three additional levels branching off
from the dominant table, SiteInfo. It is in this hierarchy where a site’s basic information, design
specifications, cost and maintenance data, and most importantly, monitoring data are stored.
October 5, 2010
Page B‐3
Appendix B ‐ Database Structure and Specifications
4.1 Dominant Table
The table SiteInfo is the dominant table of the sites hierarchy and of the whole database. It stores the
most rudimentary information about stormwater and BMP sites.
SiteInfo table columns:
• sID – integer, sequence, primary key
• sName – text, name of the site
• stCode – integer, references lookup, distinguishes BMP/Stormwater sites
• trpaID – integer, references TRPA, defines watershed of site
• bt – integer, references lookup, defines type of BMP if applicable
• bst – integer, references lookup, defines subtype of BMP if applicable
• numInlets – integer, number of inlets leading to site
• numOutlets – integer, number of outlets draining away from site
• dateInstalled – date, date of installation of BMP or monitoring equipment
• metGrid – integer, relevant metGrid
• metStationID – integer, not used
• hDatum – integer, references lookup, horizontal survey datum of site's coordinates
• vDatum – integer, references lookup, vertical survey datum of site's elevation
• descr – text, general notes on the site
• created – date/time, date the site was first entered into the database
• modified – date/time, date of the last modifications of the site's info
4.2 First­Level Dependent Tables
The first‐level dependent tables in the sites hierarchy all relate to the SiteInfo table via the sID column.
The Location table defines locations by their coordinates, relationship to the BMP or stormwater site
(e.g., centroid, inlet, outlet), and the site to which it is related.
Location table columns:
• locID – integer, sequence, primary key
• sID –integer, references SiteInfo
• lat – double, latitude of location
• long – double, longitude of location
• elev – double, elevation of location
• descr – text, general notes on the location
• BMPRelaCode – integer, references lookup, specifies the relationship of the location to its site
(applies to both stormwater and BMP sites)
October 5, 2010
Page B‐4
Appendix B ‐ Database Structure and Specifications
The DrainageArea table stores basic information describing the tributary area to an inlet of a site. When
the Tahoe Database application is used to create a record in DrainageArea, a corresponding record is
simultaneously created in Location to describe the inlet itself.
DrainageArea table columns:
• daID – integer, sequence
• sID – integer, primary key, references SiteInfo
• inletNo – integer, primary key, inlet number (i.e., 1, 2, ... , SiteInfo.numInlets)
• locID – integer, references Location
• acreage – double, total tributary area (in acres) draining to inlet
• Slope – double, average percent slope of the tributary area
• IMP – double, area (in acres) with impervious cover
• DCIA – double, area (in acres) with directly connected impervious area
• flag – integer, number of errors in the relationship between acreage, IMP, DCIA, and the
corresponding values in LandUse
The BMPOutlets table stores information regarding the outlets draining away from a stormwater site or
BMP. Similar to the DrainageArea table, creating an outlet for a site will populate this table and
simultaneously create a record in the Location table.
BMPOutlet table columns:
• outletID – integer, sequence
• sID – integer, primary key, references SiteInfo
• outNo – integer, primary key, outlet number (i.e., 1, 2, ... , SiteInfo.numOutlets)
• locID – integer, references Location
• outletCode – integer, references lookup, defines the type of outlet
The CostBatch table store simple cost information such as the site to which the data relate and the
agency that paid for the costs. This applies only to BMPs
CostBatch table columns:
• costID – integer, sequence, primary key
• sID – integer, references SiteInfo
• agID – integer, references AgencyInfo
October 5, 2010
Page B‐5
Appendix B ‐ Database Structure and Specifications
Information regarding the maintenance of BMPs is stored in the Maintenance table.
Maintenance table columns:
• mntID –integer, sequence, primary key
• sID –integer, references SiteInfo
• agID – integer, references AgencyInfo
• mntDT – date, date and time that maintenance was performed
• mntCode –integer, references lookup, defines the type of maintenance performed
• actDescr –text, general description of the maintenance performed
• locDescr – text, describes the general area in which the maintenance occurred (e.g., cleared the
inlet)
• yieldDescr – text, results of the maintenance (e.g., 5 lbs of sediment removed from inlet)
• ramScore – integer, standard RAM Score of the BMP at time of maintenance
The design of a BMP is stored in the Design table.
Design table columns:
• desID –integer, sequence, primary key
• sID – integer, references SiteInfo
• dcpID – integer, references DesignCompPar, defines the design parameter
• dValue – text, value of the design parameter
Lastly, information pertinent to acquiring documents about a BMP is housed in the Document table.
Document table columns:
• docID –integer, sequence, primary key
• sID –integer, references SiteInfo
• cID – integer, references ContactInfo
• dCode –integer, references lookup, defines the type of document
• fCode –integer, references lookup, defines the type of file
• fname – text, name of the file
• descr – text, general description of the file
• url – text, web address of the file, if available.
October 5, 2010
Page B‐6
Appendix B ‐ Database Structure and Specifications
4.3 Second­Level Dependent Tables
These second‐level dependent tables all relate to the SiteInfo table through an intermediate first‐level
dependent table. These tables extend the information contained in the first‐level table to which they
relate.
The MonitoringLocations table is used to extend properties of existing locations in the Location table as
they relate to the monitoring of stormwater. This relationship is structured in such a way that multiple
monitoring stations can exist at a single location.
MonitoringLocations table columns:
• monlocID – integer, sequence, primary key
• locID –integer, references Location
• mltCode –integer, references lookup, defines the type of monitoring location
• descr – text, general description of the monitoring location
The LandUse table extends the DrainageArea table by providing a statistical breakdown of predefined
landuse types contained within a drainage area.
LandUse table columns:
• luID – integer, sequence
• luCode – integer, primary key, references lookup, defines the landuse type
• daID – integer, references DrainageArea
• Area – double, total area (in acres) draining to inlet of luCode's landuse type
• IMP –double, area (in acres) of luCode's landuse type with impervious cover
• DCIA – double, area (in acres) of luCode's landuse type with directly connected impervious area
The Costs table contains the specific information of each record in the CostBatch table.
Costs table columns:
• costID – integer, primary key, references CostBatch
• costCode – integer, primary key, references lookup, defines the nature of the cost
• amount – double, the amount paid
• cdate –date, the date the cost was paid
• descr – general description of the cost
October 5, 2010
Page B‐7
Appendix B ‐ Database Structure and Specifications
4.4 Third ­Level Dependent Tables
All third‐level dependent tables contain actual monitoring and ultimately relate to the SiteInfo table via
the monlocID column of MonitoringLocations.
The StormEvent table includes all of the information regarding the collection of composite data during a
runoff or storm event. A second table, CompositeEvent, actually stores the composite data and could
technically be considered a fourth‐level dependent table, but is included in this section for convenience.
CompositeEvent relates to StormEvent through each storm event’s ID.
StormEvent table columns:
•
seID – text, primary key, constructed from seUserID and monlocID
•
seUserID – text, user‐defined name of the storm for their reference
•
seCode – integer, references lookup, defines type of storm
•
monlocID – integer, references MonitoringLocations
•
runoffStart – date/time, date and time runoff starts
•
runoffEnd – date/time, date and time runoff ends
•
monStart – date/time, date and time monitoring starts
•
monEnd – date/time, date and time monitoring ends
•
stormDepth – double, vertical depth in inches of rainfall
•
monVol – double, percentage of runoff volume monitored during event
•
descr – text, general description of the storm and/or sample compositing procedure
CompositeEvent table columns:
• cmpID – integer, sequence
• seID – integer, primary key, references StormEvent
• pID – integer, primary key, references Parameters
• pValue – double, value of the parameter defined by pID
• flag – text, any laboratory or QA/QC flags qualifying the pValue
• detLimit – double, detection limit of the parameter defined by pID
• repLimit – double, reporting limit of the parameter defined by pID
October 5, 2010
Page B‐8
Appendix B ‐ Database Structure and Specifications
The DiscreteEvent table stores grab sample/discrete datasets for which is there no corresponding storm
event. Each record contains all of the relevant sampling information.
DiscreteEvent table columns:
• disID – integer, sequence
• monlocID – integer, primary key, references MonitoringLocations
• disDT – date/time, primary key, date and time of sampling
• pID – integer, primary key, references Parameters
• pValue – double, value of the parameter defined by pID
• flag – text, any laboratory or QA/QC flags qualifying the pValue
• detLimit – double, detection limit of the parameter defined by pID
• repLimit – double, reporting limit of the parameter defined by pID
Lastly, meteorological time series data is stored in the table MetTS.
MetTS table columns:
• metID – integer, sequence
• monclocID – integer, primary key, references MonitoringLocations
• metDT – date/time, primary key, date and time of meteorological observation
• pID – integer, primary key, references Parameter, defines the parameter measured
• pVal – values of the measured parameter
4.5 Database Relationship Diagram
October 5, 2010
Page B‐9
Appendix B ‐ Database Structure and Specifications
pName
pID
Parameter
pUC
pGID
pLong
pShort
metDT
monlocID
metID
MetTS
pID
seID
monlocID
disID
DiscreteEvent
disDT
seUserID
StormEvent
pCode
pVal
detLimit
pUnitCode
flag
runoffEnd
runoffStart
monlocID
seCode
repLimit
detLimit
flag
pValue
pID
seID
monlocID
cmpID
CompositeEvent
repLimit
monStart
pValue
lookup
locID
sID
lat
long
elev
descr
BMPRelaCode
SSMA_TimeStamp
priority
trpaName
acreage
sID
costID
CostBatch
agID
descr
mltCode
locID
sID
monlocID
SSMA_TimeStamp
MonitoringLocations
monEnd
descr
cdate
amount
costCode
costID
Costs
modified
created
descr
vDatum
hDatum
metStationID
metGrid
dateInstalled
numOutlets
numInlets
bst
bt
trpaID
stCode
sName
sID
SiteInfo
Location
stormDepth
SSMA_TimeStamp
flag
DCIA
IMP
Slope
acreage
inletNo
locID
sID
daID
monVol
outletID
sID
locID
outNo
outletCode
agID
agName
cID
trpaID
code
DrainageArea
TRPA
descr
luID
luCode
agCode
sID
agID
val1
BMPOutlets
AgencyRoles
val2
LandUse
daID
Area
IMP
DCIA
Document
docID
sID
cID
dCode
fCode
fname
descr
url
sID
desID
Design
dcpID
dValue
sID
mntID
Maintenance
AgencyInfo
rel
DesignCompPar
dcpID
dcCode
contactName
dpCode
agID
name
agID
email
btCode
ContactInfo
state
address
zip
city
phone
mntDT
actDescr
url
mntCode
locDescr
req
yieldDescr
descr
ramScore
Page B‐10
October 5, 2010
Appendix C
Tahoe Stormwater and BMP Performance Database
Treatment BMP Design Parameters
October 5, 2010
Appendix C – Treatment BMP Design Parameters
Tables C1 through C5 list key design parameters for specific stormwater treatment BMPs and indicate whether the associated inputs in the BMP database are
required or optional. A user must provide a value for a required input parameter whenever the relevant design component is included. Optional parameters
are not required, but are beneficial for future BMP performance analyses.
Table C1. Key Design Parameters for Dry Basins.
Design
Component
Inlet Works /
Pretreatment
Forebay /
Presettling
Basin
Storage
Volume
Vegetation
Soils /
Subsurface
Outlet Works
Design Parameter/Attribute
Units
User
Input
Description
Treatment diversion flow, if offline
cfs
Optional
Pretreatment devices
n/a
Optional
Forebay included? Yes/no
n/a
Required
Flow splitter design flow rate for which all higher flows bypass the basin
List of devices separated by commas (e.g., trash rack, hydrodynamic device,
sedimentation manhole)
Presence/absence of forebay or presettling basin
Volume
cu‐ft
Optional
Total volume of forebay/presettling basin below overflow berm/outlet
Depth
ft
Optional
Average depth of forebay/presettling basin
Extended detention design volume
cu‐ft
Required
Volume of basin below spillway/overflow outlet
Extended detention design depth
ft
Required
Average depth of basin below spillway/overflow outlet
Drain time when full (at design depth)
hr
Required
Drawdown time for complete extended detention design volume
Drain time half full to empty
hr
Required
Drawdown time for bottom 50% of extended detention design volume
Top surface area
sq‐ft
Optional
Surface area of basin at design depth
Bottom surface area
sq‐ft
Optional
Excluding side slopes
Length to width ratio (at mid‐depth)
unitless
Optional
Approximate length to width ratio at mid design depth
Vegetative cover
%
Optional
Percent of basin area (projected from top surface area) covered by vegetation
Vegetation description
n/a
Optional
Narrative description of vegetation types and density on bottom and side slopes
Basin infiltration rate
in/hr
Required
Approximate infiltration rate of soils beneath basin
Depth to groundwater
ft‐bgs
Optional
Outlet type(s)
n/a
Required
Micropool? Yes/no
n/a
Optional
Depth below basin bottom to seasonal high groundwater table
List of outlets separated by commas (e.g., perforated riser, orifice plate, broad
crested weir, etc.)
Presence/absence of small permanent pool near outlet
Stage‐discharge curve
n/a
Optional
Paired data set with stage (ft) and outlet discharge flow (cfs)
Outlet protection? Yes/no
n/a
Optional
Presence/absence of protected outlet structures/energy dissipation
October 5, 2010
Page C‐1
Appendix C – Treatment BMP Design Parameters
Table C2. Key Design Parameters for Wet Basins.
Design
Component
Inlet Works /
Pretreatment
Forebay /
Presettling
Basin
Permanent
Pool
Surcharge
Volume
Vegetation
Soils /
Subsurface
Outlet Works
Design Parameter/Attribute
Units
User
Input
Description
Treatment diversion flow, if offline
cfs
Optional
Pretreatment devices
n/a
Optional
Forebay included? Yes/no
n/a
Required
Flow splitter design flow rate for which all higher flows bypass the basin
List of devices separated by commas (e.g., trash rack, hydrodynamic device,
sedimentation manhole)
Presence/absence of forebay or presettling basin
Volume
cu‐ft
Optional
Total volume of forebay/presettling basin below overflow berm/outlet
Depth
ft
Optional
Average depth of forebay/presettling basin
Permanent pool volume
cu‐ft
Required
Average volume of permanent pool during wet season
Permanent pool surface area
sq‐ft
Required
Surface area of permanent pool during wet season
Pool area <12” deep
%
Optional
Percent of permanent pool area less than 1 foot deep
Pool area 12”‐24” deep
%
Optional
Percent of permanent pool area 1‐2 feet deep
Pool area 24”‐48” deep
%
Optional
Percent of permanent pool area 2‐4 feet deep
Pool area >48” deep
%
Optional
Percent of permanent pool area greater than 4 feet deep
Permanent pool length
ft
Optional
Flow length (at wet season depth) of permanent pool in primary direction of flow
Average wet season base flow
cfs
Optional
Estimated base flow during wet season
Extended detention design volume
cu‐ft
Required
Volume of basin above permanent pool and below spillway/overflow outlet
Extended detention design depth
ft
Required
Average depth above permanent pool and below spillway/overflow outlet
Drain time when full (at design depth)
hr
Required
Drawdown time for complete extended detention design volume
Drain time half full to empty
hr
Required
Drawdown time for bottom 50% of extended detention design volume
Top surface area
sq‐ft
Optional
Surface area of basin at design depth
Emergent vegetative cover
%
Optional
Percent of permanent pool with emergent vegetation
Wetland plant species description
n/a
Optional
Narrative description of wetland plant types and density within the permanent pool
Depth to groundwater
Soil type
ft‐bgs
n/a
Optional
Optional
Outlet type(s)
n/a
Required
Outlet protection? Yes/no
n/a
Optional
Depth below basin bottom to seasonal high groundwater table
NRCS soil survey soil map unit and description
List of outlets separated by commas (e.g., perforated riser, orifice plate, broad
crested weir, etc.)
Presence/absence of protected outlet structures/energy dissipation
October 5, 2010
Page C‐2
Appendix C – Treatment BMP Design Parameters
Table C3. Key Design Parameters for Infiltration Basins.
Design
Component
Inlet Works /
Pretreatment
Forebay /
Presettling
Basin
Storage
Volume
Soils /
Subsurface
Vegetation
Outlet Works
Design Parameter/Attribute
Units
User
Input
Description
Treatment diversion flow, if offline
cfs
Optional
Pretreatment devices
n/a
Optional
Forebay included? Yes/no
n/a
Required
Flow splitter design flow rate for which all higher flows bypass the basin
List of devices separated by commas (e.g., trash rack, hydrodynamic device,
sedimentation manhole)
Presence/absence of forebay or presettling basin
Volume
cu‐ft
Optional
Total volume of forebay/presettling basin below overflow berm/outlet
Depth
ft
Optional
Average depth of forebay/presettling basin
Storage volume of basin
cu‐ft
Required
Volume of basin below spillway/overflow outlet
Storage depth of basin
ft
Required
Average depth of basin below spillway/overflow outlet
Drain time when full (at design depth)
hr
Required
Drawdown time for complete design volume
Top surface area
sq‐ft
Optional
Surface area of basin at design depth
Bottom surface area
sq‐ft
Optional
Excluding side slopes
Basin infiltration rate
in/hr
Required
Design infiltration rate or field measured infiltration rate
Saturated hydraulic conductivity
in/hr
Optional
Saturated hydraulic conductivity of underlying soils
Soil type
n/a
Optional
NRCS soil survey soil map unit and description
Depth to impermeable layer
ft
Optional
If known, provide depth to impermeable layer
Depth to groundwater
ft‐bgs
Optional
Depth below basin bottom to seasonal high groundwater table
Vegetative cover
%
Optional
Percent of basin area (projected from top surface area) covered by vegetation
Vegetation description
n/a
Optional
Outlet type(s)
n/a
Required
Outlet protection? Yes/no
n/a
Optional
Narrative description of vegetation types and density on bottom and side slopes
List of outlets separated by commas (e.g., underdrain, perforated riser, orifice plate,
broadcrested weir, etc.)
Presence/absence of protected outlet structures/energy dissipation
October 5, 2010
Page C‐3
Appendix C – Treatment BMP Design Parameters
Table C4. Key Design Parameters for Treatment Vaults.
Design
Component
Inlet Works /
Pretreatment
Storage
Volume
Vault
configuration
Outlet Works
Design Parameter/Attribute
Units
User
Input
Description
Treatment diversion flow, if offline
cfs
Optional
Pretreatment devices
n/a
Optional
Storage volume in vault
cu‐ft
Required
Flow splitter design flow rate for which all higher flows bypass the basin
List of devices separated by commas (e.g., trash rack, hydrodynamic device,
sedimentation manhole)
Total volume of all chambers
Storage depth in vault
ft
Optional
Average storage depth of treatment chambers
Number of treatment chambers
n/a
Required
Type and configuration of chambers
n/a
Required
Minimum treatment flow rate
cfs
Optional
Maximum treatment flow rate
cfs
Required
Outlet type(s)
n/a
Required
Outlet protection? Yes/no
n/a
Optional
The quantity of separate treatment chambers
Description of each chamber or treatment component separated by commas going
from upstream to downstream (e.g., hydrodynamic separation, sedimentation,
floatables baffle, and sand filtration)
Minimum rate required for flow through treatment (e.g., hydrodynamic device may
need minimum)
Design treatment flow rate for entire system
List of outlets separated by commas (e.g., underdrain, perforated riser, orifice plate,
broadcrested weir, etc.)
Presence/absence of protected outlet structures/energy dissipation
October 5, 2010
Page C‐4
Appendix C – Treatment BMP Design Parameters
Table C5. Key Design Parameters for Cartridge Filters.
Design
Component
Inlet Works /
Pretreatment
Storage
Volume
Filter Media
Outlet Works
Design Parameter/Attribute
Units
User
Input
Description
Treatment diversion flow, if offline
cfs
Optional
Pretreatment devices
n/a
Optional
Storage volume in filter vault
cu‐ft
Required
Flow splitter design flow rate for which all higher flows bypass the filter
List of devices separated by commas (e.g., trash rack, hydrodynamic device,
sedimentation manhole)
Volume within cartridge vault
Depth in filter vault
ft
Optional
Average depth above bottom of filter cartridges and below spillway/overflow outlet
Maximum treatment flow of system
cfs
Required
Design treatment flow rate of filter (all cartridges combined)
Filter media type
n/a
Required
Media type for cartridges (e.g., perlite, compost, zeolite, polymer)
Number of filter cartridges
#
Required
Quantity of filter cartridges in vault
Filter cartridge configuration
n/a
Optional
Description of where filters are configured (e.g., manhole, catch basin, vault)
Outlet type(s)
n/a
Required
Outlet protection? Yes/no
n/a
Optional
October 5, 2010
List of outlets separated by commas (e.g., underdrain, perforated riser, orifice plate,
broadcrested weir, etc.)
Presence/absence of protected outlet structures/energy dissipation
Page C‐5
Appendix C – Treatment BMP Design Parameters
Table C6. Key Design Parameters for Bed Filters.
Design
Component
Inlet Works /
Pretreatment
Forebay /
Presettling
Basin
Storage
Volume
Filter Media
Soils /
Subsurface
Outlet Works
Design Parameter/Attribute
Units
User
Input
Description
Treatment diversion flow, if offline
cfs
Optional
Pretreatment devices
n/a
Optional
Forebay included? Yes/no
n/a
Required
Flow splitter design flow rate for which all higher flows bypass the basin
List of devices separated by commas (e.g., trash rack, hydrodynamic device,
sedimentation manhole)
Presence/absence of forebay or presettling basin
Volume
cu‐ft
Optional
Total volume of forebay/presettling basin below overflow berm/outlet
Depth
ft
Optional
Average depth of forebay/presettling basin
Storage volume above filter
cu‐ft
Required
Volume above filter surface and below spillway/overflow outlet
Depth above filter
ft
Required
Average depth above filter surface and below spillway/overflow outlet
Top surface area
sq‐ft
Optional
Surface area of basin at design depth
Bottom surface area
sq‐ft
Optional
Excluding side slopes
Maximum treatment flow
in/hr
Required
Design treatment flow rate of filter
Media type
n/a
Required
List of media types separated by commas included in filter (e.g., sand, compost, etc.)
Media depth
ft
Required
Design depth of media bed
D10
in
Optional
Grain size for which 10% of particles are finer by weight
D60
in
Optional
Grain size for which 60% of particles are finer by weight
Infiltration rate beneath underdrain
in/hr
Optional
Approximate infiltration rate of soils beneath filter bed if unlined
Soil type
n/a
Optional
NRCS soil survey soil map unit and description
Depth to groundwater
ft‐bgs
Optional
Outlet type(s)
n/a
Required
Outlet protection? Yes/no
n/a
Optional
Depth below filter bed to seasonal high groundwater table
List of outlets separated by commas (e.g., underdrain, perforated riser, orifice plate,
broadcrested weir, etc.)
Presence/absence of protected outlet structures/energy dissipation
October 5, 2010
Page C‐6
Appendix D
Tahoe Stormwater and BMP Performance Database
Monitoring and Analytical QA/QC
October 5, 2010
Appendix D ‐ Monitoring and Analytical QA/QC
The Database is designed to assemble information from a variety of sources, individuals and institutions, so it is
important that these data conform to consistent standards in sample collection, analysis and reporting. The Tahoe
Regional Storm Water Monitoring Program (RSWMP) has outlined preliminary requirements for a Quality
Assurance and Quality Control (QA/QC) program. The essential elements of this program are outline below as
relevant to the Database.
D.1 QUALITY CONTROL SAMPLES
Stormwater sampling should adhere to specific quality control (QC) procedures to ensure proper design,
implementation, and analysis. These QC procedures include field blanks and duplicates as well as the laboratory
quality control samples and standards as shown in Table D1. The analytic laboratory should be familiar with most
of these QC sample types.
Table D1. Recommended quality control samples and frequency.
Sample Type
Field duplicate
Field blank
Composite replicate
Method blank
Analytic replicate
Sample Frequency
Description
One per 5% of samples analyzed, or
at least one per event, rotate sites
One per event per 10 sites, rotate
sites
One per event per 10 sites, rotate
sites
One per 20 samples processed for
each analyte, or one per run
At least one per run for each
analyte, or 10% of samples
Collected as a manually triggered or grab sample
immediately following a normal sample
DI water deployed in standard field sample
container during event or pre‐event
Processing and creation of a replicate composite
sample at the laboratory
DI water passed through standard laboratory
sample processing procedure
Analytic blank
One per run for each analyte
Matrix spikes
At least one per run for each
analyte, or 10% of samples
SRM or QCS
One per run for each analyte
External audit
samples
Once per year
Internal audit
samples (RSWMP)
Six samples per year (minimum)
Split from sample added to analytic run
DI water passed through analytic procedure
with samples
Percentage recovery from spiked sample during
analytic run
Standard material from different source than
calibration standards, analyzed with samples
during analytic run
These samples are obtained from the US EPA or
other agencies with a QA/QC audit sample
program
These samples are prepared and distributed by
the RSWMP Technical Unit (See Section 14.3).
Field duplicates, field blanks, compositing replicates and sample processing blanks are generally the responsibility
of the monitoring group submitting samples for analysis. The exception is if samples are submitted directly to the
laboratory for event compositing, in which case the composite replicates and sample processing blanks will be
created at the analytic laboratory.
October 5, 2010
Page D‐1
Page D‐2 | A p p e n d i x D ‐ M o n i t o r i n g a n d A n a l y t i c a l Q A / Q C
Tahoe RSWMP personnel will periodically collect the QA/QC information and data from participating laboratories
and verify that appropriate methods and detection limits are used. Results from field and processing QC samples
should be submitted on a quarterly basis to RSWMP staff for programmatic assessment of data quality.
D.2 ANALYTIC METHODS AND REPORTING LIMITS
Concentrations of stormwater runoff and BMP effluent within the Lake Tahoe Basin can often be much lower than
typically observed from municipal stormwater monitoring at other locations around the country. These low‐level
analyte characteristics necessitate high quality laboratory standards and very low method detection limits. The
following table shows recommended analytic methods and reporting limits for analytes of concern. Note that lab‐
specific method detection limits can change over time and must always be less than the reporting limits.
Laboratory methods will be those that have been routinely used by Tahoe laboratories for analysis of LTIMP and
TMDL samples, with desired (target) reporting limits for these analytical methods as shown below (Table D2).
Note, however, that all analytic laboratories must achieve, or better, the maximum reporting limits listed. Any
analytic results below laboratory reporting limits are shown as non‐detects.
Table D2. Recommended analytic methods and reporting limits.
Analyte
Soluble Reactive
Phosphorus (or dissolved
orthophosphate as P)
Total Dissolved
Phosphorus as P
Total Phosphorus as P
Nitrate + Nitrite as N
Dissolved Ammonia as N
Methods
EPA 365.1; or EPA 365.2; or
EPA 365.3; or SM 4500‐P‐E
EPA 365.1 w/ USGS I‐4600‐85; or
EPA 365.2; or EPA 365.3; or SM 4500‐P‐F
EPA 365.1 w/ USGS I‐4600‐85; or
EPA 365.2; or EPA 365.3; or SM 4500‐P‐F
EPA 353.1; or EPA 353.2; or
SM 4500‐NO3‐F
EPA 350.1; or SM 4500‐NH3 H; or
SM 4500‐NH3‐D
Target
Reporting
Limit
Maximum
Reporting
Limit
1 µg/L
10 µg/L
1 µg/L
10 µg/L
1 µg/L
10 µg/L
1 µg/L
10 µg/L
1 µg/L
10 µg/L
Total Kjeldahl Nitrogen
EPA 351.1; or EPA 351.2
50 µg/L
100 µg/L
Total Suspended Solids
EPA 160.2; or SM 2540‐D
0.1 mg/L
1 mg/L
Suspended Sediment
Concentration
ASTM D3977
1 mg/L
10 mg/L
Turbidity
EPA 180.1; or SM 2130‐B
0. 1 NTU
1 NTU
Electrical Conductivity
EPA 120.1; or SM 2510‐B
1 µS/cm
1 µS/cm
pH
SM 4500‐H‐B or EPA 150.1
0.01
0.1
Particle Size Distribution
SM 2560
NA
NA
October 5, 2010
Page D‐2