Coordinated Assessments Data Exchange Template s1

Coordinated Assessments Data Exchange Standard

Version 20150619

Effective Date: June 19, 2015

Prepared by: Pacific States Marine Fisheries Commission StreamNet Project

for

Pacific Northwest Coordinated Assessments Data Exchange Standard Development Team Preface This 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 Number of natural origin fish that actually spawn, not Spawner abundance Natural origin NOSA (A1) necessarily the number of fish returning to a spawning area. Number of natural origin juvenile fish in a population. Usually PresmoltAbundance Presmolt abundance Natural origin late summer parr, but may be any time and stage. (A6) Number of fish passing a defined point as they migrate JuvenileOutmigrants Number of outmigrants Natural origin downstream. (A4) 100 X the point estimate of the number of returning natural Smolt to adult ratio (percentage) Natural origin origin adults, divided by the point estimate of the number of SAR (A2) smolts that produced those returning adults. 100 X the point estimate of the number of returning hatchery Smolt to adult ratio (percentage) Hatchery origin origin adults, divided by the point estimate of the number of SAR_hatchery (B4) smolts that produced those returning adults. 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 RperS (A3) Recruits per spawner: juveniles Natural origin "recruits" can be defined at any life stage. Recruit per spawner ratios are specific to the locations and Recruits per spawner: adults Hatchery origin seasons described in each record of data. The number of RperS_hatchery (B5) "recruits" can be defined only for adults at this time. Number of fish spawned in a hatchery under a hatchery program Proportion of hatchery broodstock that are Indicators for evaluating the success of hatchery programs. HatcherySpawning (B1) natural origin fish Egg take Estimate of the relative selection pressure of the natural Proportionate natural influence (PNI) of environment on hatchery origin fish in an integrated natural / PNI (B2) supplementation hatcheries hatchery population. Egg to release survival rates for hatchery Hachery origin These survival rates are specific to a production group. EggToRelease (B3) programs

Coordinated Assessments Data Exchange Standard 20150619 Page 2 of 105 Table Of Contents

Preface------2 I. Introduction------4 II. Data Tables------5 Section A: Indicators for Populations of Natural Origin Fishes...... 5 A1. NOSA Table...... 5 A2. SAR Table...... 12 A3. RperS Table...... 19 A4. JuvenileOutmigrants Table...... 26 A5. JuvenileOutmigrantsDetail Table...... 31 A6. PresmoltAbundance Table...... 34 Section B: Indicators for Hatchery Programs and Populations of Hatchery Origin Fishes 40 B1. HatcherySpawning Table...... 40 B2. PNI Table...... 47 B3. EggToRelease Table...... 52 B4. SAR_Hatchery Table...... 57 B5. RperS_Hatchery Table...... 63 III. Appendices------71 Appendix A. Fields included in every table by reference...... 71 Appendix B. Glossary...... 73 Appendix C. Recovery Domains, Species, ESUs, MPGs, and Populations Defined by NMFS and NPCC/CBFWA/CRITFC 74 Interior Columbia Recovery Domain...... 74 Oregon Coast Recovery Domain...... 81 Puget Sound Recovery Domain Geographic Regions and MPGs...... 83 Willamette/Lower Columbia Recovery Domain Strata...... 86 Appendix D. Names of Populations Defined by NPCC / CBFWA / CRITFC (from Subbasin Planning) 91 Chinook salmon...... 91 Chum salmon...... 92 Coho salmon...... 92 Kokanee...... 93 Sockeye salmon...... 93 Steelhead...... 93 Appendix E. Defining New Populations...... 95 Appendix E1. Populations Table...... 95 Appendix F. Hatchery names and codes...... 97 Appendix G. MS-Access 2010 Data Types...... 101

Coordinated Assessments Data Exchange Standard 20150619 Page 3 of 105 Coordinated Assessments Data Exchange Standard 20150619 Page 4 of 105 I. Introduction 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 This document contains the Coordinated Assessments Data Exchange to the Field Description column for business rules on when the field is Standard. It includes 1) the names and purposes of tables, 2) required. relationships among tables, and 3) the names, purposes, and properties of fields within tables. This data exchange standard was created by The data types listed in the tables' Data Type column are Microsoft Pacific Northwest United States representatives from state and federal Access 2010 data types. Appendix G contains details regarding these and tribal fisheries management and regulatory agencies, private data types. consultants, and federal funding agencies. For help understanding the data tables or this document, contact Mike This document has three main divisions: this introduction; the Banach with Pacific States Marine Fisheries Commission (503-595- descriptions of the data tables; and appendices. Sections within the 3152; [email protected]). 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

Coordinated Assessments Data Exchange Standard 20150619 Page 5 of 105 II. Data Tables

Section A: Indicators for Populations of Natural Origin Fishes

A1. NOSA Table This table stores information concerning natural origin spawner abundance (NOSA). "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 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). (unique)  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://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 If not applicable then enter "N/A" (e.g., for bull trout). ESU_DPS For populations listed under the federal ESA, this 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Coordinated Assessments Data Exchange Standard 20150619 Page 6 of 105 Field Name Field Description Data Type Codes/Conventions for NOSA Table RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls. geographically. See Appendix C for the list of MPGs / strata. PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the NOSA estimate corresponds to the  Same [Estimate represents one entire population, the whole population, and nothing but the population.] geographic definition of 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 Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish spawner abundance value corresponds to the for which the NOSA estimate was made. defined population. WaterBody Name of the body of water associated with the Text 255 This may be any of the following: time series.  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 Integer In cases where an unusual population begins spawning uncharacteristically early (before January 1 for spring spawners) or late species (and run where appropriate) began. (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.

Coordinated Assessments Data Exchange Standard 20150619 Page 7 of 105 Field Name Field Description Data Type Codes/Conventions for NOSA Table TRTmethod Flag indicating whether the methods used to Text 3 Acceptable values: generate the values in this record are those  Yes [The record reflects the TRT method; it will be submitted to NMFS's SPS database.] defined by the TRT.  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 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

This field is used in conjunction with the 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 ContactAgency field. See the Codes/Conventions methods changed, you can enter "1" for all records if there is always only one record per year for a population. column for details. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 8 of 105 Field Name Field Description Data Type Codes/Conventions for NOSA Table NOSAIJAlpha The significance level for the NOSAIJ confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. NOSAEJ The point estimate for natural origin spawner Single Estimated number of natural origin spawners contributing to spawning in a particular year. Includes only "adults" of natural abundance, excluding jacks. origin, excluding jacks. "Natural origin" means the fish's parents spawned in the wild.

This field is required if the NOSAIJ field is null Provide this estimate ONLY if one of the following is true: and NullRecord = "No".  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 Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. NOSAEJ field. NOSAEJUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. NOSAEJ field. NOSAEJAlpha The significance level for the NOSAEJ Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha. NOBroodStockRemoved The number of additional natural origin fish Single This value reflects fish taken for hatchery use from the indicated spawning group. Details should be explained in the Methods (adults plus jacks) that would have spawned, had citation. there not been removal of natural origin fish for use as hatchery broodstock. Metrics supporting the "Indicators" fields above pHOSij Point estimate for the proportion of fish spawning Single Express these values as numbers from zero to one, with three digits to the right of the decimal point. naturally, including jacks, that are hatchery origin fish. pHOSijLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. pHOSij field. pHOSijUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. pHOSij field. pHOSijAlpha The significance level for the pHOSij confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. pHOSej Point estimate for the proportion of fish spawning Single Express these values as numbers from zero to one, with three digits to the right of the decimal point. naturally, excluding jacks, that are hatchery origin fish. pHOSejLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. pHOSej field. pHOSejUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. pHOSej field. pHOSejAlpha The significance level for the pHOSej confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. NOSJF The point estimate for the natural origin spawners Single Proportion of natural origin spawners that are jacks. Express these values as numbers from zero to one, with three digits to the jack fraction. right of the decimal point. NOSJFLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. NOSJF field. NOSJFUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. NOSJF field.

Coordinated Assessments Data Exchange Standard 20150619 Page 9 of 105 Field Name Field Description Data Type Codes/Conventions for NOSA Table NOSJFAlpha The significance level for the NOSJF confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. HOSJF The point estimate for the hatchery origin Single Proportion of hatchery origin spawners that are jacks. Express these values as numbers from zero to one, with three digits to spawners jack fraction. the right of the decimal point. TSAIJ The point estimate for total spawner abundance, Single Estimated total number of fish contributing to spawning in a particular year. Includes both natural origin and hatchery origin including jacks. returns, and adult and jack age classes. TSAIJLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. TSAIJ field. TSAIJUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. TSAIJ field. TSAIJAlpha The significance level for the TSAIJ confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. TSAEJ The point estimate for total spawner abundance, Single Estimated total number of fish contributing to spawning in a particular year. Includes both natural origin and hatchery origin excluding jacks. returns, for adult age classes excluding jacks. TSAEJLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. TSAEJ field. TSAEJUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. TSAEJ field. TSAEJAlpha The significance level for the TSAEJ confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. Age determination Age2Prop The proportion of natural origin fish that were age Single Values must be between 0 and 1. Express with 3 digits to the right of the decimal point. 2 (brood year +2). 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 Single The associated alpha value is in the AgePropAlpha field, which is found below after the fields for age 11+. Age2Prop field. 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 Single See the Codes/Conventions for the Age2PropLowerLimit field. Age2Prop field. Minimum value = 0.

Coordinated Assessments Data Exchange Standard 20150619 Page 10 of 105 Field Name Field Description Data Type Codes/Conventions for NOSA Table Age3Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 3 (brood year +3). Age3PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age3Prop field. Age3PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age3Prop field. Age4Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 4 (brood year +4). Age4PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age4Prop field. Age4PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age4Prop field. Age5Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 5 (brood year +5). Age5PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age5Prop field. Age5PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age5Prop field. Age6Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 6 (brood year +6). Age6PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age6Prop field. Age6PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age6Prop field. Age7Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 7 (brood year +7). Age7PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age7Prop field. Age7PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age7Prop field. Age8Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 8 (brood year +8). Age8PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age8Prop field. Age8PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age8Prop field. Age9Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 9 (brood year +9). Age9PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age9Prop field. Age9PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age9Prop field. Age10Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 10 (brood year +10). Age10PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age10Prop field. Age10PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age10Prop field.

Coordinated Assessments Data Exchange Standard 20150619 Page 11 of 105 Field Name Field Description Data Type Codes/Conventions for NOSA Table Age11PlusProp The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 11 (brood year +11) or older. Age11PlusPropLowerLi The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. mit Age11PlusProp field. Age11PlusPropUpperLi The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. mit Age11PlusProp field. AgePropAlpha The significance level for the Age_x_Prop Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence intervals, expressed as alpha. Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (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 Memo Give a brief description of changes or adjustments to a standard method if they are NOT described in the methods that are not described in the method citations documentation already provided. If multiple documentation sources are cited, be sure to indicate which method from which above but are important. document was adjusted.

Coordinated Assessments Data Exchange Standard 20150619 Page 12 of 105 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 Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s). MetricLocation Where the supporting metrics are maintained at Memo If online, provide URL(s). the source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used for these calculations. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

A2. SAR Table This table stores information concerning smolt to adult ratios (SAR). 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 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). (unique)  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.

