Search Help Show/Hide Menu
This is a deprecated version of the NOAA Data Management Plan template.
InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.

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:
WCR Marine Salmon Essential Fish Habitat Geodatabase
1.2. Summary description of the data:

The Magnuson-Stevens Fishery Conservation and Management Act (MSA) requires that regional management councils describe EFH in their fishery management plans (FMPs), that they minimize to the extent practicable adverse effects on EFH from fishing activities, and that federal agencies consult with the National Marine Fisheries Service on activities that may adversely affect EFH, among other things. Actions that occur outside of EFH, but that may adversely affect EFH, also warrant an EFH consultation. EFH means those waters and substrate necessary to fish for spawning, breeding, feeding, or growth to maturity (50 CFR 600.10). FMPs must describe and identify EFH in text that clearly states the habitats or habitat types determined to be EFH for each life stage of the managed species, if possible. The text descriptions are ultimately determinative of the limits of EFH. Those text descriptions of marine salmon EFH can be found in the Salmon Fishery Management Plan (FMP) available on the Pacific Fishery Management Council (Council) website: https://www.pcouncil.org/. In addition, FMPs must include maps that display, within the constraints of available information, the geographic locations of EFH or the geographic boundaries within which EFH for each species and life stage is found (50 CFR 600.815(a)(1)(v)(A)). This Geographic Information System (GIS) data which depicts the EFH of marine salmon within the EEZ off the U.S. West Coast, was developed to meet that requirement.This geodatabase (GDB) contains three feature classes, providing marine EFH data for the following species:Chinook salmonCoho salmonPuget Sound Pink salmon Naming Convention: The names of the GDB and its feature classes include the date (YYYYMMDD) that the National Marine Fisheries Service (NMFS) approved Amendment 18 to the FMP, updating the marine salmon EFH components.Citation details for 79 FR 75450Fisheries Off West Coast States; West Coast Salmon Fisheries; Amendment 18 to the Salmon Fishery Management PlanA Rule by the Commerce Department, and the National Oceanic and Atmospheric AdministrationPublication date: December 18, 2014Effective date: January 20, 2015

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: -129.162414, E: -120.47044, N: 49, S: 34.448845
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.)
No information found
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
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:
No information found
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:
No information found
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:
No information found
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:
Stephani Onisko
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
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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):

Lineage Statement:
The West Coast Region (WCR) marine salmon EFH GIS data was developed using spatial descriptions from the Pacific Fishery Management Council (PFMC) Fishery Management Plan (FMP). The primary reference document is: Pacific Fishery Management Council (2014). Appendix A to the Pacific Coast Salmon Fishery Management Plan, as modified by Amendment 18: Identification and description of essential fish habitat, adverse impacts, and recommended conservation measures for salmon (Portland, OR). Available at: https://www.pcouncil.org/documents/2019/08/salmon-efh-appendix-a.pdf Marine Coho and Chinook Salmon EFH Boundary Definitions and Source Data: The following spatial parameters and source datasets were utilized to define the West Coast Region (WCR) marine Coho and Chinook salmon Essential Fish Habitat (EFH) boundaries: Northern Extent: Defined by the U.S. Exclusive Economic Zone (EEZ) and the International Maritime Boundary (Source: NOAA U.S. Maritime Limits & Boundaries). Southern Extent: Terminated at Point Conception, California (approx. 34.448° N). Western/Seaward Extent: Bounded by the U.S. Exclusive Economic Zone (EEZ) as delineated on NOAA Nautical Charts. Eastern/Shoreward Extent (North of Pajaro River): Aligned with the shoreward limit of the 2014 WCR freshwater Chinook and Coho salmon EFH data (Source: NOAA EFH Mapper). Eastern/Shoreward Extent (South of Pajaro River): For the coastal segment extending from the mouth of the Pajaro River south to Point Conception, the NOAA Historical Medium Resolution Shoreline was utilized to maintain consistency with the shoreline source cited in the 2014 WCR freshwater salmon EFH metadata. Exclusions: All internal bays, estuaries, and inlets were explicitly excluded from the marine EFH polygon in this southern segment to maintain the coastal marine designation. Marine Puget Sound Pink Salmon EFH Boundary Definitions and Source Data: The following spatial parameters and source datasets were utilized to define the Essential Fish Habitat (EFH) for WCR marine Puget Sound Pink Salmon: Northern/Seaward Extent: Defined by the seaward expansion of the 2014 WCR Puget Sound pink salmon baseline (Source: NOAA EFH Mapper) to the U.S. Exclusive Economic Zone (EEZ) and International Maritime Boundary. This encompasses all marine waters north and east of Cape Flattery, WA, including the Strait of Juan de Fuca, the Strait of Georgia, and Puget Sound. Western/Seaward Extent: Bounded by the U.S. EEZ and limited to marine waters north of the 48° N latitude parallel. Eastern/Shoreward Extent: Bounded by the landward limit of the 2014 WCR Puget Sound pink salmon EFH dataset, serving as the interface between freshwater and marine designations.

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

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.6. Type(s) of data
  • 1.7. Data collection method(s)
  • 2.1. Point of Contact Name
  • 2.4. Point of Contact Email
  • 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:
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
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
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:
No information found.
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
7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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
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
Long Beach, CA
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
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

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