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
During the spring of 1999, the Delaware Coastal Programs(DCP) identified the spatial extent of macroalgae in the shallow portions of Rehoboth Bay utilizing traditional photogrammetric methods. The DCP used true color aerial photographs, image processing software, a geographical information system (GIS), and a limited field survey to identify 1.88 square kilometers of macroalgae in all but the deepest parts of the bay. Turbid conditions prevented identification of the full extent of the vegetation.Although the 1999 effort was highly successful, it was clear that aerial photography could not penetrate to the deeper parts of the bay or where conditions were turbid.For the 2000 effort, the DCP partnered with the National Oceanic and Atmospheric Administration (NOAA) Office for Coastal Management Coastal Remote Sensing Program. The Benthic Habitat Mapping project, a part of the Center's Coastal Remote Sensing program, utilized a RoxAnn acoustic sensor to identify benthic cover in turbid areas of the bay June 12- 16, 2000.The instrument was used to identify bottom type by extracting data on bottom roughness and bottom hardness from the primary and secondary sounder echoes. The data is classified on-the-fly, using a towed video camera for field validation, and subject to a post-processing classification. The unit collected data throughout the bay in areas greater than 1.4 meters in depth and serves as a powerful complement to the aerial photography. The RoxAnn data points were exported into a geographic information system (GIS) and post-processed to remove unreliable data points and re-classified. This data set is comprised of the cleaned, attributed point data. The attributes include location, date, time, depth, field derived classification,and the classification derived from post-processing the data. This system is fully described in "Development of a System for Classification of Habitats in Estuarine and Marine Environments (SCHEME) for Florida, Report to U.S. EPA - Gulf of Mexico Program, Florida Fish and Wildlife Conservation Commission, Florida Marine Research Institute.Review Draft 12/04/02."
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):
- 2000-06-19 00:00:00 - In June of 2000, the RoxAnn acoustic sensor was run in North-South and East-West transects across Rehoboth bay,recording geographically referenced point measurements of the acoustic data. The RoxAnn system analyzes two acoustic signals, bottom roughness (E1) and bottom hardness (E2).The ratios of these two measurements were calibrated in the field to known bottom types. Ground-truthing the measurements in the field was accomplished by under water video, grab samples and visual verification. The field database collected from June 12 - 16, 2000 was exported from the RoxMap software as a text file.Unreliable data points indicated by impossible bathymetry data were removed (i.e. depths in excess of 3 meters). In addition, series of identical points were reduced to the initial value and the remaining points from the data set.The fifteen original field derived classes developed in the field varied in level of descriptiveness: ulva; mud and algae; sand and algae; algae; gracilaria; gracilaria on mud; sand; bioturbated mud; shell/mud/algae; sandy mud;hard sand; mud with 15% algae; soft mud; mud and unknown.These overlapping and varying classifications were grouped to four general classes which comprised the bottom types observed equally general: algae (greater than 15%), mud(15% algae cover or less on soft mud), sand (15% algae or less on harder mud/sand) and unknown. The benthic data was then classified according to the System for Classification of Habitats in Estuarine and Marine Environments (SCHEME).This system is fully described in "Development of a System for Classification of Habitats in Estuarine and Marine Environments (SCHEME) for Florida, Report to U.S. EPA -Gulf of Mexico Program, Florida Fish and Wildlife Conservation Commission, Florida Marine Research Institute.Review Draft 12/04/02." These classes were then aggregated to either algae or no algae classes.
(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.
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.