Data Management Plan
GUID: gov.noaa.nmfs.inport:65317 | 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
Main Hawaiian Islands (MHI): Hawaiian monk seal critical habitat in the terrestrial environments of Kauai, Lehua, Oahu, Maui Nui (including Kahoolawe, Lanai, Maui, Molokai), and Hawaii extends from the water's edge (mean lower low water line) inland 5 meters (in length) past the shoreline. The shoreline is described by the upper reaches of the wash of the waves, other than storm or seismic waves, at high tide during the season in which the highest wash of the waves occurs, usually evidenced by the edge of vegetation growth or the upper limit of debris.Areas ineligible for designation as critical habitat and areas that were excluded from critical habitat were clipped out of this dataset. The final rule (August 21, 2015 80 FR 50926) describes ineligible and excluded areas. Critical habitat does not include the following particular areas where they overlap with the locations described above: all cliffs and manmade structures, such as docks, seawalls, piers, fishponds, roads, pipelines, boat ramps, platforms, buildings, ramparts and pilings existing within the legal boundaries on September 21, 2015.
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.
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:
- 2015-08-21 00:00:00 - Coastline locations designated as Hawaiian monk seal critical habitat (in addition to marine areas) were determined via a multi-step process. First, location data records from the Pacific Islands Fisheries Science Center were plotted as points. These data include sighting locations from 2007 - 2011, cell phone tag data, and aerial survey data from a survey completed in 2008. Five kilometer grid cell fishnets were created and placed over each island to create a standardized grid and a spatial join combined the location data with the grid cells. The attribute "Join Count" in that new grid file indicates how many location data points are within each grid cell. Based on expert opinion of the monk seal critical habitat team, it was determined that sites within any grid cell with a join count equalling 10% or more of the highest individual join count value for each island respectively would be considered to contain high use areas for inclusion in critical habitat. After isolating those grid cells, we used Google Earth imaging to refine the coastline areas within the grid cells to be included in critical habitat based on landscape features (i.e hardened shorelines or cliff faces were eliminated, continuous stretches of beach that were part inside and part outside of a grid cell were either included fully or eliminated, etc.). This was done with the help of an expert from the monk seal research program most famliar with the habitat use of seals at different locations around the MHI. The marine component and other portion of the terrestrial component of Hawaiian monk seal critical habitat is depcited in a seaprate polygon dataset.
- 2020-04-16 00:00:00 - Lines were copied from Final_HMSCH_Terr_MHI_2015.shp into this feature class during the NMFS 2020 national critical habitat standardization project. The data were processed to represent the final rule accurately. Minor edits (e.g., line removed around Kaula Island and lines removed around Niihau because they were deemed ineligible for designation in the final rule) were made to geometry in cases where the shapefile data did not represent the final CH designation. To support map service queries from this dataset, some line segments were dissolved to consolidate attributes. Note: there are inconsistencies in the final rule for Oahu between the line labels in the table (pg 50974) and the line labels on the map (pg 50984). The values for the Unit field in this feautre class were taken from the table (not the map).
(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)
- 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.