Coordinated Assessments Data Exchange Standard 20150619 Page 13 of 105 Field Name Field Description Data Type Codes/Conventions for SAR Table 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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name. RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls. geographically. See Appendix C for the list of MPGs / strata. PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 14 of 105 Field Name Field Description Data Type Codes/Conventions for SAR Table PopFit Categorization of how well the geographic extent Text 8 Acceptable values: of the SAR estimate corresponds to the  Same [Estimate represents one entire population, the whole population, and nothing but the population.] geographic definition of the population.  Fill in PopID and/or CBFWApopName fields. Leave PopFitNotes and PopAggregation fields blank.  Portion [Estimate represents a portion of one 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 PopAggregation field.)]  Leave PopID and CBFWA and PopFitNotes fields blank. Fill in PopAggregation field. PopFitNotes Text description of how well the SAR value Memo This field is required if the PopFit field is "Portion". Otherwise it must be null. corresponds to the defined population. 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 Memo This field is required if the PopFit field is "Multiple". Otherwise it must be null. populations, enter the names of populations If the record is for multiple populations then fill in this PopAggregation field and leave the PopID and CBFWApopName fields included. 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 Text 255 This may be any of the following: abundance numbers were determined.  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 Text 255 There should be a PTAGIS code for most locations where smolts were trapped. Provide that code, or multiple codes if smolts enumerated. were trapped at multiple locations for this population. AdultLocation The specific location(s) for where the adult Text 255 This may be any of the following: abundance numbers were determined.  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 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 for details. 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: the Text 255 Identify the specific population(s), ESU(s), etc. that apply. Don't enter "ESU" or "MPG" or "Population", but instead the specific population(s); specific ESU/DPS(s); specific ESU(s) or MPG(s) or population(s) represented, such as "Scappoose Creek population" or "All populations above specific MPG(s); etc. represented. Lower Granite Dam" or other appropriate entry. OutmigrationYear The four-digit year for which this SAR is Integer Year in which the fish migrated to the ocean. This is often not the same as brood year. calculated, defined as the year the group migrated to sea. TRTmethod Flag indicating whether the methods used to Text 3 Acceptable values: generate the values in this record are those  Yes [The record reflects the TRT method; it will be submitted to NMFS's SPS database.] defined by the TRT.  No [The record does not reflect the TRT method; it will not be submitted to NMFS's SPS database.]

Coordinated Assessments Data Exchange Standard 20150619 Page 15 of 105 Field Name Field Description Data Type Codes/Conventions for SAR Table ContactAgency Agency, tribe, or other entity, or person 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

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 Single This field holds a numeric value only -- the percent sign is implied but not included. SAR field. 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 Single This field holds a numeric value only -- the percent sign is implied but not included. SAR field. Minimum value = 0. SARAlpha The significance level for the SAR confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha.

Coordinated Assessments Data Exchange Standard 20150619 Page 16 of 105 Field Name Field Description Data Type Codes/Conventions for SAR Table ReturnsMissing This field indicates whether any adult return years Text 3 Acceptable values: for this out-migration year were missing.  Yes [Years were missing.]  No [No years missing; return estimates were complete.] If some years were missing, describe how that gap was addressed under ReturnMissingExplanation ReturnsMissingExplanati If some return data are not accounted for in the Memo Describe how any gap in return years was addressed: Filled in with an interpolated estimate, ignored, etc. on SAR estimate, explain the gap. RearingType The rearing type (origin; production type) of the Text 8 Acceptable values: [Note: Disagreement exists re: is this an "indicator" fish represented by this record.  Natural (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;  Mixed [Known to include both hatchery and natural origin fish] if in key then >1 record/pop/yr is possible. To start we'll have  Unknown [None of the above can be confidently applied] 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 Single This should be the denominator in the ratio calculation, with all previous losses (handling mortality, tag loss estimate, etc.) number of smolts for this outmigration year, or already taken out. The Methods citation should address how this was done. the number of marked smolts used to calculate the SAR. TSOLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. TSO field. TSOUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. TSO field. TSOAlpha The significance level for the TSO confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. TAR Total adult return. Point estimate of the number Single For iteroparous species such as steelhead, include only those adults returning to spawn for the first time. (Failure to do so will of adults returning for the first time from the result in some adults being counted twice for returns purposes.) indicated outmigration year, or the group of marked smolts (as appropriate), to match the outmigrants in the TSO field. TARLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. TAR field. TARUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. TAR field. TARAlpha The significance level for the TAR confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 17 of 105 Field Name Field Description Data Type Codes/Conventions for SAR Table HarvestAdj How was the return adjusted to account for Text 35 Acceptable values: harvest? (Are harvested fish included in the  Ocean [Value in the TAR field was adjusted for harvest in the ocean, but not in the mainstem and not in tributaries.] estimate of number of adults?)  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 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 the smolt group indicated in the TSO field that to adjust the return/recruit estimate to add back harvested fish. were harvested in the ocean. 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 Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies). Provide this estimate the smolt group indicated in the TSO field that ONLY if it was used to adjust the return/recruit estimate to add back harvested fish. were harvested in the mainstem. 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 Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate ONLY if it was used to adjust the the smolt group indicated in the TSO field that return/recruit estimate to add back harvested fish. were harvested in tributaries. 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 Single This value reflects fish taken for hatchery use from the indicated smolt group -- they may be all natural origin, all hatchery returned from the smolt group indicated in the origin, or mixed origin, as indicated by the RearingType field. Details should be explained in the Methods citation. TSO field, had there not been removal of fish for use as hatchery broodstock. Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link.

Coordinated Assessments Data Exchange Standard 20150619 Page 18 of 105 Field Name Field Description Data Type Codes/Conventions for SAR Table ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

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 Memo indicator that were not already captured in other places. Supporting information NullRecord In some years data may not be collected and so a Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s). MetricLocation Where the supporting metrics are maintained at Memo If online, provide URL(s). the source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used for these calculations. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record.

Coordinated Assessments Data Exchange Standard 20150619 Page 19 of 105 Field Name Field Description Data Type Codes/Conventions for SAR Table ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

A3. RperS Table This table stores information concerning recruits per spawner (R/S). Recruit per spawner ratios are specific to the locations 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 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). (unique)  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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Coordinated Assessments Data Exchange Standard 20150619 Page 20 of 105 Field Name Field Description Data Type Codes/Conventions for RperS Table RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls. geographically. See Appendix C for the list of MPGs / strata. PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the recruits per spawner estimate corresponds  Same [Estimate represents one entire population, the whole population, and nothing but the population.] to the geographic definition of 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 Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish spawner value corresponds to the defined for which the recruits per spawner estimate was made. population. SpawnerLocation The specific location(s) for where the spawner Text 255 This may be any of the following: abundance numbers were determined.  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 Text 255 This field describes the location where the abundance of recruits is determined, and may be any of the following: abundance numbers were determined.  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 Integer This field is used to tie juvenile ‘recruits’ or adult returns (over multiple return years) to a specific spawning year. This is the spawner ratio is calculated. Same as "spawning year in which spawning of this species (and run where appropriate) began. year" for the parent generation. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 21 of 105 Field Name Field Description Data Type Codes/Conventions for RperS Table RperStype The type of recruit per spawner estimate, in terms Text 255 Acceptable values: of what fish are included in the estimates of For adult to adult R/S estimates: number of spawners and number of recruits.  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 Text 3 Acceptable values: generate the values in this record are those  Yes [The record reflects the TRT method; it will be submitted to NMFS's SPS database.] defined by the TRT.  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 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

Coordinated Assessments Data Exchange Standard 20150619 Page 22 of 105 Field Name Field Description Data Type Codes/Conventions for RperS Table Indicator RperS The point estimate for the ratio of recruits from Single Required if NullRecord = "No". the designated brood year and RperStype, divided For iteroparous species such as steelhead, adult recruits should include all fish from the brood year that return to spawn, by the number of parent spawners responsible for including repeat spawners, since repeat spawners add to the productivity of the population. that brood year. Straight ratio calculation, not a For juvenile recruits, the total of all of the target life stage from the brood year. For some species and life stages, these may log/natural log transformation. recruit in multiple years. RperSLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. RperS field. RperSUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. RperS field. RperSAlpha The significance level for the RperS confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. Metrics supporting the "Indicator" fields above TotalSpawners Point estimate for the total number of parent Single 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. TotalSpawnersLowerLim The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. it TotalSpawners field. TotalSpawnersUpperLimi The upper limit of the confidence interval for the Single Minimum value = 0. t TotalSpawners field. TotalSpawnersAlpha The significance level for the TotalSpawners Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha. HatcherySpawners Point estimate for the number of parent spawners Single of hatchery origin that contributed to the brood year this record reflects.

This number is the hatchery portion of the TotalSpawners field. HatcherySpawnersLower The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. Limit HatcherySpawners field. HatcherySpawnersUpper The upper limit of the confidence interval for the Single Minimum value = 0. Limit HatcherySpawners field. HatcherySpawnersAlpha The significance level for the HatcherySpawners Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha. Recruits Point estimate for the total number of natural 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 origin recruits from the indicated combination of recruited to the location indicated in the RecruitLocation field. Adult recruits should include all fish from the brood year that species, run, population, spawner location, recruit return to spawn, including repeat spawners, since repeat spawners add to the productivity of the population. location, brood year, and RperStype. RecruitsLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. Recruits field.

Coordinated Assessments Data Exchange Standard 20150619 Page 23 of 105 Field Name Field Description Data Type Codes/Conventions for RperS Table RecruitsUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. Recruits field. RecruitsAlpha The significance level for the Recruits confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. RecruitsMissing This field indicates whether any recruits for this 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 brood year were missing. the RecruitsMissingExplanation field and in the Methods citation.

This field and the next are intended mainly for Acceptable values: adult recruits data. An example where this field  Yes [Years were missing.] may be useful for juvenile fish is if an  No [No years missing; recruit estimates were complete.] outmigration estimate is done only for spring- migrating fish, but it's known that some fish out- If some years were missing, describe how that gap was addressed under RecruitsMissingExplanation. migrate during fall or winter. If such R/S estimates are done, then these fields would be helpful for juveniles also. RecruitsMissingExplanati If some recruits data are not accounted for in the Memo Explain how any gaps in returns from this year class were addressed (estimated to fill in, ignored, etc.). on RperS estimate, explain the gap. HarvestAdj For adult returns, how was the return adjusted to Text 35 Acceptable values: account for harvest?  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 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 the spawner group indicated in the TotalSpawners to adjust the return/recruit estimate to add back harvested fish. field that were harvested in the ocean. 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 Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies) defining the population, the spawner group indicated in the TotalSpawners and including the estuary. Provide this estimate ONLY if it was used to adjust the return/recruit estimate to add back harvested field that were harvested in the mainstem. 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 Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate ONLY if it was used to adjust the the spawner group indicated in the TotalSpawners return/recruit estimate to add back harvested fish. field that were harvested 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 natural origin group. Leave blank for juvenile recruits. NOBroodStockRemoved The number of additional recruits that would have Single Details should be explained in the Methods citation. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 24 of 105 Field Name Field Description Data Type Codes/Conventions for RperS Table Age determination Juvenile Recruits: YOY Total number of juvenile recruits (parr or smolts) Single Number of juvenile recruits (parr or smolts as listed in Type field) prior to forming the first annulus (e.g. ocean type Chinook). that were enumerated prior to forming the first annulus. 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 Single Ages in this table are based on the year spawning occurred, not necessarily the year they hatched, so care must be taken in (brood year +2). 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 Single See the Codes/Conventions column for the Age2Adults field. (brood year +3). Age4Adults Total number of recruits that recruited at age 4 Single See the Codes/Conventions column for the Age2Adults field. (brood year +4). Age5Adults Total number of recruits that recruited at age 5 Single See the Codes/Conventions column for the Age2Adults field. (brood year +5). Age6Adults Total number of recruits that recruited at age 6 Single See the Codes/Conventions column for the Age2Adults field. (brood year +6). Age7Adults Total number of recruits that recruited at age 7 Single See the Codes/Conventions column for the Age2Adults field. (brood year +7). Age8Adults Total number of recruits that recruited at age 8 Single See the Codes/Conventions column for the Age2Adults field. (brood year +8). Age9Adults Total number of recruits that recruited at age 9 Single See the Codes/Conventions column for the Age2Adults field. (brood year +9). Age10Adults Total number of recruits that recruited at age 10 Single See the Codes/Conventions column for the Age2Adults field. (brood year +10). Age11PlusAdults Total number of recruits that recruited at age 11 Single See the Codes/Conventions column for the Age2Adults field. (brood year +11 or more). Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title(s) of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 25 of 105 Field Name Field Description Data Type Codes/Conventions for RperS Table ProtMethURL URL(s) for published protocols and methods Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

Coordinated Assessments Data Exchange Standard 20150619 Page 26 of 105 Field Name Field Description Data Type Codes/Conventions for RperS Table ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

A4. JuvenileOutmigrants Table This 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. (Back to Table of Contents.) Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants 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. 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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwr.noaa.gov/ESA-Salmon-Listings/Salmon-Populations/Maps/Index.cfm. as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Coordinated Assessments Data Exchange Standard 20150619 Page 27 of 105 Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls. Enter geographically. See Appendix B for the list of MPGs / strata. “N/A” if not applicable. PopID Code for the TRT population of fish represented Integer See Appendix B for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. What do we do for places like are defined by NMFS Northwest Region; the codes for these populations are created by StreamNet to reference those NMFS mainstem dams? Answer: we provide guidance populations. 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”. CBFWApopName Population name as defined by CBFWA for Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix C for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the juvenile outmigrants estimate corresponds  Same [Estimate represents one entire population, the whole population, and nothing but the population.] to the geographic definition of 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 Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish outmigrants value corresponds to the defined for which the juvenile outmigrants estimate was made. population. SmoltEqLocation The specific location(s) for where the smolt Text 255 This may be any of the following: equivalent abundance numbers were determined.  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 Integer Juvenile anadromous fishes generally migrate to the ocean in the spring. However, a significant portion of the migration may outmigration of this species occurred. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 28 of 105 Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table ContactAgency Agency, tribe, or other entity, or person 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 29 of 105 Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table Indicators TotalNatural The point estimate, to the location defined in the Single Estimated total number of natural origin fish that outmigrated in a particular year. "Natural origin" means the fish's parents SmoltEqLocation field, of: spawned in the wild. The statistical approach used to generate the estimate should be thoroughly explained in the methods  the number of spring/summer smolt referenced in the MethodDocumentation field. equivalents for o bull trout Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population. o coastal cutthroat trout o coho salmon o east-side spring/summer (stream-type) Chinook salmon, and o steelhead;  the total number of outmigrants of all types for o fall Chinook salmon o lower Columbia spring Chinook salmon o upper Columbia summer Chinook salmon o Willamette spring Chinook salmon;  the number of smolts for o chum salmon o pink salmon. o sockeye salmon. TotalNaturalLowerLimit The lower limit of the confidence interval for the Single TotalNatural field. TotalNaturalUpperLimit The upper limit of the confidence interval for the Single TotalNatural field. TotalNaturalAlpha The significance level for the TotalNatural Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha.

Coordinated Assessments Data Exchange Standard 20150619 Page 30 of 105 Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table Metrics supporting the "Indicators" fields above 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 Single Values must be between 0 and 1. Express with 3 digits to the right of the decimal point. 0 (brood year +0). 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 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 Single The associated alpha value is in the AgePropAlpha field, which is found below after the fields for age 4+. Age0Prop field. Age0PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age0Prop field. Age1Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 1 (brood year +1). Age1PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age1Prop field. Age1PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age2PropLowerLimit field. Age1Prop field. Age2Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age2Prop field. 2 (brood year +2). Age2PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age2Prop field. Age2PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age2Prop field. Age3Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age0Prop field. 3 (brood year +3). Age3PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age3Prop field.

Coordinated Assessments Data Exchange Standard 20150619 Page 31 of 105 Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrants Table Age3PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age3Prop field. Age4PlusProp The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age0Prop field. 4 or higher (brood year +4 or more). Age4PlusPropLowerLimi The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. t Age4PlusProp field. Age4PlusPropUpperLimi The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. t Age4PlusProp field. AgePropAlpha The significance level for the Age_x_Prop Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence intervals, expressed as alpha. Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

Coordinated Assessments Data Exchange Standard 20150619 Page 32 of 105 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 Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. 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 Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo

A5. JuvenileOutmigrantsDetail Table This 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 Text 36 the JuvenileOutmigrants table. Metrics supporting the "Indicators" fields in the JuvenileOutmigrants table Location The specific location (trapping site) where Text 255 This may be any of the following: abundance numbers were determined.  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.

Coordinated Assessments Data Exchange Standard 20150619 Page 33 of 105 Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrantsDetail Table LocPTcode 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.

For For For  Lower Columbia spring Chinook  Fall Chinook  Coho  Willamette spring Chinook  East-side spring/summer (stream- use the following: type) Chinook o Subyearling use the following:  Steelhead o Yearling o Fry o Subyearling use the following: o Yearling o Fry o Parr o Presmolt o Smolt For For The suite of life stages to report are not  Upper Columbia summer Chinook  Chum yet determined for bull trout, coastal  Pink cutthroat trout, and any other species use the following:  Sockeye not explicitly listed here. o Fry o Subyearling use the following: o Smolt TotalNatural The point estimate for the number of natural Single Estimated number of natural origin smolts that outmigrated in a particular year. The statistical approach used to generate the origin fish of the indicated life stage passing the estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field. indicated location. TotalNaturalLowerLimit The lower limit of the confidence interval for the Single TotalNatural field. TotalNaturalUpperLimit The upper limit of the confidence interval for the Single TotalNatural field. TotalNaturalAlpha The significance level for the TotalNatural Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha. SurvivalRate The point estimate for the survival rate of fish Single Express as a proportion from 0 to 1. from the life stage and trapping site indicated by the LifeStage and Location fields of this table to The Location field of this table tells where abundance numbers were determined for a specific trapping site and life stage. The the smolt equivalent estimation site indicated by SmoltEqLocation field of the JuvenileOutmigrants table (this table's parent table) tells the location for which the number of the SmoltEqLocation in the JuvenileOutmigrants smolt equivalents was estimated. In cases where Location=SmoltEqLocation and LifeStage="Smolt", this value will equal "1" table. 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 Single SmolSurvRate field. SurvivialRateUpperLimit The upper limit of the confidence interval for the Single SmolSurvRate field. SurvivalRateAlpha The significance level for the SmoltSurvRate Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha.

Coordinated Assessments Data Exchange Standard 20150619 Page 34 of 105 Field Name Field Description Data Type Codes/Conventions for JuvenileOutmigrantsDetail Table ContactAgency Agency, tribe, or other entity, or person 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Memo that were not already captured in other places. Supporting information JMXID PRODUCTION_ESTIMATE_ID value from the Text 35 This value lets this table refer to the corresponding record in the WDFW/NWIFC Juvenile Migrant Exchange (JMX) and thus JMX system that corresponds to this record. allows for easy access to detailed data for the record. NullRecord In some years data may not be collected and so a Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. MetricLocation Where this supporting metric is maintained at the Memo If online, provide URL(s). source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used to calculate this metric. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record.

Coordinated Assessments Data Exchange Standard 20150619 Page 35 of 105 A6. PresmoltAbundance Table This 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 estimated 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 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). (unique)  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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name. RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls. geographically. See Appendix C for the list of MPGs / strata.

Coordinated Assessments Data Exchange Standard 20150619 Page 36 of 105 Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance Table PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the abundance estimate corresponds to the  Same [Estimate represents one entire population, the whole population, and nothing but the population.] geographic definition of 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 Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish spawner abundance value corresponds to the for which the abundance estimate was made. defined population. WaterBody Name of the body of water associated with the Text 255 This may be any of the following: time series.  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. Integer StartMonth 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 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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

Coordinated Assessments Data Exchange Standard 20150619 Page 37 of 105 Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance Table MethodNumber This field represents the method(s) used to Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

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 Text 255 Acceptable values: Notes to include in the MethodAdjustments field: abundance estimate.  Snorkeling  For mark/recapture estimates include number of reaches  Mark/recapture estimate sampled, total number of reaches, reach lengths, total  Removal estimate survey length/area by habitat type, total length/area  Presmolt tagging with downmigrant trap recapture expanded to by habitat type, and density (by habitat type).  Down-migrant trapping  For presmolt tagging with downmigrant trap recaptures include parr to smolt survival rate & smolt abundance (to (Contact Mike Banach at 503-595-3152 if you need to add to back-calculate summer parr numbers), number of parr this list.) 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 Single Required if NullRecord = "No". abundance. 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 Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. Abundance field. AbundanceUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. Abundance field. AbundanceAlpha The significance level for the Abundance Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 38 of 105 Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance Table Age determination Age0Prop The proportion of natural origin fish that were age Single Values must be between 0 and 1. Express with 3 digits to the right of the decimal point. 0 (brood year +0). 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.

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 Single The associated alpha value is in the AgePropAlpha field, which is found below after the fields for age 4+. Age2Prop field. 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 Single See the Codes/Conventions for the Age0PropLowerLimit field. Age2Prop field. Minimum value = 0. Age1Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age0Prop field. 2 (brood year +1). Age1PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age2Prop field. Age1PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age2Prop field. Age2Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age0Prop field. 2 (brood year +2). Age2PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age2Prop field. Age2PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age2Prop field. Age3Prop The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age0Prop field. 3 (brood year +3). Age3PropLowerLimit The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age3Prop field.

Coordinated Assessments Data Exchange Standard 20150619 Page 39 of 105 Field Name Field Description Data Type Codes/Conventions for PresmoltAbundance Table Age3PropUpperLimit The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. Age3Prop field. Age4PlusProp The proportion of natural origin fish that were age Single See the Codes/Conventions column for the Age0Prop field. 4 or higher (brood year +4 or more). Age4PlusPropLowerLimi The lower limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. t Age4PlusProp field. Age4PlusPropUpperLimi The upper limit of the confidence interval for the Single See the Codes/Conventions for the Age0PropLowerLimit field. t Age4PlusProp field. AgePropAlpha The significance level for the Age_x_Prop Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence intervals, expressed as alpha. Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (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 Memo Be sure to include information specified in the MethodAdjustments field, as appropriate. that are not described in the method citations above but are important. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 40 of 105 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 Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s). MetricLocation Where the supporting metrics are maintained at Memo If online, provide URL(s). the source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used for these calculations. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 41 of 105 Section B: Indicators for Hatchery Programs and Populations of Hatchery Origin Fishes

B1. HatcherySpawning Table This table stores information concerning hatchery spawning. "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 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). (unique)  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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 42 of 105 Field Name Field Description Data Type Codes/Conventions for HatcherySpawning Table RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls geographically.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls geographically. See Appendix C for the list of MPGs / strata. geographically. PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 3 Acceptable values: of the ESU or DPS in which it falls  Yes geographically.  No If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found at https://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 Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the hatchery spawners estimate corresponds to  Same [Estimate represents one entire population, the whole population, and nothing but the population.] the geographic definition of 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 hatchery origin Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish spawner abundance value corresponds to the for which the hatchery spawners estimate was made. defined population. HatcheryProgramName Hatchery program this record describes. Text 255 HatcheryStockName Stock of hatchery fish this record describes. Text 255 Hatchery Name of the hatchery or hatchery complex Text 255 This may be any of the following: associated with the time series.  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 F.

Coordinated Assessments Data Exchange Standard 20150619 Page 43 of 105 Field Name Field Description Data Type Codes/Conventions for HatcherySpawning Table HatcheryProgramType Purpose of the hatchery program this record Text 40 Acceptable values for this field are taken from the "Implementation and Compliance Monitoring" section of Appendix C in represents. 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://old.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 Integer In cases where an unusual population is spawned uncharacteristically early (before January 1 for spring spawners) or late (after species (and run where appropriate) began. 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 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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

Coordinated Assessments Data Exchange Standard 20150619 Page 44 of 105 Field Name Field Description Data Type Codes/Conventions for HatcherySpawning Table MethodNumber This field represents the method(s) used to Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

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. 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 Express these values as numbers from zero to one, with three digits to the right of the decimal point. Single origin fish. pNOBLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. pNOB field. pNOBUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. pNOB field. pNOBAlpha The significance level for the pNOB confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. EggsTaken The total number of eggs taken and fertilized. 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 Long int This value must be a whole number. EggsTaken field. 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 Long int This value must be a whole number. EggsTaken field. Minimum value = 0. EggsTakenAlpha The significance level for the EggsTaken Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". confidence interval, expressed as alpha. Metrics supporting the "Indicators" fields above HOSIJ The number of hatchery origin fish spawned, Single "Hatchery origin" means the fish's parents were spawned in captivity rather than spawning naturally in the wild. including jacks.

Coordinated Assessments Data Exchange Standard 20150619 Page 45 of 105 Field Name Field Description Data Type Codes/Conventions for HatcherySpawning Table HOSEJ The number of hatchery origin fish spawned, Single Includes only "adults" of hatchery origin, excluding jacks. "Hatchery origin" is as defined in the HOSIJ field. excluding jacks. 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, Single This value reflects natural origin fish taken and spawned in the hatchery as part of the year's egg take operations. "Natural including jacks. origin" means the fish's parents spawned in the wild. NOSEJ The number of natural origin fish spawned, Single Includes only "adults" of natural origin, excluding jacks. "Natural origin" is as defined in the NOSIJ field. excluding jacks. 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 Integer Age fields in this table show numbers of fish, not proportions. Values must be whole numbers. were age 2 (brood year +2). 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 Integer See the Codes/Conventions column for the Age2H field. were age 3 (brood year +3). Age4H The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 4 (brood year +4). Age5H The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 5 (brood year +5). Age6H The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 6 (brood year +6). Age7H The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 7 (brood year +7). Age8H The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 8 (brood year +8). Age9H The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were at age 9 (brood year +9). Age10H The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 10 (brood year +10). Age11PlusH The number of spawned hatchery origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 11 (brood year +11) or older. Age2N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 2 (brood year +2). Age3N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 3 (brood year +3).

Coordinated Assessments Data Exchange Standard 20150619 Page 46 of 105 Field Name Field Description Data Type Codes/Conventions for HatcherySpawning Table Age4N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 4 (brood year +4). Age5N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 5 (brood year +5). Age6N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 6 (brood year +6). Age7N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 7 (brood year +7). Age8N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 8 (brood year +8). Age9N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were at age 9 (brood year +9). Age10N The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 10 (brood year +10). Age11PlusN The number of spawned natural origin fish that Integer See the Codes/Conventions column for the Age2H field. were age 11 (brood year +11) or older. Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

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.

Coordinated Assessments Data Exchange Standard 20150619 Page 47 of 105 Field Name Field Description Data Type Codes/Conventions for HatcherySpawning Table Comments about the data Comments Any issues, problems, questions about this Memo indicator that were not already captured in other places. Supporting information NullRecord In some years data may not be collected and so a Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s). MetricLocation Where the supporting metrics are maintained at Memo If online, provide URL(s). the source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used for these calculations. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 48 of 105 B2. PNI Table This 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 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). (unique)  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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. 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. RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls geographically.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls geographically. See Appendix C for the list of MPGs / strata. geographically.

