Data Management Plan
GUID: gov.noaa.nmfs.inport:39326 | 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
This project is a cooperative effort among the National Ocean Service, National Centers for Coastal Ocean Science, Center for Coastal Monitoring and Assessment; the University of Hawaii; and Analytical Laboratories of Hawaii, LLC. The goal of the work was to develop coral reef mapping methods and compare benthic habitat maps generated by photointerpreting georeferenced color aerial photography, hyperspectral and IKONOS satellite imagery. Twenty-seven distinct benthic habitat types within eleven zones were mapped directly into a GIS system using visual interpretation of orthorectified aerial photographs and hyperspectral imagery. Benthic features were mapped that covered an area of 790 km^2. In all, 204 km^2 of unconsolidated sediment, 171 km^2 of submerged vegetation, and 415 km^2 of coral reef and colonized hardbottom were mapped.
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:
- 2001-10-10 00:00:00 - Benthic habitat maps were digitized by delineating habitat boundaries from georeferenced imagery loaded into ArcView 3.2 GIS software with the Image Analysis and NOAA Coral Reef Habitat Digitizing extensions both activated. Digitizing was conducted using heads-up computer screen methods with the minimum mapping unit (MMU) set to 1 acre and the image scale at 1:6,000. All three types of remotely sensed imagery were processed by NOS prior to map production. Individual color aerial photographs were georeferenced and mosaicked. The hyperspectral data composed of 72 ten nm wide bands were subsetted to three band composites that enhanced deep and shallow water features. IKONOS satellite imagery was corrected for atmospheric and water column effects. During the digitizing process, image stretched and manipulating image contrast, brightness and color balance were performed in the ArcView Image Analysis Extension to enhance features in the processed imagery. A first draft map was completed and features in the imagery where uncertainties existed, due to confusing or difficult to interpret signatures, were identified for future ground validation effort. An ArcView GIS point theme was generated with points positioned on the features of uncertain habitat type or along transects though gradients between habitat types. The GIS points were converted to GPS waypoints using Trimble Pathfinder Software and were navigated to in the field using a Trimble GeoExplorer 3 GPS data logger. A benthic habitat characterization was conducted at each site by snorkeling, free diving, or via observations from the surface where water depth and clarity permitted. GPS data were collected at each location and site ID, depth, habitat type, zone and the method used to make the assessment were recorded. The ground validation data were incorporated into the second draft of each 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.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.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.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.
None
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.