PSMFC Homepage
HOME
StreamNet's home page StreamNet's mission, services, and participants Locate fish-related data StreamNet's largest data resource, regularly updated ("integrated" interface). StreamNet's largest data resource, regularly updated (traditional interface). Locate data from a map interface. Obtain maps and GIS layers. Locate static data sets. Also, add your data sets to the archive. A full service library containing fish and wildlife literature and reports. Various other useful materials Links to other fisheries related resources on the Web 2004 U.S. District Court ruling on pesticides near salmon streams Stream reaches where hydroelectric development is discouraged Information and data in support of the NPCC Fish and Wildlife program Documents, reports, and newsletters produced by the StreamNet project Recommendations on how to cite data and information obtained from StreamNet Various other useful materials The latest data, but in the old look.









WEB QUERY SYSTEM USER'S GUIDE

The StreamNet web query system is a powerful tool for locating, displaying and downloading data from the StreamNet database. The best way to learn how to use the query system is to try it. This User's Guide walks you through an example of how to use the query system to find information. Be sure to check out the General Guidelines and Tips at the end of this guide.

If you get lost or make a mistake you can always use your browser's Back button. By selecting New Query at the top of a page, any existing query will be cleared and you will be ready to start afresh.

If you experience problems in either accessing or using the StreamNet data, please contact StreamNet by clicking the "Contact us" button at the top of the page. We are happy to help!


Getting Started

Access the query system by clicking the Query the main database link on the left side of any StreamNet web page. The Select Criteria box comes up containing all of the criteria available. You may choose any combination of criteria for which information is available. Most criteria are one of four broad types:

Data category
Includes such things as fish distribution, adult returns, and maps.
Species/run
Such as Chinook salmon, spring run.
Geographic area
Such as state, subbasin, county, and stream.
Point feature
Such as a dam or hatchery.

 

If you are unsure of which criteria are appropriate for your needs, hover your mouse over the question marks next to each criterion for more information about that criterion.

The system queries the database each time a criterion is selected and returns only those remaining values that contain data. This prevents building a query that results in no data. If a value does not appear at a subsequent step, that means that there are no data of that type for the criteria you have already selected. For example, chum salmon will not appear in the species list if you have already selected State = Idaho, where chum salmon are not found.

The only criterion that is required is the Data Category. (This is the key thing you will need to know to use this system). You can select criteria in any order. In general, select the criterion that is of primary concern first and then narrow your search from there. For example, if you are interested in a specific kind of information, then choose Data Category first. If you are most interested in a specific species, select the Species of interest and then proceed to a geographic area, a data category, or other criterion. If instead you wish to view data for a given location, select the geographic area first. Select no more criteria than you need.


EXAMPLE

In the following step-by-step example we perform a data query starting with a geographic area. Let's say we know we want information for a specific Columbia River subbasin (as defined by NPCC in 2001 for subbasin planning purposes).

 1. First we click on the criterion "Columbia Subbasin 2001."

 

 2. Second we select a specific subbasin - you can click directly on the map, or select the subbasin from the list. Here we choose the John Day subbasin in central Oregon.

On the maps, green indicates data exist for that area.

 

3. The subbasin we selected is shown on the right side of the query box as we build our query. We see from the highlighted area under Your Criteria that we still must choose a Data Category before viewing any data, so letís do that now.

As each criterion is selected it appears under Your Criteria in the right side of the query box. You can remove a criterion by clicking the X for that criterion under Clear on the far right side of the query box.

 

4. The data category list contains only those categories for which data exist for the criteria already selected (in this case, for subbasin = John Day). We see there are 12 kinds of data available. We next click on the Data Category of interest. Let's examine an index of spawning population size by selecting Redd Counts. After selecting Data Category = Redd counts, we will also select Species = Chinook salmon and Run = spring.

 

5. After choosing our data category, species, and run, we see there are 26 "trends" available for spring run Chinook salmon redd counts in the John Day subbasin. (In the StreamNet query system, the term "Trend" is used informally to refer to a time series data set.) We now click on View Available Data to see our list of available data.

 

6. The page that comes up is the Trend List page. This page shows the basics for each trend such as location, species, and year range covered. We can view our data in a variety of ways. View information for an individual trend (time series) by clicking on its link. We can also see a Summary table for all the trends listed; see a Summary Graph for all the trends listed; or Download the data for all trends listed. These last three options are shown on the blue toolbar. First, let's click on Trend Number 52055.

 

7. After clicking on a trend number, in this case 52055, we see detailed information for that data set only, including each year's redd count. Several items are of interest on this page. The number of redds (in the Count column), number of redds per mile (in the Count Per Mile column), and the length of the reach surveyed (in the Miles Surveyed column) are shown. Some trends, such as this one, show both Count and Count per mile, while others show only one of these, depending on the information provided by the data collecting agency.

Note: Inconsistent information can show on this page. In this example the Location in the header says this redd count occurs from river mile 0 to 9.3, the Trend Comment in the header says the reach is 2.5 miles, and the Miles Surveyed in the table ranges from 0.5 to 3.0 miles. This is instructive in several ways. 1) Sometimes the area surveyed really is inconsistent among years. That was the case for this survey, where in the early years the best survey location was being determined -- all surveys after 1966 are 2.5 miles. 2) Because the exact 2.5 mile reach has not yet been georeferenced we purposely avoid misleading precision in the Location and define it as the entire stream length. Precision will be added as we further develop the database. 3) To help sort out such issues, we provide links to the source documents for all data. Clicking the number in the Reference column takes you to the list of references used for the trend. Click the reference title to see detailed information on a reference. A copy of the report for any reference can be obtained from the StreamNet Library.

