Data Management Plan
GUID: gov.noaa.nmfs.inport:65371 | Published / External
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 two specific marine areas in Cook Inlet, Alaska. These areas are bounded on the upland by Mean High Water (MHW) datum, except for the lower reaches of four tributary rivers. Critical habitat shall not extend into the tidally-influenced channels of tributary waters of Cook Inlet, with the exceptions noted in the descriptions of each critical habitat area.(1) Area 1. All marine waters of Cook Inlet north of a line from the mouth of Threemile Creek (61°08.5ⲠN., 151°04.4ⲠW.) connecting to Point Possession (61°02.1ⲠN., 150°24.3ⲠW.), including waters of the Susitna River south of 61°20.0ⲠN., the Little Susitna River south of 61°18.0ⲠN., and the Chickaloon River north of 60°53.0ⲠN.(2) Area 2. All marine waters of Cook Inlet south of a line from the mouth of Threemile Creek (61°08.5ⲠN., 151°04.4ⲠW.) to Point Possession (61°02.1ⲠN., 150°24.3ⲠW.) and north of 60°15.0ⲠN., including waters within 2 nautical miles seaward of MHW along the western shoreline of Cook Inlet between 60°15.0ⲠN. and the mouth of the Douglas River (59°04.0ⲠN., 153°46.0ⲠW.); all waters of Kachemak Bay east of 151°40.0ⲠW.; and waters of the Kenai River below the Warren Ames bridge at Kenai, Alaska.Critical habitat does not include manmade structures and the land on which they rest within the designated boundaries that were in existence as of May 11, 2011.Critical habitat does not include the following areas owned by the Department of Defense or for which the Secretary has determined to exclude for reasons of national security:(1) All property and overlying waters of Joint Base Elmendorf-Richardson between Mean Higher High Water and Mean High Water; and(2) All waters off the Port of Anchorage which are east of a line connecting Cairn Point (61°15.4ⲠN., 149°52.8ⲠW.) and Point MacKenzie (61°14.3ⲠN., 149°59.2ⲠW.) and north of a line connecting Point MacKenzie and the north bank of the mouth of Ship Creek (61°13.6ⲠN., 149°53.8ⲠW.).
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.
W: -154.263922, E: -148.540899, N: 61.522161, S: 59.001668
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.
4. Resources
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):
Process Steps:
- 2011-05-06 00:00:00 - Data creation process 2011. CIB_critical_habitat.shp (NAD_1983_Alaska_Albers) Attributes were updated 02-24-2017.
- 2021-02-01 00:00:00 - AK source data CIB_critical_habitat.shp (NAD_1983_Alaska_Albers) -> converted to feature class WhaleBeluga_CookInletDPS_20110411 (GCS_WGS_1984). Field "Name" into "Unit" and field "SubName" into "Notes". Geometry was not edited, attributes were edited, metadata was edited and populated using the source shapefile, final rule, and CFR.
(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.
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)
- 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?
(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.