+ All Categories
Home > Documents > Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated...

Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated...

Date post: 23-Jun-2020
Category:
Upload: others
View: 1 times
Download: 0 times
Share this document with a friend
174
Coordinated Assessments Data Exchange Standard Version 20140725 20150 619 Effective Date: July 25, 2014 June 19, 2015 Prepared by: Pacific States Marine Fisheries Commission StreamNet Project for Pacific Northwest Coordinated Assessments Data Exchange Standard Development Team
Transcript
Page 1: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Coordinated Assessments Data Exchange Standard

Version 2014072520150619

Effective Date: July 25, 2014June 19, 2015

Prepared by:

Pacific States Marine Fisheries CommissionStreamNet Project

for

Pacific Northwest Coordinated Assessments Data Exchange Standard Development Team

Page 2: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

PrefaceThis document contains data structures for sharing information about several "indicators". You can use the table below to find which data table in the document contains the indicator of interest to you.

Indicator Rearing Type Description Table

Spawner abundance Natural origin Number of natural origin fish that actually spawn, not necessarily the number of fish returning to a spawning area. NOSA (A1)

Presmolt abundance Natural origin Number of natural origin juvenile fish in a population. Usually late summer parr, but may be any time and stage.

PresmoltAbundance (A6)

Number of outmigrants Natural origin Number of fish passing a defined point as they migrate downstream.

JuvenileOutmigrants (A4)

Smolt to adult ratio (percentage) Natural origin100 X the point estimate of the number of returning natural origin adults, divided by the point estimate of the number of smolts that produced those returning adults.

SAR (A2)

Smolt to adult ratio (percentage) Hatchery origin100 X the point estimate of the number of returning hatchery origin adults, divided by the point estimate of the number of smolts that produced those returning adults.

SAR_hatchery (B4)

Recruits per spawner: adults Natural origin Recruit per spawner ratios are specific to the locations and seasons described in each record of data. The number of "recruits" can be defined at any life stage.

RperS (A3)Recruits per spawner: juveniles Natural origin

Recruits per spawner: adults Hatchery originRecruit per spawner ratios are specific to the locations and seasons described in each record of data. The number of "recruits" can be defined only for adults at this time.

RperS_hatchery (B5)

Number of fish spawned in a hatchery under a hatchery program

Indicators for evaluating the success of hatchery programs. HatcherySpawning (B1)Proportion of hatchery broodstock that are natural origin fishEgg take

Proportionate natural influence (PNI) of supplementation hatcheries

Estimate of the relative selection pressure of the natural environment on hatchery origin fish in an integrated natural / hatchery population.

PNI (B2)

Egg to release survival rates for hatchery programs Hatchery origin Thiese survival rates are specific to a production group. EggToRelease (B3)

Coordinated Assessments Data Exchange Standard 2014072550619 Page 2 of 113

Page 3: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Table Of Contents

Preface-----------------------------------------------------------------------------2I. Introduction-------------------------------------------------------------------4II. Data Tables-------------------------------------------------------------------5

Section A: Indicators for Populations of Natural Origin Fishes.............5A1. NOSA Table...................................................................................5A2. SAR Table....................................................................................12A3. RperS Table.................................................................................19A4. JuvenileOutmigrants Table...........................................................26A5. JuvenileOutmigrantsDetail Table..................................................32A6. PresmoltAbundance Table...........................................................35

Section B: Indicators for Hatchery Programs and Populations of Hatchery Origin Fishes 41B1. HatcherySpawning Table.............................................................41B2. PNI Table.....................................................................................48B3. EggToRelease Table....................................................................53B4. SAR_Hatchery Table....................................................................58B5. RperS_Hatchery Table.................................................................64

III. Appendices----------------------------------------------------------------72Appendix A. Fields included in every table by reference......................72Appendix B. Glossary..............................................................................74Appendix C. Recovery Domains, Species, ESUs, MPGs, and Populations Defined by NMFS and NPCC/CBFWA/CRITFC 75

Interior Columbia Recovery Domain....................................................75Oregon Coast Recovery Domain.........................................................82Puget Sound Recovery Domain Geographic Regions and MPGs.......84Willamette/Lower Columbia Recovery Domain Strata.........................87

Appendix D. Names of Populations Defined by NPCC / CBFWA / CRITFC (from Subbasin Planning) 92Chinook salmon...................................................................................92Chum salmon.......................................................................................93Coho salmon........................................................................................93Kokanee...............................................................................................94Sockeye salmon..................................................................................94Steelhead.............................................................................................94

Appendix E. Defining New Populations..................................................96Appendix E1. Populations Table.........................................................96

Appendix F. Hatchery names and codes................................................98Appendix G. MS-Access 2010 Data Types...............................................102

Coordinated Assessments Data Exchange Standard 2014072550619 Page 3 of 113

Page 4: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Coordinated Assessments Data Exchange Standard 2014072550619 Page 4 of 113

Page 5: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

I. Introduction

This document contains the Coordinated Assessments Data Exchange Standard. It includes 1) the names and purposes of tables, 2) relationships among tables, and 3) the names, purposes, and properties of fields within tables. This data exchange standard was created by Pacific Northwest United States representatives from state and federal and tribal fisheries management and regulatory agencies, private consultants, and federal funding agencies.

This document has three main divisions: this introduction; the descriptions of the data tables; and appendices. Sections within the data tables division describe tables that have a common theme: the first section contains the tables for indicators meant to characterize the status of naturally-spawning fish populations; the second section contains the tables meant to characterize the success of hatchery programs and the status of hatchery populations.

The tables in this document represent data tables in a computer file. The tables in this document are comprised of 4 columns. Field Name is the name of the field in the data table. Underlined field names indicate primary key designations; multiple underlined field names indicate a multi-field key. The word "unique" in parentheses under a field name indicates that each value in that field must be unique within the table: that is, the field cannot have duplicate values. Field Description is a brief definition or description of the field. The descriptions in the Field Description column are the most important part of the tables in this document. Data Type specifies the field's Microsoft Access 2010 data type; the number after a "Text" data type indicates the maximum width of the entry, in characters, for that field. Codes/Conventions provides lookup codes, business rules, or other information applicable to the field. Required fields are indicated by bold red font in the Field Name and Data Type columns. If the Field

Name and Data Type are bold and red and italicized, then whether the field is required varies according to other entries in the record -- refer to the Field Description column for business rules on when the field is required.

The data types listed in the tables' Data Type column are Microsoft Access 2010 data types. Appendix FG contains details regarding these data types.

For help understanding the data tables or this document, contact Mike Banach with Pacific States Marine Fisheries Commission (503-595-3152; [email protected]).

Coordinated Assessments Data Exchange Standard 2014072550619 Page 5 of 113

Page 6: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

II. Data Tables

Section A: Indicators for Populations of Natural Origin Fishes

A1. NOSA TableThis table stores information concerning natural origin spawner abundance (NOSA) as defined by the Coordinated Assessments project. "Spawner abundance" refers to the number of fish that actually spawn, not necessarily the total number of fish returning to a spawning area -- all pre-spawning mortality has already been accounted for in the numbers represented in this table. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for NOSA TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon SteelheadAdditional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.

Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer

If not applicable then enter "N/A" (e.g., for bull trout).ESU_DPS For populations listed under the federal ESA, this is

the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

Page 7: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA TableRecoveryDomain Name of the "recovery domain," as defined by the

NMFS Northwest Region, in which the population falls.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

MajorPopGroup Name of "major population group" (MPG) or “stratum” as defined by the NMFS Northwest Region, in which the population falls.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the NOSA estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents theone entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of theone population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the natural origin spawner abundance value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the NOSA estimate was made.

WaterBody Name of the body of water associated with the time series.

Text 255 This may be any of the following: the name of a fluvial water body. the name of an impounded fluvial water body (reservoir). the name of a lentic water body. a description of multiple water bodies if appropriate for the time series.

To allow for easy sorting, follow these general format examples: River or stream – John Day River; Fifteen Mile Creek. Fork of a river, main name first – John Day River, North Fork

o [for North Fork John Day River] Salmon River, East Fork South Fork

o [for East Fork South Fork Salmon River] Reservoir (the word "Lake" comes first) – Lake Billy Chinook; Cougar Reservoir. Natural lake (the word "Lake" comes last) – Alturas Lake.

SpawningYear The four-digit year in which spawning of this species (and run where appropriate) began.

Integer In cases where an unusual population begins spawning uncharacteristically early (before January 1 for spring spawners) or late (after December 31 for fall spawners) for the species (and perhaps run), assign the year based on the majority of populations of this species/run in order to be consistent for all members of the spawning cohort. For example, most coho spawn in fall but a few populations do not begin spawning until after Jan. 1. The spawning year assigned for these unusual populations would match the other populations that spawned in the fall, even though these particular populations did not begin spawning until after December 31.

Page 8: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA TableTRTmethod Flag indicating whether the methods used to

generate the values in this record are those defined by the TRT.

Text 3 Acceptable values: Yes [The record reflects the TRT method; it will be submitted to NMFS's SPS database.] No [The record does not reflect the TRT method; it will not be submitted to NMFS's SPS database.]

ContactAgency Agency, tribe, or other entity, or person responsible for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

MethodNumber This field represents the method(s) used to calculate the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Indicators

NOSAIJ The point estimate for natural origin spawner abundance, including jacks.

This field is required if the NOSAEJ field is null and NullRecord = "No".

Single Estimated number of natural origin spawners contributing to spawning in a particular year.  “Spawners” includes jacks, all of natural origin. "Natural origin" means the fish's parents spawned in the wild. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

Provide this estimate ONLY if one of the following is true: it represents the whole population -- that is, the estimate is for the whole population. this sub-portion of the population is formally used by the TRT to represent the population.

For populations for which "jacks" are not recognized, enter the NOSA estimate in this field and fill in the associated confidence limits information in the NOSAIJLowerLimit, NOSAIJUpperLimit, NOSAIJAlpha fields. The only species for which jacks are recognized are Chinook salmon, coho salmon, chum salmon (rarely), and winter steelhead (rarely).

NOSAIJLowerLimit The lower limit of the confidence interval for the NOSAIJ field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

NOSAIJUpperLimit The upper limit of the confidence interval for the NOSAIJ field.

Single Minimum value = 0.

NOSAIJAlpha The significance level for the NOSAIJ confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Page 9: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA TableNOSAEJ The point estimate for natural origin spawner

abundance, excluding jacks.

This field is required if the NOSAIJ field is null and NullRecord = "No".

Single Estimated number of natural origin spawners contributing to spawning in a particular year.  Includes only "adults" of natural origin, excluding jacks. "Natural origin" means the fish's parents spawned in the wild.

Provide this estimate ONLY if one of the following is true: it represents the whole population. That is, the estimate is for the whole population. this sub-portion of the population is formally used by the TRT to represent the population.

For populations for which "jacks" are not recognized, leave this field and the associated confidence limits fields blank (NOSAEJLowerLimit, NOSAEJUpperLimit, NOSAEJAlpha). The only species for which jacks are recognized are Chinook salmon, coho salmon, chum salmon (rarely), and winter steelhead (rarely).

NOSAEJLowerLimit The lower limit of the confidence interval for the NOSAEJ field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

NOSAEJUpperLimit The upper limit of the confidence interval for the NOSAEJ field.

Single Minimum value = 0.

NOSAEJAlpha The significance level for the NOSAEJ confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

NOBroodStockRemoved The number of additional natural origin fish (adults plus jacks) that would have spawned, had there not been removal of natural origin fish for use as hatchery broodstock.

Single This value reflects fish taken for hatchery use from the indicated spawning group. Details should be explained in the Methods citation.

Metrics supporting the "Indicators" fields above

pHOSij Point estimate for the proportion of fish spawning naturally, including jacks, that are hatchery origin fish.

Single Express these values as numbers from zero to one, with three digits to the right of the decimal point.

pHOSijLowerLimit The lower limit of the confidence interval for the pHOSij field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

pHOSijUpperLimit The upper limit of the confidence interval for the pHOSij field.

Single Minimum value = 0.

pHOSijAlpha The significance level for the pHOSij confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

pHOSej Point estimate for the proportion of fish spawning naturally, excluding jacks, that are hatchery origin fish.

Single Express these values as numbers from zero to one, with three digits to the right of the decimal point.

pHOSejLowerLimit The lower limit of the confidence interval for the pHOSej field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

pHOSejUpperLimit The upper limit of the confidence interval for the pHOSej field.

Single Minimum value = 0.

pHOSejAlpha The significance level for the pHOSej confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

NOSJF The point estimate for the natural origin spawners jack fraction.

Single Proportion of natural origin spawners that are jacks. Express these values as numbers from zero to one, with three digits to the right of the decimal point.

NOSJFLowerLimit The lower limit of the confidence interval for the NOSJF field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

NOSJFUpperLimit The upper limit of the confidence interval for the NOSJF field.

Single Minimum value = 0.

NOSJFAlpha The significance level for the NOSJF confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Page 10: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA TableHOSJF The point estimate for the hatchery origin spawners

jack fraction.Single Proportion of hatchery origin spawners that are jacks. Express these values as numbers from zero to one, with three digits to

the right of the decimal point.TSAIJ The point estimate for total spawner abundance,

including jacks.Single Estimated total number of fish contributing to spawning in a particular year. Includes both natural origin and hatchery origin

returns, and adult and jack age classes.TSAIJLowerLimit The lower limit of the confidence interval for the

TSAIJ field.Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

TSAIJUpperLimit The upper limit of the confidence interval for the TSAIJ field.

Single Minimum value = 0.

TSAIJAlpha The significance level for the TSAIJ confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

TSAEJ The point estimate for total spawner abundance, excluding jacks.

Single Estimated total number of fish contributing to spawning in a particular year. Includes both natural origin and hatchery origin returns, for adult age classes excluding jacks.

TSAEJLowerLimit The lower limit of the confidence interval for the TSAEJ field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

TSAEJUpperLimit The upper limit of the confidence interval for the TSAEJ field.

Single Minimum value = 0.

TSAEJAlpha The significance level for the TSAEJ confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Age determination

Age2Prop The proportion of natural origin fish that were age 2 (brood year +2).

Single Values must be between 0 and 1. Express with 3 digits to the right of the decimal point.

Ages in this table are based on the year spawning occurred, not necessarily the year eggs hatched, so care must be taken in reporting ages.Assigning age can be complicated based on the life history (generally, salmon return and spawn in one year but hatch in the next, steelhead spawn and hatch in the same year). Make sure these details are accounted for in assigning ages.

The age distribution numbers reported here must meet three criteria. If these criteria are not met then do not report ages.1. These age fields contain proportions by age for the natural origin fish. They are not the numbers of fish actually aged, nor

are they the expanded numbers for a population. Consider this scenario: 10,000 fish spawn (as reported in the NOSAIJ field) 500 fish were aged After age analysis is completed it is determined that 1% of the fish (meaning 100 of the 10,000) were age 2. In this case the value in this field should be 0.01 (100/10,000) not 100, 500, or 10,000. Nor is it 0.2 (100/500).

2. The values of the Age2Prop through Age11PlusProp fields must sum to 1.00 ± 0.01.3. The age distribution must be derived only from the natural origin fish of the specific population this record represents.

Therefore, do not include age data that are derived in part or in whole from any other group of fish.The age information may represent the exact group of spawning fish indicated in the NOSAIJ field, or a somewhat different group of fish. For example, the ages may represent the population as the fish passed a dam on their way to the spawning areas. Whatever may be the case, ensure this information is included in the protocol and method documentation section below.

Age2PropLowerLimit The lower limit of the confidence interval for the Age2Prop field.

Single The associated alpha value is in the AgePropAlpha field, which is found below after the fields for age 11+.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.Age2PropUpperLimit The upper limit of the confidence interval for the

Age2Prop field.Single See the Codes/Conventions for the Age2PropLowerLimit field.

Minimum value = 0.Age3Prop The proportion of natural origin fish that were age 3

(brood year +3).Single See the Codes/Conventions column for the Age2Prop field.

Page 11: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA TableAge3PropLowerLimit The lower limit of the confidence interval for the

Age3Prop field.Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age3PropUpperLimit The upper limit of the confidence interval for the Age3Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age4Prop The proportion of natural origin fish that were age 4 (brood year +4).

Single See the Codes/Conventions column for the Age2Prop field.

Age4PropLowerLimit The lower limit of the confidence interval for the Age4Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age4PropUpperLimit The upper limit of the confidence interval for the Age4Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age5Prop The proportion of natural origin fish that were age 5 (brood year +5).

Single See the Codes/Conventions column for the Age2Prop field.

Age5PropLowerLimit The lower limit of the confidence interval for the Age5Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age5PropUpperLimit The upper limit of the confidence interval for the Age5Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age6Prop The proportion of natural origin fish that were age 6 (brood year +6).

Single See the Codes/Conventions column for the Age2Prop field.

Age6PropLowerLimit The lower limit of the confidence interval for the Age6Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age6PropUpperLimit The upper limit of the confidence interval for the Age6Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age7Prop The proportion of natural origin fish that were age 7 (brood year +7).

Single See the Codes/Conventions column for the Age2Prop field.

Age7PropLowerLimit The lower limit of the confidence interval for the Age7Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age7PropUpperLimit The upper limit of the confidence interval for the Age7Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age8Prop The proportion of natural origin fish that were age 8 (brood year +8).

Single See the Codes/Conventions column for the Age2Prop field.

Age8PropLowerLimit The lower limit of the confidence interval for the Age8Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age8PropUpperLimit The upper limit of the confidence interval for the Age8Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age9Prop The proportion of natural origin fish that were age 9 (brood year +9).

Single See the Codes/Conventions column for the Age2Prop field.

Age9PropLowerLimit The lower limit of the confidence interval for the Age9Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age9PropUpperLimit The upper limit of the confidence interval for the Age9Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age10Prop The proportion of natural origin fish that were age 10 (brood year +10).

Single See the Codes/Conventions column for the Age2Prop field.

Age10PropLowerLimit The lower limit of the confidence interval for the Age10Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age10PropUpperLimit The upper limit of the confidence interval for the Age10Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Page 12: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA TableAge11PlusProp The proportion of natural origin fish that were age

11 (brood year +11) or older.Single See the Codes/Conventions column for the Age2Prop field.

Age11PlusPropLowerLimit

The lower limit of the confidence interval for the Age11PlusProp field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age11PlusPropUpperLimit

The upper limit of the confidence interval for the Age11PlusProp field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

AgePropAlpha The significance level for the Age_x_Prop confidence intervals, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Page 13: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA Table

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, Rrefer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managersnot listed here.

A2. SAR TableThis table stores information concerning smolt to adult ratios (SAR) as defined by the Coordinated Assessments project. Smolt to adult ratios are specific to the smolt and adult locations described in each row of data. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for SAR TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.

Page 14: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR TableCommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon SteelheadAdditional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.

Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized funs. For example, bull trout.]

If not applicable then enter "N/A" (e.g., for bull trout).ESU_DPS For populations listed under the federal ESA, this is

the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

RecoveryDomain Name of the "recovery domain," as defined by the NMFS Northwest Region, in which the population falls.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

MajorPopGroup Name of "major population group" (MPG) or “stratum” as defined by the NMFS Northwest Region, in which the population falls.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.

Page 15: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR TablePopFit Categorization of how well the geographic extent of

the SAR estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents theone entire population, the whole population, and nothing but the population.]

Fill in PopID and/or CBFWApopName fields. Leave PopFitNotes and PopAggregation fields blank. Portion [Estimate represents a portion of theone population. (Describe in PopFitNotes field.)]

Fill in PopID and/or CBFWApopName fields. Fill in PopFitNotes field. Leave PopAggregation field blank. Multiple [Estimate is from more than one population. (Describe in PopAggregationFitNotes field.)]

Leave PopID and CBFWA and PopFitNotes fields blank. Fill in PopAggregation field.PopFitNotes Text description of how well the SAR value

corresponds to the defined population.Memo IThis field is required if the PopFit field is "Portion". Otherwise it must be null. or "Multiple", d

Describe the lack of correspondence between the defined population and the fish for which the SAR estimate was made.PopAggregation If the data are for an aggregation of defined

populations, enter the names of populations included.

Memo This field is required if the PopFit field is "Multiple". Otherwise it must be null. If the record is for multiple populations then fill in this PopAggregation field and leave the PopID and CBFWApopName fields blank. If the record is for a single population then fill in the PopID and/or CBFWApopName fields above and leave this one blank.

SmoltLocation The specific location(s) for where the smolt abundance numbers were determined.

Text 255 This may be any of the following: the name of a fluvial water body and text description of where on that stream or river (river mile preferred, but river

kilometer, lat/long, or other characterization allowable). the name of an impounded fluvial water body (reservoir) and description of where on that reservoir. the name of a lentic water body, and description of where on that lake. a description of multiple water bodies if appropriate for the time series, with descriptions of specific locations. the name of a dam.

SmoltLocPTcode PTAGIS code for the location where smolts were enumerated.

Text 255 There should be a PTAGIS code for most locations where smolts were trapped. Provide that code, or multiple codes if smolts were trapped at multiple locations for this population.

AdultLocation The specific location(s) for where the adult abundance numbers were determined.

Text 255 This may be any of the following: the name of a fluvial water body, with specific location described (river mile preferred, but river kilometer, lat/long, or

other characterization allowable). the name of an impounded fluvial water body (reservoir), with specific location described the name of a lentic water body, with specific location described a description of multiple water bodies if appropriate for the time series. the name of a dam.

SARtype Type of SAR. See Codes/Conventions column for details.

Text 255 This field is used to describe the category of SAR for the current record, in terms of where the smolt and adult numbers were determined that went into the SAR. Current list of acceptable values are shown below. If you have a need for other types, contact the Coordinated Assessment group to define the new type. Tributary to tributary [Smolt numbers determined in tributary; adult numbers determined in tributary] Tributary to named dam [Smolt numbers determined in tributary; adult numbers determined at first mainstem dam] Named dam to named dam [Smolt numbers determined at first mainstem dam; adult numbers determined at first

mainstem dam] Named dam to tributary [Smolt numbers determined at first mainstem dam; adult numbers determined in tributary]

The values in the "SmoltLocation" and "AdultLocation" fields should match the categorization in this field.ScopeOfInference Description of what this SAR represents: athe

specific population(s); specific ESU/DPS(s); specific MPG(s); etc. represented.

Text 255 Identify the specific population(s), ESU(s), etc. that applyies. Don't enter "ESU" or "MPG" or "Population", but instead the specific ESU(s) or MPG(s) or population(s) represented, such as "Scappoose Creek population" or "All populations above Lower Granite Dam" or other appropriate entry.

OutmigrationYear The four-digit year for which this SAR is calculated, defined as the year the group migrated to sea.

Integer Year in which the fish migrated to the ocean. This is often not the same as brood year.

TRTmethod Flag indicating whether the methods used to generate the values in this record are those defined by the TRT.

Text 3 Acceptable values: Yes [The record reflects the TRT method; it will be submitted to NMFS's SPS database.] No [The record does not reflect the TRT method; it will not be submitted to NMFS's SPS database.]

Page 16: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR TableContactAgency Agency, tribe, or other entity, or person responsible

for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

MethodNumber This field represents the method(s) used to calculate the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Indicator

SAR The point estimate for smolt-to-adult ratio, calculated as 100 X the point estimate of the number of returning natural origin adults, divided by the point estimate of the number of smolts that produced those returning adults.

Single Required if NullRecord = "No".Express these values as percentages (numbers from zero to one hundred), with two digits to the right of the decimal point. Examples: .020 = 2.00, .0015 = 0.15.

This field holds a numeric value only -- the percent sign is implied but not included.

Do NOT include repeat spawners in the number of adult returns. (A fish only returns once from smolting; subsequent returns are not appropriate for inclusion in smolt-to-adult estimates because they head to sea as adults on subsequent trips and thus are not exposed to the same suite of mortality factors.)

SARLowerLimit The lower limit of the confidence interval for the SAR field.

Single This field holds a numeric value only -- the percent sign is implied but not included.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.SARUpperLimit The upper limit of the confidence interval for the

SAR field.Single This field holds a numeric value only -- the percent sign is implied but not included.

Minimum value = 0.SARAlpha The significance level for the SAR confidence

interval, expressed as alpha.Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Page 17: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR TableReturnsMissing This field indicates whether any adult return years

for this out-migration year were missing.Text 3 Acceptable values:

Yes [Years were missing.] No [No years missing; return estimates were complete.]

If some years were missing, describe how that gap was addressed under ReturnMissingExplanationReturnsMissingExplanation

If some return data are not accounted for in the SAR estimate, explain the gap.

Memo Describe how any gap in return years was addressed: Filled in with an interpolated estimate, ignored, etc.

RearingType The rearing type (origin; production type) of the fish represented by this record.

Text 8 Acceptable values: Hatchery Natural Mixed [Known to include both hatchery and natural origin fish] Unknown [None of the above can be confidently applied]

[Note: Disagreement exists re: is this an "indicator" (attribute along w/ SAR value), or if it should be part of the key for the table. If indicator then only one record/pop/year; if in key then >1 record/pop/yr is possible. To start we'll have it in the key to allow flexibility in the data. If that causes trouble we'll address it at that time.]

Metrics supporting the "Indicator" fields above

TSO Total smolt outmigration. Point estimate of the number of smolts for this outmigration year, or the number of marked smolts used to calculate the SAR.

Single This should be the numerdenominator in the ratio calculation, with all previous losses (handling mortality, tag loss estimate, etc.) already taken out. The Methods citation should address how this was done.

TSOLowerLimit The lower limit of the confidence interval for the TSO field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

TSOUpperLimit The upper limit of the confidence interval for the TSO field.

