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
Methods used were adapted from a "cookbook" of instructions developed by Kyle Hogref
for using IKONOS imagery data to derive seafloor elevations in optically clear
water. This dataset was derived from high-resolution (2 m) imagery from DigitalGlobe's
WorldView-2 sensor of the Kaanapali area of Maui, Hawaii. Sensor bands 1,2
and 5 (coastal, blue and near IR respectively) were used to derive depth information.
The method assumes uniform water clarity but deviations from that condition
made extraction difficult in water greater than 30 m depth in the Kaanapali scene
used. Results show that biotic material or sediment in the water column skewed results
shallower if the material has a high albedo and deeper if the material has a low
albedo. Nearshore areas were significantly less impacted in the Kaanapali area,
due to the geomorphology of the area and the hi resolution and quality of the imagery,
allowing visual descrimination of apparent sediment in the water column.
For presentation purposes the map product shows an Inverse Distance Weighted interpolated
bathymetry surface, restricted to data within 600 m of the shoreline.
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):
- 2011-10-12 00:00:00 - Multiple tools in ENVI 4.8 were used to complete the following processing steps: Data conversion from digital number to radiance, correction for atmosphere and water surface reflection, linearization of spectral decay as function of depth, masking of non-applicable values, and bathymetric derivation using variables from multiple linear regression analysis. Multiple tools in ArcGIS 10.0 were used for dataset integration and to extract values for the multiple linear regression analysis and subsequent error analyses. The statisitcs program Matlab was used for the multiple linear regression analysis to provide original variables for depth derivation. The multivariate slope intercept formula used to derive depth was D = a + (bi)(xi) + (bj)(xj) Where: D = depth a = intercept b = slope x = the linearized spectral value resulted in 7.8491 - 2.8696(b1) + 7.9593(b2) b1 is the output masked linearized pictral value of each pixel of Coastal band b2 is the output masked linearized pictral value of each pixel of Blue band More information on this integration process is provided in the product error analysis, availble from PIBHMC upon request. This mosaiced derived bathymetry product (JohDBall3) was then integrated with the multibeam sonar data, with sonar data prioritized over derived data, to create the final product (JohDB3MB). A detailed description of all processing steps is available at: ftp://ftp.soest.hawaii.edu/pibhmc/website/webdocs/documentation/Cookbook_042108.pdf An error analysis of each derived bathymetry grid used is available from PIBHMC upon request. To produce the interpolated surface shown in the map, the floating point grid was converted to a point shapefile in Arc GIS 9.3 using the 'float to raster' and 'raster to point' tools in the Arc Toolbox. A buffer of 600m from the shoreline was created and the derived bathymetry points were clipped to exclude data outside this buffer. This distance was chosen to exclude areas of deeper water that were erroneously returning shallow depth values, due to characteristics of the water column. An Inverse Distance Weighted interpolation was run using 3D Analyst, to produce an interpolated surface, with a grid cell size of 10 m, a variable search radius with a maximum distance of 60 m, and using the coastline as a barrier. All other settings used were default. The interpolated surface was clipped using the coastline and a small number of isolated cells were manually deleted.
(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.7. Data collection method(s)
- 7.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
(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.
Data can be accessed online via the NOAA National Centers for Environmental Information (NCEI) Ocean Archive, accession #.
ADD ACCESSION ONCE ASSIGNED
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
NOAA IRC and NOAA Fisheries ITS resources and assets.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.