Data Management Plan

DMP Template v2.0.1 (2015-01-01)

Please provide the following information, and submit to the NOAA DM Plan Repository.

Reference to Master DM Plan (if applicable)

As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:

Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:

Sockeye salmon Snake River ESU critical habitat for use in ESA/FIFRA consultations

Taken From: Item Identification | Title

1.2. Summary description of the data:

These data represent critical habitat designated (December 28, 1993, 58 FR 68543) under the Endangered Species Act for the Snake River sockeye salmon ESU. The official NMFS critical habitat (SalmonSockeye_SnakeRiverESU_19931228) for this sockeye salmon is comprised of both lake (polygon) data and river/stream (line) data; together the polygons and lines represent the entire final critical habitat designation.Critical habitat includes the water, waterway bottom, and adjacent riparian zone of specified river reaches. Adjacent riparian zones are defined as those areas within a horizontal distance of 300 feet (91.4 m) from the normal line of high water of a stream channel (600 feet or 182.8 m, when both sides of the stream channel are included) or from the shoreline of a standing body of water.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.

1.3. Is this a one-time data collection, or an ongoing series of measurements?

No information found

Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.

1.4. Actual or planned temporal coverage of the data:

No information found

Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.

1.5. Actual or planned geographic coverage of the data:

W: -124.083015, E: -113.879946, N: 46.703183, S: 43.883074
W: -124.083015, E: -113.879946, N: 46.703183, S: 43.883074
W: -124.083015, E: -113.879946, N: 46.703183, S: 43.883074
W: -119.075983, E: -113.679244, N: 46.845724, S: 43.788004

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.

1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)

Map (digital)

Taken From: Data Set Information | Data Presentation Form

1.7. Data collection method(s):
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)

No information found

Taken From: Acquisition Information | Instruments, Platforms

1.8. If data are from a NOAA Observing System of Record, indicate name of system:

Always left blank due to field exemption

1.8.1. If data are from another observing system, please specify:

Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:

Karrin Goodman

Taken From: Support Roles (Metadata Contact) | Person
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.

2.2. Title:

Metadata Contact

Always listed as "Metadata Contact"

2.3. Affiliation or facility:

Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.

2.4. E-mail address:

karrin.goodman@noaa.gov

Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.

2.5. Phone number:

â€ª(301) 427-8435â€¬

Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

3. Responsible Party for Data Management

Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.

3.1. Name:

Karrin Goodman

Taken From: Support Roles (Data Steward) | Person
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.

3.2. Position Title:

Data Steward

Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?

No information found

Taken From: Data Management | Have resources for management of these data been identified?

4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):

No information found

Taken From: Data Management | Approximate percentage of budget for these data devoted to data management

5. Data Lineage and Quality

NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Process Steps:

2018-10-31 00:00:00 - Data creation process 2018. SOSNR_CH.gdb -> SOSNR (feature dataset) -> SOSNR_line (feature class) Data were developed as part of an effort to interpret and depict several salmonid critical habitat designations completed in the 1990s that relied on text-based descriptions but lacked GIS data. Habitat areas for Snake River sockeye were identified based on the following: 1) The regulatory definition of ESA critical habitat for this species found at 50 CFR 226.205(a) and the supporting final rule (58 FR 68543, December 28, 1993); 2) The USGS high resolution National Hydrography Dataset (NHD) - downloaded February 2018; 3) Intrinsic Potential (IP) GIS data developed by the NMFS Northwest Fisheries Science Center; 4) National Elevation Dataset and Digital Topographic Maps; 5) Fish Passage Barriers data from StreamNet www.StreamNet.org; 6) NMFS recovery planning documents for the Snake River basin; 7) The professional judgment of biologists from the NMFS Interior Columbia Basin Office; 8) Maps and documentation found in the references below. Evermann, B.W. 1896. A Report upon Salmon Investigations in the Headwaters of the Columbia River, in the State of Idaho, in 1895 Together with Notes upon the Fishes Observed in that State in 1894 and 1895. NMFS. 2015. ESA Recovery Plan for Snake River Sockeye Salmon (Oncorhynchus nerka). June 8, 2015. National Marine Fisheries Service, West Coast Region. Teuscher, D., D. Taki., W. Wurtsbaugh, C. Luecke, P. Bundy, H.P. Gross, and G. Steinhart. 1993. Snake River sockeye salmon habitat and limnological research. Annual Report 1993. Prepared for U. S. Department of Energy, Bonneville Power Administration, Division of Fish and Wildlife, P.O. Box 3621, Portland, OR 97208-3621. Project Number 91-7 1. Contract Number DE-BI79-91BP22548. June 1994) Upstream extent notes. Used NHD flowlines to identify perennial* inlet creeks (including their perennial tributaries and any braided reaches) from their confluence with the nursery lake upstream to the first endpoint using the following criteria: (a) the first 20% gradient barrier calculated from DEM data (Tile 08 Idaho, National Elevation Dataset (NED), with a Horizontal Grid Spacing of 1/3 arc second, approx. 10 meters); or (b) the first impassable falls (based on StreamNet barrier data); or (c) the first confluence (intermittent or perennial) upstream of a reach classified as High IP for spring/summer Chinook; or (d) the end of the NHD reach. * The only exception to this was if an intermittent inlet creek had supplemental information indicating sockeye presence (e.g., the south inlet of Pettit Lake).
2019-07-17 00:00:00 - SOSNR_line feature class (GCS_North_American_1983 wkid 4269) geographic transformation not necessary, saved as SOSNR_ch.shp (GCS_North_American_1983 wkid 4269). Geometry was not edited, attributes were not edited, metadata was edited.
2021-04-26 00:00:00 - The 2019 version SOSNR_ch.shp (GCS_North_American_1983 wkid 4269) was converted into the standardized feature class SalmonSockeye_SnakeRiverESU_19931228_line (GCS_WGS_84 wkid 4326) using the National Critical Habitat Geodatabase processing protocol. During standardization, geometry was not edited. Attributes were edited. Metadata was edited and populated using the final rule and metadata from the source SOSNR_CH.gdb -> SOSNR (feature dataset) -> SOSNR_line (feature class) (GCS_North_American_1983 wkid 4269). Migrated fields: "GNIS_Name" into "UNIT", "FCode" into "NOTES" (populated descriptions with FCode values) Dropped fields: OBJECTID, Perm_ID, FDate, Resolution, GNIS_ID, LengthKM, ReachCode, DPS, ShapeLength
2023-03-30 00:00:00 - As described above, this species’ HUC-based critical habitat dataset was modified from the line- and polygon-based species “agency-official” NMFS critical habitat data. This HUC-based critical habitat file represents the HUC-12 watersheds (USGS Watershed Boundary Dataset; https://www.usgs.gov/national-hydrography/watershed-boundary-dataset) that intersect with the “agency-official” critical habitat line-based and polygon-based data. The data were reviewed and revised to add any additional HUC-12 watersheds that were determined to have hydrologic connectivity to the critical habitat.

Taken From: Lineage | Lineage Statement, Process Steps (Process Date/Time, Source Citation Title, Description)

5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:

Always left blank

5.2. Quality control procedures employed
(describe or provide URL of description):

No information found

Taken From: Data Quality | Quality Control Procedures Employed

6. Data Documentation

The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.

6.1. Does metadata comply with EDMC Data Documentation directive?

No

Notes: All required DMP fields must be populated and valid to comply with the directive.

6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

1.3. Is this a one-time data collection, or an ongoing series of measurements?
1.4. Actual or planned temporal coverage of the data
1.7. Data collection method(s)
4.1. Have resources for management of these data been identified?
4.2. Approximate percentage of the budget for these data devoted to data management
5.2. Quality control procedures employed
7.1. Do these data comply with the Data Access directive?
7.1.1. If data are not available or has limitations, has a Waiver been filed?
7.1.2. If there are limitations to data access, describe how data are protected
7.2. Name of organization of facility providing data access
7.2.1. If data hosting service is needed, please indicate
7.3. Data access methods or services offered
7.4. Approximate delay between data collection and dissemination
8.1. Actual or planned long-term data archive location
8.2. Data storage facility prior to being sent to an archive facility
8.3. Approximate delay between data collection and submission to an archive facility
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?

Notes: Required DMP fields that are not populated or invalid are listed here.

6.2. Name of organization or facility providing metadata hosting:

NMFS Office of Science and Technology

Always listed as "NMFS Office of Science and Technology"

6.2.1. If service is needed for metadata hosting, please indicate:

Always left blank

6.3. URL of metadata folder or data catalog, if known:

https://www.fisheries.noaa.gov/inport/item/72815

Always listed as the URL to the InPort Data Set record

6.4. Process for producing and maintaining metadata
(describe or provide URL of description):

Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf

Always listed with the above statement

7. Data Access

NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.

7.1. Do these data comply with the Data Access directive?

No information found

Taken From: Data Management | Do these data comply with the Data Access directive?

7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?

No information found

Taken From: Data Management | Is access to the data limited based on an approved waiver?

7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

No information found.

Taken From: Access Info | Data Access Constraints

7.2. Name of organization of facility providing data access:

No information found

Taken From: Support Roles (Distributor) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.

7.2.1. If data hosting service is needed, please indicate:

No information found

Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.

7.2.2. URL of data access service, if known:

Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.

7.3. Data access methods or services offered:

No information found

Taken From: Access Info | Data Access Procedure

7.4. Approximate delay between data collection and dissemination:

No information found

Taken From: Data Management | Approximate delay between data collection and dissemination

7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

Taken From: Data Management | If delay is longer than latency of automated processing, indicate under what authority data access is delayed
Notes: This field is required if applicable.

8. Data Preservation and Protection

The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.

8.1. Actual or planned long-term data archive location:
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)

No information found

Taken From: Data Management | Actual or planned long-term data archive location

8.1.1. If World Data Center or Other, specify:

Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.

8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:

Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.

8.2. Data storage facility prior to being sent to an archive facility (if any):

Partial information found
Portland, OR

Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.

8.3. Approximate delay between data collection and submission to an archive facility:

No information found

Taken From: Data Management | Approximate delay between data collection and submission to an archive facility

8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection

No information found

Taken From: Data Management | How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank