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 for the Mexico DPS of humpback whales includes all marine waters within these designated areas: (1) Alaska. The nearshore boundaries are generally defined by the 1-m isobath relative to mean lower low water (MLLW). On the north side of the Aleutian Islands, the seaward boundary of the critical habitat is defined by a line extending from 55Â° 41 N, 162Â° 41' W west to 55Â° 41' N, 169Â° 30' W, then southward through Samalga Pass to a boundary drawn along the 2,000-m isobath on the south side of the islands. This isobath forms the southern boundary of the critical habitat, eastward to 164Â° 25' W. From this point, the 1,000-m isobath forms the offshore boundary, which extends eastward to 158Â° 39' W. Critical habitat also includes the waters around Kodiak Island and the Barren Islands. The western boundary for this area runs southward along 154Â° 54' W to the 1,000-m depth contour, and then extends eastward to a boundary at 150Â° 40' W. The area also extends northward to the mouth of Cook Inlet where it is bounded by a line that extends from Cape Douglas across the inlet to Cape Adam. Critical habitat also includes the Prince William Sound area and associated waters defined by an eastern boundary at 148Â° 31' W, a western boundary at 145Â° 27' W, and a seaward boundary drawn along the 1,000-m isobath. (2) Washington. The nearshore boundary is defined by the 50-m isobath, and the offshore boundary is defined by the 1,200-m isobath relative to MLLW. Critical habitat also includes waters within the U.S. portion of the Strait of Juan de Fuca to an eastern boundary line at Angeles Point at 123Â° 33' W. (3) Oregon. The nearshore boundary is defined by the 50-m isobath. The offshore boundary is defined by the 1,200-m isobath relative to MLLW; except, in areas off Oregon south of 42Â° 10', the offshore boundary is defined by the 2,000-m isobath. (4) California. The nearshore boundary is defined by the 50-m isobath relative to MLLW except, from 38Â° 40' N to 36Â° 00' N, the nearshore boundary is defined by the 15-m isobath relative to MLLW; and from 36Â° 00' N to 34Â° 30' N, the nearshore boundary is defined by the 30-m isobath relative to MLLW. North of 40Â° 20' N, the offshore boundary of the critical habitat is defined by a line corresponding to the 2,000-m isobath, and from 40Â° 20' N to 38Â° 40' N, the offshore boundary is defined by the 3,000-m isobath. From 38Â° 40' N southward, the remaining areas have an offshore boundary defined by a line corresponding to the 3,700-m isobath. Critical habitat does not include manmade structures (e.g., ferry docks, sea plane facilities) and the land on which they rest within the critical habitat boundaries. Critical habitat does not include the following particular areas owned or controlled by the Department of Defense, or designated for its use, where they overlap with the critical habitat: (1) Pursuant to ESA section 4(a)(3)(B), all areas subject to the Naval Base Ventura County, Point Mugu, CA, and the Naval Outlying Field, San Nicolas Island, CA approved Integrated Natural Resource Management Plans (INRMPs); (2) Pursuant to ESA section 4(b)(2), the Quinault Range Site (QRS) with an additional 10-km buffer that extends along the southern edge of the QRS and along the northern edge of the QRS except in areas past 10-km into the Olympic Coast National Marine Sanctuary. Please see the final rule for additional information.
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):
(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)
- 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.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
- 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.