Single Minimum value = 0.

TSOAlpha The significance level for the TSO confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

TAR Total adult return. Point estimate of the number of adults returning for the first time from the indicated outmigration year, or the group of marked smolts (as appropriate), to match the outmigrants in the TSO field.

Single For iteroparous species such as steelhead, include only those adults returning to spawn for the first time. (Failure to do so will result in some adults being counted twice for returns purposes.)

TARLowerLimit The lower limit of the confidence interval for the TAR field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

TARUpperLimit The upper limit of the confidence interval for the TAR field.

Single Minimum value = 0.

TARAlpha The significance level for the TAR confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

ReturnDef How "return" is defined for this SAR. Memo Examples: Adults migrating to/past a point(s). Estimated number of fish to the spawning grounds. Estimated number of fish that actually spawn. Number of marked fish captured. Etcetera.

HarvestAdj How was the return adjusted to account for harvest? (Are harvested fish included in the estimate of number of adults?)

Text 35 Acceptable values: Ocean [Value in the TAR field was adjusted for harvest in the ocean, but not in the mainstem and not in tributaries.] Ocean and mainstem [Value in the TAR field was adjusted for harvest in the ocean and mainstem, but not in tributaries.] Ocean and mainstem and tributaries [Value in the TAR field was adjusted for harvest in the ocean, mainstem, and

tributaries.] Mainstem [Value in the TAR field was adjusted for harvest in the mainstem but not in tributaries.] Mainstem and tributaries [Value in the TAR field was adjusted for harvest in both the mainstem and tributaries.] Tributaries [Value in the TAR field was adjusted for harvest in tributaries but not in the mainstem.] Not adjusted [Value in the TAR field was not adjusted for harvest.]

Page 18: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR TableOceanHarvest The estimated number of adults and jacks from the

smolt group indicated in the TSO field that were harvested in the ocean.

Single This field is for harvests in the ocean, which is defined as not including the estuary. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated natural origin group. Leave blank for juvenile recruits.

MainstemHarvest The estimated number of adults and jacks from the smolt group indicated in the TSO field that were harvested in the mainstem.

Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies). Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This harvest value reflects fish harvested from the indicated smolt group -- they may be all natural origin, all hatchery origin, or mixed origin, as indicated by the RearingType field. This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation.

TribHarvest The estimated number of adults and jacks from the smolt group indicated in the TSO field that were harvested in tributaries.

Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This harvest value reflects fish harvested from the indicated smolt group -- they may be all natural origin, all hatchery origin, or mixed origin, as indicated by the RearingType field. This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation.

BroodStockRemoved The number of additional adults that would have returned from the smolt group indicated in the TSO field, had there not been removal of fish for use as hatchery broodstock.

Single This value reflects fish taken for hatchery use from the indicated smolt group -- they may be all natural origin, all hatchery origin, or mixed origin, as indicated by the RearingType field. Details should be explained in the Methods citation.

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

Page 19: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR TableMethodAdjustments Minor adjustments to a method in a given year that

are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.Refer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managers.

Page 20: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

A3. RperS TableThis table stores information concerning recruits per spawner (R/S) as defined by the Coordinated Assessments project. Recruit per spawner ratios are specific to the locations and seasons described in each record of data. This table can include the number of juvenile or adult recruits as measures, or full life cycle productivity. That is, "recruit" can be defined at any life stage. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for RperS TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon SteelheadAdditional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.

Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

If not applicable then enter "N/A" (e.g., for bull trout).ESU_DPS For populations listed under the federal ESA, this is

the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

Page 21: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS TableRecoveryDomain Name of the "recovery domain," as defined by the

NMFS Northwest Region, in which the population falls.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

MajorPopGroup Name of "major population group" (MPG) or “stratum” as defined by the NMFS Northwest Region, in which the population falls.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the recruits per spawner estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents theone entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of theone population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the recruits per spawner value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the recruits per spawner estimate was made.

SpawnerLocation The specific location(s) for where the spawner abundance numbers were determined.

Text 255 This may be any of the following: the name of a fluvial water body. the name of a lentic water body. a description of multiple water bodies if appropriate for the time series.

RecruitLocation The specific location(s) for where the recruit abundance numbers were determined.

Text 255 This field describes the location where the abundance of recruits is determined, and may be any of the following: the name of a fluvial water body. the name of a lentic water body. a dam or other location where fish numbers can be estimated. a description of multiple water bodies if appropriate for the time series. other, as appropriate.

BroodYear The four-digit brood year for which the recruit per spawner ratio is calculated. Same as "spawning year" for the parent generation.

Integer This field is used to tie juvenile ‘recruits’ or adult returns (over multiple return years) to a specific spawning year. This is the year in which spawning of this species (and run where appropriate) began.

In cases where an unusual population begins spawning uncharacteristically early (before January 1 for spring spawners) or late (after December 31 for fall spawners) for the species (and perhaps run), assign the year based on the majority of populations of this species/run in order to be consistent for all members of the spawning cohort. For example, most coho spawn in fall but a few populations do not begin spawning until after Jan. 1. The brood year assigned for these unusual populations would match the other populations that spawned in the fall, even though these particular populations did not begin spawning until after December 31.

Page 22: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS TableRperStype The type of recruit per spawner estimate, in terms of

what fish are included in the estimates of number of spawners and number of recruits.

Text 255 Acceptable values:For adult to adult R/S estimates: Total recruits per total spawners [Includes males and jacks] Adult recruits per adult spawners [Includes adult males, but not jacks] Female recruits per female spawners [All males excluded]For R/S estimates for juvenile ‘recruits’: Parr per total spawners [Includes males and jacks] Smolts per total spawners [Includes males and jacks] Parr per adult spawners [Includes adult males, but not jacks] Smolts per adult spawners [Includes adult males, but not jacks] Parr per female spawners [Includes female parents only] Smolts per female spawners [Includes female parents only]

If more than one type of estimate is done for one brood year for a population, the estimates go in separate data records.TRTmethod Flag indicating whether the methods used to

generate the values in this record are those defined by the TRT.

Text 3 Acceptable values: Yes [The record reflects the TRT method; it will be submitted to NMFS's SPS database.] No [The record does not reflect the TRT method; it will not be submitted to NMFS's SPS database.]

ContactAgency Agency, tribe, or other entity, or person responsible for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

MethodNumber This field represents the method(s) used to calculate the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Page 23: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS Table

Indicator

RperS The point estimate for the ratio of recruits from the designated brood year and RperStype, divided by the number of parent spawners responsible for that brood year. Straight ratio calculation, not a log/natural log transformation.

Single Required if NullRecord = "No".For iteroparous species such as steelhead, adult recruits should include all fish from the brood year that return to spawn, including repeat spawners, since repeat spawners add to the productivity of the population.For juvenile recruits, the total of all of the target life stage from the brood year. For some species and life stages, these may recruit in multiple years.

RperSLowerLimit The lower limit of the confidence interval for the RperS field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

RperSUpperLimit The upper limit of the confidence interval for the RperS field.

Single Minimum value = 0.

RperSAlpha The significance level for the RperS confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Metrics supporting the "Indicator" fields above

TotalSpawners Point estimate for the total number of parent spawners, both natural and hatchery origin, that produced the brood year this record reflects.

The number in this field reflects the RperStype field above. That is, if this record is for total spawners then this number will be the total number of spawners; if this record is for females to females, then this number will be only the female spawners.

Single

TotalSpawnersLowerLimit

The lower limit of the confidence interval for the TotalSpawners field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

TotalSpawnersUpperLimit

The upper limit of the confidence interval for the TotalSpawners field.

Single Minimum value = 0.

TotalSpawnersAlpha The significance level for the TotalSpawners confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

HatcherySpawners Point estimate for the number of parent spawners of hatchery origin that contributed to the brood year this record reflects.

This number is the hatchery portion of the TotalSpawners field.

Single

HatcherySpawnersLowerLimit

The lower limit of the confidence interval for the HatcherySpawners field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

HatcherySpawnersUpperLimit

The upper limit of the confidence interval for the HatcherySpawners field.

Single Minimum value = 0.

HatcherySpawnersAlpha The significance level for the HatcherySpawners confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Recruits Point estimate for the total number of natural origin recruits from the indicated combination of species, run, population, spawner location, recruit location, brood year, and RperStype.

Single This is the sum of returns by juvenile life stage or age group as specified in the RperStype field. This is the number of fish recruited to the location indicated in the RecruitLocation field. Adult recruits should include all fish from the brood year that return to spawn, including repeat spawners, since repeat spawners add to the productivity of the population.

RecruitsLowerLimit The lower limit of the confidence interval for the Recruits field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

Page 24: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS TableRecruitsUpperLimit The upper limit of the confidence interval for the

Recruits field.Single Minimum value = 0.

RecruitsAlpha The significance level for the Recruits confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

RecruitsMissing This field indicates whether any recruits for this brood year were missing.

This field and the next are intended mainly for adult recruits data. An example where this field may be useful for juvenile fish is if an outmigration estimate is done only for spring-migrating fish, but it's known that some fish out-migrate during fall or winter. If such R/S estimates are done, then these fields would be helpful for juveniles also.

Text 3 Indicate if recruit estimates for any year were missing. If so, indicate in this field, and explain how the gap was addressed in the RecruitsMissingExplanation field and in the Methods citation.

Acceptable values: Yes [Years were missing.] No [No years missing; recruit estimates were complete.]

If some years were missing, describe how that gap was addressed under RecruitsMissingExplanation.

RecruitsMissingExplanation

If some recruits data are not accounted for in the RperS estimate, explain the gap.

Memo Explain how any gaps in returns from this year class were addressed (estimated to fill in, ignored, etc.).

HarvestAdj For adult returns, how was the return adjusted to account for harvest?

Text 35 Acceptable values: Ocean [Value in the Recruits field was adjusted for harvest in the ocean, but not in the mainstem and not in tributaries.] Ocean and mainstem [Value in the Recruits field was adjusted for harvest in the ocean and mainstem, but not in

tributaries.] Ocean and mainstem and tributaries [Value in the Recruits field was adjusted for harvest in the ocean, mainstem, and

tributaries.] Mainstem [Value in the Recruits field was adjusted for harvest in the mainstem but not in tributaries.] Mainstem and tributaries [Value in the Recruits field was adjusted for harvest in both the mainstem and tributaries.] Tributaries [Value in the Recruits field was adjusted for harvest in tributaries but not in the mainstem.] Not adjusted [Value in the Recruits field was not adjusted for harvest.]

OceanHarvest The estimated number of adults and jacks from the spawner group indicated in the TotalSpawners field that were harvested in the ocean.

Single This field is for harvests in the ocean, which is defined as not including the estuary. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated natural origin group. Leave blank for juvenile recruits.

MainstemHarvest The estimated number of adults and jacks from the spawner group indicated in the TotalSpawners field that were harvested in the mainstem.

Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies) defining the population, and including the estuary. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated natural origin group. Leave blank for juvenile recruits.

TribHarvest The estimated number of adults and jacks from the spawner group indicated in the TotalSpawners field that were harvested in tributaries.

Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated natural origin group. Leave blank for juvenile recruits.

NOBroodStockRemoved The number of additional recruits that would have returned from the group indicated in the TotalSpawners field, had there not been removal of fish from this brood year for use as hatchery broodstock.

Single Details should be explained in the Methods citation.

Page 25: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS Table

Age determination

Juvenile Recruits:YOY Total number of juvenile recruits (parr or smolts)

that were enumerated prior to forming the first annulus.

Single Number of juvenile recruits (parr or smolts as listed in Type field) prior to forming the first annulus (e.g. ocean type Chinook).

Age1Juvs Total number of recruits at age 1. Single Number of juvenile recruits of Age 1.Age2Juvs Total number of recruits at age 2. Single Number of juvenile recruits of Age 2.Age3Juvs Total number of recruits at age 3. Single Number of juvenile recruits of Age 3.Age4PlusJuvs Total number of recruits at age 4 or more. Single Number of juvenile recruits of age 4 or more (e.g. older steelhead smolts).Adult Recruits:Age2Adults Total number of recruits that recruited at age 2

(brood year +2).Single Ages in this table are based on the year spawning occurred, not necessarily the year they hatched, so care must be taken in

assigning returning fish to a brood year.Assigning returning fish to a brood year can be complicated based on the life history (generally, salmon return and spawn in one year but hatch in the next, steelhead spawn and hatch in the same year). Make sure these details are accounted for in assigning returns to a year class.Adult recruits should include all fish from the brood year that return to spawn, including repeat spawners, since repeat spawners add to the productivity of the population.

Age3Adults Total number of recruits that recruited at age 3 (brood year +3).

Single See the Codes/Conventions column for the Age2Adults field.

Age4Adults Total number of recruits that recruited at age 4 (brood year +4).

Single See the Codes/Conventions column for the Age2Adults field.

Age5Adults Total number of recruits that recruited at age 5 (brood year +5).

Single See the Codes/Conventions column for the Age2Adults field.

Age6Adults Total number of recruits that recruited at age 6 (brood year +6).

Single See the Codes/Conventions column for the Age2Adults field.

Age7Adults Total number of recruits that recruited at age 7 (brood year +7).

Single See the Codes/Conventions column for the Age2Adults field.

Age8Adults Total number of recruits that recruited at age 8 (brood year +8).

Single See the Codes/Conventions column for the Age2Adults field.

Age9Adults Total number of recruits that recruited at age 9 (brood year +9).

Single See the Codes/Conventions column for the Age2Adults field.

Age10Adults Total number of recruits that recruited at age 10 (brood year +10).

Single See the Codes/Conventions column for the Age2Adults field.

Age11PlusAdults Total number of recruits that recruited at age 11 (brood year +11 or more).

Single See the Codes/Conventions column for the Age2Adults field.

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title(s) of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

Page 26: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS TableProtMethURL URL(s) for published protocols and methods

describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

Page 27: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS TableContactPersonFirst First name of person who is the best contact for

questions that may arise about this data record.Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.Refer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managers.

A 4. JuvenileOutmigrants TableThis table stores information concerning the number of natural origin juvenile outmigrants to the location defined in each data record. The definition of "juvenile outmigrant" varies by species, run, and geographic area.steelhead, coho, coastal cutthroat, bull trout, and east-sideummer (stame) Cch data record. "Juvenile outmigrantto the tottmigrants of al lower Colubg Chinooummer Chinook, and all fall Chinook. "Juvenilouhe number of smolts fo Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants TableFields for defining a unique record

ID Value used by computer to identify a record. Text 36 This value is a globally unique identifier GUID. It must be included for all new and updated records. It is also needed when indicating records to delete.

CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following: Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon SteelheadAdditional species may be added in the future: refer to http://www.streamnet.org/SpeciesInFW.html for common names.

Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

Page 28: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants TableESU-DPS For populations listed under the federal ESA, this is

the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.

RecoveryDomain Name of the "recovery domain," as defined by the NMFS Northwest Region, in which the population falls.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.MajorPopGroup Name of "major population group" (MPG) or

“stratum” as defined by the NMFS Northwest Region, in which the population falls. Enter “N/A” if not applicable.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix B for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record. What do we do for places like mainstem dams? Answer: we provide guidance that info is to fill in all fields for esu/mpg/pop, but only down to the lowest level available. And have PopFit apply to all levels. We need to create code for “N/A”.

Integer See Appendix B for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix C for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the juvenile outmigrants estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents one entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of one population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the juvenile outmigrants value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the juvenile outmigrants estimate was made.

SmoltEqLocation The specific location(s) for where the smolt equivalent abundance numbers were determined.

Text 255 This may be any of the following: the name of a fluvial water body and text description of where on that stream or river (river mile preferred, but river

kilometer, lat/long, or other characterization allowable). the name of an impounded fluvial water body (reservoir) and description of where on that reservoir. the name of a lentic water body, and description of where on that lake. a description of multiple water bodies if appropriate for the time series, with descriptions of specific locations. the name of a dam.

SmoltEqLocPTcode PTAGIS code for the SmoltEqLocation field. Text 255 There should be a PTAGIS code for most locations where smolts were trapped. Provide that code if available, or multiple codes if smolts were trapped at multiple locations for this population.

OutmigrationYear The four-digit year of the spring/summer in which outmigration of this species occurred.

Integer Juvenile anadromous fishes generally migrate to the ocean in the spring. However, a significant portion of the migration may occur in the fall or winter before, or continue into summer. Enter here the year of the spring migration even if the migration begins earlier.

Page 29: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants TableContactAgency Agency, tribe, or other entity, or person responsible

for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe of Idaho Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

MethodNumber This field represents the method(s) used to calculate the values in the "Indicators" and "Metrics" sections.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions, or for different locations, life stages, etc.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Page 30: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table

Indicators

TotalNatural The point estimate, to the location defined in the SmoltEqLocation field, of: the number of spring/summer smolt equivalents

foro bull trouto coastal cutthroat trouto coho salmono east-side spring/summer (stream-type)

Chinook salmon, ando steelhead;

the total number of outmigrants of all types foro fall Chinook salmono lower Columbia spring Chinook salmono upper Columbia summer Chinook salmono Willamette spring Chinook salmon;

the number of smolts foro chum salmono pink salmon.o sockeye salmon.

numbe ummer smoltivalor eastteelhead and most other stream-type fishthe lococation field.

Single Estimated total number of natural origin fish that outmigrated in a particular year. "Natural origin" means the fish's parents spawned in the wild. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population.

TotalNaturalLowerLimit The lower limit of the confidence interval for the TotalNatural field.

Single

TotalNaturalUpperLimit The upper limit of the confidence interval for the TotalNatural field.

Single

TotalNaturalAlpha The significance level for the TotalNatural confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Page 31: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table

Metrics supporting the "Indicators" fields above

Metrics can be found in the JuvenileOutmigrantDetail table (below), which is a child of this table.

Age determination

Age0Prop The proportion of natural origin fish that were age 0 (brood year +0).

Single Values must be between 0 and 1. Express with 3 digits to the right of the decimal point.

Ages in this table are based on the year spawning occurred, not necessarily the year eggs hatched, so care must be taken in reporting ages.

Assigning age can be complicated based on the life history (generally, salmon return and spawn in one year but hatch in the next, steelhead spawn and hatch in the same year). Make sure these details are accounted for in assigning ages. [ Note – This means we would never refer to age 0 salmon, because they hatch in the year after the eggs are laid, but for steelhead and other spring spawners age 0 is a valid age we would expect to see. ]

The age distribution numbers reported here must meet three criteria. If these criteria are not met then do not report ages.1. These age fields contain proportions by age for the natural origin fish. They are not the numbers of fish actually aged, nor

are they the expanded numbers for a population. Consider this scenario: The juvenile outmigrants estimate is 100,000 fish (as reported in the TotalNatural field) 500 fish were aged After age analysis is completed it is determined that 45% of the fish (meaning 45,000 of the 100,000) were age 0. In this case the value in this field should be 0.45 (45,000/100,000) not 45,000, 500, or 100,000.

2. The values of the Age0Prop through Age4PlusProp fields must sum to 1.00 ± 0.01.3. The age distribution must be derived only from the natural origin fish of the specific population and year this record

represents. Therefore, do not include age data that are derived in part or in whole from any other group of fish.

The age information may represent the exact group of fish indicated in the Abundance field, or a somewhat different group of fish. For example, the ages may have been taken from a geographic or temporal subset of the population. Whatever may be the case, ensure this information is included in the protocol and method documentation section below.

Age0PropLowerLimit The lower limit of the confidence interval for the Age0Prop field.

Single The associated alpha value is in the AgePropAlpha field, which is found below after the fields for age 4+.

Age0PropUpperLimit The upper limit of the confidence interval for the Age0Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age1Prop The proportion of natural origin fish that were age 1 (brood year +1).

Single See the Codes/Conventions column for the Age2Prop field.

Age1PropLowerLimit The lower limit of the confidence interval for the Age1Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age1PropUpperLimit The upper limit of the confidence interval for the Age1Prop field.

Single See the Codes/Conventions for the Age2PropLowerLimit field.

Age2Prop The proportion of natural origin fish that were age 2 (brood year +2).

Single See the Codes/Conventions column for the Age2Prop field.

Age2PropLowerLimit The lower limit of the confidence interval for the Age2Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age2PropUpperLimit The upper limit of the confidence interval for the Age2Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age3Prop The proportion of natural origin fish that were age 3 (brood year +3).

Single See the Codes/Conventions column for the Age0Prop field.

Page 32: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants TableAge3PropLowerLimit The lower limit of the confidence interval for the

Age3Prop field.Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age3PropUpperLimit The upper limit of the confidence interval for the Age3Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age4PlusProp The proportion of natural origin fish that were age 4 or higher (brood year +4 or more).

Single See the Codes/Conventions column for the Age0Prop field.

Age4PlusPropLowerLimit

The lower limit of the confidence interval for the Age4PlusProp field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age4PlusPropUpperLimit

The upper limit of the confidence interval for the Age4PlusProp field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

AgePropAlpha The significance level for the Age_x_Prop confidence intervals, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Page 33: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).ContactPersonFirst First name of person who is the best contact for

questions that may arise about this data record.Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. Memo

A 5. JuvenileOutmigrantsDetail TableThis table is a child of the JuvenileOutmigrants table. It stores metrics (outmigrant numbers) specific to the trapping site(s) and life stages used to calculate the juvenile outmigrant estimates captured in the JuvenileOutmigrants table. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrantsDetail Table

Fields for defining a unique record

ID Value used by computer to identify a record. Text 36 This value is a globally unique identifier GUID. It must be included for all new and updated records. It is also needed when indicating records to delete.

JuvenileOutmigrantsID Foreign key used to identify the parent record in the JuvenileOutmigrants table.

Text 36

Metrics supporting the "Indicators" fields in the JuvenileOutmigrants table

Location The specific location (trapping site) where abundance numbers were determined.

Text 255 This may be any of the following: the name of a fluvial water body and text description of where on that stream or river (river mile preferred, but river

kilometer, lat/long, or other characterization allowable). the name of an impounded fluvial water body (reservoir) and description of where on that reservoir. the name of a lentic water body, and description of where on that lake. the name of a dam.

Page 34: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrantsDetail TableLocPTcode PTAGIS code for the SmoltEqLocation field. Text 255 There should be a PTAGIS code for most locations where smolts were trapped. Provide that code if available, or multiple

codes if smolts were trapped at multiple locations for this population.LifeStage Life stage the record represents. Text 11 Acceptable values: use one of the following sets of values, depending on the fish.

Smolt

For Lower Columbia spring Chinook

use the following:o Subyearlingo Yearling

For Fall Chinook Willamette spring Chinook

use the following:o Fryo Subyearlingo Yearling

For Coho East-side spring/summer (stream-

type) Chinook Steelhead

use the following:o Fryo Parro Presmolto Smolt

For Upper Columbia summer Chinook

use the following:o Fryo Subyearling

For Chum Pink Sockeye

use the following:o Smolt

The suite of life stages to report are not yet determined for bull trout, coastal cutthroat trout, and any other species not explicitly listed here.

TotalNatural The point estimate for the number of natural origin fish of the indicated life stage passing the indicated location.

Single Estimated number of natural origin smolts that outmigrated in a particular year. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

TotalNaturalLowerLimit The lower limit of the confidence interval for the TotalNatural field.

Single

TotalNaturalUpperLimit The upper limit of the confidence interval for the TotalNatural field.

Single

TotalNaturalAlpha The significance level for the TotalNatural confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

SurvivalRate The point estimate for the survival rate of fish from the life stage and trapping site indicated by the LifeStage and Location fields of this table to the smolt equivalent estimation site indicated by the SmoltEqLocation in the JuvenileOutmigrants table.

Single Express as a proportion from 0 to 1.

