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.
1. General Description of Data to be Managed
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.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(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.)
2. Point of Contact for this Data Management Plan (author or maintainer)
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.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
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.
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.
Programs must identify resources within their own budget for managing the data they produce.
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.
(describe or provide URL of description):
- 2017-02-02 00:00:00 - Data creation process 2017. FCH_CKSRF_2017.shp 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 fall Chinook were identified based on the following: 1) The regulatory definition of ESA critical habitat for this species found at 50 CFR 226.205(c) and the supporting final rule (58 FR 68543, December 28, 1993); 2) The USGS high resolution National Hydrography Dataset (NHD) - downloaded 2015; 3) NMFS recovery planning documents for the Snake River basin; 4) The professional judgment of biologists from the NMFS West Coast Region (Interior Columbia Basin Office and Protected Resources Division), Washington Department of Fish and Wildlife, Oregon Department of Fish and Wildlife, and the Nez Perce Tribe. We used 2017 StreamNet fish distribution data and the professional judgement of local biologists to map stream reaches presently or historically accessible to Snake River fall Chinook. Where fall Chinook have expanded their range since 1993 when critical habitat was designated, we generally assume that this expansion expresses the species' historic range. However, because the critical habitat designation is limited to the specfic 4th field HUC subbasins identified in 58 FR 68543, even if fall Chinook salmon expand their range in the future to areas upstream from those subbasins - indicating that those upstream reaches may have been "historically accessible" - those additional reaches would not be considered part of designated critical habitat. The line work comprising this dataset was extracted from the 2015 National Hydrography Dataset, a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of water, paths through which water flows, and related entities (nhd.usgs.gov). The original arcs were split at endpoints identified by NMFS and those arcs not designated as critical habitat were deleted, leaving in this dataset, only those arcs that are considered critical habitat.
- 2019-07-17 00:00:00 - FCH_CKSRF_2017.shp (GCS_North_American_1983 wkid 4269) geographic transformation not necessary, saved as CKSRF_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 CKSRF_ch.shp (GCS_North_American_1983 wkid 4269) was converted into the standardized feature class SalmonChinook_SnakeRiverfallrunESU_19931228 (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 FCH_CKSRF_2017.shp (GCS_North_American_1983 wkid 4269). Migrated field: "GNIS_Name" into "UNIT" Dropped field: FID
(describe or provide URL of description):
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.
- 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)
- 3.1. Responsible Party for Data Management
- 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?
(describe or provide URL of description):
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.
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.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
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.
(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)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.