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
The Klawock River on Alaska's Prince of Wales Island drains a 29,061 acre watershed with 132 miles of streambed habitat supporting seven salmon and trout species. Traditionally the river and lagoon supported salmon harvests exceeding 30,000 fish annually. The salmon fishery is an important economic factor and food source in the Klawock area. It is also an important cultural resource to local inhabitants. In 1964 a causeway was constructed blocking access to the lagoon from adjacent Klawock Bay. This has resulted in dramatic decreases in salmon harvests. The Nature Conservancy has lead a broad partnership to construct a culvert through the causeway thus re-establishing free passage between the river and Klawock Bay which is expected to help restore a full use of the river as spawning habitat by salmon and generally improve the quality of the lagoon. Benthic habitats in the lagoon and adjacent Klawock Bay and Klawock Harbor were mapped in spring 2011 to establish a baseline of benthic communities in the area with emphasis on eelgrass beds which are essential to the early survival of salmon fry. The habitat map will guide ongoing monitoring activities in the lagoon and form the basis of future change detection efforts.
Aerial multi-spectral imagery was collected over the lagoon, bay, and harbor during the week of April 19, 2011. The mission was timed to coincide with the breaching of the causeway. The environmental considerations important to successful benthic mapping were incorporated into the mission planning. These included, imagery to be collected within 1.5 hours of a zero or negative tide, clear water conditions (no algal blooms, or sediment plumes from runoff), low winds to avoid surface waves, and sufficient solar illumination to image submerged areas. These collection parameters were defined by the Office for Coastal Management prior to collection of the imagery. Despite weather and water conditions which were not ideal, imagery adequate to map most of the habitats in the lagoon was successfully collected on April 19, 2011.
Eelgrass habitats in the Lagoon did not have sufficient biomass or illumination through the water column at the time of the aerial mission to be mapped from that source so eelgrass habitats were determined by two field-digitizing processes, one in August 2010 and one in September 2011. The final hybrid map captures habitats 10m x 10m or larger and has the same positional accuracy as the source imagery.
Field data to guide the mapping was supplied by several project partners. A comparison between the field data and the map shows high levels of agreement, although no traditional quantitative accuracy assessment was conducted.
Original contact information:
Contact Org: NOAA Office for Coastal Management
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-04-01 00:00:00 - The imagery was flown on 4/19/2011 between 9:35 and 10:24 A.M. by Geovantage Inc. The horizontal spatial accuracy of the imagery reported by the vendor is within +/- 3 meters CE95 of position on the ground. The radiometric resolution of the 4 band image composites is 12-bit. The imagery was processed to remove atmospheric effects such as haze and to highlight the spectral response of submerged areas. The imagery has some exposure variation between adjacent flight lines and between sunlit and cloud shaded areas. The 4 band imagery is provided in GeoTIFF format. The imagery was captured at a spatial resolution (pixel size) of 0.25m x 0.25m and was delivered in a Universal Transverse Mercator - Zone 8 projection using the NAD1983 datum.
- 2011-10-01 00:00:00 - The benthic habitat map was developed through image segmentation using the Trimble eCognition Developer software. Image segments representing spectrally homogenous area in the source imagery were generated using a scale factor 20-25. A draft map was generated by classifying the image segments into one of 5 habitat classes (coastal marsh, unconsolidated sediments, unconsolidated bottom, macroalgae, and eelgrass) using the Nearest Neighbor classifier in Trimble eCognition Developer. Training data was derived through photo interpretation using available provided field information as a reference. The resulting draft map was reviewed by the project team through visual inspection and comparison to ground photos. Additional edits were made through manual labeling of the segments. Due to poor water clarity in Klawock Lagoon eelgrass habitat boundaries in the lagoon were generated by staff kayaking along the perimeter of the beds with a GPS logging their position every second. Two of these kayak-digitized polygons (one collected in August 2010 and one in September 2011) were merged to create a maximum extent of eelgrass polygon which was incorporated into the final benthic habitat map.
- 2015-01-01 00:00:00 - The data were converted from a single ESRI polygon shapefile classified according to the System for Classifying Habitats in Estuarine and Marine Environments (SCHEME) to the Coastal and Marine Ecological Classification Standard (CMECS) 2012 format (which can be found at https://coast.noaa.gov/digitalcoast/tools/cmecs-crosswalk) which produces separate geoform, geoform, and geoform feature layers from the original input benthic habitat dataset. This geoform feature layer contains CMECS geoform component attributes where an "Equal" or "Nearly Equal" SCHEME value was present in the original data. Polygons for which no geoform information was present have been removed. No other changes to the original polygon boundaries or any other alterations of the original SCHEME data were made during this process.
(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)
- 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.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.
Data is available upon request
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.