The Location field of this table tells where abundance numbers were determined for a specific trapping site and life stage. The SmoltEqLocation field of the JuvenileOutmigrants table (this table's parent table) tells the location for which the number of smolt equivalents was estimated. In cases where Location=SmoltEqLocation and LifeStage="Smolt", this value will equal "1" because the data (TotalNatural field) already indicate the number of smolts at the smolt equivalent location.

SurvivalRateLowerLimit The lower limit of the confidence interval for the SmolSurvRate field.

Single

SurvivialRateUpperLimit The upper limit of the confidence interval for the SmolSurvRate field.

Single

SurvivalRateAlpha The significance level for the SmoltSurvRate confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Page 35: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrantsDetail TableContactAgency Agency, tribe, or other entity, or person responsible

for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe of Idaho Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

Comments about the metrics data

Comments Any issues, problems, questions about this record that were not already captured in other places.

Memo

Supporting information

JMXID PRODUCTION_ESTIMATE_ID value from the JMX system that corresponds to this record.

Text 35 This value lets this table refer to the corresponding record in the WDFW/NWIFC Juvenile Migrant Exchange (JMX) and thus allows for easy access to detailed data for the record.

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

MetricLocation Where this supporting metric is maintained at the source.

Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used to calculate this metric.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

Page 36: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

A 6. PresmoltAbundance TableThis table stores information concerning natural origin presmolt abundance. "Presmolt abundance" is the total number of fish estimated for the population and time frame (year and months) indicated by each record. Most commonly these records will represent parr numbers are ested for late summer, but other times may be entered, and all presmolt life stages are included in these estimates. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon SteelheadAdditional species may be added in the future: refer to http://old.streamnet.org/SpeciesInFW.html for common names.

Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

ESU_DPS For populations listed under the federal ESA, this is the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

RecoveryDomain Name of the "recovery domain," as defined by the NMFS Northwest Region, in which the population falls.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.MajorPopGroup Name of "major population group" (MPG) or

“stratum” as defined by the NMFS Northwest Region, in which the population falls.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

Page 37: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance TableCBFWApopName Population name as defined by CBFWA for

subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the abundance estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents one entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of one population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the natural origin spawner abundance value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the abundance estimate was made.

WaterBody Name of the body of water associated with the time series.

Text 255 This may be any of the following: the name of a fluvial water body. the name of an impounded fluvial water body (reservoir). the name of a lentic water body. a description of multiple water bodies if appropriate for the time series.

To allow for easy sorting, follow these general format examples: River or stream – John Day River; Fifteen Mile Creek. Fork of a river, main name first – John Day River, North Fork

o [for North Fork John Day River] Salmon River, East Fork South Fork

o [for East Fork South Fork Salmon River] Reservoir (the word "Lake" comes first) – Lake Billy Chinook; Cougar Reservoir. Natural lake (the word "Lake" comes last) – Alturas Lake.

Year The four-digit year represented. IntegerStartMonth The month presmolt sampling started. Text 9 Enter full name of month, correctly spelled.EndMonth The month presmolt sampling ended. Text 9 Enter full name of month, correctly spelled.ContactAgency Agency, tribe, or other entity, or person responsible

for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

Page 38: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance TableMethodNumber This field represents the method(s) used to calculate

the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

GeneralApproach The general class of method(s) used to make the abundance estimate.

Text 255 Acceptable values: Snorkeling Mark/recapture estimate Removal estimate Presmolt tagging with downmigrant trap recapture Down-migrant trapping

(Contact Mike Banach at 503-595-3152 if you need to add to this list.)

Notes to include in the MethodAdjustments field: For mark/recapture estimates include number of reaches

sampled, total number of reaches, reach lengths, total survey length/area by habitat type, total length/area expanded to by habitat type, and density (by habitat type).

For presmolt tagging with downmigrant trap recaptures include parr to smolt survival rate & smolt abundance (to back-calculate summer parr numbers), number of parr marked, and number recaptured.

For down-migrant trapping, include total number captured and overall trapping efficiency weighted by trapping period, if available.

Indicators

Abundance The point estimate for natural origin presmolt abundance.

Single Required if NullRecord = "No".Estimated number of natural origin presmolts for the particular year (date?) indicated. "Natural origin" means the fish's parents spawned in the wild. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population.AbundanceLowerLimit The lower limit of the confidence interval for the

Abundance field.Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

AbundanceUpperLimit The upper limit of the confidence interval for the Abundance field.

Single Minimum value = 0.

AbundanceAlpha The significance level for the Abundance confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Metrics supporting the "Indicators" fields above

Because of the diversity of ways in which presmolt numbers may be determined, there is not a common set of fields to act as "Metrics" for this data type. Therefore, at least initially, there are no "metrics" fields in this table.

Page 39: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance Table

Age determination

Age0Prop The proportion of natural origin fish that were age 0 (brood year +0).

Single Values must be between 0 and 1. Express with 3 digits to the right of the decimal point.

Ages in this table are based on the year spawning occurred, not necessarily the year eggs hatched, so care must be taken in reporting ages.

Assigning age can be complicated based on the life history (generally, salmon return and spawn in one year but hatch in the next, steelhead spawn and hatch in the same year). Make sure these details are accounted for in assigning ages. [ Note – This means we would never refer to age 0 salmon, because they hatch in the year after the eggs are laid, but for steelhead and other spring spawners age 0 is a valid age we would expect to see. ]

The age distribution numbers reported here must meet three criteria. If these criteria are not met then do not report ages.1. These age fields contain proportions by age for the natural origin fish. They are not the numbers of fish actually aged, nor

are they the expanded numbers for a population. Consider this scenario:a. The presmolt number estimate is 100,000 fish (as reported in the Abundance field)b. 500 fish were agedc. After age analysis is completed it is determined that 45% of the fish (meaning 45,000 of the 100,000) were age 0.d. In this case the value in this field should be 0.45 (45,000/100,000) not 45,000, 500, or 100,000.

2. The values of the Age0Prop through Age4PlusProp fields must sum to 1.00 ± 0.01.3. The age distribution must be derived only from the natural origin fish of the specific population and year this record

represents. Therefore, do not include age data that are derived in part or in whole from any other group of fish.

The age information may represent the exact group of fish indicated in the Abundance field, or a somewhat different group of fish. For example, the ages may have been taken from a geographic or temporal subset of the population. Whatever may be the case, ensure this information is included in the protocol and method documentation section below.

Age0PropLowerLimit The lower limit of the confidence interval for the Age2Prop field.

Single The associated alpha value is in the AgePropAlpha field, which is found below after the fields for age 4+.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.Age0PropUpperLimit The upper limit of the confidence interval for the

Age2Prop field.Single See the Codes/Conventions for the Age0PropLowerLimit field.

Minimum value = 0.Age1Prop The proportion of natural origin fish that were age 2

(brood year +1).Single See the Codes/Conventions column for the Age0Prop field.

Age1PropLowerLimit The lower limit of the confidence interval for the Age2Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age1PropUpperLimit The upper limit of the confidence interval for the Age2Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age2Prop The proportion of natural origin fish that were age 2 (brood year +2).

Single See the Codes/Conventions column for the Age0Prop field.

Age2PropLowerLimit The lower limit of the confidence interval for the Age2Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age2PropUpperLimit The upper limit of the confidence interval for the Age2Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age3Prop The proportion of natural origin fish that were age 3 (brood year +3).

Single See the Codes/Conventions column for the Age0Prop field.

Age3PropLowerLimit The lower limit of the confidence interval for the Age3Prop field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Page 40: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance TableAge3PropUpperLimit The upper limit of the confidence interval for the

Age3Prop field.Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age4PlusProp The proportion of natural origin fish that were age 4 or higher (brood year +4 or more).

Single See the Codes/Conventions column for the Age0Prop field.

Age4PlusPropLowerLimit

The lower limit of the confidence interval for the Age4PlusProp field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

Age4PlusPropUpperLimit

The upper limit of the confidence interval for the Age4PlusProp field.

Single See the Codes/Conventions for the Age0PropLowerLimit field.

AgePropAlpha The significance level for the Age_x_Prop confidence intervals, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Be sure to include information specified in the MethodAdjustments field, as appropriate.

Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Page 41: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance Table

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.

Page 42: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Section B: Indicators for Hatchery Programs and Populations of Hatchery Origin Fishes

B1. HatcherySpawning TableThis table stores information concerning hatchery spawning as defined by the Coordinated Assessments project. "Spawners" refers to the number of fish that were actually spawned in a hatchery or hatchery complex under a specific program, not necessarily the total number of fish spawned at the hatchery (complex). Excess non-spawned fish are ignored and are not included in this table. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for HatcherySpawning TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon Steelhead

Additional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not

recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

ESU_DPS For populations listed under the federal ESA, this is the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS in which the population falls geographically. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

Page 43: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for HatcherySpawning TableRecoveryDomain Name of the "recovery domain," as defined by the

NMFS Northwest Region, in which the population falls geographically.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

MajorPopGroup Name of "major population group" (MPG) or “stratum” as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

ESAlisted Flag indicating whether the hatchery fish are part of the ESU or DPS in which it falls geographically.

Text 3 Acceptable values: Yes No

If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found athttps://www.federalregister.gov/articles/2014/04/14/2014-08347/endangered-and-threatened-wildlife-final-rule-to-revise-the-code-of-federal-regulations-for-species.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the hatchery spawners estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents theone entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of theone population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the hatchery origin spawner abundance value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the hatchery spawners estimate was made.

HatcheryProgramName Hatchery program this record describes. Text 255HatcheryStockName Stock of hatchery fish this record describes. Text 255Hatchery Name of the hatchery or hatchery complex

associated with the time series.Text 255 This may be any of the following:

the name of a hatchery. the name of a hatchery complex. a description of multiple hatcheries if appropriate for the time series. (Providing alphabetically is preferred.)

Use the hatchery names shown in Appendix EF.

Page 44: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for HatcherySpawning TableHatcheryProgramType Purpose of the hatchery program this record

represents.Text 40 Acceptable values for this field are taken from the "Implementation and Compliance Monitoring" section of Appendix C in

Beasley, C.A., et al. 2008. Recommendations for broad scale monitoring to evaluate the effects of hatchery supplementation on the fitness of natural salmon and steelhead populations. Final report of the Ad hoc supplementation monitoring and evaluation workgroup. Available at http://wwwold.streamnet.org/CoordinatedAssessments/AHSWG-2008-FinalReport.pdf. Descriptions (in italics) are derived from the entire document as necessary. Segregated harvest augmentation [Purpose is to provide for harvest while attempting to keep hatchery origin fish from

spawning in the wild with natural origin fish.] Integrated supplementation [Purpose is to rebuild abundance of depressed naturally-spawning populations. Hatchery

origin and natural origin fish are intentionally encouraged to interbreed in the hatchery and in the natural environment.] Integrated supplementation/mitigation [Like "integrated supplementation" program, but with added purpose of providing

for harvest to mitigate for loss of harvest opportunities.] Conservation [This hatchery program type was listed in Appendix C of Beasley et al. 2008, but the document did not

provide any definition or description of this program type.]BroodstockType Method(s) used to raise hatchery fish. Text 18 Acceptable values:

Captive broodstock Segregated Integrated Experimental

SpawningYear The four-digit year in which spawning of this species (and run where appropriate) began.

Integer In cases where an unusual population is spawned uncharacteristically early (before January 1 for spring spawners) or late (after December 31 for fall spawners) for the species (and perhaps run), assign the year based on the majority of populations of this species/run in order to be consistent for all members of the spawning cohort. For example, most coho spawn in fall but a few populations do not begin spawning until after Jan. 1. The spawning year assigned for these unusual populations would match the other populations that spawned in the fall, even though these particular populations did not begin spawning until after December 31.

ContactAgency Agency, tribe, or other entity, or person responsible for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

Page 45: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for HatcherySpawning TableMethodNumber This field represents the method(s) used to calculate

the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Indicators

NumberSpawned The total number of fish spawned.

This field is required if the EggsTaken field is null.

Integer Required if the EggsTaken field is null and NullRecord = "No".This is the total number of fish used in spawning, which includes hatchery and natural origin fish of all ages. This value must be a whole number.

pNOB Proportion of hatchery broodstock that are natural origin fish. Single Express these values as numbers from zero to one, with three digits to the right of the decimal point.

pNOBLowerLimit The lower limit of the confidence interval for the pNOB field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

pNOBUpperLimit The upper limit of the confidence interval for the pNOB field.

Single Minimum value = 0.

pNOBAlpha The significance level for the pNOB confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

EggsTaken The total number of eggs taken and fertilized.

This field is required if the NumberSpawned field is null.

Long int Required if the NumberSpawned field is null and NullRecord = "No".This value must be a whole number.

EggsTakenLowerLimit The lower limit of the confidence interval for the EggsTaken field.

Long int This value must be a whole number.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.EggsTakenUpperLimit The upper limit of the confidence interval for the

EggsTaken field.Long int This value must be a whole number.

Minimum value = 0.EggsTakenAlpha The significance level for the EggsTaken confidence

interval, expressed as alpha.Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Metrics supporting the "Indicators" fields above

HOSIJ The number of hatchery origin fish spawned, including jacks.

Single "Hatchery origin" means the fish's parents were spawned in captivity rather than spawning naturally in the wild.

Page 46: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for HatcherySpawning TableHOSEJ The number of hatchery origin fish spawned,

excluding jacks.Single Includes only "adults" of hatchery origin, excluding jacks. "Hatchery origin" is as defined in the HOSIJ field.

For populations where jills occur, include them in the number of adult spawners; they will be accounted for in the “age determination” fields below.

For populations for which "jacks" are not recognized, leave this field blank. The only species for which jacks are recognized are Chinook salmon, coho salmon, chum salmon (rarely), and winter steelhead (rarely).

NOSIJ The number of natural origin fish spawned, including jacks.

Single This value reflects natural origin fish taken and spawned in the hatchery as part of the year's egg take operations. "Natural origin" means the fish's parents spawned in the wild.

NOSEJ The number of natural origin fish spawned, excluding jacks.

Single Includes only "adults" of natural origin, excluding jacks. "Natural origin" is as defined in the NOSIJ field.

For populations for which "jacks" are not recognized, leave this field blank. The only species for which jacks are recognized are Chinook salmon, coho salmon, chum salmon (rarely), and winter steelhead (rarely).

Age determination

Age2H The number of spawned hatchery origin fish that were age 2 (brood year +2).

Integer Age fields in this table show numbers of fish, not proportions. Values must be whole numbers.

Ages in this table are based on the year spawning occurred, not necessarily the year eggs hatched, so care must be taken in reporting ages.Assigning age can be complicated based on the life history (generally, salmon return and are spawned in one year but hatch in the next, steelhead are spawned and hatch in the same year). Make sure these details are accounted for in assigning ages.

These age fields contain the estimated numbers of fish spawned, by age, for hatchery origin fish (first set of age fields) and natural origin fish (second set of age fields). The values of the Age2H through Age11PlusN fields ideally should sum to the value in the NumberSpawned field, but imperfect data are allowable.

Age3H The number of spawned hatchery origin fish that were age 3 (brood year +3).

Integer See the Codes/Conventions column for the Age2H field.

Age4H The number of spawned hatchery origin fish that were age 4 (brood year +4).

Integer See the Codes/Conventions column for the Age2H field.

Age5H The number of spawned hatchery origin fish that were age 5 (brood year +5).

Integer See the Codes/Conventions column for the Age2H field.

Age6H The number of spawned hatchery origin fish that were age 6 (brood year +6).

Integer See the Codes/Conventions column for the Age2H field.

Age7H The number of spawned hatchery origin fish that were age 7 (brood year +7).

Integer See the Codes/Conventions column for the Age2H field.

Age8H The number of spawned hatchery origin fish that were age 8 (brood year +8).

Integer See the Codes/Conventions column for the Age2H field.

Age9H The number of spawned hatchery origin fish that were at age 9 (brood year +9).

Integer See the Codes/Conventions column for the Age2H field.

Age10H The number of spawned hatchery origin fish that were age 10 (brood year +10).

Integer See the Codes/Conventions column for the Age2H field.

Age11PlusH The number of spawned hatchery origin fish that were age 11 (brood year +11) or older.

Integer See the Codes/Conventions column for the Age2H field.

Age2N The number of spawned natural origin fish that were age 2 (brood year +2).

Integer See the Codes/Conventions column for the Age2H field.

Age3N The number of spawned natural origin fish that were age 3 (brood year +3).

Integer See the Codes/Conventions column for the Age2H field.

Page 47: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for HatcherySpawning TableAge4N The number of spawned natural origin fish that were

age 4 (brood year +4).Integer See the Codes/Conventions column for the Age2H field.

Age5N The number of spawned natural origin fish that were age 5 (brood year +5).

Integer See the Codes/Conventions column for the Age2H field.

Age6N The number of spawned natural origin fish that were age 6 (brood year +6).

Integer See the Codes/Conventions column for the Age2H field.

Age7N The number of spawned natural origin fish that were age 7 (brood year +7).

Integer See the Codes/Conventions column for the Age2H field.

Age8N The number of spawned natural origin fish that were age 8 (brood year +8).

Integer See the Codes/Conventions column for the Age2H field.

Age9N The number of spawned natural origin fish that were at age 9 (brood year +9).

Integer See the Codes/Conventions column for the Age2H field.

Age10N The number of spawned natural origin fish that were age 10 (brood year +10).

Integer See the Codes/Conventions column for the Age2H field.

Age11PlusN The number of spawned natural origin fish that were age 11 (brood year +11) or older.

Integer See the Codes/Conventions column for the Age2H field.

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Page 48: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for HatcherySpawning Table

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.Refer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managers.

Page 49: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

B2. PNI TableThis table stores information about proportionate natural influence (PNI) of supplementation hatcheries, which is an estimate of the relative selection pressure of the natural environment on hatchery origin fish in an integrated natural / hatchery population. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for PNI TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon Steelhead

Additional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not

recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

ESU_DPS For populations listed under the federal ESA, this is the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS in which the population falls geographically. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

RecoveryDomain Name of the "recovery domain," as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

MajorPopGroup Name of "major population group" (MPG) or “stratum” as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

Page 50: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PNI TablePopID Code for the TRT population of fish represented by

this record.Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations

are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

ESAlisted Flag indicating whether the hatchery fish are part of the ESU or DPS in which it falls geographically.

Text 3 Acceptable values: Yes No

If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found athttps://www.federalregister.gov/articles/2014/04/14/2014-08347/endangered-and-threatened-wildlife-final-rule-to-revise-the-code-of-federal-regulations-for-species.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the hatchery spawners PNI estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents theone entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of theone population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the hatchery origin spawner abundance PNI value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the hatchery spawners estimate was made.

HatcheryProgramName Hatchery program this record describes. Text 255HatcheryStockName Stock of hatchery fish this record describes. Text 255Hatchery Name of the hatchery or hatchery complex

associated with the time series.Text 255 This may be any of the following:

the name of a hatchery. the name of a hatchery complex. a description of multiple hatcheries if appropriate for the time series. (Providing alphabetically is preferred.)

To allow for easy sorting, it is preferable to use the hatchery name as listed in the StreamNet database at http://q.streamnet.org/Request.cfm?cmd=BuildPicklist&NewQuery=BuildCriteria&PicklistItem=Hatchery.

HatcheryProgramType Purpose of the hatchery program this record represents. is an integrated hatchery / natural production supplementation effort meant to increase the number of natural spawners in the population.

Text 3 Acceptable values: [See notes in HatcherySpawning table above.]

SpawningYear The four-digit year in which spawning of this species (and run where appropriate) began.

Integer In cases where an unusual population is spawned uncharacteristically early (before January 1 for spring spawners) or late (after December 31 for fall spawners) for the species (and perhaps run), assign the year based on the majority of populations of this species/run in order to be consistent for all members of the spawning cohort. For example, most coho spawn in fall but a few populations do not begin spawning until after Jan. 1. The spawning year assigned for these unusual populations would match the other populations that spawned in the fall, even though these particular populations did not begin spawning until after December 31.

Page 51: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PNI TableContactAgency Agency, tribe, or other entity, or person responsible

for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

MethodNumber This field represents the method(s) used to calculate the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Indicators

PNIIJ Proportionate natural influence index, calculated as

pNOB/(pNOB + pHOS)

where:pNOB = proportion of hatchery broodstock that are natural origin fish.pHOS = proportion of fish spawning naturally that are hatchery origin fish.

Include jacks when calculating this value.

This field is required if the PNIEJ field is null.

Single Required if the PNIEJ field is null and NullRecord = "No".This is equation 11 from Appendix A of Hatchery Scientific Review Group. 2009. Columbia River Hatchery Reform System-Wide Report. 278 pp. plus appendices. Available from http://www.hatcheryreform.us.

When calculating PNI, do not weight contribution of jacks according to differential reproductive success in the hatchery or the wild. Rather, weight all fish equally based on numbers that spawned.

Express these values as numbers from zero to one, with three digits to the right of the decimal point.

The only species for which jacks are recognized are Chinook salmon, coho salmon, chum salmon (rarely), and winter steelhead (rarely).

Page 52: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PNI TablePNIEJ Proportionate natural influence index, calculated as

pNOB/(pNOB + pHOS)

where:pNOB = proportion of hatchery broodstock that are natural origin fish.pHOS = proportion of fish spawning naturally that are hatchery origin fish.

Exclude jacks when calculating this value.

This field is required if the PNIIJ field is null.

Single Required if the PNIIJ field is null and NullRecord = "No".This is equation 11 from Appendix A of Hatchery Scientific Review Group. 2009. Columbia River Hatchery Reform System-Wide Report. 278 pp. plus appendices. Available from http://www.hatcheryreform.us.

Because jacks are not included in this value, the issue of weighting jack contributions is not applicable to this field.

Express these values as numbers from zero to one, with three digits to the right of the decimal point.

The only species for which jacks are recognized are Chinook salmon, coho salmon, chum salmon (rarely), and winter steelhead (rarely).

Metrics supporting the "Indicators" fields above

HOSIJH The number of hatchery origin fish spawned in the hatchery, including jacks. (This is the same value reported in HOSIJ field of the HatcherySpawning table.)

Single "Hatchery origin" means the fish's parents were spawned in captivity rather than spawning naturally in the wild.

NOSIJH The number of natural origin fish spawned in the hatchery, including jacks. (This is the same value reported in NOSIJ field of the HatcherySpawning table.)

Single This value reflects natural origin fish taken and spawned in the hatchery as part of the year's egg take operations. "Natural origin" means the fish's parents spawned in the wild.

NOSAIJ The point estimate for natural origin spawner abundance, including jacks, spawning in the wild.(This is the same value reported in NOSAIJ field of the NOSA table for the population and year specified for the current record.)

Single Estimated number of natural origin spawners contributing to spawning in the wild in a particular year.  “Spawners” includes jacks. "Natural origin" means the fish's parents spawned in the wild. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population.HOSAIJ The point estimate for hatchery origin spawner

abundance, including jacks, spawning in the wild.Single Estimated number of hatchery origin spawners contributing to spawning in the wild in a particular year.  “Spawners” includes

jacks. "Hatchery origin" means the fish's parents were spawned in captivity. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population.HOSEJH The number of hatchery origin fish spawned in the

hatchery, excluding jacks. (This is the same value reported in HOSEJ field of the HatcherySpawning table.)

Single "Hatchery origin" means the fish's parents were spawned in captivity rather than spawning naturally in the wild.

NOSEJH The number of natural origin fish spawned in the hatchery, excluding jacks. (This is the same value reported in NOSEJ field of the HatcherySpawning table.)

Single This value reflects natural origin fish taken and spawned in the hatchery as part of the year's egg take operations. "Natural origin" means the fish's parents spawned in the wild.

NOSAEJ The point estimate for natural origin spawner abundance, excluding jacks, spawning in the wild.(This is the same value reported in NOSAIJ field of the NOSA table for the population and year specified for the current record.)

Single Estimated number of natural origin spawners contributing to spawning in the wild in a particular year.  “Spawners” does not include jacks. "Natural origin" means the fish's parents spawned in the wild. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population.

Page 53: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PNI TableHOSAEJ The point estimate for hatchery origin spawner

abundance, excluding jacks, spawning in the wild.Single Estimated number of hatchery origin spawners contributing to spawning in the wild in a particular year.  “Spawners” does not

include jacks. "Hatchery origin" means the fish's parents were spawned in captivity. The statistical approach used to generate the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field.

Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population.

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

Page 54: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for PNI TableDataStatus Status of the data in the current record. Text 255 Acceptable values:

Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.Refer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managers.

B3. EggToRelease TableThis table stores information concerning egg to release survival rates for hatchery fish as defined by the Coordinated Assessments project. Egg to release survival rates are specific to a production group, as well as to the specific egg stage and release stage being described in each record of data.

(Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for EggToRelease TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.

Page 55: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for EggToRelease TableCommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon Steelhead

Additional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not

recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

ESU_DPS For populations listed under the federal ESA, this is the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS in which the population falls geographically. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

RecoveryDomain Name of the "recovery domain," as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

MajorPopGroup Name of "major population group" (MPG) or “stratum” as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

ESAlisted Flag indicating whether the hatchery fish are part of the ESU or DPS in which it falls geographically.

Text 3 Acceptable values: Yes No

If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found athttps://www.federalregister.gov/articles/2014/04/14/2014-08347/endangered-and-threatened-wildlife-final-rule-to-revise-the-code-of-federal-regulations-for-species.

Page 56: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for EggToRelease TableCBFWApopName Population name as defined by CBFWA for

subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the ETR estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents theone entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of theone population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the hatchery origin spawner abundance ETR value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the ETR estimate was made.

HatcheryProgramName Hatchery program this record describes. Text 255HatcheryStockName Stock of hatchery fish this record describes. Text 255Hatchery Name of the hatchery or hatchery complex

associated with the time series.Text 255 This may be any of the following:

the name of a hatchery. the name of a hatchery complex. a description of multiple hatcheries if appropriate for the time series. (Providing alphabetically is preferred.)

To allow for easy sorting, it is preferable to use the hatchery name as listed in the StreamNet database at http://q.streamnet.org/Request.cfm?cmd=BuildPicklist&NewQuery=BuildCriteria&PicklistItem=Hatchery.

SpawningYear The four-digit year in which spawning of this species (and run where appropriate) began.

Integer In cases where an unusual population is spawned uncharacteristically early (before January 1 for spring spawners) or late (after December 31 for fall spawners) for the species (and perhaps run), assign the year based on the majority of populations of this species/run in order to be consistent for all members of the spawning cohort. For example, most coho spawn in fall but a few populations do not begin spawning until after Jan. 1. The spawning year assigned for these unusual populations would match the other populations that spawned in the fall, even though these particular populations did not begin spawning until after December 31.

EggStage Life stage at which the number of eggs was determined.

[The number of eggs is shown in the "Eggs" field.]

Text 30 Acceptable values: Unfertilized eggs Fertilized eggs before eye-up Eyed eggs

ReleaseStage Life stage at which the eggs or fish were released into the wild.

Text 15 This value must be a whole number.Acceptable values: Egg [Unhatched eggs.] Unfed fry [Hatched juvenile fish that have not yet been fed in the hatchery.] Juvenile [For the purposes of this table, these are fish no longer "unfed fry", but not yet smolts.] Age 0 smolt [Fish that smolt in the same year the eggs hatched.] Age 1+ smolt [Fish that smolt at age 1 or older. That is, they smolt in a year other than when the eggs hatch.]

Page 57: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for EggToRelease TableContactAgency Agency, tribe, or other entity, or person responsible

for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

MethodNumber This field represents the method(s) used to calculate the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Indicator

ETR The point estimate for egg-to-release survival rate, calculated as 100 X the point estimate of the number of released fish, divided by the point estimate of the number of eggs that produced those released fish.

Single Required if NullRecord = "No".Express these values as percentages (numbers from zero to one hundred), without a percent sign, with one digit to the right of the decimal point. Example: 0.923 = 92.3.

This field holds a numeric value only -- the percent sign is implied but not included.ETRLowerLimit The lower limit of the confidence interval for the

ETR field.Single This field holds a numeric value only -- the percent sign is implied but not included.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.ETRUpperLimit The upper limit of the confidence interval for the

ETR field.Single This field holds a numeric value only -- the percent sign is implied but not included.

Minimum value = 0.ETRAlpha The significance level for the ETR confidence

interval, expressed as alpha.Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Metrics supporting the "Indicator" fields above

Eggs The point estimate for the number of eggs that produced the released fish. Do not include culled eggs in the egg count used to calculate this egg-to-release survival rate.

Long int This value must be a whole number.

Page 58: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for EggToRelease TableEggsLowerLimit The lower limit of the confidence interval for the

Eggs field.Long int This value must be a whole number.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.EggsUpperLimit The upper limit of the confidence interval for the

Eggs field.Long int This value must be a whole number.

Minimum value = 0.EggsAlpha The significance level for the Eggs confidence

interval, expressed as alpha.Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Released The point estimate for the number of eggs planted or fish released.

Long int This value must be a whole number.

ReleasedLowerLimit The lower limit of the confidence interval for the Released field.

Long int This value must be a whole number.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.ReleasedUpperLimit The upper limit of the confidence interval for the

Released field.Long int This value must be a whole number.

Minimum value = 0.ReleasedAlpha The significance level for the Released confidence

interval, expressed as alpha.Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Page 59: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for EggToRelease Table

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.Refer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managers.

Page 60: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

B4. SAR_Hatchery TableThis table stores information concerning smolt to adult ratios (SAR) as defined by the Coordinated Assessments project. Smolt to adult ratios are specific to the smolt and adult locations described in each row of data. Adult returns include all fish that reach the location where adults are counted, regardless of their disposition after that point: strays, harvested fish, and fish with other dispositions are included as long as they reached the adult counting location. (Back to Table of Contents.)

Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery TableFields for defining a unique record

ID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID.) When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon Steelhead