Coordinated Assessments Data Exchange Standard 20150619 Page 49 of 105 Field Name Field Description Data Type Codes/Conventions for PNI Table PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 3 Acceptable values: of the ESU or DPS in which it falls  Yes geographically.  No If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found at https://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 Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the PNI estimate corresponds to the geographic  Same [Estimate represents one entire population, the whole population, and nothing but the population.] definition of 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 PNI value Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish corresponds to the defined population. for which the hatchery spawners estimate was made. HatcheryProgramName Hatchery program this record describes. Text 255 HatcheryStockName Stock of hatchery fish this record describes. Text 255 Hatchery Name of the hatchery or hatchery complex Text 255 This may be any of the following: associated with the time series.  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 Text 3 Acceptable values: represents. is an integrated hatchery / natural  [See notes in HatcherySpawning table above.] production supplementation effort meant to increase the number of natural spawners in the population. SpawningYear The four-digit year in which spawning of this Integer In cases where an unusual population is spawned uncharacteristically early (before January 1 for spring spawners) or late (after species (and run where appropriate) began. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 50 of 105 Field Name Field Description Data Type Codes/Conventions for PNI Table ContactAgency Agency, tribe, or other entity, or person 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

Coordinated Assessments Data Exchange Standard 20150619 Page 51 of 105 Field Name Field Description Data Type Codes/Conventions for PNI Table PNIEJ Proportionate natural influence index, calculated Single Required if the PNIIJ field is null and NullRecord = "No". as 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. pNOB/(pNOB + pHOS) Because jacks are not included in this value, the issue of weighting jack contributions is not applicable to this field. where: pNOB = proportion of hatchery broodstock that Express these values as numbers from zero to one, with three digits to the right of the decimal point. are natural origin fish. pHOS = proportion of fish spawning naturally The only species for which jacks are recognized are Chinook salmon, coho salmon, chum salmon (rarely), and winter steelhead that are hatchery origin fish. (rarely).

Exclude jacks when calculating this value. Metrics supporting the "Indicators" fields above HOSIJH The number of hatchery origin fish spawned in Single "Hatchery origin" means the fish's parents were spawned in captivity rather than spawning naturally in the wild. the hatchery, including jacks. (This is the same value reported in HOSIJ field of the HatcherySpawning table.) NOSIJH The number of natural origin fish spawned in the Single This value reflects natural origin fish taken and spawned in the hatchery as part of the year's egg take operations. "Natural hatchery, including jacks. (This is the same value origin" means the fish's parents spawned in the wild. reported in NOSIJ field of the HatcherySpawning table.) NOSAIJ The point estimate for natural origin spawner Single Estimated number of natural origin spawners contributing to spawning in the wild in a particular year. “Spawners” includes abundance, including jacks, spawning in the wild. jacks. "Natural origin" means the fish's parents spawned in the wild. The statistical approach used to generate the estimate (This is the same value reported in NOSAIJ field should be thoroughly explained in the methods referenced in the MethodDocumentation field. of the NOSA table for the population and year specified for the current record.) 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 Single Estimated number of hatchery origin spawners contributing to spawning in the wild in a particular year. “Spawners” includes abundance, including jacks, spawning in the wild. 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 Single "Hatchery origin" means the fish's parents were spawned in captivity rather than spawning naturally in the wild. the hatchery, excluding jacks. (This is the same value reported in HOSEJ field of the HatcherySpawning table.) NOSEJH The number of natural origin fish spawned in the Single This value reflects natural origin fish taken and spawned in the hatchery as part of the year's egg take operations. "Natural hatchery, excluding jacks. (This is the same value origin" means the fish's parents spawned in the wild. reported in NOSEJ field of the HatcherySpawning table.) NOSAEJ The point estimate for natural origin spawner Single Estimated number of natural origin spawners contributing to spawning in the wild in a particular year. “Spawners” does not abundance, excluding jacks, spawning in the wild. include jacks. "Natural origin" means the fish's parents spawned in the wild. The statistical approach used to generate the (This is the same value reported in NOSAIJ field estimate should be thoroughly explained in the methods referenced in the MethodDocumentation field. of the NOSA table for the population and year specified for the current record.) Provide this estimate ONLY if it represents the whole population -- that is, the estimate is for the whole population.

Coordinated Assessments Data Exchange Standard 20150619 Page 52 of 105 Field Name Field Description Data Type Codes/Conventions for PNI Table HOSAEJ The point estimate for hatchery origin spawner Single Estimated number of hatchery origin spawners contributing to spawning in the wild in a particular year. “Spawners” does not abundance, excluding jacks, spawning in the wild. 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 Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

Coordinated Assessments Data Exchange Standard 20150619 Page 53 of 105 Field Name Field Description Data Type Codes/Conventions for PNI Table 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 Date/Time If an exact date is not known, give an estimate. record was last updated. IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s). MetricLocation Where the supporting metrics are maintained at Memo If online, provide URL(s). the source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used for these calculations. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

B3. EggToRelease Table This table stores information concerning egg to release survival rates for hatchery fish. 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 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). (unique)  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://old.streamnet.org/SpeciesInFW.html for common names.

Coordinated Assessments Data Exchange Standard 20150619 Page 54 of 105 Field Name Field Description Data Type Codes/Conventions for EggToRelease Table 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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. 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. RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls geographically.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls geographically. See Appendix C for the list of MPGs / strata. geographically. PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 3 Acceptable values: of the ESU or DPS in which it falls  Yes geographically.  No If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found at https://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 Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the ETR estimate corresponds to the  Same [Estimate represents one entire population, the whole population, and nothing but the population.] geographic definition of 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 hatchery origin Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish ETR value corresponds to the defined population. for which the ETR estimate was made.

Coordinated Assessments Data Exchange Standard 20150619 Page 55 of 105 Field Name Field Description Data Type Codes/Conventions for EggToRelease Table HatcheryProgramName Hatchery program this record describes. Text 255 HatcheryStockName Stock of hatchery fish this record describes. Text 255 Hatchery Name of the hatchery or hatchery complex Text 255 This may be any of the following: associated with the time series.  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 Integer In cases where an unusual population is spawned uncharacteristically early (before January 1 for spring spawners) or late (after species (and run where appropriate) began. 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 Text 30 Acceptable values: determined.  Unfertilized eggs  Fertilized eggs before eye-up [The number of eggs is shown in the "Eggs"  Eyed eggs field.] ReleaseStage Life stage at which the eggs or fish were released Text 15 This value must be a whole number. into the wild. 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.] ContactAgency Agency, tribe, or other entity, or person 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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

Coordinated Assessments Data Exchange Standard 20150619 Page 56 of 105 Field Name Field Description Data Type Codes/Conventions for EggToRelease Table MethodNumber This field represents the method(s) used to Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

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, Single Required if NullRecord = "No". calculated as 100 X the point estimate of the Express these values as percentages (numbers from zero to one hundred), without a percent sign, with one digit to the right of number of released fish, divided by the point the decimal point. Example: 0.923 = 92.3. estimate of the number of eggs that produced those released fish. 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 Single This field holds a numeric value only -- the percent sign is implied but not included. ETR field. 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 Single This field holds a numeric value only -- the percent sign is implied but not included. ETR field. Minimum value = 0. ETRAlpha The significance level for the ETR confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. Metrics supporting the "Indicator" fields above Eggs The point estimate for the number of eggs that Long int This value must be a whole number. produced the released fish. Do not include culled eggs in the egg count used to calculate this egg-to- release survival rate. EggsLowerLimit The lower limit of the confidence interval for the Long int This value must be a whole number. Eggs field. 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 Long int This value must be a whole number. Eggs field. Minimum value = 0. EggsAlpha The significance level for the Eggs confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. Released The point estimate for the number of eggs planted Long int This value must be a whole number. or fish released.

Coordinated Assessments Data Exchange Standard 20150619 Page 57 of 105 Field Name Field Description Data Type Codes/Conventions for EggToRelease Table ReleasedLowerLimit The lower limit of the confidence interval for the Long int This value must be a whole number. Released field. 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 Long int This value must be a whole number. Released field. Minimum value = 0. ReleasedAlpha The significance level for the Released confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used. This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

Coordinated Assessments Data Exchange Standard 20150619 Page 58 of 105 Field Name Field Description Data Type Codes/Conventions for EggToRelease Table Supporting information NullRecord In some years data may not be collected and so a Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s). MetricLocation Where the supporting metrics are maintained at Memo If online, provide URL(s). the source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used for these calculations. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

B4. SAR_Hatchery Table This table stores information concerning smolt to adult ratios (SAR). 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 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.) (unique)  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.

Coordinated Assessments Data Exchange Standard 20150619 Page 59 of 105 Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery Table 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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. 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. RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls geographically.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls geographically. See Appendix C for the list of MPGs / strata. geographically. PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 3 Acceptable values: of the ESU or DPS in which it falls  Yes geographically.  No If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found at https://www.federalregister.gov/articles/2014/04/14/2014-08347/endangered-and-threatened-wildlife-final-rule-to-revise-the- code-of-federal-regulations-for-species.

Coordinated Assessments Data Exchange Standard 20150619 Page 60 of 105 Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery Table CBFWApopName Population name as defined by CBFWA for Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the hatchery origin SAR estimate corresponds  Same [Estimate represents one entire population, the whole population, and nothing but the population.] to the geographic definition of 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 hatchery origin Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish SAR value corresponds to the defined population. for which the hatchery spawners estimate was made. HatcheryProgramName Hatchery program this record describes. Text 255 HatcheryStockName Stock of hatchery fish this record describes. Text 255 Hatchery Name of the hatchery or hatchery complex Text 255 This may be any of the following: associated with the time series.  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 Text 255 This may be any of the following: released or the abundance was determined.  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 Text 255 There should be a PTAGIS code for most locations where smolts were enumerated. Provide that code, or multiple codes if enumerated. smolts were enumerated at multiple locations for this population. AdultLocation The specific location(s) for where the adult Text 255 This may be any of the following: abundance numbers were determined.  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 Text 255 Follow example 2 fields above counted. SARtype Type of SAR. See Codes/Conventions column 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 for details. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 61 of 105 Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery Table OutmigrationYear The four-digit year for which this SAR is Integer Year in which the fish migrated to the ocean. This is often not the same as brood year. calculated, defined as the year the group migrated to sea. ContactAgency Agency, tribe, or other entity, or person 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

Coordinated Assessments Data Exchange Standard 20150619 Page 62 of 105 Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery Table SARAlpha The significance level for the SAR confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. ReturnsMissing This field indicates whether any adult return years Text 3 Acceptable values: for this out-migration year were missing.  Yes [Years were missing.]  No [No years missing; return estimates were complete.] If some years were missing, describe how that gap was addressed under ReturnMissingExplanation ReturnsMissingExplanati If some return data are not accounted for in the Memo Describe how any gap in return years was addressed: Filled in with an interpolated estimate, ignored, etc. on SAR estimate, explain the gap. Metrics supporting the "Indicator" fields above TSR Total smolts released. Point estimate of the Single This should be the denominator in the ratio calculation, with all previous losses (handling mortality, tag loss estimate, etc.) number of smolts released for this outmigration already taken out. The Methods citation should address how this was done. year, or the number of marked smolts used to calculate the SAR. TSRLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. TSR field. TSRUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. TSR field. TSRAlpha The significance level for the TSR confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. TAR Total adult return. Point estimate of the number Single For iteroparous species such as steelhead, include only those adults returning to spawn for the first time. (Failure to do so will of adults returning for the first time from the result in some adults being counted twice for returns purposes.) 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. TARLowerLimit The lower limit of the confidence interval for the Single Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. TAR field. TARUpperLimit The upper limit of the confidence interval for the Single Minimum value = 0. TAR field. TARAlpha The significance level for the TAR confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. HarvestAdj How was the return adjusted to account for Text 35 Acceptable values: harvest? (Are harvested fish included in the  Ocean [Value in the TAR field was adjusted for harvest in the ocean, but not in the mainstem and not in tributaries.] estimate of number of adults?)  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 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 the smolt group indicated in the TSR field that to adjust the return/recruit estimate to add back harvested fish. were harvested in the ocean. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 63 of 105 Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery Table MainstemHarvest The estimated number of adults and jacks from Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies). Provide this estimate the smolt group indicated in the TSR field that ONLY if it was used to adjust the return/recruit estimate to add back harvested fish. were harvested in the mainstem. 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 Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate ONLY if it was used to adjust the the smolt group indicated in the TSR field that return/recruit estimate to add back harvested fish. were harvested in tributaries. 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 Memo Provide title of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol. provide a new link. ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