Another inconsistency you may encounter is a Count Per Mile that does not match the Count column divided by the Miles Surveyed column. These cases occur when the source document is inconsistent. We try to provide all the information available; in these cases the Count Type indicates which parameter is primary, as reported by the agency that conducted the survey.

 

8. Clicking on Counts Graph on the blue toolbar produces a line graph displaying the counts by year for this particular trend. Though not presentation quality, this graph provides a quick visualization of the data.

Note: This screen always graphs the "counts," even when a "count per mile" is the primary variable of interest. In this example we see that "Redds per mile" is the primary parameter reported by the data collector, but number of redds is graphed.

Note: Let's take a detour: Two screens back, on the Trend List page's blue toolbar, was a link to a Summary Graph. This returns a line graph of the summed counts for all the listed trends, superimposed on a bar chart showing number of observations contributing to each value, as shown below. When the same set of time series contribute to a range of years the summary graph can be a useful visualization of the combined data sets. But use caution in interpreting summary graphs. Varying numbers of observations per year, varying survey lengths, and other complications can result in misleading graphs.



Now let's return to where we were. Click your browser's Back button.


9. To obtain data for analysis in your own spreadsheet, click Download on the blue toolbar. The download option appears at several levels in the query system. The data downloaded will reflect the data set(s) currently within the scope of the query. When examining a single trend, the download will be only for that trend. In this example we will click the Download link when a list of trends is shown. This will allow us to download the data for all spring Chinook salmon trends in the John Day subbasin at once.

There are several options for constructing the download file. Once the options are chosen, click the Create Zip File button.


The download file is zipped to compress the data and save space, allowing the download to run faster. The file must be unzipped before use. If you have questions about doing this, please contact us by clicking the Contact Us button above or by telephone at 503-595-3100.

 

 

10. After creating the zip file, download it to your computer by clicking on the file link. Give it an appropriate file name to remember what it is.

Once the file is downloaded to your computer it can be unzipped. After unzipping, open the file in an appropriate application, such as Microsoft Excel. If you need to analyze data from several locations or of related types, it may be necessary to download several individual data files and then combine them for analysis. Note: The same data can be associated with more than one geographic area, though, so if you combine data sets be sure to look for duplicate data. It is possible to download large portions of the database. However, the size of the download files may be too large to easily work with. If you need a large file, contact us by using the Contact Us button or by phone at 503-595-3100 and we will be happy to run the query and provide the file.


Another Query Approach

Besides the standard query system, you can also use the interactive StreamNet Mappers. This method lets you work interactively with a map to select your area of interest and then obtain the data available for that area. This query approach is much different and has it's own help page.

 

General Guidelines and Tips

Be patient. The system queries the database each time a criterion is selected, which takes time. This prevents building a query that results in no data.

Beware of huge downloads. A little forethought will give you a hint of how large a download you are requesting. If you select Stream or Dam as the first criterion, you will get a list of thousands of items, which can take minutes to download and even longer for your web browser to render. For this reason we limit to 1000 the number of items that can be shown on screen. Narrowing your search strategically will help you avoid these roadblocks. No matter how many records you select, though, you can always create a downloadable file of all records in the set.

Narrow your search criteria as quickly as possible. In general, use the fewest criteria necessary. For example, there is no need to click State then Subbasin then HUC 4 if you know what HUC you want data for. You can go to the HUC 4 criterion directly.

Multiple data. The query system currently does not allow locating data for multiple streams, locations, or species at the same time. If you need such data, you will need to download the individual data sets and combine them. (But, see "Data crossing boundaries" below.) Alternatively, you can download a superset of the items of interest and then cull the data that are not needed.

Contact us! Because of the complexity of the StreamNet database, it can require some experience to become proficient at using the query system. We find that too many people give up when they are not certain what to do next. We are happy to answer questions or to provide guidance on how to meet your objectives. We can even run queries for you and provide the results! Just use the Contact Us button, or phone us at 503-595-3100 and ask for the StreamNet office. We are usually able to respond to questions and requests within one business day.

Data crossing boundaries. The data in the StreamNet database are biological in origin and generally relate to natural features such as streams or subbasins. Political boundaries generally do not coincide with natural boundaries, or in other cases the natural feature is the boundary and it is thus in two jurisdictions. This results in some waters and associated data occurring in two political units. This creates a potentially difficult situation for managing these data. For example, if a count transect on a stream crosses a county line it would be possible to double count the data if queried separately for each county. Please be aware that as a general convention, the StreamNet database links data to a political unit if any portion of the observation occurred within that unit. Though less common, the same occurrence will happen if a data set crosses subbasin or HUC boundaries. Thus, you must be aware of the possibility of double counting if data are totaled for several political (county, state) or geographic (HUC, subbasin) units. Also, because some sample sites may cross unit lines, the total for a unit might also include some data obtained from outside that unit. It is generally impossible to split data that cross unit boundaries. We can provide assistance and advice if you are faced with these problems.