Additional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not

recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

ESU_DPS For populations listed under the federal ESA, this is the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS in which the population falls geographically. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

RecoveryDomain Name of the "recovery domain," as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

Page 61: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery TableMajorPopGroup Name of "major population group" (MPG) or

“stratum” as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

ESAlisted Flag indicating whether the hatchery fish are part of the ESU or DPS in which it falls geographically.

Text 3 Acceptable values: Yes No

If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found athttps://www.federalregister.gov/articles/2014/04/14/2014-08347/endangered-and-threatened-wildlife-final-rule-to-revise-the-code-of-federal-regulations-for-species.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the hatchery origin spawners SAR estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents theone entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of theone population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the hatchery origin spawner abundance SAR value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the hatchery spawners estimate was made.

HatcheryProgramName Hatchery program this record describes. Text 255HatcheryStockName Stock of hatchery fish this record describes. Text 255Hatchery Name of the hatchery or hatchery complex

associated with the time series.Text 255 This may be any of the following:

the name of a hatchery. the name of a hatchery complex. a description of multiple hatcheries if appropriate for the time series. (Providing alphabetically is preferred.)

To allow for easy sorting, it is preferable to use the hatchery name as listed in the StreamNet database at http://q.streamnet.org/Request.cfm?cmd=BuildPicklist&NewQuery=BuildCriteria&PicklistItem=Hatchery.

SmoltLocation The specific location(s) for where the fish were released or the abundance was determined.

Text 255 This may be any of the following: the name of a hatchery facility the name of a fluvial water body and text description of where on that stream or river (river mile preferred, but river

kilometer, lat/long, or other characterization allowable). the name of an impounded fluvial water body (reservoir) and description of where on that reservoir. the name of a lentic water body, and description of where on that lake. a description of multiple water bodies if appropriate for the time series, with descriptions of specific locations. the name of a dam.

SmoltLocPTcode PTAGIS code for the location where fish were enumerated.

Text 255 There should be a PTAGIS code for most locations where smolts were enumerated. Provide that code, or multiple codes if smolts were enumerated at multiple locations for this population.

Page 62: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery TableAdultLocation The specific location(s) for where the adult

abundance numbers were determined.Text 255 This may be any of the following:

the name of a fluvial water body, with specific location described (river mile preferred, but river kilometer, lat/long, or other characterization allowable).

the name of an impounded fluvial water body (reservoir), with specific location described the name of a lentic water body, with specific location described a description of multiple water bodies if appropriate for the time series. the name of a dam.

AdultLocPTcode PTAGIS code for the location where adults were counted.

Text 255 Follow example 2 fields above

SARtype Type of SAR. See Codes/Conventions column for details.

Text 255 This field is used to describe the category of SAR for the current record, in terms of where the smolt and adult numbers were determined that went into the SAR. Current list of acceptable values are shown below. If you have a need for other types, contact the Coordinated Assessment group to define the new type. Release site to release site Release site to dam Named dam to named dam Named dam to release site

The values in the "SmoltLocation" and "AdultLocation" fields should match the categorization in this field.OutmigrationYear The four-digit year for which this SAR is calculated,

defined as the year the group migrated to sea.Integer Year in which the fish migrated to the ocean. This is often not the same as brood year.

ContactAgency Agency, tribe, or other entity, or person responsible for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

MethodNumber This field represents the method(s) used to calculate the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Page 63: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery Table

Indicator

SAR The point estimate for smolt-to-adult ratio, calculated as 100 X the point estimate of the number of returning hatchery origin adults, divided by the point estimate of the number of smolts that produced those returning adultss.

Single Required if NullRecord = "No".Express these values as percentages (numbers from zero to one hundred), with one digit to the right of the decimal point. Examples: .024 = 2.4, .001 = 0.1.

This field holds a numeric value only -- the percent sign is implied but not included.

Do NOT include repeat spawners in the number of adult returns. (A fish only returns once from smolting; subsequent returns are not appropriate for inclusion in smolt-to-adult estimates because they head to sea as adults on subsequent trips and thus are not exposed to the same suite of mortality factors.)

SARLowerLimit The lower limit of the confidence interval for the SAR field.

Single This field holds a numeric value only -- the percent sign is implied but not included.

Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.SARUpperLimit The upper limit of the confidence interval for the

SAR field.Single This field holds a numeric value only -- the percent sign is implied but not included.

Minimum value = 0.SARAlpha The significance level for the SAR confidence

interval, expressed as alpha.Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

ReturnsMissing This field indicates whether any adult return years for this out-migration year were missing.

Text 3 Acceptable values: Yes [Years were missing.] No [No years missing; return estimates were complete.]

If some years were missing, describe how that gap was addressed under ReturnMissingExplanationReturnsMissingExplanation

If some return data are not accounted for in the SAR estimate, explain the gap.

Memo Describe how any gap in return years was addressed: Filled in with an interpolated estimate, ignored, etc.

Metrics supporting the "Indicator" fields above

TSR Total smolts released. Point estimate of the number of smolts released for this outmigration year, or the number of marked smolts used to calculate the SAR.

Single This should be the numerdenominator in the ratio calculation, with all previous losses (handling mortality, tag loss estimate, etc.) already taken out. The Methods citation should address how this was done.

TSRLowerLimit The lower limit of the confidence interval for the TSR field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

TSRUpperLimit The upper limit of the confidence interval for the TSR field.

Single Minimum value = 0.

TSRAlpha The significance level for the TSR confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

TAR Total adult return. Point estimate of the number of adults returning for the first time from the indicated release year, or the group of marked smolts (as appropriate), to match the smolts in the TSR field. Includes fish of all dispositions – harvested above adult return site, strays, etc.

Single For iteroparous species such as steelhead, include only those adults returning to spawn for the first time. (Failure to do so will result in some adults being counted twice for returns purposes.)

TARLowerLimit The lower limit of the confidence interval for the TAR field.

Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

TARUpperLimit The upper limit of the confidence interval for the TAR field.

Single Minimum value = 0.

TARAlpha The significance level for the TAR confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Page 64: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery TableHarvestAdj How was the return adjusted to account for harvest?

(Are harvested fish included in the estimate of number of adults?)

Text 35 Acceptable values: Ocean [Value in the TAR field was adjusted for harvest in the ocean, but not in the mainstem and not in tributaries.] Ocean and mainstem [Value in the TAR field was adjusted for harvest in the ocean and mainstem, but not in tributaries.] Ocean and mainstem and tributaries [Value in the TAR field was adjusted for harvest in the ocean, mainstem, and

tributaries.] Mainstem [Value in the TAR field was adjusted for harvest in the mainstem but not in tributaries.] Mainstem and tributaries [Value in the TAR field was adjusted for harvest in both the mainstem and tributaries.] Tributaries [Value in the TAR field was adjusted for harvest in tributaries but not in the mainstem.] Not adjusted [Value in the TAR field was not adjusted for harvest.]

OceanHarvest The estimated number of adults and jacks from the smolt group indicated in the TSR field that were harvested in the ocean.

Single This field is for harvests in the ocean, which is defined as not including the estuary. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated natural origin group. Leave blank for juvenile recruits.

MainstemHarvest The estimated number of adults and jacks from the smolt group indicated in the TSR field that were harvested in the mainstem.

Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies). Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This harvest value reflects fish harvested from the indicated smolt group -- they may be all natural origin, all hatchery origin, or mixed origin, as indicated by the RearingType field. This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation.

TribHarvest The estimated number of adults and jacks from the smolt group indicated in the TSR field that were harvested in tributaries.

Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This harvest value reflects fish harvested from the indicated smolt group -- they may be all natural origin, all hatchery origin, or mixed origin, as indicated by the RearingType field. This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation.

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol.

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

Page 65: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery TableProtMethDocumentation Citation or documentation that describes the

protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

Page 66: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery TableContactEmail Email address of person who is the best contact for

questions that may arise about this data record.Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.Refer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managers.

B5. RperS_Hatchery TableThis table stores information concerning recruits per spawner (R/S) for hatchery origin fish as defined by the Coordinated Assessments project. Recruit per spawner ratios are specific to the locations and seasons described in each record of data. This table is for adult recruits only.

(Back to Table of Contents.)Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table

Fields for defining a unique recordID(unique)

Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). When submitting a new record you may include this value or leave it blank. If you include this value then it will be used by

the central system. If you leave it blank then a value will be created for you, and it will be sent back to your system where it must be incorporated.

When updating or deleting records this value must be included.CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following:

Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon Steelhead

Additional species may be added in the future: refer to http://wwwold.streamnet.org/SpeciesInFW.html for common names.Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not

recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

ESU_DPS For populations listed under the federal ESA, this is the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS in which the population falls geographically. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed athttp://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm.ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.Many hatchery populations are not part of an ESU. In such cases leave this field blank.

Page 67: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery TableRecoveryDomain Name of the "recovery domain," as defined by the

NMFS Northwest Region, in which the population falls geographically.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list. Many hatchery populations are not part of a recovery domain. In such cases leave this field blank. Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Recovery domains are listed and mapped athttp://www.nwr.noaa.gov/Salmon-Recovery-Planning/Recovery-Domains/Index.cfm. Further information about recovery domains can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.

MajorPopGroup Name of "major population group" (MPG) or “stratum” as defined by the NMFS Northwest Region, in which the population falls geographically.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

PopID Code for the TRT population of fish represented by this record.

Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

ESAlisted Flag indicating whether the hatchery fish are part of the ESU or DPS in which it falls geographically.

Text 3 Acceptable values: Yes No

If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found athttps://www.federalregister.gov/articles/2014/04/14/2014-08347/endangered-and-threatened-wildlife-final-rule-to-revise-the-code-of-federal-regulations-for-species.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.PopFit Categorization of how well the geographic extent of

the recruits per spawner estimate corresponds to the geographic definition of the population.

Text 8 Acceptable values: Same [Estimate represents one entire population, the whole population, and nothing but the population.] Portion [Estimate represents a portion of one population.] Multiple [Estimate is from more than one population. (Describe in PopFitNotes field.)]

PopFitNotes Text description of how well the recruits per spawner value corresponds to the defined population.

Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish for which the recruits per spawner estimate was made.

HatcheryProgramName Hatchery program this record describes. Text 255HatcheryStockName Stock of hatchery fish this record describes. Text 255Hatchery Name of the hatchery or hatchery complex

associated with the time series.Text 255 This may be any of the following:

the name of a hatchery. the name of a hatchery complex. a description of multiple hatcheries if appropriate for the time series. (Providing alphabetically is preferred.)

To allow for easy sorting, it is preferable to use the hatchery name as listed in the StreamNet database at http://q.streamnet.org/Request.cfm?cmd=BuildPicklist&NewQuery=BuildCriteria&PicklistItem=Hatchery.

Page 68: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery TableReleaseLocation The specific location(s) for where the fish were

released.Text 255 This may be any of the following:

the name of a hatchery facility the name of a fluvial water body and text description of where on that stream or river (river mile preferred, but river

kilometer, lat/long, or other characterization allowable). the name of an impounded fluvial water body (reservoir) and description of where on that reservoir. the name of a lentic water body, and description of where on that lake. a description of multiple water bodies if appropriate for the time series, with descriptions of specific locations. the name of a dam.

RecruitLocation The specific location(s) for where the recruit abundance numbers were determined.

Text 255 This field describes the location where the abundance of recruits is determined, and may be any of the following: the name of a fluvial water body. the name of a lentic water body. a dam or other location where fish numbers can be estimated. a description of multiple water bodies if appropriate for the time series. other, as appropriate.

BroodYear The four-digit brood year for which the recruit per spawner ratio is calculated. Same as "spawning year" for the parent generation.

Integer This field is used to tie juvenile ‘recruits’ or adult returns (over multiple return years) to a specific spawning year. This is the year in which spawning of this species (and run where appropriate) began.

In cases where an unusual population begins spawning uncharacteristically early (before January 1 for spring spawners) or late (after December 31 for fall spawners) for the species (and perhaps run), assign the year based on the majority of populations of this species/run in order to be consistent for all members of the spawning cohort. For example, most coho spawn in fall but a few populations do not begin spawning until after Jan. 1. The brood year assigned for these unusual populations would match the other populations that spawned in the fall, even though these particular populations did not begin spawning until after December 31.

RperStype The type of recruit per spawner estimate, in terms of what fish are included in the estimates of number of spawners and number of recruits.

Text 255 Juvenile recruits are not included in this table. Acceptable values:For adult to adult R/S estimates: Total recruits per total spawners [Includes males and jacks] Adult recruits per adult spawners [Includes adult males, but not jacks] Female recruits per female spawners [All males excluded]If more than one type of estimate is done for one brood year for a population, the estimates go in separate data records.

ContactAgency Agency, tribe, or other entity, or person responsible for these data that is the best contact for questions that may arise about this data record.

Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

Page 69: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery TableMethodNumber This field represents the method(s) used to calculate

the values in the "Indicators" and "Metrics" sections.

This field is used in conjunction with the ContactAgency field. See the Codes/Conventions column for details.

Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, it is possible to share values that are based on different assumptions.

If only one set of methods is used to calculate the values for all years for a population, enter "1" for all records. Even if methods changed, you can enter "1" for all records if there is always only one record per year for a population.

If more than one set of methods is used to calculate final values over a range of years for a population, use this field to indicate which records are meant to go together. For example, if method 1 was used to calculate values for 1960 through 1994, and method 2 was used to calculate values for 1980 through 2013, then there will be more than one record for the years 1980 through 1994. In such cases you would enter "1" for records that result from the 1960-1994 method, and "2" for records that result from the 1980-2013 method. Similarly, if 3 different methods are proposed in an area for the same years, then use "1" and "2" and "3" to indicate which records belong together. This lets a data user know which records belong together.

When more than one record exists for a population X year combination, it is up to biologists using the data to select the value of most use when conducting their day to day business. The ContactAgency and MethodNumber fields allow for this.

Indicator

RperS The point estimate for the ratio of recruits from the designated brood year and type, divided by the number of parent spawners responsible for that brood year. Straight ratio calculation, not a log/natural log transformation.

Single Required if NullRecord = "No".For iteroparous species such as steelhead, adult recruits should include all fish from the brood year that return to spawn, including repeat spawners, since repeat spawners add to the productivity of the population.

Juvenile recruits are not included in this table.RperSLowerLimit The lower limit of the confidence interval for the

RperS field.Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

RperSUpperLimit The upper limit of the confidence interval for the RperS field.

Single Minimum value = 0.

RperSAlpha The significance level for the RperS confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Metrics supporting the "Indicator" fields above

NumberSpawned The total number of fish spawned. Integer This is the total number of fish used in spawning, which includes hatchery and natural origin fish of all ages. Not included are pre-spawn mortalities and excess non-spawned (culled) fish. This value must be a whole number.

Recruits Point estimate for the total number of recruits from the indicated combination of species, run, population, hatchery program, release location, recruit location, brood year, and RperStype.

Long int Adult recruits should include all fish from the brood year that return to the recruit location, including repeat spawners, since repeat spawners add to the productivity of the population.

RecruitsLowerLimit The lower limit of the confidence interval for the Recruits field.

Long int Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field.

RecruitsUpperLimit The upper limit of the confidence interval for the Recruits field.

Long int Minimum value = 0.

RecruitsAlpha The significance level for the Recruits confidence interval, expressed as alpha.

Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95".

Page 70: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery TableRecruitsMissing This field indicates whether any recruits for this

brood year were missing.Text 3 Indicate if recruit estimates for any year were missing. If so, indicate in this field, and explain how the gap was addressed in

the RecruitsMissingExplanation field and in the Methods citation.

Acceptable values: Yes [Years were missing.] No [No years missing; recruit estimates were complete.]

If some years were missing, describe how that gap was addressed under RecruitsMissingExplanation.RecruitsMissingExplanation

If some recruits data are not accounted for in the RperS estimate, explain the gap.

Memo Explain how any gaps in returns from this year class were addressed (estimated to fill in, ignored, etc.).

HarvestAdj For adult returns, how was the return adjusted to account for harvest?

Text 35 Acceptable values: Ocean [Value in the Recruits field was adjusted for harvest in the ocean, but not in the mainstem and not in tributaries.] Ocean and mainstem [Value in the Recruits field was adjusted for harvest in the ocean and mainstem, but not in

tributaries.] Ocean and mainstem and tributaries [Value in the Recruits field was adjusted for harvest in the ocean, mainstem, and

tributaries.] Mainstem [Value in the Recruits field was adjusted for harvest in the mainstem but not in tributaries.] Mainstem and tributaries [Value in the Recruits field was adjusted for harvest in both the mainstem and tributaries.] Tributaries [Value in the Recruits field was adjusted for harvest in tributaries but not in the mainstem.] Not adjusted [Value in the Recruits field was not adjusted for harvest.]

OceanHarvest The estimated number of adults and jacks from the spawner group indicated in the NumberSpawned field that were harvested in the ocean.

Single This field is for harvests in the ocean, which is defined as not including the estuary. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested fish.

This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated natural origin group. Leave blank for juvenile recruits.

MainstemHarvest The estimated number of adults and jacks from the spawner group indicated in the NumberSpawned field that were harvested in the mainstem.

Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies) defining the population, in including the estuary. Provide this estimate regardless of whether the number of recruits was adjusted for mainstem harvest.

This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated release group.

TribHarvest The estimated number of adults and jacks from the spawner group indicated in the NumberSpawned field that were harvested in tributaries.

Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate regardless of whether the number of recruits was adjusted for the harvest in tributaries.This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This harvest value reflects fish harvested from the indicated release group.

Age determination

Age2Adults Total number of recruits that recruited at age 2 (brood year +2).

Single Ages in this table are based on the year spawning occurred, not necessarily the year they hatched, so care must be taken in assigning returning fish to a brood year.Assigning returning fish to a brood year can be complicated based on the life history (generally, salmon return and spawn in one year but hatch in the next, steelhead spawn and hatch in the same year). Make sure these details are accounted for in assigning returns to a year class.Adult recruits should include all fish from the brood year that return to spawn, including repeat spawners, since repeat spawners add to the productivity of the population.

Age3Adults Total number of recruits that recruited at age 3 (brood year +3).

Single See the Codes/Conventions column for the Age2Adults field.

Age4Adults Total number of recruits that recruited at age 4 (brood year +4).

Single See the Codes/Conventions column for the Age2Adults field.

Age5Adults Total number of recruits that recruited at age 5 (brood year +5).

Single See the Codes/Conventions column for the Age2Adults field.

Page 71: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery TableAge6Adults Total number of recruits that recruited at age 6

(brood year +6).Single See the Codes/Conventions column for the Age2Adults field.

Age7Adults Total number of recruits that recruited at age 7 (brood year +7).

Single See the Codes/Conventions column for the Age2Adults field.

Age8Adults Total number of recruits that recruited at age 8 (brood year +8).

Single See the Codes/Conventions column for the Age2Adults field.

Age9Adults Total number of recruits that recruited at age 9 (brood year +9).

Single See the Codes/Conventions column for the Age2Adults field.

Age10Adults Total number of recruits that recruited at age 10 (brood year +10).

Single See the Codes/Conventions column for the Age2Adults field.

Age11PlusAdults Total number of recruits that recruited at age 11 (brood year +11 or more).

Single See the Codes/Conventions column for the Age2Adults field.

Protocol and method documentation

ProtMethName The name(s) of all protocols and associated data collection and data analysis methods used to calculate the indicator estimate.

Memo Provide title(s) of protocol and name(s) of relevant methods used.

Documentation should include the study design (including spatial, temporal, response and inference designs), annual implementation notes on variations from routine step by step procedures or design criteria, also known as survey design, description of field methodology and analytical approach.

ProtMethURL URL(s) for published protocols and methods describing the methodology and documenting the derivation of the indicator. If published in MonitoringMethods.org, this link will provide access to study design information and all methods associated with the protocol

Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods documentation should include survey design, description of field methodology and analytical approach. URL links may be to online methods documentation resources like MonitoringMethods.org, other online resources, or online literature.

If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, provide a new link.

ProtMethDocumentation Citation or documentation that describes the protocol and/or method(s) listed in the ProtMethName field. Include references not documented in MonitoringMethods.org, such as reports, journal articles or other publications that describe the survey design, field methodology and analytical approach used to derive the indicator estimate.

Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other publications that describe the study design (including spatial, temporal, response and inference designs), variations from routine step by step procedures or design criteria, description of field methodology and analytical approach. If the methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide the URL). Leave this field blank if methodology is described in MonitoringMethods.org.

Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

If methodology is unchanged from a previous year, use the previous link or reference citation. If methodology changed, provide a new link or reference citation.

MethodAdjustments Minor adjustments to a method in a given year that are not described in the method citations above but are important.

Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which document was adjusted.

In MonitoringMethods.org, documentation of changes or adjustments to methods or protocols can be described in the Implementation Notes section of each published method or protocol.

Comments about the data

Comments Any issues, problems, questions about this indicator that were not already captured in other places.

Memo

Page 72: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table

Supporting information

NullRecord In some years data may not be collected and so a value cannot be calculated. For example, high muddy water or wildfires can prevent redd counts. This field is used to indicate that a record does not exist because the data do not exist to calculate it.

Text 3 Normally "No".A value of "Yes" in this field is a positive statement that the data do not exist to calculate the indicator for the population and time period specified.

The value of including this field is so that missing data are explicitly accounted for rather than being a perpetually open question that is repeatedly researched. Explain in the Comments field why the data do not exist.

DataStatus Status of the data in the current record. Text 255 Acceptable values: Draft [Values in this record are preliminary and have not been thoroughly reviewed.] Reviewed [Values in this record have been reviewed but are not yet approved as "final".] Final [Values in this record have been thoroughly reviewed and are considered "final".](Note: We will watch this field until about January 2016. If nobody uses anything but “Final” then we can delete this field.)

LastUpdated Date (and time if desired) the information in this record was last updated.

Date/Time If an exact date is not known, give an estimate.

IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s).MetricLocation Where the supporting metrics are maintained at the

source.Memo If online, provide URL(s).

MeasureLocation Where the measurements are maintained that were used for these calculations.

Memo If online, provide URL(s).

ContactPersonFirst First name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPersonLast Last name of person who is the best contact for questions that may arise about this data record.

Text 30

ContactPhone Phone number of person who is the best contact for questions that may arise about this data record.

Text 30

ContactEmail Email address of person who is the best contact for questions that may arise about this data record.

Text 50

MetaComments Comments regarding the supporting information. MemoFields needed by people programming the Exchange Network

If you are a programmer or database manager, refer to Appendix A for additional fields that are part of this table but are not listed here.Refer to Appendix A for additional fields that are part of this table but are needed only by programmers and database managers.

Page 73: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

III. Appendices

Appendix A. Fields included in every table by reference

The fields shown in this appendix are included in all tables of sections A and B of this document. These fields are for use by the programmers implementing the Exchange Network system; everyone else can ignore them. In the interest of saving space in the document, easing editing of this document, and keeping these fields out of the way of people who don't need to see them, these fields are included here by reference rather than being shown in every table above. At this time none of these fields are required except the "SubmitAgency" and "Publish" fields.

Field Name Field Description Data Type Codes/Conventions for RperS-Hatchery TableFields needed by people programming the Exchange Network