Coordinated Assessments Data Exchange Standard 20150619 Page 64 of 105 Field Name Field Description Data Type Codes/Conventions for SAR_Hatchery Table Supporting information NullRecord In some years data may not be collected and so a Text 3 Normally "No". value cannot be calculated. For example, high 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 muddy water or wildfires can prevent redd counts. time period specified. This field is used to indicate that a record does not exist because the data do not exist to calculate it. 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 Date/Time If an exact date is not known, give an estimate. record was last updated. IndicatorLocation Where this indicator is maintained at the source. Memo If online, provide URL(s). MetricLocation Where the supporting metrics are maintained at Memo If online, provide URL(s). the source. MeasureLocation Where the measurements are maintained that were Memo If online, provide URL(s). used for these calculations. ContactPersonFirst First name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPersonLast Last name of person who is the best contact for Text 30 questions that may arise about this data record. ContactPhone Phone number of person who is the best contact Text 30 for questions that may arise about this data record. ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

B5. RperS_Hatchery Table This table stores information concerning recruits per spawner (R/S) for hatchery origin fish. 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 record ID Value used by computer to identify a record. Text 36 This value is a globally unique identifier (GUID). (unique)  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.

Coordinated Assessments Data Exchange Standard 20150619 Page 65 of 105 Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table 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://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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. as defined by NMFS Northwest Region or by USFWS in which the population falls Many hatchery populations are not part of an ESU. In such cases leave this field blank. geographically. For non-listed populations this is the DPS or other name. RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list. Many hatchery populations are not part of a recovery domain. In such cases leave this field blank. falls geographically.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls geographically. See Appendix C for the list of MPGs / strata. geographically. PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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 Text 3 Acceptable values: of the ESU or DPS in which it falls  Yes geographically.  No If you are unsure about a particular hatchery stock's inclusion in an ESU/DPS, information can be found at https://www.federalregister.gov/articles/2014/04/14/2014-08347/endangered-and-threatened-wildlife-final-rule-to-revise-the- code-of-federal-regulations-for-species.

Coordinated Assessments Data Exchange Standard 20150619 Page 66 of 105 Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table CBFWApopName Population name as defined by CBFWA for Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 Text 8 Acceptable values: of the recruits per spawner estimate corresponds  Same [Estimate represents one entire population, the whole population, and nothing but the population.] to the geographic definition of 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 Memo If the PopFit field is "Portion" or "Multiple", describe the lack of correspondence between the defined population and the fish spawner value corresponds to the defined for which the recruits per spawner estimate was made. population. HatcheryProgramName Hatchery program this record describes. Text 255 HatcheryStockName Stock of hatchery fish this record describes. Text 255 Hatchery Name of the hatchery or hatchery complex Text 255 This may be any of the following: associated with the time series.  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. ReleaseLocation The specific location(s) for where the fish were Text 255 This may be any of the following: released.  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 Text 255 This field describes the location where the abundance of recruits is determined, and may be any of the following: abundance numbers were determined.  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 Integer This field is used to tie juvenile ‘recruits’ or adult returns (over multiple return years) to a specific spawning year. This is the spawner ratio is calculated. Same as "spawning year in which spawning of this species (and run where appropriate) began. year" for the parent generation. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 67 of 105 Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table RperStype The type of recruit per spawner estimate, in terms Text 255 Juvenile recruits are not included in this table. Acceptable values: of what fish are included in the estimates of  Total recruits per total spawners [Includes males and jacksI number of spawners and number of recruits.  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 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 responsible for these data that is the best contact is not found here, contact your agency StreamNet representative, or call PSMFC's StreamNet staff at 503-595-3100. for questions that may arise about this data record.  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 Byte This field, along with the "ContactAgency" field above, identifies which entity calculated the values in the record and which calculate the values in the "Indicators" and (set of) methods where used to calculate them. These fields allow for multiple entries for the same population and year. Thus, "Metrics" sections. it is possible to share values that are based on different assumptions.

Coordinated Assessments Data Exchange Standard 20150619 Page 68 of 105 Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table 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 Long int Adult recruits should include all fish from the brood year that return to the recruit location, including repeat spawners, since from the indicated combination of species, run, repeat spawners add to the productivity of the population. population, hatchery program, release location, recruit location, brood year, and RperStype. RecruitsLowerLimit The lower limit of the confidence interval for the Long int Minimum value = 0. If the calculated lower limit of the confidence interval is less than zero then report 0 in this field. Recruits field. RecruitsUpperLimit The upper limit of the confidence interval for the Long int Minimum value = 0. Recruits field. RecruitsAlpha The significance level for the Recruits confidence Single Express these values as alpha values. For example, for the 95% confidence limits enter "0.05" in this field, not "95". interval, expressed as alpha. RecruitsMissing This field indicates whether any recruits for this 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 brood year were missing. 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. RecruitsMissingExplanati If some recruits data are not accounted for in the Memo Explain how any gaps in returns from this year class were addressed (estimated to fill in, ignored, etc.). on RperS estimate, explain the gap. HarvestAdj For adult returns, how was the return adjusted to Text 35 Acceptable values: account for harvest?  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 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 the spawner group indicated in the to adjust the return/recruit estimate to add back harvested fish. NumberSpawned field that were harvested in the ocean. 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 Single This field is only for harvests in the mainstem, which is defined as all rivers below the tributary(ies) defining the population, in the spawner group indicated in the including the estuary. Provide this estimate regardless of whether the number of recruits was adjusted for mainstem harvest. NumberSpawned field that were harvested in the mainstem. 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 Single "Tributaries" is defined as the tributary(ies) the population resides in. Provide this estimate regardless of whether the number the spawner group indicated in the of recruits was adjusted for the harvest in tributaries. NumberSpawned field that were harvested in This may or may not include indirect fishery impacts, and these details should be explained in the Methods citation. This tributaries. harvest value reflects fish harvested from the indicated release group.

Coordinated Assessments Data Exchange Standard 20150619 Page 69 of 105 Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table Age determination Age2Adults Total number of recruits that recruited at age 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 (brood year +2). 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 Single See the Codes/Conventions column for the Age2Adults field. (brood year +3). Age4Adults Total number of recruits that recruited at age 4 Single See the Codes/Conventions column for the Age2Adults field. (brood year +4). Age5Adults Total number of recruits that recruited at age 5 Single See the Codes/Conventions column for the Age2Adults field. (brood year +5). Age6Adults Total number of recruits that recruited at age 6 Single See the Codes/Conventions column for the Age2Adults field. (brood year +6). Age7Adults Total number of recruits that recruited at age 7 Single See the Codes/Conventions column for the Age2Adults field. (brood year +7). Age8Adults Total number of recruits that recruited at age 8 Single See the Codes/Conventions column for the Age2Adults field. (brood year +8). Age9Adults Total number of recruits that recruited at age 9 Single See the Codes/Conventions column for the Age2Adults field. (brood year +9). Age10Adults Total number of recruits that recruited at age 10 Single See the Codes/Conventions column for the Age2Adults field. (brood year +10). Age11PlusAdults Total number of recruits that recruited at age 11 Single See the Codes/Conventions column for the Age2Adults field. (brood year +11 or more). Protocol and method documentation ProtMethName The name(s) of all protocols and associated data Memo Provide title(s) of protocol and name(s) of relevant methods used. collection and data analysis methods used to calculate the indicator estimate. 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 Memo Provide URL(s) to source documentation of methodology. For MonitoringMethods.org provide link to the protocol. Methods describing the methodology and documenting the documentation should include survey design, description of field methodology and analytical approach. URL links may be to derivation of the indicator. If published in online methods documentation resources like MonitoringMethods.org, other online resources, or online literature. MonitoringMethods.org, this link will provide access to study design information and all If methodology is unchanged from a previous year, use the previous link references. If methodology changed for this estimate, methods associated with the protocol provide a new link.

Coordinated Assessments Data Exchange Standard 20150619 Page 70 of 105 Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table ProtMethDocumentation Citation or documentation that describes the Memo Provide a citation(s) to documentation of the methodology used, This may be in the form of reports, journal articles, or other protocol and/or method(s) listed in the publications that describe the study design (including spatial, temporal, response and inference designs), variations from ProtMethName field. Include references not routine step by step procedures or design criteria, description of field methodology and analytical approach. If the documented in MonitoringMethods.org, such as methodology is not yet published, either insert here, or describe in a separate document and make it available online (provide reports, journal articles or other publications that the URL). Leave this field blank if methodology is described in MonitoringMethods.org. describe the survey design, field methodology and analytical approach used to derive the indicator Note: If there is no link to a cited document online, provide a copy of the document to the StreamNet Library estimate. (streamnetlibrary.org). The library will scan the document and provide a URL. Post the URL in the ProtMethURL field.

Coordinated Assessments Data Exchange Standard 20150619 Page 71 of 105 Field Name Field Description Data Type Codes/Conventions for RperS_Hatchery Table ContactEmail Email address of person who is the best contact Text 50 for questions that may arise about this data record. MetaComments Comments regarding the supporting information. Memo Fields 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 72 of 105 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 Fields needed by people programming the Exchange Network SubmitAgency Initials or acronym for the agency, tribe, or other 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 entity, or name of person, that sent this record of individual. Here are the ones most likely needed. If yours is not found here, contact your agency StreamNet representative, or data to the exchange network node at StreamNet. call PSMFC's StreamNet staff at 503-595-3100.  CRITFC = Columbia River Inter-Tribal Fish Commission Note that it is possible for one entity to share data  CCT = Colville Confederated Tribes with another, and that second entity sends the  YIN = Confederated Tribes and Bands of the Yakama Indian Nation record to the exchange network node. For  CTUIR = Confederated Tribes of the Umatilla Indian Reservation example, the Shoshone-Bannock Tribes may send  CTWSIR = Confederated Tribes of the Warm Springs Reservation of Oregon data to IDFG, who in turn sends those data to the  IDFG = Idaho Department of Fish and Game exchange network. In such a case the Sho-Ban  NPT = Nez Perce Tribe Tribes would be identified as the contact agency  ODFW = Oregon Department of Fish and Wildlife for the data, but the "SubmitAgency" would be 1 IDFG.  STOI = Spokane Tribe of Indians  WDFW = Washington Department of Fish and Wildlife RefID The unique StreamNet reference ID number that Long int Pre-Data Exchange - 0 - 1,000 identifies the source document or database from WDFW = 10,000-19,999; 100,000-199,999 which the record was obtained. CRITFC = 20,000-29,999; 200,000-299,999 USFWS = 30,000-39,999; 300,000-399,999 IDFG = 40,000-49,999; 400,000-499,999 ODFW = 50,000-59,999; 500,000-599,999 PSMFC = 60,000-69,999; 600,000-699,999 MFWP = 70,000-89,999; 700,000-799,999 CDFG = 90,000-99,999; 800,000-899,999 UpdDate The date and time that the record was created or Datetime This can be the time a record was created, the last time it was edited, or the last time it was QCd. 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. DataEntry Compiler's name. Text 50 The name of the person who entered the record. DataEntryNotes Notes about this record by the compiler identified Memo Notes for the compiler to reference field office, contact, or any other information. in the "DataEntry" field.

Coordinated Assessments Data Exchange Standard 20150619 Page 73 of 105 Field Name Field Description Data Type Codes/Conventions CompilerRecordID Agency record ID maintained by the data 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 submitter. Coordinated Assessments exchange network and an internal system such as ODFW's Salmon Tracker. Publish Yes/no value indicating whether this record Text 3 Acceptable values: should be shared freely with all public users via  Yes [Record will be shared with public via Exchange Network.] the Exchange Network. If "No" then the record  No [Record will not be shared with public via Exchange Network.] can only be accessed by using the apikey that 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" created it. 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.

Coordinated Assessments Data Exchange Standard 20150619 Page 74 of 105 Appendix B. Glossary

Terms in this list are defined in the following way in this document. ... For later inclusion ...

Coordinated Assessments Data Exchange Standard 20150619 Page 75 of 105 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.

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/.

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 ] Population Recovery Domain 2  Species o Etc.

Interior Columbia Recovery Domain  Chinook salmon o Salmon, Chinook (Snake River fall-run ESU) . Snake River MPG  [ 1 ] Salmon, Chinook (Snake River fall-run ESU) Snake River Lower Mainstem - fall . Unassigned (above Hells Canyon Dam) MPG  [ 391 ] Salmon, Chinook (Snake River fall-run ESU) Marsing Reach - fall