SubmitAgency Initials or acronym for the agency, tribe, or other entity, or name of person, that sent this record of data to the exchange network node at StreamNet.

Note that it is possible for one entity to share data with another, and that second entity sends the record to the exchange network node. For example, the Shoshone-Bannock Tribes may send data to IDFG, who in turn sends those data to the exchange network. In such a case the Sho-Ban Tribes would be identified as the contact agency for the data, but the "SubmitAgency" would be IDFG.

Text 255 Entries in this field must precisely match a name in the Acronym field of the StreamNet agency list unless it is for an individual. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. CRITFC = Columbia River Inter-Tribal Fish Commission CCT = Colville Confederated Tribes YIN = Confederated Tribes and Bands of the Yakama Indian Nation CTUIR = Confederated Tribes of the Umatilla Indian Reservation CTWSIR = Confederated Tribes of the Warm Springs Reservation of Oregon IDFG = Idaho Department of Fish and Game NPT = Nez Perce Tribe ODFW = Oregon Department of Fish and Wildlife STOI = Spokane Tribe of Indians1

WDFW = Washington Department of Fish and WildlifeRefID The unique StreamNet reference ID number that

identifies the source document or database from which the record was obtained.

Long int Pre-Data Exchange - 0 - 1,000WDFW = 10,000-19,999; 100,000-199,999CRITFC = 20,000-29,999; 200,000-299,999USFWS = 30,000-39,999; 300,000-399,999IDFG = 40,000-49,999; 400,000-499,999ODFW = 50,000-59,999; 500,000-599,999PSMFC = 60,000-69,999; 600,000-699,999MFWP = 70,000-89,999; 700,000-799,999CDFG = 90,000-99,999; 800,000-899,999

UpdDate The date and time that the record was created or updated. For data obtained in electronic format from another source it can reflect the date and time of data capture or of conversion to Coordinated Assessment/StreamNet standards.

Datetime This can be the time a record was created, the last time it was edited, or the last time it was QCd.

DataEntry Compiler's name. Text 50 The name of the person who entered the record.DataEntryNotes Notes about this record by the compiler identified in

the "DataEntry" field.Memo Notes for the compiler to reference field office, contact, or any other information.

CompilerRecordID Agency record ID maintained by the data submitter. Text 36 This field can be used in any way the compiler may find helpful. For example, it can be used to create a link between the Coordinated Assessments exchange network and an internal system such as ODFW's Salmon Tracker.

Page 74: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for RperS-Hatchery TablePublish Yes/no value indicating whether this record should

be shared freely with all public users via the Exchange Network. If "No" then the record can only be accessed by using the apikey that created it.

Text 3 Acceptable values: Yes [Record will be shared with public via Exchange Network.] No [Record will not be shared with public via Exchange Network.]

Default value = "No" in the central database, which means that if a record is sent without this field then this value is set to "No" and the record will not show to the public. Setting this value to "No" lets you test your systems and avoid having such test records be output on the public system.

Page 75: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Appendix B. Glossary

Terms in this list are defined in the following way in this document....For later inclusion...

Page 76: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Appendix C. Recovery Domains, Species, ESUs, MPGs, and Populations Defined by NMFS and NPCC/CBFWA/CRITFC

The tables in the main portion of this document ask that the recovery domain, evolutionarily significant unit (ESU), major population groups (MPG), and fish population code be provided whenever possible and appropriate. Listed below in hierarchical order are the names of the recovery domains, ESUs, MPGs, and fish populations recognized by NMFS as of April 20, 2015.September 26, 2012. The names shown were provided by Jeff Cowen of NMFS on September 26, 2012.

MPGs are groups of populations intermediate in scope between individual populations and ESUs. MPGs are sometimes called "strata" in the Willamette/Lower Columbia recovery domain and "geographic regions" in the Puget Sound recovery area. Further information about MPGs can be found at http://www.nwfsc.noaa.gov/trt/domains.cfm.

The hierarchical list below follows the following format. The "PopID" value is used in the tables of this document to indicate the population. Pay close attention to the PopID value you choose – nearly all, but not all, values are in numerical order. Those not in order are highlighted in blue text.

Recovery Domain 1 Species

o ESU MPG

[ PopID ] PopulationRecovery Domain 2

Specieso Etc.

Interior Columbia Recovery Domain Chinook salmon

o Snake River Fall-run Chinook Salmon ESUSalmon, Chinook (Snake River fall-run ESU) Snake River MPG

[ 1 ] Chinook Salmon (Snake River Fall-run ESU) - Snake River Lower MainstemSalmon, Chinook (Snake River fall-run ESU) Snake River Lower Mainstem - fall

Unassigned (above Hells Canyon Dam) MPG

Page 77: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 391 ] Salmon, Chinook (Snake River fall-run ESU) Marsing Reach - fall [ 392 ] Salmon, Chinook (Snake River fall-run ESU) Salmon Falls - fall

o Snake River Spring/Summer-run Chinook Salmon ESUSalmon, Chinook (Snake River spring/summer-run ESU) Dry Clearwater MPG