Coordinated Assessments Data Exchange Standard 20150619 Page 76 of 105  [ 392 ] Salmon, Chinook (Snake River fall-run ESU) Salmon Falls - fall o Salmon, Chinook (Snake River spring/summer-run ESU) . Dry Clearwater MPG  [ 2 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lapwai/Big Canyon Creeks - unknown  [ 3 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lawyer Creek - unknown  [ 4 ] Salmon, Chinook (Snake River spring/summer-run ESU) Potlatch River - unknown  [ 5 ] Salmon, Chinook (Snake River spring/summer-run ESU) South Fork Clearwater River Upper Mainstem - unknown . Grande Ronde / Imnaha MPG  [ 6 ] Salmon, Chinook (Snake River spring/summer-run ESU) Big Sheep Creek - spring  [ 7 ] Salmon, Chinook (Snake River spring/summer-run ESU) Catherine Creek - spring  [ 8 ] Salmon, Chinook (Snake River spring/summer-run ESU) Grande Ronde River Upper Mainstem - spring  [ 9 ] Salmon, Chinook (Snake River spring/summer-run ESU) Imnaha River Mainstem - spring/summer  [ 10 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lookingglass Creek - unknown  [ 12 ] Salmon, Chinook (Snake River spring/summer-run ESU) Minam River - spring  [ 11 ] Salmon, Chinook (Snake River spring/summer-run ESU) Wallowa/Lostine Rivers - spring  [ 13 ] Salmon, Chinook (Snake River spring/summer-run ESU) Wenaha River - spring . Lower Snake MPG  [ 14 ] Salmon, Chinook (Snake River spring/summer-run ESU) Asotin Creek - spring  [ 15 ] Salmon, Chinook (Snake River spring/summer-run ESU) Tucannon River - spring . Middle Fork Salmon River MPG  [ 16 ] Salmon, Chinook (Snake River spring/summer-run ESU) Bear Valley Creek - spring  [ 17 ] Salmon, Chinook (Snake River spring/summer-run ESU) Big Creek - spring/summer  [ 18 ] Salmon, Chinook (Snake River spring/summer-run ESU) Camas Creek - spring/summer  [ 19 ] Salmon, Chinook (Snake River spring/summer-run ESU) Chamberlain Creek - spring  [ 20 ] Salmon, Chinook (Snake River spring/summer-run ESU) Loon Creek - spring/summer  [ 21 ] Salmon, Chinook (Snake River spring/summer-run ESU) Marsh Creek - spring  [ 22 ] Salmon, Chinook (Snake River spring/summer-run ESU) Middle Fork Salmon River Lower Mainstem - spring/summer  [ 23 ] Salmon, Chinook (Snake River spring/summer-run ESU) Middle Fork Salmon River Upper Mainstem - spring  [ 24 ] Salmon, Chinook (Snake River spring/summer-run ESU) Sulphur Creek - spring

Coordinated Assessments Data Exchange Standard 20150619 Page 77 of 105 . South Fork Salmon River MPG  [ 25 ] Salmon, Chinook (Snake River spring/summer-run ESU) East Fork South Fork Salmon River - summer  [ 26 ] Salmon, Chinook (Snake River spring/summer-run ESU) Little Salmon River - spring/summer  [ 27 ] Salmon, Chinook (Snake River spring/summer-run ESU) Secesh River - summer  [ 28 ] Salmon, Chinook (Snake River spring/summer-run ESU) South Fork Salmon River - summer . Upper Salmon River MPG  [ 29 ] Salmon, Chinook (Snake River spring/summer-run ESU) East Fork Salmon River - spring/summer  [ 30 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lemhi River - spring  [ 31 ] Salmon, Chinook (Snake River spring/summer-run ESU) North Fork Salmon River - spring  [ 32 ] Salmon, Chinook (Snake River spring/summer-run ESU) Pahsimeroi River - summer  [ 33 ] Salmon, Chinook (Snake River spring/summer-run ESU) Panther Creek - unknown  [ 34 ] Salmon, Chinook (Snake River spring/summer-run ESU) Salmon River Lower Mainstem - spring/summer  [ 35 ] Salmon, Chinook (Snake River spring/summer-run ESU) Salmon River Upper Mainstem - spring  [ 36 ] Salmon, Chinook (Snake River spring/summer-run ESU) Valley Creek - spring/summer  [ 37 ] Salmon, Chinook (Snake River spring/summer-run ESU) Yankee Fork - spring . Wet Clearwater MPG  [ 38 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lochsa River - unknown  [ 39 ] Salmon, Chinook (Snake River spring/summer-run ESU) Lolo Creek - unknown  [ 41 ] Salmon, Chinook (Snake River spring/summer-run ESU) Meadow Creek - unknown  [ 42 ] Salmon, Chinook (Snake River spring/summer-run ESU) Moose Creek - unknown  [ 40 ] Salmon, Chinook (Snake River spring/summer-run ESU) North Fork Clearwater River Lower Mainstem - unknown  [ 43 ] Salmon, Chinook (Snake River spring/summer-run ESU) North Fork Clearwater River Upper Mainstem - unknown  [ 44 ] Salmon, 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

Coordinated Assessments Data Exchange Standard 20150619 Page 78 of 105  [ 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 o Salmon, Chinook (Upper Columbia River spring-run ESU) . North Cascades MPG  [ 45 ] Salmon, Chinook (Upper Columbia River spring-run ESU) Entiat River - spring  [ 46 ] Salmon, 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 ] Salmon, 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

Coordinated Assessments Data Exchange Standard 20150619 Page 79 of 105 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]  Sockeye o Salmon, sockeye (Snake River ESU) . Sawtooth Valley MPG  [ 51 ] Salmon, sockeye (Snake River ESU) Alturas Lake - summer  [ 52 ] Salmon, sockeye (Snake River ESU) Hell Roaring Lake - summer  [ 53 ] Salmon, sockeye (Snake River ESU) Pettit Lake - summer  [ 54 ] Salmon, sockeye (Snake River ESU) Redfish Lake - summer  [ 55 ] Salmon, sockeye (Snake River ESU) Stanley Lake - summer  [ 56 ] Salmon, sockeye (Snake River ESU) Yellow Belly Lake - summer  Steelhead o Steelhead (Middle Columbia River DPS) . Cascades Eastern Slope Tributaries MPG  [ 57 ] Steelhead (Middle Columbia River DPS) Crooked River - summer  [ 58 ] Steelhead (Middle Columbia River DPS) Deschutes River Eastside - summer  [ 59 ] Steelhead (Middle Columbia River DPS) Deschutes River Westside - summer  [ 60 ] Steelhead (Middle Columbia River DPS) Fifteenmile Creek - winter  [ 61 ] Steelhead (Middle Columbia River DPS) Klickitat River - summer and winter  [ 62 ] Steelhead (Middle Columbia River DPS) Rock Creek - summer  [ 63 ] Steelhead (Middle Columbia River DPS) White Salmon River - summer . John Day River MPG  [ 64 ] Steelhead (Middle Columbia River DPS) John Day River Lower Mainstem Tributaries - summer  [ 65 ] Steelhead (Middle Columbia River DPS) John Day River Upper Mainstem - summer  [ 66 ] Steelhead (Middle Columbia River DPS) Middle Fork John Day River - summer  [ 67 ] Steelhead (Middle Columbia River DPS) North Fork John Day River - summer  [ 68 ] Steelhead (Middle Columbia River DPS) South Fork John Day River - summer . Umatilla And Walla Walla River MPG  [ 69 ] Steelhead (Middle Columbia River DPS) Touchet River - summer  [ 70 ] Steelhead (Middle Columbia River DPS) Umatilla River - summer

Coordinated Assessments Data Exchange Standard 20150619 Page 80 of 105  [ 71 ] Steelhead (Middle Columbia River DPS) Walla Walla River - summer  [ 72 ] Steelhead (Middle Columbia River DPS) Willow Creek - summer . Yakima River MPG  [ 73 ] Steelhead (Middle Columbia River DPS) Naches River - summer  [ 74 ] Steelhead (Middle Columbia River DPS) Satus Creek - summer  [ 75 ] Steelhead (Middle Columbia River DPS) Toppenish Creek - summer  [ 76 ] Steelhead (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 Steelhead (Snake River Basin DPS) . Clearwater River MPG  [ 77 ] Steelhead (Snake River Basin DPS) Clearwater River Lower Mainstem - summer  [ 78 ] Steelhead (Snake River Basin DPS) Lochsa River - summer  [ 79 ] Steelhead (Snake River Basin DPS) Lolo Creek - summer  [ 80 ] Steelhead (Snake River Basin DPS) North Fork Clearwater River - summer  [ 81 ] Steelhead (Snake River Basin DPS) Selway River - summer  [ 82 ] Steelhead (Snake River Basin DPS) South Fork Clearwater River - summer . Grande Ronde River MPG  [ 83 ] Steelhead (Snake River Basin DPS) Grande Ronde River Lower Mainstem - summer  [ 84 ] Steelhead (Snake River Basin DPS) Grande Ronde River Upper Mainstem - summer  [ 85 ] Steelhead (Snake River Basin DPS) Joseph Creek - summer  [ 86 ] Steelhead (Snake River Basin DPS) Wallowa River - summer . Hells Canyon MPG  [ 87 ] Steelhead (Snake River Basin DPS) Hells Canyon - summer . Imnaha River MPG  [ 89 ] Steelhead (Snake River Basin DPS) Imnaha River - summer . Lower Snake MPG  [ 90 ] Steelhead (Snake River Basin DPS) Asotin Creek - summer  [ 91 ] Steelhead (Snake River Basin DPS) Tucannon River - summer . Salmon River MPG  [ 93 ] Steelhead (Snake River Basin DPS) Chamberlain Creek - summer

Coordinated Assessments Data Exchange Standard 20150619 Page 81 of 105  [ 94 ] Steelhead (Snake River Basin DPS) East Fork Salmon River - summer  [ 95 ] Steelhead (Snake River Basin DPS) Lemhi River - summer  [ 96 ] Steelhead (Snake River Basin DPS) Little Salmon River - summer  [ 92 ] Steelhead (Snake River Basin DPS) Middle Fork Salmon River Lower Mainstem - summer  [ 97 ] Steelhead (Snake River Basin DPS) Middle Fork Salmon River Upper Mainstem - summer  [ 98 ] Steelhead (Snake River Basin DPS) North Fork Salmon River - summer  [ 99 ] Steelhead (Snake River Basin DPS) Pahsimeroi River - summer  [ 100 ] Steelhead (Snake River Basin DPS) Panther Creek - summer  [ 101 ] Steelhead (Snake River Basin DPS) Salmon River Upper Mainstem - summer  [ 102 ] Steelhead (Snake River Basin DPS) Secesh River - summer  [ 103 ] Steelhead (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 Steelhead (Upper Columbia River DPS) . North Cascades MPG  [ 104 ] Steelhead (Upper Columbia River DPS) Crab Creek - summer  [ 105 ] Steelhead (Upper Columbia River DPS) Entiat River - summer  [ 106 ] Steelhead (Upper Columbia River DPS) Methow River - summer

Coordinated Assessments Data Exchange Standard 20150619 Page 82 of 105  [ 107 ] Steelhead (Upper Columbia River DPS) Okanogan River - summer  [ 108 ] Steelhead (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 Salmon, coho (Oregon Coast ESU) . Lakes MPG  [ 109 ] Salmon, coho (Oregon Coast ESU) Siltcoos Lake - fall  [ 110 ] Salmon, coho (Oregon Coast ESU) Sutton Lake/Mercer Lake - fall  [ 111 ] Salmon, coho (Oregon Coast ESU) Tahkenitch Lake - fall  [ 112 ] Salmon, coho (Oregon Coast ESU) Tenmile Lake - fall . Mid-Coast MPG  [ 113 ] Salmon, coho (Oregon Coast ESU) Alsea River - fall  [ 114 ] Salmon, coho (Oregon Coast ESU) Beaver Creek - fall  [ 115 ] Salmon, coho (Oregon Coast ESU) Berry Creek - fall  [ 116 ] Salmon, coho (Oregon Coast ESU) Big (near Alsea) Creek - fall  [ 117 ] Salmon, coho (Oregon Coast ESU) Big (near Siuslaw) Creek - fall  [ 118 ] Salmon, coho (Oregon Coast ESU) Big (near Yaquina) Creek - fall  [ 119 ] Salmon, coho (Oregon Coast ESU) Bob Creek - fall  [ 120 ] Salmon, coho (Oregon Coast ESU) Cape Creek - fall  [ 121 ] Salmon, coho (Oregon Coast ESU) China Creek - fall  [ 122 ] Salmon, coho (Oregon Coast ESU) Coal Creek - fall  [ 123 ] Salmon, coho (Oregon Coast ESU) Cummins Creek - fall  [ 124 ] Salmon, coho (Oregon Coast ESU) Depoe Bay Creek - fall

Coordinated Assessments Data Exchange Standard 20150619 Page 83 of 105  [ 125 ] Salmon, coho (Oregon Coast ESU) Devils Lake - fall  [ 126 ] Salmon, coho (Oregon Coast ESU) Fogarty Creek - fall  [ 127 ] Salmon, coho (Oregon Coast ESU) Moolack Creek - fall  [ 128 ] Salmon, coho (Oregon Coast ESU) Rock Creek - fall  [ 129 ] Salmon, coho (Oregon Coast ESU) Rocky Creek - fall  [ 130 ] Salmon, coho (Oregon Coast ESU) Salmon River - fall  [ 131 ] Salmon, coho (Oregon Coast ESU) Schoolhouse Creek - fall  [ 132 ] Salmon, coho (Oregon Coast ESU) Siletz River - fall  [ 133 ] Salmon, coho (Oregon Coast ESU) Siuslaw River - fall  [ 134 ] Salmon, coho (Oregon Coast ESU) Spencer Creek - fall  [ 135 ] Salmon, coho (Oregon Coast ESU) Tenmile Creek - fall  [ 136 ] Salmon, coho (Oregon Coast ESU) Thiel Creek - fall  [ 137 ] Salmon, coho (Oregon Coast ESU) Vingie Creek - fall  [ 138 ] Salmon, coho (Oregon Coast ESU) Wade Creek - fall  [ 139 ] Salmon, coho (Oregon Coast ESU) Yachats River - fall  [ 140 ] Salmon, coho (Oregon Coast ESU) Yaquina River - fall . Mid-South Coast MPG  [ 141 ] Salmon, coho (Oregon Coast ESU) Coos River - fall  [ 142 ] Salmon, coho (Oregon Coast ESU) Coquille River - fall  [ 143 ] Salmon, coho (Oregon Coast ESU) Floras Creek/New River - fall  [ 144 ] Salmon, coho (Oregon Coast ESU) Johnson Creek - fall  [ 145 ] Salmon, coho (Oregon Coast ESU) Sixes River - fall  [ 146 ] Salmon, coho (Oregon Coast ESU) Threemile Creek - fall  [ 147 ] Salmon, coho (Oregon Coast ESU) Twomile Creek - fall . North Coast MPG  [ 148 ] Salmon, coho (Oregon Coast ESU) Arch Cape Creek - fall  [ 149 ] Salmon, coho (Oregon Coast ESU) Ecola Creek - fall  [ 150 ] Salmon, coho (Oregon Coast ESU) Necanicum River - fall  [ 151 ] Salmon, coho (Oregon Coast ESU) Nehalem River - fall  [ 152 ] Salmon, coho (Oregon Coast ESU) Neskowin Creek - fall  [ 153 ] Salmon, coho (Oregon Coast ESU) Nestucca River - fall

Coordinated Assessments Data Exchange Standard 20150619 Page 84 of 105  [ 154 ] Salmon, coho (Oregon Coast ESU) Netarts Bay - fall  [ 155 ] Salmon, coho (Oregon Coast ESU) Rover Creek - fall  [ 156 ] Salmon, coho (Oregon Coast ESU) Sand Creek - fall  [ 157 ] Salmon, coho (Oregon Coast ESU) Short Sand Creek - fall  [ 158 ] Salmon, coho (Oregon Coast ESU) Spring Creek - fall  [ 159 ] Salmon, coho (Oregon Coast ESU) Tillamook Bay - fall  [ 160 ] Salmon, coho (Oregon Coast ESU) Watseco Creek - fall . Umpqua MPG  [ 161 ] Salmon, coho (Oregon Coast ESU) Lower Umpqua River - fall  [ 162 ] Salmon, coho (Oregon Coast ESU) Middle Umpqua River - fall  [ 163 ] Salmon, coho (Oregon Coast ESU) North Umpqua River - fall  [ 164 ] Salmon, coho (Oregon Coast ESU) South Umpqua River - fall

Puget Sound Recovery Domain Geographic Regions and MPGs  Chinook salmon o Salmon, Chinook (Puget Sound ESU) . Puget Sound Central East MPG  [ 165 ] Salmon, Chinook (Puget Sound ESU) Cascade River - spring  [ 166 ] Salmon, Chinook (Puget Sound ESU) Lower Sauk River - summer  [ 167 ] Salmon, Chinook (Puget Sound ESU) Lower Skagit River - fall  [ 168 ] Salmon, Chinook (Puget Sound ESU) North Fork Stillaguamish River - summer  [ 169 ] Salmon, Chinook (Puget Sound ESU) Skykomish River - summer  [ 170 ] Salmon, Chinook (Puget Sound ESU) Snoqualmie River - fall  [ 171 ] Salmon, Chinook (Puget Sound ESU) South Fork Stillaguamish River - fall  [ 172 ] Salmon, Chinook (Puget Sound ESU) Suiattle River - spring  [ 173 ] Salmon, Chinook (Puget Sound ESU) Upper Sauk River - spring  [ 174 ] Salmon, Chinook (Puget Sound ESU) Upper Skagit River - summer . Puget Sound Central West MPG  [ 175 ] Salmon, Chinook (Puget Sound ESU) Mid-Hood Canal - fall  [ 176 ] Salmon, Chinook (Puget Sound ESU) Skokomish River - fall

Coordinated Assessments Data Exchange Standard 20150619 Page 85 of 105 . Puget Sound North East MPG  [ 177 ] Salmon, Chinook (Puget Sound ESU) North Fork Nooksack River - spring  [ 178 ] Salmon, Chinook (Puget Sound ESU) South Fork Nooksack River - spring . Puget Sound North West MPG  [ 179 ] Salmon, Chinook (Puget Sound ESU) Dungeness River - summer  [ 180 ] Salmon, Chinook (Puget Sound ESU) Elwha River - fall . Puget Sound South MPG  [ 181 ] Salmon, Chinook (Puget Sound ESU) Cedar River - fall  [ 182 ] Salmon, Chinook (Puget Sound ESU) Green River - fall  [ 183 ] Salmon, Chinook (Puget Sound ESU) Nisqually River - fall  [ 184 ] Salmon, Chinook (Puget Sound ESU) Puyallup River - fall  [ 185 ] Salmon, Chinook (Puget Sound ESU) Sammamish River - fall  [ 186 ] Salmon, Chinook (Puget Sound ESU) White River - spring  Chum salmon o Salmon, chum (Hood Canal summer-run ESU) . Hood Canal MPG  [ 187 ] Salmon, chum (Hood Canal summer-run ESU) Hood Canal - summer  [ 188 ] Salmon, chum (Hood Canal summer-run ESU) Strait of Juan de Fuca - summer  Sockeye salmon o Salmon, sockeye (Ozette Lake ESU) . Ozette Lake MPG  [ 194 ] Salmon, sockeye (Ozette Lake ESU) Ozette Lake - summer  Steelhead o Steelhead (Puget Sound DPS) . Central and South Puget Sound MPG  [ 332 ] Steelhead (Puget Sound DPS) Cedar River - winter  [ 335 ] Steelhead (Puget Sound DPS) East Kitsap Peninsula Tributaries - winter  [ 198 ] Steelhead (Puget Sound DPS) Green River - winter  [ 200 ] Steelhead (Puget Sound DPS) Nisqually River - winter  [ 338 ] Steelhead (Puget Sound DPS) North Lake Washington and Lake Sammamish - winter  [ 203 ] Steelhead (Puget Sound DPS) Puyallup River/Carbon River - winter

Coordinated Assessments Data Exchange Standard 20150619 Page 86 of 105  [ 208 ] Steelhead (Puget Sound DPS) South Puget Sound Tributaries – winter  [ 211 ] Steelhead (Puget Sound DPS) White River - winter . Hood Canal and Strait of Juan de Fuca MPG  [ 195 ] Steelhead (Puget Sound DPS) Dungeness River - summer and winter  [ 196 ] Steelhead (Puget Sound DPS) East Hood Canal Tributaries - winter  [ 197 ] Steelhead (Puget Sound DPS) Elwha River - winter  [ 340 ] Steelhead (Puget Sound DPS) Sequim/Discovery Bays Tributaries - winter  [ 206 ] Steelhead (Puget Sound DPS) Skokomish River - winter  [ 343 ] Steelhead (Puget Sound DPS) South Hood Canal Tributaries - winter  [ 326 ] Steelhead (Puget Sound DPS) Strait of Juan de Fuca Tributaries - winter  [ 210 ] Steelhead (Puget Sound DPS) West Hood Canal Tributaries - winter . Northern Cascades MPG  [ 330 ] Steelhead (Puget Sound DPS) Baker River - summer and winter  [ 331 ] Steelhead (Puget Sound DPS) Canyon Creek - summer  [ 333 ] Steelhead (Puget Sound DPS) Deer Creek - summer  [ 334 ] Steelhead (Puget Sound DPS) Drayton Harbor Tributaries - winter  [ 336 ] Steelhead (Puget Sound DPS) Nookachamps Creek - winter  [ 201 ] Steelhead (Puget Sound DPS) Nooksack River - winter  [ 337 ] Steelhead (Puget Sound DPS) North Fork Skykomish River - summer  [ 324 ] Steelhead (Puget Sound DPS) Pilchuck River - winter  [ 204 ] Steelhead (Puget Sound DPS) Samish River and Bellingham Bay Tributaries - winter  [ 339 ] Steelhead (Puget Sound DPS) Sauk River - summer and winter  [ 205 ] Steelhead (Puget Sound DPS) Skagit River - summer and winter  [ 341 ] Steelhead (Puget Sound DPS) Snohomish/Skykomish Rivers - winter  [ 325 ] Steelhead (Puget Sound DPS) Snoqualmie River - winter  [ 342 ] Steelhead (Puget Sound DPS) South Fork Nooksack River - summer  [ 209 ] Steelhead (Puget Sound DPS) Stillaguamish River - winter  [ 329 ] Steelhead (Puget Sound DPS) Tolt River - summer

Coordinated Assessments Data Exchange Standard 20150619 Page 87 of 105 Willamette/Lower Columbia Recovery Domain Strata  Chinook salmon o Salmon, Chinook (Lower Columbia River ESU) . Cascade MPG  [ 212 ] Salmon, Chinook (Lower Columbia River ESU) Cispus River - spring  [ 244 ] Salmon, Chinook (Lower Columbia River ESU) Clackamas River - fall  [ 213 ] Salmon, Chinook (Lower Columbia River ESU) Coweeman River - fall  [ 214 ] Salmon, Chinook (Lower Columbia River ESU) Kalama River - fall  [ 215 ] Salmon, Chinook (Lower Columbia River ESU) Kalama River - spring  [ 217 ] Salmon, Chinook (Lower Columbia River ESU) Lewis River - fall  [ 216 ] Salmon, Chinook (Lower Columbia River ESU) Lewis River - late fall  [ 218 ] Salmon, Chinook (Lower Columbia River ESU) Lower Cowlitz River - fall  [ 219 ] Salmon, Chinook (Lower Columbia River ESU) North Fork Lewis River - spring  [ 220 ] Salmon, Chinook (Lower Columbia River ESU) Salmon Creek - fall  [ 222 ] Salmon, Chinook (Lower Columbia River ESU) Sandy River - fall  [ 221 ] Salmon, Chinook (Lower Columbia River ESU) Sandy River - late fall  [ 223 ] Salmon, Chinook (Lower Columbia River ESU) Sandy River - spring  [ 224 ] Salmon, Chinook (Lower Columbia River ESU) Tilton River - spring  [ 225 ] Salmon, Chinook (Lower Columbia River ESU) Toutle River - fall  [ 226 ] Salmon, Chinook (Lower Columbia River ESU) Toutle River - spring  [ 227 ] Salmon, Chinook (Lower Columbia River ESU) Upper Cowlitz River - fall  [ 228 ] Salmon, Chinook (Lower Columbia River ESU) Upper Cowlitz River - spring  [ 229 ] Salmon, Chinook (Lower Columbia River ESU) Washougal River - fall . Coastal MPG  [ 230 ] Salmon, Chinook (Lower Columbia River ESU) Big Creek - fall  [ 232 ] Salmon, Chinook (Lower Columbia River ESU) Clatskanie River - fall  [ 233 ] Salmon, Chinook (Lower Columbia River ESU) Elochoman River - fall  [ 234 ] Salmon, Chinook (Lower Columbia River ESU) Grays and Chinook Rivers - fall  [ 235 ] Salmon, Chinook (Lower Columbia River ESU) Mill, Abernathy, and Germany Creeks - fall  [ 236 ] Salmon, Chinook (Lower Columbia River ESU) Scappoose Creek - fall  [ 237 ] Salmon, Chinook (Lower Columbia River ESU) Youngs Bay - fall

Coordinated Assessments Data Exchange Standard 20150619 Page 88 of 105 . Gorge MPG  [ 238 ] Salmon, Chinook (Lower Columbia River ESU) Hood River - fall  [ 239 ] Salmon, Chinook (Lower Columbia River ESU) Hood River - spring  [ 240 ] Salmon, Chinook (Lower Columbia River ESU) Lower Gorge Tributaries - fall  [ 241 ] Salmon, Chinook (Lower Columbia River ESU) Upper Gorge Tributaries - fall  [ 242 ] Salmon, Chinook (Lower Columbia River ESU) White Salmon River - fall  [ 243 ] Salmon, Chinook (Lower Columbia River ESU) White Salmon River - spring o Salmon, Chinook (Upper Willamette River ESU) . Willamette MPG  [ 245 ] Salmon, Chinook (Upper Willamette River ESU) Calapooia River - spring  [ 246 ] Salmon, Chinook (Upper Willamette River ESU) Clackamas River - spring  [ 247 ] Salmon, Chinook (Upper Willamette River ESU) McKenzie River - spring  [ 248 ] Salmon, Chinook (Upper Willamette River ESU) Middle Fork Willamette River - spring  [ 249 ] Salmon, Chinook (Upper Willamette River ESU) Molalla River - spring  [ 250 ] Salmon, Chinook (Upper Willamette River ESU) North Santiam River - spring  [ 251 ] Salmon, Chinook (Upper Willamette River ESU) South Santiam River - spring  Chum salmon o Salmon, chum (Columbia River ESU) . Cascade MPG  [ 267 ] Salmon, chum (Columbia River ESU) Clackamas River - fall  [ 252 ] Salmon, chum (Columbia River ESU) Cowlitz River - fall  [ 344 ] Salmon, chum (Columbia River ESU) Cowlitz River - summer  [ 253 ] Salmon, chum (Columbia River ESU) Kalama River - fall  [ 254 ] Salmon, chum (Columbia River ESU) Lewis River - fall  [ 255 ] Salmon, chum (Columbia River ESU) Salmon Creek - fall  [ 256 ] Salmon, chum (Columbia River ESU) Sandy River - fall  [ 257 ] Salmon, chum (Columbia River ESU) Washougal River - fall . Coastal MPG  [ 258 ] Salmon, chum (Columbia River ESU) Big Creek - fall  [ 259 ] Salmon, chum (Columbia River ESU) Clatskanie River - fall  [ 260 ] Salmon, chum (Columbia River ESU) Elochoman River - fall  [ 261 ] Salmon, chum (Columbia River ESU) Grays and Chinook Rivers - fall

Coordinated Assessments Data Exchange Standard 20150619 Page 89 of 105  [ 262 ] Salmon, chum (Columbia River ESU) Mill, Abernathy, and Germany Creeks - fall  [ 263 ] Salmon, chum (Columbia River ESU) Scappoose Creek - fall  [ 264 ] Salmon, chum (Columbia River ESU) Youngs Bay - fall . Gorge MPG  [ 265 ] Salmon, chum (Columbia River ESU) Lower Gorge Tributaries - fall  [ 266 ] Salmon, chum (Columbia River ESU) Upper Gorge Tributaries - fall  Coho salmon o Salmon, coho (Lower Columbia River ESU) . Cascade MPG  [ 268 ] Salmon, coho (Lower Columbia River ESU) Cispus River - early and late  [ 292 ] Salmon, coho (Lower Columbia River ESU) Clackamas River - early and late  [ 269 ] Salmon, coho (Lower Columbia River ESU) Coweeman River - late  [ 270 ] Salmon, coho (Lower Columbia River ESU) East Fork Lewis River - early and late  [ 271 ] Salmon, coho (Lower Columbia River ESU) Kalama River - late  [ 272 ] Salmon, coho (Lower Columbia River ESU) Lower Cowlitz River - late  [ 273 ] Salmon, coho (Lower Columbia River ESU) North Fork Lewis River - early and late  [ 274 ] Salmon, coho (Lower Columbia River ESU) North Fork Toutle River - early and late  [ 275 ] Salmon, coho (Lower Columbia River ESU) Salmon Creek - late  [ 276 ] Salmon, coho (Lower Columbia River ESU) Sandy River - early and late  [ 277 ] Salmon, coho (Lower Columbia River ESU) South Fork Toutle River - early and late  [ 278 ] Salmon, coho (Lower Columbia River ESU) Tilton River - early and late  [ 279 ] Salmon, coho (Lower Columbia River ESU) Upper Cowlitz River - early and late  [ 280 ] Salmon, coho (Lower Columbia River ESU) Washougal River - late . Coastal MPG  [ 281 ] Salmon, coho (Lower Columbia River ESU) Big Creek - late  [ 282 ] Salmon, coho (Lower Columbia River ESU) Clatskanie River - late  [ 283 ] Salmon, coho (Lower Columbia River ESU) Elochoman River - late  [ 284 ] Salmon, coho (Lower Columbia River ESU) Grays and Chinook Rivers - late  [ 285 ] Salmon, coho (Lower Columbia River ESU) Mill, Abernathy, and Germany Creeks - late  [ 286 ] Salmon, coho (Lower Columbia River ESU) Scappoose Creek - late  [ 287 ] Salmon, coho (Lower Columbia River ESU) Youngs Bay - late

Coordinated Assessments Data Exchange Standard 20150619 Page 90 of 105 . Gorge MPG  [ 288 ] Salmon, coho (Lower Columbia River ESU) Lower Gorge Tributaries - late  [ 290 ] Salmon, coho (Lower Columbia River ESU) Oregon Upper Gorge Tributaries and Hood River - early  [ 291 ] Salmon, coho (Lower Columbia River ESU) Washington Upper Gorge Tributaries and White Salmon River - late  Steelhead o Steelhead (Lower Columbia River DPS) . Cascade MPG  [ 293 ] Steelhead (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  [ 295 ] Steelhead (Lower Columbia River DPS) East Fork Lewis River - summer  [ 296 ] Steelhead (Lower Columbia River DPS) East Fork Lewis River - winter  [ 297 ] Steelhead (Lower Columbia River DPS) Kalama River - summer  [ 298 ] Steelhead (Lower Columbia River DPS) Kalama River - winter  [ 299 ] Steelhead (Lower Columbia River DPS) Lower Cowlitz River - winter  [ 300 ] Steelhead (Lower Columbia River DPS) North Fork Lewis River - summer  [ 301 ] Steelhead (Lower Columbia River DPS) North Fork Lewis River - winter  [ 302 ] Steelhead (Lower Columbia River DPS) North Fork Toutle River - winter  [ 303 ] Steelhead (Lower Columbia River DPS) Salmon Creek - winter  [ 304 ] Steelhead (Lower Columbia River DPS) Sandy River - winter  [ 305 ] Steelhead (Lower Columbia River DPS) South Fork Toutle River - winter  [ 306 ] Steelhead (Lower Columbia River DPS) Tilton River - winter  [ 307 ] Steelhead (Lower Columbia River DPS) Upper Cowlitz River - winter  [ 308 ] Steelhead (Lower Columbia River DPS) Washougal River - summer  [ 309 ] Steelhead (Lower Columbia River DPS) Washougal River - winter . Gorge MPG  [ 310 ] Steelhead (Lower Columbia River DPS) Hood River - summer  [ 311 ] Steelhead (Lower Columbia River DPS) Hood River - winter  [ 312 ] Steelhead (Lower Columbia River DPS) Lower Gorge Tributaries - winter  [ 313 ] Steelhead (Lower Columbia River DPS) Upper Gorge Tributaries - winter  [ 314 ] Steelhead (Lower Columbia River DPS) Wind River - summer

Coordinated Assessments Data Exchange Standard 20150619 Page 91 of 105 . 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 Steelhead (Upper Willamette River DPS) . Willamette MPG  [ 316 ] Steelhead (Upper Willamette River DPS) Calapooia River - winter  [ 317 ] Steelhead (Upper Willamette River DPS) Molalla River - winter  [ 318 ] Steelhead (Upper Willamette River DPS) North Santiam River - winter  [ 319 ] Steelhead (Upper Willamette River DPS) South Santiam River - winter

Coordinated Assessments Data Exchange Standard 20150619 Page 92 of 105 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 o Umatilla River Fall Chinook  Fall o Upper Cowlitz River Fall Chinook o Big Creek Fall Chinook o Washougal River Fall Chinook o Clackamas River Fall Chinook o White Salmon Bright Fall Chinook o Clatskanie River Fall Chinook o White Salmon Tule Fall Chinook o Clearwater River Fall Chinook o Youngs Bay Fall Chinook o Columbia Upper Gorge Tributaries Fall Chinook  Spring o Coweeman River Fall Chinook o American River Spring Chinook o Deschutes River Fall Chinook o Calapooia River Spring Chinook o Elochoman River Fall Chinook o Catherine Creek Spring Chinook o Grande Ronde River Fall Chinook o Cispus River Spring Chinook o Grays River Fall Chinook o Clackamas River Spring Chinook o Hanford Reach Fall Chinook o East Fork Salmon River Spring Chinook o Hood River Fall Chinook o Entiat River Spring Chinook o Imnaha River Fall Chinook o Granite Creek John Day Spring Chinook o Kalama River Fall Chinook o Hood River Spring Chinook o Klickitat River Fall Chinook o Kalama River Spring Chinook o Lewis River Early Fall Chinook o Klickitat River Spring Chinook o Lewis River Late Fall Chinook o Lewis River Spring Chinook o Lower Columbia Gorge Tributaries Fall Chinook o Little White Salmon River Spring Chinook o Lower Cowlitz River Fall Chinook o Lolo Creek Spring Chinook o Lower Snake River Fall Chinook o Lookingglass Creek Spring Chinook o Lower Yakima River Fall Chinook o Malheur River Spring Chinook o Mill Creek Fall Chinook o McKenzie River Spring Chinook o Rock Creek Fall Chinook o Methow River Spring Chinook o Salmon Creek Early Fall Chinook o Middle Fork John Day Spring Chinook o Sandy River Early Fall Chinook o Middle Fork Willamette River Spring Chinook o Scappoose Creek Fall Chinook o Minam River Spring Chinook o Snake Hell's Canyon Fall Chinook o Molalla/Pudding River Spring Chinook o Toutle River Fall Chinook o Naches River Spring Chinook o Tucannon River Fall Chinook o North Fork John Day Spring Chinook o North Santiam River Spring Chinook

Coordinated Assessments Data Exchange Standard 20150619 Page 93 of 105 o Okanogan River Spring Chinook o Salmon River Lower Mainstem below Redfish Lake Spring/Summer Chinook o Potlatch River Spring Chinook o Salmon River Upper Mainstem above Redfish Lake Spring/Summer Chinook o Sandy River Spring Chinook o Secesh River Spring/Summer Chinook o Shitike Creek Spring Chinook o South Fork Salmon River Spring/Summer Chinook o South Santiam River Spring Chinook o Sulphur Creek Spring/Summer Chinook o Tilton River Spring Chinook o Tucannon River Spring/Summer Chinook o Toutle River Spring Chinook o Upper North Fork Clearwater River Spring/Summer Chinook o Umatilla River Spring Chinook o Upper Selway River Spring/Summer Chinook o Upper Cowlitz River Spring Chinook o Upper South Fork Clearwater River Spring/Summer Chinook o Upper Grande Ronde Spring Chinook o Valley Creek Spring/Summer Chinook o Upper John Day Spring Chinook o Wenaha River Spring/Summer Chinook o Upper Yakima River Spring Chinook o Yankee Fork Spring/Summer Chinook o Walla Walla Spring Chinook o Wallowa - Lostine River Spring Chinook Chum salmon Warm Springs River Spring Chinook o  Fall o Wenatchee River Spring Chinook o Cowlitz River Fall Chum o White Salmon Spring Chinook  (No run indicated) o Wind River Spring Chinook o Big Creek Chum  Spring/summer o Clackamas River Chum o Asotin Creek Spring/Summer Chinook o Clatskanie River Chum o Bear Valley Creek Spring/Summer Chinook o Cowlitz River Summer Chum o Big Creek Spring/Summer Chinook o Elochoman River Chum o Big Sheep Creek Spring/Summer Chinook o Grays/Chinook Rivers Chum o Camas Creek Spring/Summer Chinook o Kalama River Chum o Chamberlain Creek Spring/Summer Chinook o Lewis River Chum o East Fork South Fork Salmon River Spring/Summer Chinook o Lower Columbia Gorge Tributaries Chum o Imnaha River Mainstem Spring/Summer Chinook o Lower Columbia Mainstem Chum o Lapwai/Big Canyon Spring/Summer Chinook o Mill Creek Chum o Lawyer Creek Spring/Summer Chinook o Sandy River Chum o Lemhi River Spring/Summer Chinook o Scappoose Creek Chum o Little Salmon River Spring/Summer Chinook o Upper Gorge Tributaries Chum o Lochsa River Spring/Summer Chinook o Washougal River Chum o Loon Creek Spring/Summer Chinook o Youngs Bay Chum o Lower North Fork Clearwater River Spring/Summer Chinook o Marsh Creek Spring/Summer Chinook o Meadow Creek Spring/Summer Chinook Coho salmon o Middle Fork Salmon River above Indian Creek Spring/Summer Chinook  (No run indicated) o Middle Fork Salmon River below Indian Creek Spring/Summer Chinook o Big Creek Coho o Moose Creek Spring/Summer Chinook o Cispus River Coho o North Fork Salmon River Spring/Summer Chinook o Clackamas River Coho o Pahsimeroi River Spring/Summer Chinook o Clatskanie River Coho o Panther Creek Spring/Summer Chinook o Coweeman River Coho

Coordinated Assessments Data Exchange Standard 20150619 Page 94 of 105 o East Fork Lewis River Coho o Payette Lake Kokanee o Elochoman Coho o Priest Lake Kokanee o Entiat River Coho o Rimrock Lake Kokanee o Fifteenmile Creek Coho o San Poil River Kokanee o Grays/Chinook Rivers Coho o Spokane River Kokanee o Hood River Coho o Suttle Lake Kokanee o Kalama River Coho o Upper Columbia River Kokanee o Lower Columbia Gorge Tributaries Coho o Wallowa Lake Kokanee o Lower Cowlitz River Coho o Wickiup Reservoir Kokanee o Mill Creek Coho o Molalla/Pudding River Coho Sockeye salmon North Fork Lewis River Coho o  (No run indicated) o North Fork Toutle River Coho o Okanogan River Sockeye o North Santiam River Coho o Snake River (Redfish Lake) Sockeye Salmon o Salmon Creek Coho o Snake River Sockeye (Stanley, Petit, Alturas, other lakes) o Sandy River Coho o Wenatchee River Sockeye o Scappoose Creek Coho o Yakima River Sockeye o South Fork Toutle River Coho o Tilton River Coho o Umatilla River Coho Steelhead o Upper Cowlitz River Coho  Summer o Washougal River Coho o Asotin Creek Summer Steelhead o Wenatchee River Coho o Burnt River Summer Steelhead o White Salmon Coho o Chamberlain Creek Summer Steelhead o Youngs Bay Coho o Clearwater River Lower Mainstem Summer Steelhead o Crab Creek Summer Steelhead Kokanee o Deschutes Crooked River Summer Steelhead o Deschutes River Eastside Tributaries Summer Steelhead  (No run indicated) o Deschutes River Westside Tributaries Summer Steelhead o Bumping Lake Kokanee o East Fork Lewis River Summer Steelhead o Cle elum Lake Kokanee o East Fork Salmon River Summer Steelhead o Coeur d'Alene Lake Kokanee o Entiat River Summer Steelhead o Crab Creek Kokanee o Hood River Summer Steelhead o Crane Prairie Reservoir Kokanee o Imnaha River Summer Steelhead o Kachess Lake Kokanee o Joseph Creek Summer Steelhead o Keechelus Lake Kokanee o Kalama River Summer Steelhead o Lake Billy Chinook Kokanee o Klickitat River Summer Steelhead o Lake Chelan Kokanee o Lemhi River Summer Steelhead o Lake Osoyoos Kokanee o Little and Lower Salmon River Summer Steelhead o Lake Pend Oreille Kokanee o Lochsa River Summer Steelhead o Lake Wenatchee Kokanee o Lolo Creek Summer Steelhead o Paulina Lake Kokanee o Lower Grande Ronde Summer Steelhead

Coordinated Assessments Data Exchange Standard 20150619 Page 95 of 105 o Lower John Day Summer Steelhead o Wenatchee River Summer Steelhead o Lower Malheur River Summer Steelhead o White Salmon River Steelhead o Lower Middle Fork Salmon River Summer Steelhead o Willow Creek Summer Steelhead o Lower Owyhee River Summer Steelhead o Wind River Summer Steelhead o Methow River Summer Steelhead  Winter o Middle Fork John Day Summer Steelhead o Big Creek Winter Steelhead o Naches River Summer Steelhead o Calapooia River Winter Steelhead o North Fork Clearwater River Summer Steelhead o Cispus River Winter Steelhead o North Fork John Day Summer Steelhead o Clackamas River Winter Steelhead o North Fork Lewis River Summer Steelhead o Clatskanie River Winter Steelhead o North Fork Salmon River Summer Steelhead o Columbia Gorge Tributaries Winter Steelhead o Okanogan River Summer Steelhead o Coweeman River Winter Steelhead o Pahsimeroi River Summer Steelhead o East Fork Lewis River Winter Steelhead o Panther Creek Summer Steelhead o Elochoman Winter Steelhead o Powder River Summer Steelhead o Fifteenmile Subbasin Winter Steelhead o Rock Creek Summer Steelhead o Grays River Winter Steelhead o Salmon River Upper Mainstem Summer Steelhead o Hood River Winter Steelhead o Sandy River Summer Steelhead o Kalama River Winter Steelhead o Satus Creek Summer Steelhead o Klickitat River Winter Steelhead o Secesh River Summer Steelhead o Lower Cowlitz River Winter Steelhead o Selway River Summer Steelhead o Middle Fork Willamette River Winter Steelhead o Snake Hells Canyon Summer Steelhead o Mill Creek Winter Steelhead o South Fork Clearwater River Summer Steelhead o Molalla/Pudding River Winter Steelhead o South Fork John Day Summer Steelhead o North Fork Lewis River Winter Steelhead o South Fork Salmon River Summer Steelhead o North Fork Toutle River Winter Steelhead o Toppenish Creek Summer Steelhead o North Santiam River Winter Steelhead o Touchet River Summer Steelhead o Salmon Creek Winter Steelhead o Tucannon River Summer Steelhead o Sandy River Winter Steelhead o Umatilla River Summer Steelhead o Scappoose Creek Winter Steelhead o Upper Grande Ronde Summer Steelhead o South Fork Toutle River Winter Steelhead o Upper John Day Summer Steelhead o South Santiam River Winter Steelhead o Upper Malheur River Summer Steelhead o Tilton River Winter Steelhead o Upper Middle Fork Salmon River Summer Steelhead o Upper Columbia Gorge Tributaries Winter Steelhead o Upper Owyhee River Summer Steelhead o Upper Cowlitz River Winter Steelhead o Upper Yakima River Summer Steelhead o Washougal River Winter Steelhead o Walla Walla River Summer Steelhead o Willamette Westside Tributaries Winter Steelhead o Wallowa River Summer Steelhead o Youngs Bay Winter Steelhead o Washougal River Summer Steelhead

Coordinated Assessments Data Exchange Standard 20150619 Page 96 of 105 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.

Appendix E1. Populations Table This table stores information about populations, and records who requested each population be added. Field Name Field Description Data Type Codes/Conventions for NOSA Table PopID Code for the TRT population of fish represented Integer See Appendix C for the list of PopID codes for populations as defined by NMFS Northwest Region for ESA. The populations by this record. 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  Steelhead Additional 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 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 is the name of a defined Evolutionarily Significant be at the species, subspecies, or finer scale. ESUs of salmon north of California are listed at Unit (ESU) or Distinct Population Segment (DPS) http://www.nwfsc.noaa.gov/trt/. as defined by NMFS Northwest Region or by USFWS. For non-listed populations this is the DPS or other name.

Coordinated Assessments Data Exchange Standard 20150619 Page 97 of 105 Field Name Field Description Data Type Codes/Conventions for NOSA Table RecoveryDomain Name of the "recovery domain," as defined by the Text 255 Five recovery domains have been defined by NMFS in Washington, Oregon, and Idaho. Select the appropriate one from this NMFS Northwest Region, in which the population list: falls.  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.nwfsc.noaa.gov/trt/. MajorPopGroup Name of "major population group" (MPG) or Text 255 The term "stratum" is used in the Willamette/Lower Columbia Recovery Domain, while "major population group" is used in “stratum” as defined by the NMFS Northwest other areas. The term "stratum" includes life history considerations as well as geographic criteria, while MPGs are defined Region, in which the population falls. geographically. See Appendix C for the list of MPGs / strata. CBFWApopName Population name as defined by CBFWA for Text 255 This may include non-listed populations, or cases where geographic area does not match a defined population of a listed subbasin planning purposes, from subbasin plans species. In such cases the "PopID" field above will be blank. See Appendix D for the list of these population names. and agencies. 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 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 population be added to the list. 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

Coordinated Assessments Data Exchange Standard 20150619 Page 98 of 105 Appendix F. Hatchery names and codes

Hatchery name Code Hatchery name Code Hatchery name Code Aberdeen Net Pens at US Army COE's Pier 396 Bogachiel Hatchery 331 Clark Flat spring chinook acclimation/release site 547 Abernathy Fish Technology Center 1 Bogachiel R Rearing Pond 332 Clark Fork Fish Hatchery 231 Agate Pass Seapens 476 Bohannon Falls Fish Trap 571 Cle Elum Hatchery 542 Alder Creek Rearing Pond 293 Bonifer Pond Juvenile Acclimation/Release Facility 130 Cle Elum Ponds (aka Slough) 300 Allison Springs Rearing Pond 368 Bonneville Hatchery 26 Clear Cr Hatchery 337 Alsea Hatchery 128 Boulder Creek Screw Trap 914 Clear Creek Adult Weir 916 Alturas Lake Creek Screw Trap 907 Boyd Cr Rearing Pond 395 Clear Creek Juvenile Weir 917 American Falls Fish Hatchery 343 Brenner Trout Hatchery 401 Clear Creek Rearing Pond 371 American River Hatchery 732 Butte Falls Hatchery 131 Clear Creek Screw Trap 918 Anderson Ranch Reservoir Weir 908 Cabinet Gorge Fish Hatchery 285 Clearwater Fish Hatchery 24 Applegate Trap 575 Camas Net Pens 402 Clearwater River Scoop Trap 919 Arlington Hatchery 218 Canyon Springs Pond (Hoh Tribe) 403 Cocollala Creek Weir 920 Ashton Fish Hatchery 238 Capital Lake Rearing Pond 404 Coffee Pot Rapids Weir 921 Aspen Springs Trout Farm 268 Capitol Lake Trap 518 Cole M. Rivers Hatchery 133 Aumsville Ponds 37 Carlton Acclimation Pond 90 Coleman NFH 100 Avila Beach Sea Pens 749 Carson Depot Springs 555 Colt Killed Creek Screw Trap 922 Baker Lake Hatchery (aka Baker Spawning Beach 4) 487 Carson NFH 3 Columbia Basin Hatchery 220 (previously Sulphur Springs Hatchery) Casa Grande High School Hatchery 746 Colville Hatchery 302 Baker Lake Spawning Beach 2 516 Cascade Aqua Farms 299 Colville Tribal Hatchery 301 Baker Lake Spawning Beach 3 540 Cascade Hatchery 41 Corvallis Research Lab Hatchery 510 Bandon Hatchery 129 Catherine Creek Acclimation Pond 577 Cottonwood Creek Rearing Pond 68 Barnaby Slough Rearing Pond 330 Catherine Creek Trap 576 Coulter Creek Rearing Pond 303 Bear Springs Rearing Pond 1 294 CCF Blind Slough Net Pens 569 Coweeman Rearing Pond #1 491 Bear Springs Rearing Pond 2 538 CCF Hatchery (South Fork) 105 Coweeman Rearing Pond #2 492 Bear Valley Creek Weir 909 CCF Tongue Point Net Pens 568 Cowling Creek Hatchery 373 Beaver Creek Hatchery 55 CCF Youngs Bay Net Pens 567 Cowlitz Salmon Hatchery 72 Bellingham Hatchery 488 Cedar Creek Hatchery 132 Cowlitz Trout Hatchery 56 Big Beef Creek Hatchery 375 Cedar Flats Acclimation Facility 904 Coyote Valley Fish Facility 742 Big Canyon Ponds_Wallowa Hatchery satellite facility 52 Cedar River Hatchery 361 Creston NFH 289 Big Creek Hatchery 25 Chalaat Cr Hat (Hoh Tribe) 383 Crisp Creek Rearing Pond 304 Big Creek Hatchery 747 Chamberlain Creek Weir 915 Crooked Fork Creek Screw Trap 923 Big Springs Creek Weir Lower 910 Chambers Creek Hatchery 112 Crooked Fork Creek Weir 924 Big Springs Creek Weir Upper 911 Chambers Creek Trap 519 Crooked River Incubation Channel 925 Big White Salmon Ponds 2 Champion Pond 489 Crooked River Rearing Ponds 357 Big Wood River Weir 912 Chehalis Tribal Hatchery 405 Crooked River Satellite Fish Hatchery 109 Bills Boathouse Net Pen 517 Chelan Hatchery 60 Crooked River Scoop Trap 926 Bingham Adult Fishway & Trap 429 Chelan PUD Hatchery 297 Crooked River Screw Trap 927 Bingham Creek Hatchery 114 Chelan River Net Pens (WDFW) 647 Crystal Lake Hatchery 431 Bitterroot Fish Hatchery 275 Chewach Rearing Pond 95 Crystal Lakes 274 Black Rock Hatchery 737 Chimacum High 298 Curl Lake Rearing Ponds 70 Blackbird Island Pond 646 Chiwawa Rearing Pond 91 Darrah Springs Hatchery 731 Blackfoot River Weir 913 Clackamas Hatchery 31 Dayton Rearing Ponds 71

Coordinated Assessments Data Exchange Standard 20150619 Page 99 of 105 Hatchery name Code Hatchery name Code Hatchery name Code Deadhorse Creek Rearing Pond 520 Fish Springs Hatchery 735 Imnaha Acclimation and Collection Facility 50 Deadwood River Weir 928 Flaming Geyser Rearing Pond 514 (Lookingglass Hatchery satellite facility) Decker Ponds 355 Flathead Lake Salmon Hatchery 261 Indian Creek Incubation Channel 938 Deep R Net Pens - Upper (Rkm 8.1) 408 Ford Hatchery 494 Indian Creek Weir 939 Deer Springs Pond 230 Forks Creek Hatchery 117 Iron Gate Hatchery 97 Delph Creek Station 609 Fox Island Net Pens 468 Irrigon Hatchery 42 Dexter Pond_Willamette Hatchery satellite facility 40 Garrison Springs Hatchery 305 Issaquah Hatchery 123 Diru Cr Hatchery 364 George Adams Hatchery 150 Jack Cr spring chinook acclimation/release site 546 Ditch Creek Incubation Channel 929 Germany Creek Project 307 Jim Cr Hatchery 479 Doty Creek Pools 748 Glen Ayr Net Pens Co-op 521 Jocko River Trout Hatchery 263 Drano Lake Pens (USFWS) 409 Glenwood Springs Hatchery 522 Johns Creek Hatchery 327 Dryden Rearing Ponds 92 Gnat Creek Hatchery 27 Johnson Creek Hatchery 418 Dungeness Hatchery 151 Gobar Rearing Pond 57 Johnson Creek Screw Trap 940 Dworshak NFH 4 Goldendale Hatchery 229 Johnson Creek Weir 941 Eagle Cr Pond (Preceded Cascade Hatchery) 557 Gorst Creek Rearing Ponds 370 Josephine Creek Weir 942 Eagle Creek NFH 5 Grace Fish Hatchery 236 Kalama Creek Hatchery 365 Eagle Creek Rearing Pond 430 Granite Creek Weir 937 Kalama Falls Hatchery 75 Eagle Fish Hatchery 345 Grays River Hatchery 74 Kendall Creek Hatchery 120 East Fork Salmon River Screw Trap 930 Grays River Rearing Pond 54 Kenney Creek Rearing Pond 525 Eastbank Hatchery 87 Green River Community College Rearing Pond 638 Kern River Planting Base 739 Eastfork Satellite Fish Hatchery 107 Grovers Creek Hatchery 374 Keta Creek Hatchery 353 Easton Lake spring chinook acclimation/release site 548 Hagerman NFH 7 Klamath Hatchery 147 Easton Ponds coho acclimation/release site 610 Hagerman State Fish Hatchery 234 Klaskanine Hatchery 29 Educket Creek Hatchery 381 Hantz Creek Acclimation Pond 574 Klickitat Hatchery 76 Eells Springs Hatchery 411 Harriman Trout Company 276 Kooskia NFH 8 Eldorado Creek Weir 931 Hartman Pond 46 Kootenai Tribal Sturgeon Hatchery 286 Elk Adult Fishway & Trap 641 AKA: Wahkeena Pond_Oxbow Hatchery satellite facility La Grange Fish Facility 447 Elk Creek Weir 932 Hayden Creek Fish Hatchery 344 Lake Aberdeen Hatchery 217 Elk River Hatchery 134 Hayspur Fish Hatchery 235 Lake Creek Screw Trap 943 Elochoman Hatchery 73 Hells Canyon Dam Trap 106 Lake Creek Weir 944 Elson Creek Hatchery 369 Henrys Lake Fish Hatchery 239 Lake Sequalitchew Net Pens 366 Elwha Channel 334 Herman Creek Ponds (lower)_Oxbow Hatchery satellite 573 Lake Shannon Net Pens 526 Elwha Tribal Hatchery 379 facility Lake Wenatchee Net Pens 93 Enetai Hatchery 377 Herman Creek Ponds (upper)_Oxbow Hatchery satellite 45 Lake Whatcom Hatchery 326 Ennis National Fish Hatchery 269 facility Lakewood Hatchery 328 Entiat NFH 6 Hoko Falls Hatchery 464 Leaburg Hatchery 32 Fall Creek Rearing Ponds 442 Hollow Tree Creek Ponds 453 Leavenworth NFH 9 Fall Creek Trap 118 Hoodsport Hatchery 148 Lemhi River Screw Trap 945 Fall River Hatchery 145 Hoodsport Marina Net Pens Co-op 523 Lemhi River Weir 509 Fallert Creek Hatchery 78 Hot Creek Hatchery 734 Lenore Lake Trap 527 Feather River Hatchery 99 Hughey Creek Pond 560 Lewis River (Fish First - Echo) Net Pens 541 Fenn Ranger Station Incubation Channel 933 Humptulips Hatchery 308 Lewis River Hatchery 77 Fidalgo Net Pens 613 Hupp Springs Rearing Pond 126 Lewiston Dam Trap 946 Fillmore Hatchery 740 Hurd Creek Hatchery 378 Lion Creek Weir 947 Fish Creek Screw Trap 934 Icy Creek Rearing Pond 417 Little Blackfoot River Weir 948 Fish Creek Weir 935 Imeques C-mem-ini-kem Juvenile Acclimation/Release 564 Little Goose Dam Fingerling Rearing 352 Fish Lake Westslope Weir 936 Facility

Coordinated Assessments Data Exchange Standard 20150619 Page 100 of 105 Hatchery name Code Hatchery name Code Hatchery name Code Little Sheep Creek Pond 53 Little White Salmon NFH 10 Livingston Stone NFH 551 (Wallowa Hatchery satellite facility)

Coordinated Assessments Data Exchange Standard 20150619 Page 101 of 105 Hatchery name Code Hatchery name Code Hatchery name Code Lochsa River Screw Trap 949 Montlake Lab (NMFS NW & AK Fish Ctr) 354 Pelton Ladder_Round Butte Hatchery satellite facility 48 Lolo Creek Weir Lower 950 Moose Creek Weir 958 Pendleton Juvenile Acclimation/Release Facility 566 Lolo Creek Weir Upper 951 Morgan Creek (Priorli Cr.) Rearing Facility (STEP 351 (temporary name) Lonesome Creek Hatchery 382 facility) Percival Cove Net Pens 530 Long Live the Kings - Lilliwaup 544 Morse Creek Pond 645 Pettit Lake Creek Weir 963 Long Live the Kings - Van Winkle Cr 543 Mossyrock Hatchery 310 Pleasant Harbor Marina Net Pens Co-op 531 Lookingglass Hatchery 49 Mount Shasta State Fish Hatchery 730 Port Gamble Co-op Quilcene Bay Net Pens 474 Lost Cr coho acclimation/release site 549 Mount Whitney Hatchery 736 Port Gamble Hatchery 466 Lostine Acclimation Pond 580 Mule Pasture Pond 477 Port Gamble Net Pens 470 Louisa Creek Weir 952 Mullan Fish Hatchery 232 Powell Satellite Fish Hatchery 20 Lower Lemhi River Screw Trap 953 Murray Springs Trout Hatchery 265 Powerdale Fish Facility 616 Lower South Fork Salmon River Screw Trap 954 N/A 98 Prairie Creek (Closed) 450 Lukes Gulch Acclimation Facility 902 Naches Hatchery 61 Priest Rapids Hatchery 80 Lummi Bay Sea Ponds 469 Nampa Fish Hatchery 233 proposed - Waikiki Springs Hatchery 225 Lyons Ferry Hatchery 67 Naselle Hatchery 311 Prosser Hatchery 325 Mackay Fish Hatchery 237 Nelson Springs Rearing Pond\Raceway 62 Puyallup Hatchery (WDFW) 363 Mad River Hatchery 485 Nemah Hatchery 116 Quilcene NFH 313 Magic Valley Steelhead Hatchery 15 Newnonshish Hat (Shoalwater Bay Tribe) 393 Quinault Hatchery/Net Pens 388 Makah NFH 104 Newsome Acclimation Facility 906 Quinault NFH 315 Mamoya Rearing Pond 528 Nez Perce Tribal Fish Hatchery 901 Raft River Rearing Pond 387 Marblemount Hatchery 121 NF Toutle FCF 111 Rapid River Fish Hatchery 22 Marion Forks Hatchery 33 Niagara Springs Fish Hatchery 17 Rapid River Screw Trap 964 Marmot Acclimation Site 480 Nile Springs Pond 228 Red River Incubation Channel 965 (Satellite of Clackamas Hatchery) Nimbus Fish Hatchery 101 Red River Satellite Fish Hatchery 21 Marsh Creek Screw Trap 955 Noble Creek STEP Hatchery 561 Red River Satellite Fish Hatchery Rearing Ponds 966 Marsh Creek Weir 956 North Fork Boise River Weir 959 Red River Screw Trap 967 Matheny Cr Rearing Pond Quinault Tribe 386 North Fork Payette River Weir 960 Redfish Lake Creek Trap 508 Mattole Salmon Stock Rescue Program 750 North Lapwai Valley Acclimation Facility 905 Redwood Creek (Eel River Project) 452 Mayr Brothers Rearing Pond 389 North Nehalem Hatchery 137 Reiter Ponds 496 McAllister Hatchery 341 North Toutle Hatchery 84 Rhodes Pond 138 McCall Fish Hatchery 16 Northwestern Lake Net Pens 529 Ringold Springs Hatchery 63 McCall Satellite Fish Hatchery 113 Noyo River Egg Collection Station 554 Roaring River Hatchery 35 McKenzie Hatchery 34 NWSSC - Cedar R Trap 545 Rock Creek Hatchery 139 McKernan Hatchery 376 Oak Springs Hatchery 43 Rock Creek Pens (USFWS) 552 Meadow Creek Incubation Channel 957 Oakridge Salmon Hatchery 290 Rocky Ford Hatchery #1 532 Merced River Fish Facility 435 Omak Hatchery 227 Rocky Ford Hatchery #2 533 Merwin Dam (aka FCF) Adult Trap 644 Onalaska High School - Gheer Cr Collection 615 Round Butte Hatchery 47 Merwin Hatchery 336 Oregon Aqua-Foods/Yaquina Bay 457 Rowdy Creek Fish Hatchery 432 Meseberg Hatchery 612 Oregon Hatchery Research Center 135 Running Creek Incubation Channel 968 Methow Hatchery 88 Oxbow Fish Hatchery 18 Running Creek Screw Trap 969 Minter Creek Hatchery 149 Oxbow Hatchery 44 Running Creek Weir 970 Minthorn Springs Juvenile Acclimation/Release Facility 136 Pahsimeroi Fish Hatchery Lower Facility 19 Rush Creek Weir 971 Minto Pond_Marion Forks satellite facility 481 Pahsimeroi Fish Hatchery Upper Facility 961 Rutsatz Slough Rearing Pond 475 Moccasin Creek Hatchery 733 Pahsimeroi River Screw Trap 962 S. Fk. Klaskanine Pond 359 Modrow (aka Kalama) Adult Trap 524 Palmer Creek Trap 572 Salmon Falls Creek Weir 972 Mojave River Hatchery 741 Palmer Rearing Pond 495 Salmon River Fish Culture Facility 385 Mokelumne River Hatchery 102 Parkdale Hatchery 562 Salmon River Hatchery 140

Coordinated Assessments Data Exchange Standard 20150619 Page 102 of 105 Hatchery name Code Salmon River Screw Trap 973 Samish Hatchery 119 Samish Rearing Pond 534 San Joaquin Hatchery 738 Sandpoint Fish Hatchery 240 Sandy Hatchery 30 Satsop Springs Rearing Pond 392 Sawtooth Fish Hatchery Weir 23 Sawtooth Intake Screw Trap 974 Sawtooth Scoop Trap 975 Sawtooth Screw Trap 976 Schorno Springs Rearing Pond 478 Sea Resources Hatchery 316 Secesh River Screw Trap 977 Secesh River Weir 978 Sekokoni Springs Hatchery 277 Selway Falls Trap 108 Selway Falls Trap 979 Selway River Screw Trap 980 Shale Creek Rearing Pond 384 Shelton Rearing Ponds 611 Sherman Creek Hatchery 317 Siletz Falls Trap 570 Siletz Hatchery 291 Silver Lake Net Pen 420 Silverado Fisheries Base 438 Similkameen Rearing Pond 89 Skamania Hatchery 58 Skookum Creek Hatchery 463 Skookumchuck Dam Rearing Pond 339 Skookumchuck Hatchery 648 Skykomish Sportsmen Co-op Rearing Pond 639 Slate Creek Weir 486 Snake River Dipper Trap 982 Social Security Pens (USFWS) 553 Sol Duc Hatchery 318 Soos Creek Hatchery 124 South Fork Red River Incubation Channel 983 South Fork Salmon River Screw Trap (DS Knox) 984 South Fork Salmon River Screw Trap (US Knox) 985 South Fork Walla Walla Adult Holding & Spawning 565 Facility South Santiam Hatchery 36 South Sound Net Pens 497 South Toutle Trap 498 Speelyai Hatchery 83 Spokane Hatchery 319

Coordinated Assessments Data Exchange Standard 20150619 Page 103 of 105 Hatchery name Code Hatchery name Code Hatchery name Code Spokane Tribal Hatchery 320 Trinity River Hatchery 96 Washoe Park Trout Hatchery 266 Spring Creek NFH 11 Trojan Pond 28 Washougal Hatchery 85 Springfield Fish Hatchery 900 Trout Lodge Hatchery 537 Websters Rearing Pond 372 Springfield Production 292 Tucannon Hatchery 69 Wells Hatchery 65 Squaw Creek Weir 986 Tuffy Creek Pond_Trask Hatchery satellite facility 559 West Fork Chamberlain Creek Weir 991 Squaxin Island Sea Pens 321 Tulalip Hatchery 323 West Fork Yankee Fork Screw Trap 992 St Paul Pd 141 Tumwater Falls Hatchery 367 West Fork Yankee Fork Weir 993 St. Charles Creek Weir 987 Tuolumne River Fish Facility (closed) 752 Westslope Trout Company 272 Stayton Pond 38 Turtle Rock Rearing Ponds & Rocky Reach Annex 64 Weyco-Briscoe Ponds 391 Stiles Pond coho acclimation/release site 550 Twisp Rearing Pond 94 Whatcom Cr Hatchery 219 Stillaguamish Tribal Hatchery 360 Two Mouth Creek Weir 990 Whiskey Creek Hatchery (Private) 558 Stolle Meadows Rearing Pond 988 Umatilla Hatchery 144 White River Hatchery 362 Sullivan Springs Weir 989 Umbrella Creek Hatchery\RSI 426 Whitehorse Rearing Ponds 333 Sund Rock Net Pens Co-op 499 University of Washington Hatchery 467 Wildhorse River Weir 994 Sunset Falls Adult Trap 535 Upper Grand Ronde Pond 579 Willamette Hatchery 39 Sunset Falls FCF 640 Upper Grand Ronde Weir Trap 578 Willard NFH 13 Sweetwater Springs Fish Hatchery 288 Upper Skagit Tribal Hatchery 465 Winchester Hatchery 539 Swinomish Rearing Ponds 536 US Army Net Pens 416 Winthrop NFH 14 Tacoma Headworks Trap 614 Van Arsdale Fisheries Station (Snow Mt.) 608 Wizard Falls Hatchery 146 Tanwax Lake Net Pens 423 Vancouver Hatchery 59 Wolf Lodge Creek Weir 995 Tehama-Colusa Fish Facility (Closed) 449 Voight Creek Hatchery 125 Wynoochee Lake Net Pens (Trout) 427 Ten Mile River Hatchery 745 Waatch Cr Hat (Makah Tribe) 380 Wynoochee R Salmon Pens 390 Thornhollow Juvenile Acclimation/Release Facility 563 Walcott Slough 556 Yager Creek Hatchery 744 Three Mile Adult Holding and Spawning Facility 110 Wallace River Hatchery 122 Yakima Hatchery 66 Tiburon Sea Pens 437 Wallowa Hatchery 51 Yakima Net Pens @ Wapato Dam 428 Tokul Creek Hatchery 329 Warm Springs Fish Hatchery 103 Yoosa-Camp Creek Acclimation Facility 903 Trask River Hatchery 142 Warm Springs NFH 12 Trask River Hatchery Pond 143 Washburn Island Rearing Pond Facility 226

Coordinated Assessments Data Exchange Standard 20150619 Page 104 of 105 Appendix G. MS-Access 2010 Data Types

MS-Access 2010 Data Type Purpose Characteristics Storage Required Per Record

Numbers. Zero to 15 digits to the left of Currency 8 bytes Appropriate for numbers other than currency. the decimal point and zero to 4 digits to the right. 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 Date/Time Date and time. morning. 8 bytes A time with no date is interpreted as 12/30/1899. Calculations among records recognize and use these default values in calculations, so must be accounted for when using the data. 2 bytes / character for Unicode. Long text entries. Memo Up to 63,999 characters in length. 1 byte / character if Unicode compression enabled and (Including numbers not used in calculations.) entry is under 4,096 characters. Integers only: no decimal places. Number (Byte) Whole numbers from 0 to 255. 1 byte No negative numbers.

Decimal places and negative numbers allowed. Number (Decimal) Numbers from -9.999 X 1027 to 9.99927. 12 bytes Up to 28 significant digits.

Number (Integer) Whole numbers from -32,768 to 32,767. Integers only: no decimal places. 2 bytes

Whole numbers Number (Long Integer) Integers only: no decimal places. 4 bytes –2,147,483,648 to 2,147,483,647.

Floating point numbers Number (Single) Up to 7 significant digits. 4 bytes –3.402823 X 1038 to 3.402823 X 1038.

Floating point numbers Number (Double) Up to 15 significant digits. 8 bytes –1.79769313486231 X 10308 to 1.79769313486231 X 10308.

ReplicationID Globally unique identifier (GUID). Creates a (presumably) unique value to identify a record. 16 bytes

Text. Up to 255 characters in length. 2 bytes / character for Unicode. Text (Including numbers not used in calculations.) Maximum allowed length can be shorter than 255. 1 byte / character if Unicode compression enabled. Cannot be null. Must be one of the 2 values. Storage of values that can have only one of two values. Yes/No It is not possible to indicate such things as 1 bit Yes/No; On/Off; True/False. "Not applicable" or "Unknown".

Coordinated Assessments Data Exchange Standard 20150619 Page 105 of 105