[ 2 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lapwai/Big Canyon CreekSalmon, Chinook (Snake River spring/summer-run ESU) Lapwai/Big Canyon Creeks - unknown

[ 3 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lawyer CreekSalmon, Chinook (Snake River spring/summer-run ESU) Lawyer Creek - unknown

[ 4 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Potlatch RiverSalmon, Chinook (Snake River spring/summer-run ESU) Potlatch River - unknown

[ 5 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Upper South Fork Clearwater RiverSalmon, Chinook (Snake River spring/summer-run ESU) South Fork Clearwater River Upper Mainstem - unknown

Grande Ronde / Imnaha MPG [ 6 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Big Sheep CreekSalmon, Chinook (Snake River

spring/summer-run ESU) Big Sheep Creek - spring [ 7 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Catherine CreekSalmon, Chinook (Snake River

spring/summer-run ESU) Catherine Creek - spring [ 8 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Grande Ronde River Upper MainstemSalmon,

Chinook (Snake River spring/summer-run ESU) Grande Ronde River Upper Mainstem - spring [ 9 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Imnaha River MainstemSalmon, Chinook (Snake

River spring/summer-run ESU) Imnaha River Mainstem - spring/summer [ 10 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lookingglass CreekSalmon, Chinook (Snake River

spring/summer-run ESU) Lookingglass Creek - unknown [ 12 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Minam RiverSalmon, Chinook (Snake River

spring/summer-run ESU) Minam River - spring [ 11 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lostine RiverSalmon, Chinook (Snake River

spring/summer-run ESU) Wallowa/Lostine Rivers - spring [ 13 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Wenaha RiverSalmon, Chinook (Snake River

spring/summer-run ESU) Wenaha River - spring

Page 78: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Lower Snake MPG [ 14 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Asotin CreekSalmon, Chinook (Snake River

spring/summer-run ESU) Asotin Creek - spring [ 15 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Tucannon RiverSalmon, Chinook (Snake River

spring/summer-run ESU) Tucannon River - spring Middle Fork Salmon River MPG

[ 16 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Bear Valley CreekSalmon, Chinook (Snake River spring/summer-run ESU) Bear Valley Creek - spring

[ 17 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Big CreekSalmon, Chinook (Snake River spring/summer-run ESU) Big Creek - spring/summer

[ 18 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Camas CreekSalmon, Chinook (Snake River spring/summer-run ESU) Camas Creek - spring/summer

[ 19 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Chamberlain CreekSalmon, Chinook (Snake River spring/summer-run ESU) Chamberlain Creek - spring

[ 20 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Loon CreekSalmon, Chinook (Snake River spring/summer-run ESU) Loon Creek - spring/summer

[ 21 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Marsh CreekSalmon, Chinook (Snake River spring/summer-run ESU) Marsh Creek - spring

[ 22 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Middle Fork Salmon River below Indian CreekSalmon, Chinook (Snake River spring/summer-run ESU) Middle Fork Salmon River Lower Mainstem - spring/summer

[ 23 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Middle Fork Salmon River above Indian CreekSalmon, Chinook (Snake River spring/summer-run ESU) Middle Fork Salmon River Upper Mainstem - spring

[ 24 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Sulphur CreekSalmon, Chinook (Snake River spring/summer-run ESU) Sulphur Creek - spring

South Fork Salmon River MPG [ 25 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - East Fork South Fork Salmon RiverSalmon, Chinook

(Snake River spring/summer-run ESU) East Fork South Fork Salmon River - summer [ 26 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Little Salmon RiverSalmon, Chinook (Snake River

spring/summer-run ESU) Little Salmon River - spring/summer

Page 79: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 27 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Secesh RiverSalmon, Chinook (Snake River spring/summer-run ESU) Secesh River - summer

[ 28 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - South Fork Salmon River MainstemSalmon, Chinook (Snake River spring/summer-run ESU) South Fork Salmon River - summer

Upper Salmon River MPG [ 29 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - East Fork Salmon RiverSalmon, Chinook (Snake

River spring/summer-run ESU) East Fork Salmon River - spring/summer [ 30 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lemhi RiverSalmon, Chinook (Snake River

spring/summer-run ESU) Lemhi River - spring [ 31 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - North Fork Salmon RiverSalmon, Chinook (Snake

River spring/summer-run ESU) North Fork Salmon River - spring [ 32 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Pahsimeroi RiverSalmon, Chinook (Snake River

spring/summer-run ESU) Pahsimeroi River - summer [ 33 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Panther CreekSalmon, Chinook (Snake River

spring/summer-run ESU) Panther Creek - unknown [ 34 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Salmon River Lower Mainstem below Redfish

LakeSalmon, Chinook (Snake River spring/summer-run ESU) Salmon River Lower Mainstem - spring/summer [ 35 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Salmon River Upper Mainstem above Redfish

LakeSalmon, Chinook (Snake River spring/summer-run ESU) Salmon River Upper Mainstem - spring [ 36 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Valley CreekSalmon, Chinook (Snake River

spring/summer-run ESU) Valley Creek - spring/summer [ 37 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Yankee ForkSalmon, Chinook (Snake River

spring/summer-run ESU) Yankee Fork - spring Wet Clearwater MPG

[ 38 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lochsa RiverSalmon, Chinook (Snake River spring/summer-run ESU) Lochsa River - unknown

[ 39 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lolo CreekSalmon, Chinook (Snake River spring/summer-run ESU) Lolo Creek - unknown

[ 41 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Meadow CreekSalmon, Chinook (Snake River spring/summer-run ESU) Meadow Creek - unknown

[ 42 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Moose CreekSalmon, Chinook (Snake River spring/summer-run ESU) Moose Creek - unknown

Page 80: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 40 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Lower North Fork Clearwater RiverSalmon, Chinook (Snake River spring/summer-run ESU) North Fork Clearwater River Lower Mainstem - unknown

[ 43 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Upper North Fork Clearwater RiverSalmon, Chinook (Snake River spring/summer-run ESU) North Fork Clearwater River Upper Mainstem - unknown

[ 44 ] Chinook Salmon (Snake River Spring/Summer-run ESU) - Upper Selway RiverSalmon, Chinook (Snake River spring/summer-run ESU) Selway River Upper Mainstem - unknown

Unassigned (above Hells Canyon Dam) MPG [ 374 ] Salmon, Chinook (Snake River spring/summer-run ESU) Big Willow/Little Willow Creeks - unknown [ 378 ] Salmon, Chinook (Snake River spring/summer-run ESU) Boise River - unknown [ 370 ] Salmon, Chinook (Snake River spring/summer-run ESU) Burnt River - unknown [ 386 ] Salmon, Chinook (Snake River spring/summer-run ESU) Canyon Creek - unknown [ 371 ] Salmon, Chinook (Snake River spring/summer-run ESU) Crane Creek/Lower Weiser River - unknown [ 368 ] Salmon, Chinook (Snake River spring/summer-run ESU) Eagle Creek - unknown [ 372 ] Salmon, Chinook (Snake River spring/summer-run ESU) Little Weiser River - unknown [ 383 ] Salmon, Chinook (Snake River spring/summer-run ESU) Little Owyhee River - unknown [ 387 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lower Bruneau River - unknown [ 382 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lower Owyhee River - unknown [ 380 ] Salmon, Chinook (Snake River spring/summer-run ESU) North Fork Malheur River - unknown [ 377 ] Salmon, Chinook (Snake River spring/summer-run ESU) North Fork Payette River - unknown [ 366 ] Salmon, Chinook (Snake River spring/summer-run ESU) Pine Creek - unknown [ 369 ] Salmon, Chinook (Snake River spring/summer-run ESU) Powder River - unknown [ 390 ] Salmon, Chinook (Snake River spring/summer-run ESU) Rock Creek - unknown [ 389 ] Salmon, Chinook (Snake River spring/summer-run ESU) Salmon Falls Creek - unknown [ 384 ] Salmon, Chinook (Snake River spring/summer-run ESU) South Fork Owyhee River - unknown [ 376 ] Salmon, Chinook (Snake River spring/summer-run ESU) South Fork Payette River - unknown [ 375 ] Salmon, Chinook (Snake River spring/summer-run ESU) Squaw Creek - unknown [ 388 ] Salmon, Chinook (Snake River spring/summer-run ESU) Upper Bruneau River - unknown [ 381 ] Salmon, Chinook (Snake River spring/summer-run ESU) Upper Malheur River - unknown [ 385 ] Salmon, Chinook (Snake River spring/summer-run ESU) Upper Owyhee River - unknown [ 373 ] Salmon, Chinook (Snake River spring/summer-run ESU) Upper Weiser River - unknown [ 367 ] Salmon, Chinook (Snake River spring/summer-run ESU) Wildhorse Creek - unknown [ 379 ] Salmon, Chinook (Snake River spring/summer-run ESU) Willow Creek/Lower Malheur River - unknown

Page 81: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

o Upper Columbia River Spring-run Chinook Salmon ESUSalmon, Chinook (Upper Columbia River spring-run ESU) Upper Columbia / East Slope CascadesNorth Cascades MPG

[ 45 ] Chinook Salmon (Upper Columbia River Spring-run ESU) - Entiat RiverSalmon, Chinook (Upper Columbia River spring-run ESU) Entiat River - spring

[ 46 ] Chinook Salmon (Upper Columbia River Spring-run ESU) - Methow RiverSalmon, Chinook (Upper Columbia River spring-run ESU) Methow River - spring

[ 345 ] Salmon, Chinook (Upper Columbia River spring-run ESU) Okanogan River - spring [original extirpated population]

[ 47 ] Chinook Salmon (Upper Columbia River Spring-run ESU) - Wenatchee RiverSalmon, Chinook (Upper Columbia River spring-run ESU) Wenatchee River - spring

Unassigned (above Chief Joseph Dam) MPG [ 397 ] Salmon, Chinook (Upper Columbia River spring-run ESU) Hangman Creek - spring [ 394 ] Salmon, Chinook (Upper Columbia River spring-run ESU) Kettle River - spring [ 395 ] Salmon, Chinook (Upper Columbia River spring-run ESU) Kootenay River - spring [ 393 ] Salmon, Chinook (Upper Columbia River spring-run ESU) Sanpoil River - spring [ 396 ] Salmon, Chinook (Upper Columbia River spring-run ESU) Spokane River - spring

o Salmon, Chinook (Upper Columbia River spring-run ESU--XN) Northern Cascades MPG [unofficial]

[ 398 ] Salmon, Chinook (Upper Columbia River spring-run ESU--XN) Okanogan River - spring [reintroduced population]

Sockeyeo Snake River Sockeye Salmon ESUSalmon, sockeye (Snake River ESU)

Payette [ 48 ] Sockeye Salmon (Snake River ESU) - Little Payette River [ 49 ] Sockeye Salmon (Snake River ESU) - North Fork Payette River

Stanley BasinSawtooth Valley MPG [ 51 ] Sockeye Salmon (Snake River ESU) - Alturas CreekSalmon, sockeye (Snake River ESU) Alturas Lake - summer [ 52 ] Sockeye Salmon (Snake River ESU) - Hellroaring CreekSalmon, sockeye (Snake River ESU) Hell Roaring Lake

- summer [ 53 ] Sockeye Salmon (Snake River ESU) - Petit LakeSalmon, sockeye (Snake River ESU) Pettit Lake - summer [ 54 ] Sockeye Salmon (Snake River ESU) - Redfish LakeSalmon, sockeye (Snake River ESU) Redfish Lake - summer

Page 82: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 55 ] Sockeye Salmon (Snake River ESU) - Stanley LakeSalmon, sockeye (Snake River ESU) Stanley Lake - summer [ 56 ] Sockeye Salmon (Snake River ESU) - Yellow Belly LakeSalmon, sockeye (Snake River ESU) Yellow Belly

Lake - summer South Fork Salmon River

[ 50 ] Sockeye Salmon (Snake River ESU) - Warm Springs Wallowa

[ 322 ] Sockeye Salmon (Snake River ESU) - Wallowa Lake Steelhead

o Middle Columbia River Steelhead DPSSteelhead (Middle Columbia River DPS) Cascades Eastern Slope Tributaries MPG

[ 57 ] Steelhead (Middle Columbia River DPS) - Crooked RiverSteelhead (Middle Columbia River DPS) Crooked River - summer

[ 58 ] Steelhead (Middle Columbia River DPS) - Deschutes River - eastsideSteelhead (Middle Columbia River DPS) Deschutes River Eastside - summer

[ 59 ] Steelhead (Middle Columbia River DPS) - Deschutes River - westsideSteelhead (Middle Columbia River DPS) Deschutes River Westside - summer

[ 60 ] Steelhead (Middle Columbia River DPS) - Fifteenmile Creek Winter-runSteelhead (Middle Columbia River DPS) Fifteenmile Creek - winter

[ 61 ] Steelhead (Middle Columbia River DPS) - Klickitat RiverSteelhead (Middle Columbia River DPS) Klickitat River - summer and winter

[ 62 ] Steelhead (Middle Columbia River DPS) - Rock CreekSteelhead (Middle Columbia River DPS) Rock Creek - summer

[ 63 ] Steelhead (Middle Columbia River DPS) - White Salmon RiverSteelhead (Middle Columbia River DPS) White Salmon River - summer

John Day River MPG [ 64 ] Steelhead (Middle Columbia River DPS) - John Day River Lower Mainstem TributariesSteelhead (Middle

Columbia River DPS) John Day River Lower Mainstem Tributaries - summer [ 65 ] Steelhead (Middle Columbia River DPS) - John Day River Upper MainstemSteelhead (Middle Columbia River

DPS) John Day River Upper Mainstem - summer [ 66 ] Steelhead (Middle Columbia River DPS) - Middle Fork John Day RiverSteelhead (Middle Columbia River DPS)

Middle Fork John Day River - summer

Page 83: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 67 ] Steelhead (Middle Columbia River DPS) - North Fork John Day RiverSteelhead (Middle Columbia River DPS) North Fork John Day River - summer

[ 68 ] Steelhead (Middle Columbia River DPS) - South Fork John Day RiverSteelhead (Middle Columbia River DPS) South Fork John Day River - summer

Umatilla And Walla Walla River MPG [ 69 ] Steelhead (Middle Columbia River DPS) - Touchet RiverSteelhead (Middle Columbia River DPS) Touchet

River - summer [ 70 ] Steelhead (Middle Columbia River DPS) - Umatilla RiverSteelhead (Middle Columbia River DPS) Umatilla

River - summer [ 71 ] Steelhead (Middle Columbia River DPS) - Walla Walla RiverSteelhead (Middle Columbia River DPS) Walla

Walla River - summer [ 72 ] Steelhead (Middle Columbia River DPS) - Willow CreekSteelhead (Middle Columbia River DPS) Willow Creek

- summer Yakima River Group MPG

[ 73 ] Steelhead (Middle Columbia River DPS) - Naches RiverSteelhead (Middle Columbia River DPS) Naches River - summer

[ 74 ] Steelhead (Middle Columbia River DPS) - Satus CreekSteelhead (Middle Columbia River DPS) Satus Creek - summer

[ 75 ] Steelhead (Middle Columbia River DPS) - Toppenish CreekSteelhead (Middle Columbia River DPS) Toppenish Creek - summer

[ 76 ] Steelhead (Middle Columbia River DPS) - Yakima River upper mainstemSteelhead (Middle Columbia River DPS) Yakima River Upper Mainstem - summer

o Steelhead (Middle Columbia River DPS--XN) Cascades Eastern Slope Tributaries MPG [unofficial]

[ 399 ] Steelhead (Middle Columbia River DPS--XN) Upper Deschutes River - summer [reintroduced population]o Snake River Basin Steelhead DPSSteelhead (Snake River Basin DPS)

Clearwater River MPG [ 77 ] Steelhead (Snake River Basin DPS) - Clearwater River Lower MainstemSteelhead (Snake River Basin DPS)

Clearwater River Lower Mainstem - summer [ 78 ] Steelhead (Snake River Basin DPS) - Lochsa RiverSteelhead (Snake River Basin DPS) Lochsa River - summer [ 79 ] Steelhead (Snake River Basin DPS) - Lolo CreekSteelhead (Snake River Basin DPS) Lolo Creek - summer [ 80 ] Steelhead (Snake River Basin DPS) - North Fork Clearwater RiverSteelhead (Snake River Basin DPS) North

Fork Clearwater River - summer

Page 84: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 81 ] Steelhead (Snake River Basin DPS) - Selway RiverSteelhead (Snake River Basin DPS) Selway River - summer [ 82 ] Steelhead (Snake River Basin DPS) - South Fork Clearwater RiverSteelhead (Snake River Basin DPS) South

Fork Clearwater River - summer Grande Ronde River MPG

[ 83 ] Steelhead (Snake River Basin DPS) - Grande Ronde River Lower Mainstem TributariesSteelhead (Snake River Basin DPS) Grande Ronde River Lower Mainstem - summer

[ 84 ] Steelhead (Snake River Basin DPS) - Grande Ronde River Upper MainstemSteelhead (Snake River Basin DPS) Grande Ronde River Upper Mainstem - summer

[ 85 ] Steelhead (Snake River Basin DPS) - Joseph CreekSteelhead (Snake River Basin DPS) Joseph Creek - summer [ 86 ] Steelhead (Snake River Basin DPS) - Wallowa RiverSteelhead (Snake River Basin DPS) Wallowa River -

summer Hells Canyon MPG

[ 87 ] Steelhead (Snake River Basin DPS) - Hells CanyonSteelhead (Snake River Basin DPS) Hells Canyon - summer Imnaha River MPG

[ 88 ] Steelhead (Snake River Basin DPS) - Imnaha Camp Creek Index Area [ 89 ] Steelhead (Snake River Basin DPS) - Imnaha RiverSteelhead (Snake River Basin DPS) Imnaha River - summer

Lower Snake MPG [ 90 ] Steelhead (Snake River Basin DPS) - Asotin CreekSteelhead (Snake River Basin DPS) Asotin Creek - summer [ 91 ] Steelhead (Snake River Basin DPS) - Tucannon RiverSteelhead (Snake River Basin DPS) Tucannon River -

summer Salmon River MPG

[ 93 ] Steelhead (Snake River Basin DPS) - Chamberlain CreekSteelhead (Snake River Basin DPS) Chamberlain Creek - summer

[ 94 ] Steelhead (Snake River Basin DPS) - East Fork Salmon RiverSteelhead (Snake River Basin DPS) East Fork Salmon River - summer

[ 95 ] Steelhead (Snake River Basin DPS) - Lemhi RiverSteelhead (Snake River Basin DPS) Lemhi River - summer [ 96 ] Steelhead (Snake River Basin DPS) - Little Salmon and Rapid RiverSteelhead (Snake River Basin DPS) Little

Salmon River - summer [ 92 ] Steelhead (Snake River Basin DPS) - Big, Camas, and Loon CreekSteelhead (Snake River Basin DPS) Middle

Fork Salmon River Lower Mainstem - summer [ 97 ] Steelhead (Snake River Basin DPS) - Middle Fork Salmon River Upper MainstemSteelhead (Snake River Basin

DPS) Middle Fork Salmon River Upper Mainstem - summer

Page 85: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 98 ] Steelhead (Snake River Basin DPS) - North Fork Salmon RiverSteelhead (Snake River Basin DPS) North Fork Salmon River - summer

[ 99 ] Steelhead (Snake River Basin DPS) - Pahsimeroi RiverSteelhead (Snake River Basin DPS) Pahsimeroi River - summer

[ 100 ] Steelhead (Snake River Basin DPS) - Panther CreekSteelhead (Snake River Basin DPS) Panther Creek - summer

[ 101 ] Steelhead (Snake River Basin DPS) - Salmon River Upper MainstemSteelhead (Snake River Basin DPS) Salmon River Upper Mainstem - summer

[ 102 ] Steelhead (Snake River Basin DPS) - Secesh RiverSteelhead (Snake River Basin DPS) Secesh River - summer [ 103 ] Steelhead (Snake River Basin DPS) - South Fork Salmon RiverSteelhead (Snake River Basin DPS) South Fork

Salmon River - summer Unassigned (above Hells Canyon Dam) MPG

[ 358 ] Steelhead (Snake River Basin DPS) Boise River - summer [ 363 ] Steelhead (Snake River Basin DPS) Bruneau River - summer [ 353 ] Steelhead (Snake River Basin DPS) Burnt River - summer [ 364 ] Steelhead (Snake River Basin DPS) Canyon Creek - summer [ 359 ] Steelhead (Snake River Basin DPS) Lower Malheur River - summer [ 361 ] Steelhead (Snake River Basin DPS) Lower Owyhee River - summer [ 355 ] Steelhead (Snake River Basin DPS) Lower Payette River - summer [ 356 ] Steelhead (Snake River Basin DPS) North Fork Payette River - summer [ 352 ] Steelhead (Snake River Basin DPS) Powder River - summer [ 365 ] Steelhead (Snake River Basin DPS) Salmon Falls/Rock Creeks - summer [ 357 ] Steelhead (Snake River Basin DPS) South Fork Payette River - summer [ 360 ] Steelhead (Snake River Basin DPS) Upper Malheur River - summer [ 362 ] Steelhead (Snake River Basin DPS) Upper Owyhee River - summer [ 354 ] Steelhead (Snake River Basin DPS) Weiser River - summer

o Upper Columbia River Steelhead DPSSteelhead (Upper Columbia River DPS) Upper Columbia / East Slope CascadesNorth Cascades MPG

[ 104 ] Steelhead (Upper Columbia River DPS) - Crab CreekSteelhead (Upper Columbia River DPS) Crab Creek - summer

[ 105 ] Steelhead (Upper Columbia River DPS) - Entiat RiverSteelhead (Upper Columbia River DPS) Entiat River - summer

Page 86: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 106 ] Steelhead (Upper Columbia River DPS) - Methow RiverSteelhead (Upper Columbia River DPS) Methow River - summer

[ 107 ] Steelhead (Upper Columbia River DPS) - Okanogan RiverSteelhead (Upper Columbia River DPS) Okanogan River - summer

[ 108 ] Steelhead (Upper Columbia River DPS) - Wenatchee RiverSteelhead (Upper Columbia River DPS) Wenatchee River - summer

Unassigned (above Chief Joseph Dam) MPG [ 351 ] Steelhead (Upper Columbia River DPS) Hangman Creek - summer [ 347 ] Steelhead (Upper Columbia River DPS) Kettle River - summer [ 349 ] Steelhead (Upper Columbia River DPS) Kootenay River - summer [ 348 ] Steelhead (Upper Columbia River DPS) Pend Oreille River - summer [ 346 ] Steelhead (Upper Columbia River DPS) Sanpoil River - summer [ 350 ] Steelhead (Upper Columbia River DPS) Spokane River - summer

Oregon Coast Recovery Domain Coho salmon

o Oregon Coast Coho Salmon ESUSalmon, coho (Oregon Coast ESU) Lakes MPG

[ 109 ] Coho Salmon (Oregon Coast ESU) - Siltcoos LakeSalmon, coho (Oregon Coast ESU) Siltcoos Lake - fall [ 110 ] Coho Salmon (Oregon Coast ESU) - Sutton (Mercer Lake)Salmon, coho (Oregon Coast ESU) Sutton

Lake/Mercer Lake - fall [ 111 ] Coho Salmon (Oregon Coast ESU) - Tahkenitch LakeSalmon, coho (Oregon Coast ESU) Tahkenitch Lake -

fall [ 112 ] Coho Salmon (Oregon Coast ESU) - Tenmile LakeSalmon, coho (Oregon Coast ESU) Tenmile Lake - fall

Mid-Coast MPG [ 113 ] Coho Salmon (Oregon Coast ESU) - Alsea RiverSalmon, coho (Oregon Coast ESU) Alsea River - fall [ 114 ] Coho Salmon (Oregon Coast ESU) - Beaver CreekSalmon, coho (Oregon Coast ESU) Beaver Creek - fall [ 115 ] Coho Salmon (Oregon Coast ESU) - BerrySalmon, coho (Oregon Coast ESU) Berry Creek - fall [ 116 ] Coho Salmon (Oregon Coast ESU) - Big (near Alsea)Salmon, coho (Oregon Coast ESU) Big (near Alsea)

Creek - fall [ 117 ] Coho Salmon (Oregon Coast ESU) - Big (near Siuslaw)Salmon, coho (Oregon Coast ESU) Big (near Siuslaw)

Creek - fall

Page 87: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 118 ] Coho Salmon (Oregon Coast ESU) - Big (near Yaquina)Salmon, coho (Oregon Coast ESU) Big (near Yaquina) Creek - fall

[ 119 ] Coho Salmon (Oregon Coast ESU) - BobSalmon, coho (Oregon Coast ESU) Bob Creek - fall [ 120 ] Coho Salmon (Oregon Coast ESU) - CapeSalmon, coho (Oregon Coast ESU) Cape Creek - fall [ 121 ] Coho Salmon (Oregon Coast ESU) - ChinaSalmon, coho (Oregon Coast ESU) China Creek - fall [ 122 ] Coho Salmon (Oregon Coast ESU) - CoalSalmon, coho (Oregon Coast ESU) Coal Creek - fall [ 123 ] Coho Salmon (Oregon Coast ESU) - CumminsSalmon, coho (Oregon Coast ESU) Cummins Creek - fall [ 124 ] Coho Salmon (Oregon Coast ESU) - DepoeSalmon, coho (Oregon Coast ESU) Depoe Bay Creek - fall [ 125 ] Coho Salmon (Oregon Coast ESU) - Devils LakeSalmon, coho (Oregon Coast ESU) Devils Lake - fall [ 126 ] Coho Salmon (Oregon Coast ESU) - FogartySalmon, coho (Oregon Coast ESU) Fogarty Creek - fall [ 127 ] Coho Salmon (Oregon Coast ESU) - MoolackSalmon, coho (Oregon Coast ESU) Moolack Creek - fall [ 128 ] Coho Salmon (Oregon Coast ESU) - RockSalmon, coho (Oregon Coast ESU) Rock Creek - fall [ 129 ] Coho Salmon (Oregon Coast ESU) - RockySalmon, coho (Oregon Coast ESU) Rocky Creek - fall [ 130 ] Coho Salmon (Oregon Coast ESU) - Salmon RiverSalmon, coho (Oregon Coast ESU) Salmon River - fall [ 131 ] Coho Salmon (Oregon Coast ESU) - SchoolhouseSalmon, coho (Oregon Coast ESU) Schoolhouse Creek - fall [ 132 ] Coho Salmon (Oregon Coast ESU) - Siletz RiverSalmon, coho (Oregon Coast ESU) Siletz River - fall [ 133 ] Coho Salmon (Oregon Coast ESU) - Siuslaw RiverSalmon, coho (Oregon Coast ESU) Siuslaw River - fall [ 134 ] Coho Salmon (Oregon Coast ESU) - SpencerSalmon, coho (Oregon Coast ESU) Spencer Creek - fall [ 135 ] Coho Salmon (Oregon Coast ESU) - Tenmile CreekSalmon, coho (Oregon Coast ESU) Tenmile Creek - fall [ 136 ] Coho Salmon (Oregon Coast ESU) - TheilSalmon, coho (Oregon Coast ESU) Thiel Creek - fall [ 137 ] Coho Salmon (Oregon Coast ESU) - VingieSalmon, coho (Oregon Coast ESU) Vingie Creek - fall [ 138 ] Coho Salmon (Oregon Coast ESU) - WadeSalmon, coho (Oregon Coast ESU) Wade Creek - fall [ 139 ] Coho Salmon (Oregon Coast ESU) - YachatsSalmon, coho (Oregon Coast ESU) Yachats River - fall [ 140 ] Coho Salmon (Oregon Coast ESU) - Yaquina RiverSalmon, coho (Oregon Coast ESU) Yaquina River - fall

Mid-South Coast MPG [ 1541 ] Coho Salmon (Oregon Coast ESU) - Coos RiverSalmon, coho (Oregon Coast ESU) Coos River - fall [ 1542 ] Coho Salmon (Oregon Coast ESU) - Coquille RiverSalmon, coho (Oregon Coast ESU) Coquille River - fall [ 1543 ] Coho Salmon (Oregon Coast ESU) - Floras/New RiverSalmon, coho (Oregon Coast ESU) Floras Creek/New

River - fall [ 1544 ] Coho Salmon (Oregon Coast ESU) - JohnsonSalmon, coho (Oregon Coast ESU) Johnson Creek - fall [ 1545 ] Coho Salmon (Oregon Coast ESU) - Sixes RiverSalmon, coho (Oregon Coast ESU) Sixes River - fall [ 1546 ] Coho Salmon (Oregon Coast ESU) - ThreemileSalmon, coho (Oregon Coast ESU) Threemile Creek - fall [ 1547 ] Coho Salmon (Oregon Coast ESU) - TwomileSalmon, coho (Oregon Coast ESU) Twomile Creek - fall

Page 88: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

North Coast MPG [ 1548 ] Coho Salmon (Oregon Coast ESU) - Arch CapeSalmon, coho (Oregon Coast ESU) Arch Cape Creek - fall [ 1549 ] Coho Salmon (Oregon Coast ESU) - EcolaSalmon, coho (Oregon Coast ESU) Ecola Creek - fall [ 1650 ] Coho Salmon (Oregon Coast ESU) - Necanicum RiverSalmon, coho (Oregon Coast ESU) Necanicum River -

fall [ 1651 ] Coho Salmon (Oregon Coast ESU) - Nehalem RiverSalmon, coho (Oregon Coast ESU) Nehalem River - fall [ 1652 ] Coho Salmon (Oregon Coast ESU) - NeskowinSalmon, coho (Oregon Coast ESU) Neskowin Creek - fall [ 1653 ] Coho Salmon (Oregon Coast ESU) - Nestucca RiverSalmon, coho (Oregon Coast ESU) Nestucca River - fall [ 1654 ] Coho Salmon (Oregon Coast ESU) - NetartsSalmon, coho (Oregon Coast ESU) Netarts Bay - fall [ 1655 ] Coho Salmon (Oregon Coast ESU) - RoverSalmon, coho (Oregon Coast ESU) Rover Creek - fall [ 1656 ] Coho Salmon (Oregon Coast ESU) - SandSalmon, coho (Oregon Coast ESU) Sand Creek - fall [ 1657 ] Coho Salmon (Oregon Coast ESU) - Short SandSalmon, coho (Oregon Coast ESU) Short Sand Creek - fall [ 1658 ] Coho Salmon (Oregon Coast ESU) - Spring CreekSalmon, coho (Oregon Coast ESU) Spring Creek - fall [ 1659 ] Coho Salmon (Oregon Coast ESU) - Tillamook BaySalmon, coho (Oregon Coast ESU) Tillamook Bay - fall [ 1760 ] Coho Salmon (Oregon Coast ESU) - WatsecoSalmon, coho (Oregon Coast ESU) Watseco Creek - fall

Umpqua MPG [ 1761 ] Coho Salmon (Oregon Coast ESU) - Lower Umpqua RiverSalmon, coho (Oregon Coast ESU) Lower Umpqua

River - fall [ 1762 ] Coho Salmon (Oregon Coast ESU) - Middle Umpqua RiverSalmon, coho (Oregon Coast ESU) Middle

Umpqua River - fall [ 1763 ] Coho Salmon (Oregon Coast ESU) - North Umpqua RiverSalmon, coho (Oregon Coast ESU) North Umpqua

River - fall [ 1764 ] Coho Salmon (Oregon Coast ESU) - South Umpqua RiverSalmon, coho (Oregon Coast ESU) South Umpqua

River - fall

Page 89: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Puget Sound Recovery Domain Geographic Regions and MPGs Chinook salmon

o Puget Sound Chinook Salmon ESUSalmon, Chinook (Puget Sound ESU) Puget Sound Central East MPG

[ 1765 ] Chinook Salmon (Puget Sound ESU) - Cascade RiverSalmon, Chinook (Puget Sound ESU) Cascade River - spring

[ 1766 ] Chinook Salmon (Puget Sound ESU) - Lower Sauk RiverSalmon, Chinook (Puget Sound ESU) Lower Sauk River - summer

[ 1767 ] Chinook Salmon (Puget Sound ESU) - Lower Skagit RiverSalmon, Chinook (Puget Sound ESU) Lower Skagit River - fall

[ 1768 ] Chinook Salmon (Puget Sound ESU) - North Fork Stillaguamish RiverSalmon, Chinook (Puget Sound ESU) North Fork Stillaguamish River - summer

[ 1769 ] Chinook Salmon (Puget Sound ESU) - Skykomish RiverSalmon, Chinook (Puget Sound ESU) Skykomish River - summer

[ 170 ] Chinook Salmon (Puget Sound ESU) - Snoqualmie RiverSalmon, Chinook (Puget Sound ESU) Snoqualmie River - fall

[ 171 ] Chinook Salmon (Puget Sound ESU) - South Fork/Mainstem Stillaguamish RiverSalmon, Chinook (Puget Sound ESU) South Fork Stillaguamish River - fall

[ 172 ] Chinook Salmon (Puget Sound ESU) - Suiattle RiverSalmon, Chinook (Puget Sound ESU) Suiattle River - spring

[ 173 ] Chinook Salmon (Puget Sound ESU) - Upper Sauk RiverSalmon, Chinook (Puget Sound ESU) Upper Sauk River - spring

[ 174 ] Chinook Salmon (Puget Sound ESU) - Upper Skagit RiverSalmon, Chinook (Puget Sound ESU) Upper Skagit River - summer

Puget Sound Central West MPG [ 175 ] Chinook Salmon (Puget Sound ESU) - Mid-Hood CanalSalmon, Chinook (Puget Sound ESU) Mid-Hood Canal

- fall [ 176 ] Chinook Salmon (Puget Sound ESU) - Skokomish RiverSalmon, Chinook (Puget Sound ESU) Skokomish

River - fall

Page 90: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Puget Sound North East MPG [ 177 ] Chinook Salmon (Puget Sound ESU) - Lower/North Fork/Middle Fork NooksackSalmon, Chinook (Puget

Sound ESU) North Fork Nooksack River - spring [ 178 ] Chinook Salmon (Puget Sound ESU) - South Fork Nooksack RiverSalmon, Chinook (Puget Sound ESU) South

Fork Nooksack River - spring Puget Sound North West MPG

[ 179 ] Chinook Salmon (Puget Sound ESU) - Dungeness RiverSalmon, Chinook (Puget Sound ESU) Dungeness River - summer

[ 180 ] Chinook Salmon (Puget Sound ESU) - Elwha RiverSalmon, Chinook (Puget Sound ESU) Elwha River - fall Puget Sound South MPG

[ 181 ] Chinook Salmon (Puget Sound ESU) - Cedar RiverSalmon, Chinook (Puget Sound ESU) Cedar River - fall [ 182 ] Chinook Salmon (Puget Sound ESU) - Green RiverSalmon, Chinook (Puget Sound ESU) Green River - fall [ 183 ] Chinook Salmon (Puget Sound ESU) - Nisqually RiverSalmon, Chinook (Puget Sound ESU) Nisqually River -

fall [ 184 ] Chinook Salmon (Puget Sound ESU) - Puyallup RiverSalmon, Chinook (Puget Sound ESU) Puyallup River -

fall [ 185 ] Chinook Salmon (Puget Sound ESU) - Sammamish RiverSalmon, Chinook (Puget Sound ESU) Sammamish

River - fall [ 186 ] Chinook Salmon (Puget Sound ESU) - White RiverSalmon, Chinook (Puget Sound ESU) White River - spring

Chum salmono Hood Canal Summer-run Chum Salmon ESUSalmon, chum (Hood Canal summer-run ESU)

Hood Canal MPG [ 187 ] Chum Salmon (Hood Canal Summer-run ESU) - Hood CanalSalmon, chum (Hood Canal summer-run ESU)

Hood Canal - summer [ 188 ] Chum Salmon (Hood Canal Summer-run ESU) - Strait of Juan de FucaSalmon, chum (Hood Canal summer-run

ESU) Strait of Juan de Fuca - summer Coho salmon

o Puget Sound/Strait of Georgia Coho Salmon ESU Puget Sound

[ 189 ] Puget Sound Coho (Puget Sound ESU) - East Juan de Fuca [ 190 ] Puget Sound Coho (Puget Sound ESU) - Hood Canal [ 191 ] Puget Sound Coho (Puget Sound ESU) - Skagit River

Page 91: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 192 ] Puget Sound Coho (Puget Sound ESU) - Snohomish River [ 193 ] Puget Sound Coho (Puget Sound ESU) - Stillaguamish River

Sockeye salmono Ozette Lake Sockeye Salmon ESUSalmon, sockeye (Ozette Lake ESU)

Ozette Lake MPG [ 194 ] Sockeye Salmon (Ozette Lake ESU) - Ozette LakeSalmon, sockeye (Ozette Lake ESU) Ozette Lake - summer

Steelheado Puget Sound Steelhead DPSSteelhead (Puget Sound DPS)

Central and South Puget Sound MPG [ 332 ] Steelhead (Puget Sound DPS) - Cedar RiverSteelhead (Puget Sound DPS) Cedar River - winter [ 335 ] Steelhead (Puget Sound DPS) - Eastside Kitsap Peninsula TributariesSteelhead (Puget Sound DPS) East Kitsap

Peninsula Tributaries - winter [ 198 ] Steelhead (Puget Sound DPS) - Green RiverSteelhead (Puget Sound DPS) Green River - winter [ 200 ] Steelhead (Puget Sound DPS) - Nisqually RiverSteelhead (Puget Sound DPS) Nisqually River - winter [ 338 ] Steelhead (Puget Sound DPS) - North Lake Washington TributariesSteelhead (Puget Sound DPS) North Lake

Washington and Lake Sammamish - winter [ 203 ] Steelhead (Puget Sound DPS) - Puyallup RiverSteelhead (Puget Sound DPS) Puyallup River/Carbon River -

winter [ 208 ] Steelhead (Puget Sound DPS) - South Sound TributariesSteelhead (Puget Sound DPS) South Puget Sound

Tributaries - winter [ 211 ] Steelhead (Puget Sound DPS) - White RiverSteelhead (Puget Sound DPS) White River - winter

Hood Canal and Strait of Juan de Fuca MPG [ 195 ] Steelhead (Puget Sound DPS) - Dungeness RiverSteelhead (Puget Sound DPS) Dungeness River - summer and

winter [ 196 ] Steelhead (Puget Sound DPS) - Eastside Hood Canal TributariesSteelhead (Puget Sound DPS) East Hood Canal

Tributaries - winter [ 197 ] Steelhead (Puget Sound DPS) - Elwha RiverSteelhead (Puget Sound DPS) Elwha River - winter [ 340 ] Steelhead (Puget Sound DPS) - Sequim & Discovery Bay TributariesSteelhead (Puget Sound DPS)

Sequim/Discovery Bays Tributaries - winter [ 206 ] Steelhead (Puget Sound DPS) - Skokomish RiverSteelhead (Puget Sound DPS) Skokomish River - winter [ 343 ] Steelhead (Puget Sound DPS) - South Hood Canal TributariesSteelhead (Puget Sound DPS) South Hood Canal

Tributaries - winter

Page 92: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 326 ] Steelhead (Puget Sound DPS) - Strait of Juan de Fuca IndependentsSteelhead (Puget Sound DPS) Strait of Juan de Fuca Tributaries - winter

[ 210 ] Steelhead (Puget Sound DPS) - Westside Hood Canal TributariesSteelhead (Puget Sound DPS) West Hood Canal Tributaries - winter

North Sound MPGern Cascades MPG [ 330 ] Steelhead (Puget Sound DPS) - Baker RiverSteelhead (Puget Sound DPS) Baker River - summer and winter [ 331 ] Steelhead (Puget Sound DPS) - Canyon Creek Summer-runSteelhead (Puget Sound DPS) Canyon Creek -

summer [ 333 ] Steelhead (Puget Sound DPS) - Deer Creek Summer-runSteelhead (Puget Sound DPS) Deer Creek - summer [ 334 ] Steelhead (Puget Sound DPS) - Drayton Harbor TributariesSteelhead (Puget Sound DPS) Drayton Harbor

Tributaries - winter [ 336 ] Steelhead (Puget Sound DPS) - Nookachamps CreekSteelhead (Puget Sound DPS) Nookachamps Creek -

winter [ 201 ] Steelhead (Puget Sound DPS) - Nooksack RiverSteelhead (Puget Sound DPS) Nooksack River - winter [ 337 ] Steelhead (Puget Sound DPS) - North Fork Skykomish River Summer-runSteelhead (Puget Sound DPS) North

Fork Skykomish River - summer [ 324 ] Steelhead (Puget Sound DPS) - Pilchuck RiverSteelhead (Puget Sound DPS) Pilchuck River - winter [ 204 ] Steelhead (Puget Sound DPS) - Samish River & Bellingham Bay TributariesSteelhead (Puget Sound DPS)

Samish River and Bellingham Bay Tributaries - winter [ 339 ] Steelhead (Puget Sound DPS) - Sauk RiverSteelhead (Puget Sound DPS) Sauk River - summer and winter [ 205 ] Steelhead (Puget Sound DPS) - Skagit RiverSteelhead (Puget Sound DPS) Skagit River - summer and winter [ 341 ] Steelhead (Puget Sound DPS) - Snohomish & Skykomish RiverSteelhead (Puget Sound DPS)

Snohomish/Skykomish Rivers - winter [ 325 ] Steelhead (Puget Sound DPS) - Snoqualmie RiverSteelhead (Puget Sound DPS) Snoqualmie River - winter [ 342 ] Steelhead (Puget Sound DPS) - South Fork Nooksack River Summer-runSteelhead (Puget Sound DPS) South

Fork Nooksack River - summer [ 209 ] Steelhead (Puget Sound DPS) - Stillaguamish RiverSteelhead (Puget Sound DPS) Stillaguamish River - winter [ 329 ] Steelhead (Puget Sound DPS) - Tolt River Summer-runSteelhead (Puget Sound DPS) Tolt River - summer

South Sound MPG

Page 93: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Willamette/Lower Columbia Recovery Domain Strata Chinook salmon

o Lower Columbia River Chinook Salmon ESUSalmon, Chinook (Lower Columbia River ESU) Cascade MPG

[ 212 ] Chinook Salmon (Lower Columbia River ESU) - Cispus River Spring-runSalmon, Chinook (Lower Columbia River ESU) Cispus River - spring

[ 244 ] Salmon, Chinook (Lower Columbia River ESU) Clackamas River - fall [ 213 ] Chinook Salmon (Lower Columbia River ESU) - Coweeman River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Coweeman River - fall [ 214 ] Chinook Salmon (Lower Columbia River ESU) - Kalama River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Kalama River - fall [ 215 ] Chinook Salmon (Lower Columbia River ESU) - Kalama River Spring-runSalmon, Chinook (Lower Columbia

River ESU) Kalama River - spring [ 217 ] Chinook Salmon (Lower Columbia River ESU) - Lewis River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Lewis River - fall [ 216 ] Chinook Salmon (Lower Columbia River ESU) - Lewis River BrightSalmon, Chinook (Lower Columbia River

ESU) Lewis River - late fall [ 218 ] Chinook Salmon (Lower Columbia River ESU) - Lower Cowlitz River Fall-runSalmon, Chinook (Lower

Columbia River ESU) Lower Cowlitz River - fall [ 219 ] Chinook Salmon (Lower Columbia River ESU) - North Fork Lewis River Spring-runSalmon, Chinook (Lower

Columbia River ESU) North Fork Lewis River - spring [ 220 ] Chinook Salmon (Lower Columbia River ESU) - Salmon Creek Fall-runSalmon, Chinook (Lower Columbia

River ESU) Salmon Creek - fall [ 222 ] Chinook Salmon (Lower Columbia River ESU) - Sandy River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Sandy River - fall [ 221 ] Chinook Salmon (Lower Columbia River ESU) - Sandy River BrightSalmon, Chinook (Lower Columbia River

ESU) Sandy River - late fall [ 223 ] Chinook Salmon (Lower Columbia River ESU) - Sandy River Spring-runSalmon, Chinook (Lower Columbia

River ESU) Sandy River - spring [ 224 ] Chinook Salmon (Lower Columbia River ESU) - Tilton River Spring-runSalmon, Chinook (Lower Columbia

River ESU) Tilton River - spring [ 225 ] Chinook Salmon (Lower Columbia River ESU) - Toutle River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Toutle River - fall

Page 94: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 226 ] Chinook Salmon (Lower Columbia River ESU) - Toutle River Spring-runSalmon, Chinook (Lower Columbia River ESU) Toutle River - spring

[ 227 ] Chinook Salmon (Lower Columbia River ESU) - Upper Cowlitz River Fall-runSalmon, Chinook (Lower Columbia River ESU) Upper Cowlitz River - fall

[ 228 ] Chinook Salmon (Lower Columbia River ESU) - Upper Cowlitz River Spring-runSalmon, Chinook (Lower Columbia River ESU) Upper Cowlitz River - spring

[ 229 ] Chinook Salmon (Lower Columbia River ESU) - Washougal River Fall-runSalmon, Chinook (Lower Columbia River ESU) Washougal River - fall

Coastal MPG [ 230 ] Chinook Salmon (Lower Columbia River ESU) - Big Creek Fall-runSalmon, Chinook (Lower Columbia River

ESU) Big Creek - fall [ 231 ] Chinook Salmon (Lower Columbia River ESU) - Chinook River Fall-run [ 232 ] Chinook Salmon (Lower Columbia River ESU) - Clatskanie River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Clatskanie River - fall [ 233 ] Chinook Salmon (Lower Columbia River ESU) - Elochoman River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Elochoman River - fall [ 234 ] Chinook Salmon (Lower Columbia River ESU) - Grays River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Grays and Chinook Rivers - fall [ 235 ] Chinook Salmon (Lower Columbia River ESU) - Mill Creek Fall-runSalmon, Chinook (Lower Columbia River

ESU) Mill, Abernathy, and Germany Creeks - fall [ 236 ] Chinook Salmon (Lower Columbia River ESU) - Scappoose River Fall-runSalmon, Chinook (Lower Columbia

River ESU) Scappoose Creek - fall [ 237 ] Chinook Salmon (Lower Columbia River ESU) - Youngs Bay Fall-runSalmon, Chinook (Lower Columbia

River ESU) Youngs Bay - fall Gorge MPG

[ 238 ] Chinook Salmon (Lower Columbia River ESU) - Hood River Fall-runSalmon, Chinook (Lower Columbia River ESU) Hood River - fall

[ 239 ] Chinook Salmon (Lower Columbia River ESU) - Hood River Spring-runSalmon, Chinook (Lower Columbia River ESU) Hood River - spring

[ 240 ] Chinook Salmon (Lower Columbia River ESU) - Lower Gorge Tributaries Fall-runSalmon, Chinook (Lower Columbia River ESU) Lower Gorge Tributaries - fall

[ 241 ] Chinook Salmon (Lower Columbia River ESU) - Upper Gorge Tributaries Fall-runSalmon, Chinook (Lower Columbia River ESU) Upper Gorge Tributaries - fall

Page 95: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 242 ] Chinook Salmon (Lower Columbia River ESU) - White Salmon River Fall-runSalmon, Chinook (Lower Columbia River ESU) White Salmon River - fall

[ 243 ] Chinook Salmon (Lower Columbia River ESU) - White Salmon River Spring-runSalmon, Chinook (Lower Columbia River ESU) White Salmon River - spring

Willamette - Cascade [ 244 ] Chinook Salmon (Lower Columbia River ESU) - Clackamas River Fall-run

o Upper Willamette River Chinook Salmon ESUSalmon, Chinook (Upper Willamette River ESU) Willamette MPG

[ 245 ] Chinook Salmon (Upper Willamette River ESU) - Calapooia River Spring-runSalmon, Chinook (Upper Willamette River ESU) Calapooia River - spring

[ 246 ] Chinook Salmon (Upper Willamette River ESU) - Clackamas River Spring-runSalmon, Chinook (Upper Willamette River ESU) Clackamas River - spring

[ 247 ] Chinook Salmon (Upper Willamette River ESU) - McKenzie River Spring-runSalmon, Chinook (Upper Willamette River ESU) McKenzie River - spring

[ 248 ] Chinook Salmon (Upper Willamette River ESU) - Middle Fork Willamette River Spring-runSalmon, Chinook (Upper Willamette River ESU) Middle Fork Willamette River - spring

[ 249 ] Chinook Salmon (Upper Willamette River ESU) - Molalla River Spring-runSalmon, Chinook (Upper Willamette River ESU) Molalla River - spring

[ 250 ] Chinook Salmon (Upper Willamette River ESU) - North Santiam River Spring-runSalmon, Chinook (Upper Willamette River ESU) North Santiam River - spring

[ 251 ] Chinook Salmon (Upper Willamette River ESU) - South Santiam River Spring-runSalmon, Chinook (Upper Willamette River ESU) South Santiam River - spring

Chum salmono Columbia River Chum Salmon ESUSalmon, chum (Columbia River ESU)

Cascade MPG [ 267 ] Salmon, chum (Columbia River ESU) Clackamas River - fall [ 252 ] Chum Salmon (Columbia River ESU) - Cowlitz RiverSalmon, chum (Columbia River ESU) Cowlitz River -

fall [ 344 ] Salmon, chum (Columbia River ESU) Cowlitz River - summer [ 253 ] Chum Salmon (Columbia River ESU) - Kalama RiverSalmon, chum (Columbia River ESU) Kalama River -

fall [ 254 ] Chum Salmon (Columbia River ESU) - Lewis RiverSalmon, chum (Columbia River ESU) Lewis River - fall

Page 96: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 255 ] Chum Salmon (Columbia River ESU) - Salmon CreekSalmon, chum (Columbia River ESU) Salmon Creek - fall

[ 256 ] Chum Salmon (Columbia River ESU) - Sandy RiverSalmon, chum (Columbia River ESU) Sandy River - fall [ 257 ] Chum Salmon (Columbia River ESU) - Washougal RiverSalmon, chum (Columbia River ESU) Washougal

River - fall Coastal MPG

[ 258 ] Chum Salmon (Columbia River ESU) - Big CreekSalmon, chum (Columbia River ESU) Big Creek - fall [ 259 ] Chum Salmon (Columbia River ESU) - Clatskanie RiverSalmon, chum (Columbia River ESU) Clatskanie

River - fall [ 260 ] Chum Salmon (Columbia River ESU) - Elochoman RiverSalmon, chum (Columbia River ESU) Elochoman

River - fall [ 261 ] Chum Salmon (Columbia River ESU) - Grays & Chinook RiversSalmon, chum (Columbia River ESU) Grays

and Chinook Rivers - fall [ 262 ] Chum Salmon (Columbia River ESU) - Mill CreekSalmon, chum (Columbia River ESU) Mill, Abernathy, and

Germany Creeks - fall [ 263 ] Chum Salmon (Columbia River ESU) - Scappoose RiverSalmon, chum (Columbia River ESU) Scappoose

Creek - fall [ 264 ] Chum Salmon (Columbia River ESU) - Youngs BaySalmon, chum (Columbia River ESU) Youngs Bay - fall

Gorge MPG [ 265 ] Chum Salmon (Columbia River ESU) - Lower Gorge TributariesSalmon, chum (Columbia River ESU) Lower

Gorge Tributaries - fall [ 266 ] Chum Salmon (Columbia River ESU) - Upper Gorge TributariesSalmon, chum (Columbia River ESU) Upper

Gorge Tributaries - fall Willamette - Cascade

[ 267 ] Chum Salmon (Columbia River ESU) - Clackamas River Coho salmon

o Lower Columbia River Coho Salmon ESUSalmon, coho (Lower Columbia River ESU) Cascade MPG

[ 268 ] Coho Salmon (Lower Columbia River ESU) - Cispus RiverSalmon, coho (Lower Columbia River ESU) Cispus River - early and late

[ 292 ] Salmon, coho (Lower Columbia River ESU) Clackamas River - early and late [ 269 ] Coho Salmon (Lower Columbia River ESU) - Coweeman RiverSalmon, coho (Lower Columbia River ESU)

Coweeman River - late

Page 97: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 270 ] Coho Salmon (Lower Columbia River ESU) - East Fork Lewis RiverSalmon, coho (Lower Columbia River ESU) East Fork Lewis River - early and late

[ 271 ] Coho Salmon (Lower Columbia River ESU) - Kalama RiverSalmon, coho (Lower Columbia River ESU) Kalama River - late

[ 272 ] Coho Salmon (Lower Columbia River ESU) - Lower Cowlitz RiverSalmon, coho (Lower Columbia River ESU) Lower Cowlitz River - late

[ 273 ] Coho Salmon (Lower Columbia River ESU) - North Fork Lewis RiverSalmon, coho (Lower Columbia River ESU) North Fork Lewis River - early and late

[ 274 ] Coho Salmon (Lower Columbia River ESU) - North Fork Toutle RiverSalmon, coho (Lower Columbia River ESU) North Fork Toutle River - early and late

[ 275 ] Coho Salmon (Lower Columbia River ESU) - Salmon CreekSalmon, coho (Lower Columbia River ESU) Salmon Creek - late

[ 276 ] Coho Salmon (Lower Columbia River ESU) - Sandy RiverSalmon, coho (Lower Columbia River ESU) Sandy River - early and late

[ 277 ] Coho Salmon (Lower Columbia River ESU) - South Fork Toutle RiverSalmon, coho (Lower Columbia River ESU) South Fork Toutle River - early and late

[ 278 ] Coho Salmon (Lower Columbia River ESU) - Tilton RiverSalmon, coho (Lower Columbia River ESU) Tilton River - early and late

[ 279 ] Coho Salmon (Lower Columbia River ESU) - Upper Cowlitz RiverSalmon, coho (Lower Columbia River ESU) Upper Cowlitz River - early and late

[ 280 ] Coho Salmon (Lower Columbia River ESU) - Washougal RiverSalmon, coho (Lower Columbia River ESU) Washougal River - late

Coastal MPG [ 281 ] Coho Salmon (Lower Columbia River ESU) - Big CreekSalmon, coho (Lower Columbia River ESU) Big

Creek - late [ 282 ] Coho Salmon (Lower Columbia River ESU) - Clatskanie RiverSalmon, coho (Lower Columbia River ESU)

Clatskanie River - late [ 283 ] Coho Salmon (Lower Columbia River ESU) - Elochoman RiverSalmon, coho (Lower Columbia River ESU)

Elochoman River - late [ 284 ] Coho Salmon (Lower Columbia River ESU) - Grays & Chinook RiversSalmon, coho (Lower Columbia River

ESU) Grays and Chinook Rivers - late [ 285 ] Coho Salmon (Lower Columbia River ESU) - Mill CreekSalmon, coho (Lower Columbia River ESU) Mill,

Abernathy, and Germany Creeks - late

Page 98: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 286 ] Coho Salmon (Lower Columbia River ESU) - Scappoose RiverSalmon, coho (Lower Columbia River ESU) Scappoose Creek - late

[ 287 ] Coho Salmon (Lower Columbia River ESU) - Youngs BaySalmon, coho (Lower Columbia River ESU) Youngs Bay - late

Gorge MPG [ 288 ] Coho Salmon (Lower Columbia River ESU) - Lower Gorge TributariesSalmon, coho (Lower Columbia River

ESU) Lower Gorge Tributaries - late [ 289 ] Coho Salmon (Lower Columbia River ESU) - Mainstem section of Upper Gorge Tributaries (Hood River and

White Salmon River) [ 290 ] Coho Salmon (Lower Columbia River ESU) - Oregon Upper Gorge tributaries and Hood RiverSalmon, coho

(Lower Columbia River ESU) Oregon Upper Gorge Tributaries and Hood River - early [ 291 ] Coho Salmon (Lower Columbia River ESU) - Washington Upper Gorge tributaries and White Salmon

RiverSalmon, coho (Lower Columbia River ESU) Washington Upper Gorge Tributaries and White Salmon River - late Willamette - Cascade

[ 292 ] Coho Salmon (Lower Columbia River ESU) - Clackamas River Steelhead

o Lower Columbia River Steelhead DPSSteelhead (Lower Columbia River DPS) Cascade MPG

[ 293 ] Steelhead (Lower Columbia River DPS) - Cispus River Winter-runSteelhead (Lower Columbia River DPS) Cispus River - winter

[ 315 ] Steelhead (Lower Columbia River DPS) Clackamas River - winter [ 294 ] Steelhead (Lower Columbia River DPS) - Coweeman River Winter-runSteelhead (Lower Columbia River DPS)

Coweeman River - winter [ 295 ] Steelhead (Lower Columbia River DPS) - East Fork Lewis River Summer-runSteelhead (Lower Columbia

River DPS) East Fork Lewis River - summer [ 296 ] Steelhead (Lower Columbia River DPS) - East Fork Lewis River Winter-runSteelhead (Lower Columbia River

DPS) East Fork Lewis River - winter [ 297 ] Steelhead (Lower Columbia River DPS) - Kalama River Summer-runSteelhead (Lower Columbia River DPS)

Kalama River - summer [ 298 ] Steelhead (Lower Columbia River DPS) - Kalama River Winter-runSteelhead (Lower Columbia River DPS)

Kalama River - winter [ 299 ] Steelhead (Lower Columbia River DPS) - Lower Cowlitz River Winter-runSteelhead (Lower Columbia River

DPS) Lower Cowlitz River - winter

Page 99: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

[ 300 ] Steelhead (Lower Columbia River DPS) - North Fork Lewis River Summer-runSteelhead (Lower Columbia River DPS) North Fork Lewis River - summer

[ 301 ] Steelhead (Lower Columbia River DPS) - North Fork Lewis River Winter-runSteelhead (Lower Columbia River DPS) North Fork Lewis River - winter

[ 302 ] Steelhead (Lower Columbia River DPS) - North Fork Toutle River Winter-runSteelhead (Lower Columbia River DPS) North Fork Toutle River - winter

[ 303 ] Steelhead (Lower Columbia River DPS) - Salmon Creek Winter-runSteelhead (Lower Columbia River DPS) Salmon Creek - winter

[ 304 ] Steelhead (Lower Columbia River DPS) - Sandy River Winter-runSteelhead (Lower Columbia River DPS) Sandy River - winter

[ 305 ] Steelhead (Lower Columbia River DPS) - South Fork Toutle River Winter-runSteelhead (Lower Columbia River DPS) South Fork Toutle River - winter

[ 306 ] Steelhead (Lower Columbia River DPS) - Tilton River Winter-runSteelhead (Lower Columbia River DPS) Tilton River - winter

[ 307 ] Steelhead (Lower Columbia River DPS) - Upper Cowlitz River Winter-runSteelhead (Lower Columbia River DPS) Upper Cowlitz River - winter

[ 308 ] Steelhead (Lower Columbia River DPS) - Washougal River Summer-runSteelhead (Lower Columbia River DPS) Washougal River - summer

[ 309 ] Steelhead (Lower Columbia River DPS) - Washougal River Winter-runSteelhead (Lower Columbia River DPS) Washougal River - winter

Gorge MPG [ 310 ] Steelhead (Lower Columbia River DPS) - Hood River Summer-runSteelhead (Lower Columbia River DPS)

Hood River - summer [ 311 ] Steelhead (Lower Columbia River DPS) - Hood River Winter-runSteelhead (Lower Columbia River DPS)

Hood River - winter [ 312 ] Steelhead (Lower Columbia River DPS) - Lower Gorge Tributaries Winter-runSteelhead (Lower Columbia

River DPS) Lower Gorge Tributaries - winter [ 313 ] Steelhead (Lower Columbia River DPS) - Upper Gorge Tributaries Winter-runSteelhead (Lower Columbia

River DPS) Upper Gorge Tributaries - winter [ 314 ] Steelhead (Lower Columbia River DPS) - Wind River Summer-runSteelhead (Lower Columbia River DPS)

Wind River - summer Willamette - Cascade

[ 315 ] Steelhead (Lower Columbia River DPS) - Clackamas River Winter-run

Page 100: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Undefined Coastal MPG for populations added to list by ODFW [ 501 ] Big Creek Winter Steelhead [ 502 ] Clatskanie River Winter Steelhead [ 503 ] Scappoose Creek Winter Steelhead [ 500 ] Youngs Bay Winter Steelhead

o Upper Willamette River Steelhead DPSSteelhead (Upper Willamette River DPS) Willamette MPG

[ 316 ] Steelhead (Upper Willamette River DPS) - Calapooia River Winter-runSteelhead (Upper Willamette River DPS) Calapooia River - winter

[ 317 ] Steelhead (Upper Willamette River DPS) - Molalla River Winter-runSteelhead (Upper Willamette River DPS) Molalla River - winter

[ 318 ] Steelhead (Upper Willamette River DPS) - North Santiam River Winter-runSteelhead (Upper Willamette River DPS) North Santiam River - winter

[ 319 ] Steelhead (Upper Willamette River DPS) - South Santiam River Winter-runSteelhead (Upper Willamette River DPS) South Santiam River - winter

[ 320 ] Steelhead (Upper Willamette River DPS) - West Side Tributaries Winter-run

Page 101: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Appendix D. Names of Populations Defined by NPCC / CBFWA / CRITFC (from Subbasin Planning)

Listed below in hierarchical order are the names of fish populations used by NPCC for subbasin planning. This list was developed by CBFWA and CRITFC from the subbasin plans. The names shown were provided by David Graves of CRITFC on September 26, 2012. Geographic representations of the populations can be found at http://fishery.critfc.org/FiSci/FishUnitsIntroMap.htm.

Chinook salmon Fall

o Big Creek Fall Chinooko Clackamas River Fall Chinooko Clatskanie River Fall Chinooko Clearwater River Fall Chinooko Columbia Upper Gorge Tributaries Fall Chinooko Coweeman River Fall Chinooko Deschutes River Fall Chinooko Elochoman River Fall Chinooko Grande Ronde River Fall Chinooko Grays River Fall Chinooko Hanford Reach Fall Chinooko Hood River Fall Chinooko Imnaha River Fall Chinooko Kalama River Fall Chinooko Klickitat River Fall Chinooko Lewis River Early Fall Chinooko Lewis River Late Fall Chinooko Lower Columbia Gorge Tributaries Fall Chinooko Lower Cowlitz River Fall Chinooko Lower Snake River Fall Chinooko Lower Yakima River Fall Chinooko Marion Drain Fall Chinook [10/9/14 note from Bill Bosch (YIN) to Greg Lippert

(WDFW) says this is no longer considered a separate population.]o Mill Creek Fall Chinooko Rock Creek Fall Chinooko Salmon Creek Early Fall Chinooko Sandy River Early Fall Chinooko Scappoose Creek Fall Chinooko Snake Hell's Canyon Fall Chinooko Toutle River Fall Chinook

o Tucannon River Fall Chinooko Umatilla River Fall Chinooko Upper Cowlitz River Fall Chinooko Washougal River Fall Chinooko White Salmon Bright Fall Chinooko White Salmon Tule Fall Chinooko Youngs Bay Fall Chinook

Springo American River Spring Chinooko Calapooia River Spring Chinooko Catherine Creek Spring Chinooko Cispus River Spring Chinooko Clackamas River Spring Chinooko East Fork Salmon River Spring Chinooko Entiat River Spring Chinooko Granite Creek John Day Spring Chinooko Hood River Spring Chinooko Kalama River Spring Chinooko Klickitat River Spring Chinooko Lewis River Spring Chinooko Little White Salmon River Spring Chinooko Lolo Creek Spring Chinooko Lookingglass Creek Spring Chinooko Malheur River Spring Chinooko McKenzie River Spring Chinooko Methow River Spring Chinooko Middle Fork John Day Spring Chinooko Middle Fork Willamette River Spring Chinooko Minam River Spring Chinooko Molalla/Pudding River Spring Chinooko Naches River Spring Chinooko North Fork John Day Spring Chinook

Page 102: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

o North Santiam River Spring Chinooko Okanogan River Spring Chinooko Potlatch River Spring Chinooko Sandy River Spring Chinooko Shitike Creek Spring Chinooko South Santiam River Spring Chinooko Tilton River Spring Chinooko Toutle River Spring Chinooko Umatilla River Spring Chinooko Upper Cowlitz River Spring Chinooko Upper Grande Ronde Spring Chinooko Upper John Day Spring Chinooko Upper Yakima River Spring Chinooko Walla Walla Spring Chinooko Wallowa - Lostine River Spring Chinooko Warm Springs River Spring Chinooko Wenatchee River Spring Chinooko White Salmon Spring Chinooko Wind River Spring Chinook

Spring/summero Asotin Creek Spring/Summer Chinooko Bear Valley Creek Spring/Summer Chinooko Big Creek Spring/Summer Chinooko Big Sheep Creek Spring/Summer Chinooko Camas Creek Spring/Summer Chinooko Chamberlain Creek Spring/Summer Chinooko East Fork South Fork Salmon River Spring/Summer Chinooko Imnaha River Mainstem Spring/Summer Chinooko Lapwai/Big Canyon Spring/Summer Chinooko Lawyer Creek Spring/Summer Chinooko Lemhi River Spring/Summer Chinooko Little Salmon River Spring/Summer Chinooko Lochsa River Spring/Summer Chinooko Loon Creek Spring/Summer Chinooko Lower North Fork Clearwater River Spring/Summer Chinooko Marsh Creek Spring/Summer Chinooko Meadow Creek Spring/Summer Chinooko Middle Fork Salmon River above Indian Creek Spring/Summer Chinooko Middle Fork Salmon River below Indian Creek Spring/Summer Chinooko Moose Creek Spring/Summer Chinooko North Fork Salmon River Spring/Summer Chinooko Pahsimeroi River Spring/Summer Chinook

o Panther Creek Spring/Summer Chinooko Salmon River Lower Mainstem below Redfish Lake Spring/Summer Chinooko Salmon River Upper Mainstem above Redfish Lake Spring/Summer Chinooko Secesh River Spring/Summer Chinooko South Fork Salmon River Spring/Summer Chinooko Sulphur Creek Spring/Summer Chinooko Tucannon River Spring/Summer Chinooko Upper North Fork Clearwater River Spring/Summer Chinooko Upper Selway River Spring/Summer Chinooko Upper South Fork Clearwater River Spring/Summer Chinooko Valley Creek Spring/Summer Chinooko Wenaha River Spring/Summer Chinooko Yankee Fork Spring/Summer Chinook

Chum salmon Fallo Cowlitz River Fall Chum

(No run indicated)o Big Creek Chumo Clackamas River Chumo Clatskanie River Chumo Cowlitz River Summer Chumo Elochoman River Chumo Grays/Chinook Rivers Chumo Kalama River Chumo Lewis River Chumo Lower Columbia Gorge Tributaries Chumo Lower Columbia Mainstem Chumo Mill Creek Chumo Sandy River Chumo Scappoose Creek Chumo Upper Gorge Tributaries Chumo Washougal River Chumo Youngs Bay Chum

Coho salmon (No run indicated)o Big Creek Cohoo Cispus River Cohoo Clackamas River Cohoo Clatskanie River Coho

Page 103: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

o Coweeman River Cohoo East Fork Lewis River Cohoo Elochoman Cohoo Entiat River Cohoo Fifteenmile Creek Cohoo Grays/Chinook Rivers Cohoo Hood River Cohoo Kalama River Cohoo Lower Columbia Gorge Tributaries Cohoo Lower Cowlitz River Cohoo Mill Creek Cohoo Molalla/Pudding River Cohoo North Fork Lewis River Cohoo North Fork Toutle River Cohoo North Santiam River Cohoo Salmon Creek Cohoo Sandy River Cohoo Scappoose Creek Cohoo South Fork Toutle River Cohoo Tilton River Cohoo Umatilla River Cohoo Upper Cowlitz River Cohoo Washougal River Cohoo Wenatchee River Cohoo White Salmon Cohoo Youngs Bay Coho

Kokanee (No run indicated)o Bumping Lake Kokaneeo Cle elum Lake Kokaneeo Coeur d'Alene Lake Kokaneeo Crab Creek Kokaneeo Crane Prairie Reservoir Kokaneeo Kachess Lake Kokaneeo Keechelus Lake Kokaneeo Lake Billy Chinook Kokaneeo Lake Chelan Kokaneeo Lake Osoyoos Kokaneeo Lake Pend Oreille Kokaneeo Lake Wenatchee Kokaneeo Paulina Lake Kokanee

o Payette Lake Kokaneeo Priest Lake Kokaneeo Rimrock Lake Kokaneeo San Poil River Kokaneeo Spokane River Kokaneeo Suttle Lake Kokaneeo Upper Columbia River Kokaneeo Wallowa Lake Kokaneeo Wickiup Reservoir Kokanee

Sockeye salmon (No run indicated)o Okanogan River Sockeyeo Snake River (Redfish Lake) Sockeye Salmono Snake River Sockeye (Stanley, Petit, Alturas, other lakes)o Wenatchee River Sockeyeo Yakima River Sockeye

Steelhead Summero Asotin Creek Summer Steelheado Burnt River Summer Steelheado Chamberlain Creek Summer Steelheado Clearwater River Lower Mainstem Summer Steelheado Crab Creek Summer Steelheado Deschutes Crooked River Summer Steelheado Deschutes River Eastside Tributaries Summer Steelheado Deschutes River Westside Tributaries Summer Steelheado East Fork Lewis River Summer Steelheado East Fork Salmon River Summer Steelheado Entiat River Summer Steelheado Hood River Summer Steelheado Imnaha River Summer Steelheado Joseph Creek Summer Steelheado Kalama River Summer Steelheado Klickitat River Summer Steelheado Lemhi River Summer Steelheado Little and Lower Salmon River Summer Steelheado Lochsa River Summer Steelheado Lolo Creek Summer Steelheado Lower Grande Ronde Summer Steelhead

Page 104: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

o Lower John Day Summer Steelheado Lower Malheur River Summer Steelheado Lower Middle Fork Salmon River Summer Steelheado Lower Owyhee River Summer Steelheado Methow River Summer Steelheado Middle Fork John Day Summer Steelheado Naches River Summer Steelheado North Fork Clearwater River Summer Steelheado North Fork John Day Summer Steelheado North Fork Lewis River Summer Steelheado North Fork Salmon River Summer Steelheado Okanogan River Summer Steelheado Pahsimeroi River Summer Steelheado Panther Creek Summer Steelheado Powder River Summer Steelheado Rock Creek Summer Steelheado Salmon River Upper Mainstem Summer Steelheado Sandy River Summer Steelheado Satus Creek Summer Steelheado Secesh River Summer Steelheado Selway River Summer Steelheado Snake Hells Canyon Summer Steelheado South Fork Clearwater River Summer Steelheado South Fork John Day Summer Steelheado South Fork Salmon River Summer Steelheado Toppenish Creek Summer Steelheado Touchet River Summer Steelheado Tucannon River Summer Steelheado Umatilla River Summer Steelheado Upper Grande Ronde Summer Steelheado Upper John Day Summer Steelheado Upper Malheur River Summer Steelheado Upper Middle Fork Salmon River Summer Steelheado Upper Owyhee River Summer Steelheado Upper Yakima River Summer Steelheado Walla Walla River Summer Steelheado Wallowa River Summer Steelheado Washougal River Summer Steelhead

o Wenatchee River Summer Steelheado White Salmon River Steelheado Willow Creek Summer Steelheado Wind River Summer Steelhead

Wintero Big Creek Winter Steelheado Calapooia River Winter Steelheado Cispus River Winter Steelheado Clackamas River Winter Steelheado Clatskanie River Winter Steelheado Columbia Gorge Tributaries Winter Steelheado Coweeman River Winter Steelheado East Fork Lewis River Winter Steelheado Elochoman Winter Steelheado Fifteenmile Subbasin Winter Steelheado Grays River Winter Steelheado Hood River Winter Steelheado Kalama River Winter Steelheado Klickitat River Winter Steelheado Lower Cowlitz River Winter Steelheado Middle Fork Willamette River Winter Steelheado Mill Creek Winter Steelheado Molalla/Pudding River Winter Steelheado North Fork Lewis River Winter Steelheado North Fork Toutle River Winter Steelheado North Santiam River Winter Steelheado Salmon Creek Winter Steelheado Sandy River Winter Steelheado Scappoose Creek Winter Steelheado South Fork Toutle River Winter Steelheado South Santiam River Winter Steelheado Tilton River Winter Steelheado Upper Columbia Gorge Tributaries Winter Steelheado Upper Cowlitz River Winter Steelheado Washougal River Winter Steelheado Willamette Westside Tributaries Winter Steelheado Youngs Bay Winter Steelhead

Page 105: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Appendix E. Defining New Populations

Follow these steps to add new populations for use in the main tables.1) Request from StreamNet a PopID value for each new population you plan to submit.2) Fill out the following table as fully as possible for each population. Assign one of your new PopID values to each row of data. 3) Submit the records to StreamNet as soon as possible. The new records for the new populations need to be added before the PopID values can be used in the main tables above. Also, submitting them as early as you can allows for QC work to be done at StreamNet before the codes are needed for use.

A ppendix E1. Populations TableThis table stores information about populations, and records who requested each population be added.

Field Name Field Description Data Type Codes/Conventions for NOSA TablePopID Code for the TRT population of fish represented by

this record.Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations

are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS populations.

CommonName Common name of the taxon of fish. Text 50 Enter the name of the taxon here, even if taxon name is included in the name of the population. Select from the following: Bull trout Chinook salmon Chum salmon Coho salmon Sockeye salmon SteelheadAdditional species may be added in the future: refer to http://old.streamnet.org/SpeciesInFW.html for common names.

Run Run of fish. Text 20 Enter the name of the run here, even if run name is included in the name of the population. Entries in this field are not recognized as taxonomic divisions. Select from the following: Spring Summer Fall Winter Spring/summer N/A [For species without recognized runs. For example, bull trout.]

ESU_DPS For populations listed under the federal ESA, this is the name of a defined Evolutionarily Significant Unit (ESU) or Distinct Population Segment (DPS) as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Text 255 Enter the name of the ESU or DPS here. Entries in this field are taxonomic divisions defined by NMFS or USFWS, and may be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at http://www.westcoast.fisheries.noaa.gov.

Page 106: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Field Name Field Description Data Type Codes/Conventions for NOSA TableRecoveryDomain Name of the "recovery domain," as defined by the

NMFS Northwest Region, in which the population falls.

Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this list: Puget Sound Recovery Domain Willamette/Lower Columbia Recovery Domain Interior Columbia Recovery Domain Oregon Coast Recovery Domain Southern Oregon/Northern California Coast Recovery Domain

Further information about recovery domains can be found at http://www.westcoast.fisheries.noaa.gov.MajorPopGroup Name of "major population group" (MPG) or

“stratum” as defined by the NMFS Northwest Region, in which the population falls.

Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined geographically. See Appendix C for the list of MPGs / strata.

CBFWApopName Population name as defined by CBFWA for subbasin planning purposes, from subbasin plans and agencies.

Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names.

Fill this field even when a population's geographic extent coincides with NWR name for a listed population.CommonPopName Population name used by local biologists. Text 255 Often this is simply the name of the population as it was written on the original time series spreadsheets.ContactAgency Agency, tribe, or other entity that requested this

population be added to the list.Text 255 Entries in this field must precisely match a name in the StreamNet agency list. Here are the ones most likely needed. If yours

is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. Columbia River Inter-Tribal Fish Commission Colville Confederated Tribes Confederated Tribes and Bands of the Yakama Indian Nation Confederated Tribes of the Umatilla Indian Reservation Confederated Tribes of the Warm Springs Reservation of Oregon Idaho Department of Fish and Game Nez Perce Tribe Oregon Department of Fish and Wildlife Spokane Tribe of Indians Washington Department of Fish and Wildlife

Page 107: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Appendix EF. Hatchery names and codes

Hatchery name CodeAberdeen Net Pens at US Army COE's Pier 396Abernathy Fish Technology Center 1Agate Pass Seapens 476Alder Creek Rearing Pond 293Allison Springs Rearing Pond 368Alsea Hatchery 128Alturas Lake Creek Screw Trap 907American Falls Fish Hatchery 343American River Hatchery 732Anderson Ranch Reservoir Weir 908Applegate Trap 575Arlington Hatchery 218Ashton Fish Hatchery 238Aspen Springs Trout Farm 268Aumsville Ponds 37Avila Beach Sea Pens 749Baker Lake Hatchery (aka Baker Spawning Beach 4)(previously Sulphur Springs Hatchery)

487

Baker Lake Spawning Beach 2 516Baker Lake Spawning Beach 3 540Bandon Hatchery 129Barnaby Slough Rearing Pond 330Bear Springs Rearing Pond 1 294Bear Springs Rearing Pond 2 538Bear Valley Creek Weir 909Beaver Creek Hatchery 55Bellingham Hatchery 488Big Beef Creek Hatchery 375Big Canyon Ponds_Wallowa Hatchery satellite facility 52Big Creek Hatchery 25Big Creek Hatchery 747Big Springs Creek Weir Lower 910Big Springs Creek Weir Upper 911Big White Salmon Ponds 2Big Wood River Weir 912Bills Boathouse Net Pen 517Bingham Adult Fishway & Trap 429Bingham Creek Hatchery 114Bitterroot Fish Hatchery 275Black Rock Hatchery 737Blackbird Island Pond 646Blackfoot River Weir 913

Bogachiel Hatchery 331Bogachiel R Rearing Pond 332Bohannon Falls Fish Trap 571Bonifer Pond Juvenile Acclimation/Release Facility 130Bonneville Hatchery 26Boulder Creek Screw Trap 914Boyd Cr Rearing Pond 395Brenner Trout Hatchery 401Butte Falls Hatchery 131Cabinet Gorge Fish Hatchery 285Camas Net Pens 402Canyon Springs Pond (Hoh Tribe) 403Capital Lake Rearing Pond 404Capitol Lake Trap 518Carlton Acclimation Pond 90Carson Depot Springs 555Carson NFH 3Casa Grande High School Hatchery 746Cascade Aqua Farms 299Cascade Hatchery 41Catherine Creek Acclimation Pond 577Catherine Creek Trap 576CCF Blind Slough Net Pens 569CCF Hatchery (South Fork) 105CCF Tongue Point Net Pens 568CCF Youngs Bay Net Pens 567Cedar Creek Hatchery 132Cedar Flats Acclimation Facility 904Cedar River Hatchery 361Chalaat Cr Hat (Hoh Tribe) 383Chamberlain Creek Weir 915Chambers Creek Hatchery 112Chambers Creek Trap 519Champion Pond 489Chehalis Tribal Hatchery 405Chelan Hatchery 60Chelan PUD Hatchery 297Chelan River Net Pens (WDFW) 647Chewach Rearing Pond 95Chimacum High 298Chiwawa Rearing Pond 91Clackamas Hatchery 31Clark Flat spring chinook acclimation/release site 547

Clark Fork Fish Hatchery 231Cle Elum Hatchery 542Cle Elum Ponds (aka Slough) 300Clear Cr Hatchery 337Clear Creek Adult Weir 916Clear Creek Juvenile Weir 917Clear Creek Rearing Pond 371Clear Creek Screw Trap 918Clearwater Fish Hatchery 24Clearwater River Scoop Trap 919Cocollala Creek Weir 920Coffee Pot Rapids Weir 921Cole M. Rivers Hatchery 133Coleman NFH 100Colt Killed Creek Screw Trap 922Columbia Basin Hatchery 220Colville Hatchery 302Colville Tribal Hatchery 301Corvallis Research Lab Hatchery 510Cottonwood Creek Rearing Pond 68Coulter Creek Rearing Pond 303Coweeman Rearing Pond #1 491Coweeman Rearing Pond #2 492Cowling Creek Hatchery 373Cowlitz Salmon Hatchery 72Cowlitz Trout Hatchery 56Coyote Valley Fish Facility 742Creston NFH 289Crisp Creek Rearing Pond 304Crooked Fork Creek Screw Trap 923Crooked Fork Creek Weir 924Crooked River Incubation Channel 925Crooked River Rearing Ponds 357Crooked River Satellite Fish Hatchery 109Crooked River Scoop Trap 926Crooked River Screw Trap 927Crystal Lake Hatchery 431Crystal Lakes 274Curl Lake Rearing Ponds 70Darrah Springs Hatchery 731Dayton Rearing Ponds 71Deadhorse Creek Rearing Pond 520Deadwood River Weir 928

Page 108: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Decker Ponds 355Deep R Net Pens - Upper (Rkm 8.1) 408Deer Springs Pond 230Delph Creek Station 609Dexter Pond_Willamette Hatchery satellite facility 40Diru Cr Hatchery 364Ditch Creek Incubation Channel 929Doty Creek Pools 748Drano Lake Pens (USFWS) 409Dryden Rearing Ponds 92Dungeness Hatchery 151Dworshak NFH 4Eagle Cr Pond (Preceded Cascade Hatchery) 557Eagle Creek NFH 5Eagle Creek Rearing Pond 430Eagle Fish Hatchery 345East Fork Salmon River Screw Trap 930Eastbank Hatchery 87Eastfork Satellite Fish Hatchery 107Easton Lake spring chinook acclimation/release site 548Easton Ponds coho acclimation/release site 610Educket Creek Hatchery 381Eells Springs Hatchery 411Eldorado Creek Weir 931Elk Adult Fishway & Trap 641Elk Creek Weir 932Elk River Hatchery 134Elochoman Hatchery 73Elson Creek Hatchery 369Elwha Channel 334Elwha Tribal Hatchery 379Enetai Hatchery 377Ennis National Fish Hatchery 269Entiat NFH 6Fall Creek Rearing Ponds 442Fall Creek Trap 118Fall River Hatchery 145Fallert Creek Hatchery 78Feather River Hatchery 99Fenn Ranger Station Incubation Channel 933Fidalgo Net Pens 613Fillmore Hatchery 740Fish Creek Screw Trap 934Fish Creek Weir 935Fish Lake Westslope Weir 936Fish Springs Hatchery 735Flaming Geyser Rearing Pond 514Flathead Lake Salmon Hatchery 261

Ford Hatchery 494Forks Creek Hatchery 117Fox Island Net Pens 468Garrison Springs Hatchery 305George Adams Hatchery 150Germany Creek Project 307Glen Ayr Net Pens Co-op 521Glenwood Springs Hatchery 522Gnat Creek Hatchery 27Gobar Rearing Pond 57Goldendale Hatchery 229Gorst Creek Rearing Ponds 370Grace Fish Hatchery 236Granite Creek Weir 937Grays River Hatchery 74Grays River Rearing Pond 54Green River Community College Rearing Pond 638Grovers Creek Hatchery 374Hagerman NFH 7Hagerman State Fish Hatchery 234Hantz Creek Acclimation Pond 574Harriman Trout Company 276Hartman PondAKA: Wahkeena Pond_Oxbow Hatchery satellite facility

46

Hayden Creek Fish Hatchery 344Hayspur Fish Hatchery 235Hells Canyon Dam Trap 106Henrys Lake Fish Hatchery 239Herman Creek Ponds (lower)_Oxbow Hatchery satellite facility

573

Herman Creek Ponds (upper)_Oxbow Hatchery satellite facility

45

Hoko Falls Hatchery 464Hollow Tree Creek Ponds 453Hoodsport Hatchery 148Hoodsport Marina Net Pens Co-op 523Hot Creek Hatchery 734Hughey Creek Pond 560Humptulips Hatchery 308Hupp Springs Rearing Pond 126Hurd Creek Hatchery 378Icy Creek Rearing Pond 417Imeques C-mem-ini-kem Juvenile Acclimation/Release Facility

564

Imnaha Acclimation and Collection Facility(Lookingglass Hatchery satellite facility)

50

Indian Creek Incubation Channel 938Indian Creek Weir 939

Iron Gate Hatchery 97Irrigon Hatchery 42Issaquah Hatchery 123Jack Cr spring chinook acclimation/release site 546Jim Cr Hatchery 479Jocko River Trout Hatchery 263Johns Creek Hatchery 327Johnson Creek Hatchery 418Johnson Creek Screw Trap 940Johnson Creek Weir 941Josephine Creek Weir 942Kalama Creek Hatchery 365Kalama Falls Hatchery 75Kendall Creek Hatchery 120Kenney Creek Rearing Pond 525Kern River Planting Base 739Keta Creek Hatchery 353Klamath Hatchery 147Klaskanine Hatchery 29Klickitat Hatchery 76Kooskia NFH 8Kootenai Tribal Sturgeon Hatchery 286La Grange Fish Facility 447Lake Aberdeen Hatchery 217Lake Creek Screw Trap 943Lake Creek Weir 944Lake Sequalitchew Net Pens 366Lake Shannon Net Pens 526Lake Wenatchee Net Pens 93Lake Whatcom Hatchery 326Lakewood Hatchery 328Leaburg Hatchery 32Leavenworth NFH 9Lemhi River Screw Trap 945Lemhi River Weir 509Lenore Lake Trap 527Lewis River (Fish First - Echo) Net Pens 541Lewis River Hatchery 77Lewiston Dam Trap 946Lion Creek Weir 947Little Blackfoot River Weir 948Little Goose Dam Fingerling Rearing 352Little Sheep Creek Pond(Wallowa Hatchery satellite facility)

53

Little White Salmon NFH 10Livingston Stone NFH 551Lochsa River Screw Trap 949Lolo Creek Weir Lower 950

Page 109: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Lolo Creek Weir Upper 951 Lonesome Creek Hatchery 382 Long Live the Kings - Lilliwaup 544

Page 110: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Long Live the Kings - Van Winkle Cr 543Lookingglass Hatchery 49Lost Cr coho acclimation/release site 549Lostine Acclimation Pond 580Louisa Creek Weir 952Lower Lemhi River Screw Trap 953Lower South Fork Salmon River Screw Trap 954Lukes Gulch Acclimation Facility 902Lummi Bay Sea Ponds 469Lyons Ferry Hatchery 67Mackay Fish Hatchery 237Mad River Hatchery 485Magic Valley Steelhead Hatchery 15Makah NFH 104Mamoya Rearing Pond 528Marblemount Hatchery 121Marion Forks Hatchery 33Marmot Acclimation Site(Satellite of Clackamas Hatchery)

480

Marsh Creek Screw Trap 955Marsh Creek Weir 956Matheny Cr Rearing Pond Quinault Tribe 386Mattole Salmon Stock Rescue Program 750Mayr Brothers Rearing Pond 389McAllister Hatchery 341McCall Fish Hatchery 16McCall Satellite Fish Hatchery 113McKenzie Hatchery 34McKernan Hatchery 376Meadow Creek Incubation Channel 957Merced River Fish Facility 435Merwin Dam (aka FCF) Adult Trap 644Merwin Hatchery 336Meseberg Hatchery 612Methow Hatchery 88Minter Creek Hatchery 149Minthorn Springs Juvenile Acclimation/Release Facility 136Minto Pond_Marion Forks satellite facility 481Moccasin Creek Hatchery 733Modrow (aka Kalama) Adult Trap 524Mojave River Hatchery 741Mokelumne River Hatchery 102Montlake Lab (NMFS NW & AK Fish Ctr) 354Moose Creek Weir 958Morgan Creek (Priorli Cr.) Rearing Facility (STEP facility)

351

Morse Creek Pond 645Mossyrock Hatchery 310

Mount Shasta State Fish Hatchery 730Mount Whitney Hatchery 736Mule Pasture Pond 477Mullan Fish Hatchery 232Murray Springs Trout Hatchery 265N/A 98Naches Hatchery 61Nampa Fish Hatchery 233Naselle Hatchery 311Nelson Springs Rearing Pond\Raceway 62Nemah Hatchery 116Newnonshish Hat (Shoalwater Bay Tribe) 393Newsome Acclimation Facility 906Nez Perce Tribal Fish Hatchery 901NF Toutle FCF 111Niagara Springs Fish Hatchery 17Nile Springs Pond 228Nimbus Fish Hatchery 101Noble Creek STEP Hatchery 561North Fork Boise River Weir 959North Fork Payette River Weir 960North Lapwai Valley Acclimation Facility 905North Nehalem Hatchery 137North Toutle Hatchery 84Northwestern Lake Net Pens 529Noyo River Egg Collection Station 554NWSSC - Cedar R Trap 545Oak Springs Hatchery 43Oakridge Salmon Hatchery 290Omak Hatchery 227Onalaska High School - Gheer Cr Collection 615Oregon Aqua-Foods/Yaquina Bay 457Oregon Hatchery Research Center 135Oxbow Fish Hatchery 18Oxbow Hatchery 44Pahsimeroi Fish Hatchery Lower Facility 19Pahsimeroi Fish Hatchery Upper Facility 961Pahsimeroi River Screw Trap 962Palmer Creek Trap 572Palmer Rearing Pond 495Parkdale Hatchery 562Pelton Ladder_Round Butte Hatchery satellite facility 48Pendleton Juvenile Acclimation/Release Facility(temporary name)

566

Percival Cove Net Pens 530Pettit Lake Creek Weir 963Pleasant Harbor Marina Net Pens Co-op 531Port Gamble Co-op Quilcene Bay Net Pens 474

Port Gamble Hatchery 466Port Gamble Net Pens 470Powell Satellite Fish Hatchery 20Powerdale Fish Facility 616Prairie Creek (Closed) 450Priest Rapids Hatchery 80proposed - Waikiki Springs Hatchery 225Prosser Hatchery 325Puyallup Hatchery (WDFW) 363Quilcene NFH 313Quinault Hatchery/Net Pens 388Quinault NFH 315Raft River Rearing Pond 387Rapid River Fish Hatchery 22Rapid River Screw Trap 964Red River Incubation Channel 965Red River Satellite Fish Hatchery 21Red River Satellite Fish Hatchery Rearing Ponds 966Red River Screw Trap 967Redfish Lake Creek Trap 508Redwood Creek (Eel River Project) 452Reiter Ponds 496Rhodes Pond 138Ringold Springs Hatchery 63Roaring River Hatchery 35Rock Creek Hatchery 139Rock Creek Pens (USFWS) 552Rocky Ford Hatchery #1 532Rocky Ford Hatchery #2 533Round Butte Hatchery 47Rowdy Creek Fish Hatchery 432Running Creek Incubation Channel 968Running Creek Screw Trap 969Running Creek Weir 970Rush Creek Weir 971Rutsatz Slough Rearing Pond 475S. Fk. Klaskanine Pond 359Salmon Falls Creek Weir 972Salmon River Fish Culture Facility 385Salmon River Hatchery 140Salmon River Screw Trap 973Samish Hatchery 119Samish Rearing Pond 534San Joaquin Hatchery 738Sandpoint Fish Hatchery 240Sandy Hatchery 30Satsop Springs Rearing Pond 392Sawtooth Fish Hatchery Weir 23

Page 111: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Sawtooth Intake Screw Trap 974Sawtooth Scoop Trap 975Sawtooth Screw Trap 976Schorno Springs Rearing Pond 478Sea Resources Hatchery 316Secesh River Screw Trap 977Secesh River Weir 978Sekokoni Springs Hatchery 277Selway Falls Trap 108Selway Falls Trap 979Selway River Screw Trap 980Shale Creek Rearing Pond 384Shelton Rearing Ponds 611Sherman Creek Hatchery 317Siletz Falls Trap 570Siletz Hatchery 291Silver Lake Net Pen 420Silverado Fisheries Base 438Similkameen Rearing Pond 89Skamania Hatchery 58Skookum Creek Hatchery 463Skookumchuck Dam Rearing Pond 339Skookumchuck Hatchery 648Skykomish Sportsmen Co-op Rearing Pond 639Slate Creek Weir 486Snake River Dipper Trap 982Social Security Pens (USFWS) 553Sol Duc Hatchery 318Soos Creek Hatchery 124South Fork Red River Incubation Channel 983South Fork Salmon River Screw Trap (DS Knox) 984South Fork Salmon River Screw Trap (US Knox) 985South Fork Walla Walla Adult Holding & Spawning Facility

565

South Santiam Hatchery 36South Sound Net Pens 497South Toutle Trap 498Speelyai Hatchery 83Spokane Hatchery 319Spokane Tribal Hatchery 320Spring Creek NFH 11Springfield Fish Hatchery 900Springfield Production 292Squaw Creek Weir 986Squaxin Island Sea Pens 321St Paul Pd 141St. Charles Creek Weir 987Stayton Pond 38

Page 112: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Stiles Pond coho acclimation/release site 550Stillaguamish Tribal Hatchery 360Stolle Meadows Rearing Pond 988Sullivan Springs Weir 989Sund Rock Net Pens Co-op 499Sunset Falls Adult Trap 535Sunset Falls FCF 640Sweetwater Springs Fish Hatchery 288Swinomish Rearing Ponds 536Tacoma Headworks Trap 614Tanwax Lake Net Pens 423Tehama-Colusa Fish Facility (Closed) 449Ten Mile River Hatchery 745Thornhollow Juvenile Acclimation/Release Facility 563Three Mile Adult Holding and Spawning Facility 110Tiburon Sea Pens 437Tokul Creek Hatchery 329Trask River Hatchery 142Trask River Hatchery Pond 143Trinity River Hatchery 96Trojan Pond 28Trout Lodge Hatchery 537Tucannon Hatchery 69Tuffy Creek Pond_Trask Hatchery satellite facility 559Tulalip Hatchery 323

Tumwater Falls Hatchery 367Tuolumne River Fish Facility (closed) 752Turtle Rock Rearing Ponds & Rocky Reach Annex 64Twisp Rearing Pond 94Two Mouth Creek Weir 990Umatilla Hatchery 144Umbrella Creek Hatchery\RSI 426University of Washington Hatchery 467Upper Grand Ronde Pond 579Upper Grand Ronde Weir Trap 578Upper Skagit Tribal Hatchery 465US Army Net Pens 416Van Arsdale Fisheries Station (Snow Mt.) 608Vancouver Hatchery 59Voight Creek Hatchery 125Waatch Cr Hat (Makah Tribe) 380Walcott Slough 556Wallace River Hatchery 122Wallowa Hatchery 51Warm Springs Fish Hatchery 103Warm Springs NFH 12Washburn Island Rearing Pond Facility 226Washoe Park Trout Hatchery 266Washougal Hatchery 85Websters Rearing Pond 372

Wells Hatchery 65West Fork Chamberlain Creek Weir 991West Fork Yankee Fork Screw Trap 992West Fork Yankee Fork Weir 993Westslope Trout Company 272Weyco-Briscoe Ponds 391Whatcom Cr Hatchery 219Whiskey Creek Hatchery (Private) 558White River Hatchery 362Whitehorse Rearing Ponds 333Wildhorse River Weir 994Willamette Hatchery 39Willard NFH 13Winchester Hatchery 539Winthrop NFH 14Wizard Falls Hatchery 146Wolf Lodge Creek Weir 995Wynoochee Lake Net Pens (Trout) 427Wynoochee R Salmon Pens 390Yager Creek Hatchery 744Yakima Hatchery 66Yakima Net Pens @ Wapato Dam 428Yoosa-Camp Creek Acclimation Facility 903

Page 113: Coordinated Assessments Data Exchange Template€¦  · Web viewPacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface. This document contains

Appendix FG. MS-Access 2010 Data Types

MS-Access 2010 Data Type Purpose Characteristics Storage Required Per Record

Currency Numbers. Appropriate for numbers other than currency.

Zero to 15 digits to the left ofthe decimal point and zero to 4 digits to the right. 8 bytes

Date/Time Date and time.

Years 100 through 9999.This data type stores date AND time -- it is not possible

to store one without the other.A date with no time is interpreted as 00:00 in the

morning.A time with no date is interpreted as 12/30/1899.

Calculations among records recognize and use thesedefault values in calculations, so must be accounted

for when using the data.

8 bytes

Memo Long text entries. (Including numbers not used in calculations.) Up to 63,999 characters in length.

2 bytes / character for Unicode.1 byte / character if Unicode compression enabled and

entry is under 4,096 characters.

Number (Byte) Whole numbers from 0 to 255. Integers only: no decimal places.No negative numbers. 1 byte

Number (Decimal) Numbers from -9.999 X 1027 to 9.99927. Decimal places and negative numbers allowed.Up to 28 significant digits. 12 bytes

Number (Integer) Whole numbers from -32,768 to 32,767. Integers only: no decimal places. 2 bytes

Number (Long Integer) Whole numbers–2,147,483,648 to 2,147,483,647. Integers only: no decimal places. 4 bytes

Number (Single) Floating point numbers–3.402823 X 1038 to 3.402823 X 1038. Up to 7 significant digits. 4 bytes

Number (Double) Floating point numbers–1.79769313486231 X 10308 to 1.79769313486231 X 10308. Up to 15 significant digits. 8 bytes

ReplicationID Globally unique identifier (GUID). Creates a (presumably) unique value to identify a record. 16 bytes

Text Text.(Including numbers not used in calculations.)

Up to 255 characters in length.Maximum allowed length can be shorter than 255.

2 bytes / character for Unicode.1 byte / character if Unicode compression enabled.

Yes/No Storage of values that can have only one of two values.Yes/No; On/Off; True/False.

Cannot be null. Must be one of the 2 values.It is not possible to indicate such things as

"Not applicable" or "Unknown".1 bit


Recommended