Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:78518 | Published / External
InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.
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
These data depict areas of aquatic beds of rooted vascular plants located in coastal North Carolina. These areas primarily consist of submersed rooted vascular (SRV) plants, with some inclusion of floating rooted vascular (FRV) plants. To ensure consistency with other similar benthic datasets developed by NOAA, the original nomenclature and definitions from NOAA's Coastal Change Analysis Program (C-CAP) were crosswalked with the Florida System for Classification of Habitats in Estuarine and Marine Environments (SCHEME). The goal of this effort was to enhance the understanding of coastal photic submersed lands and how they are interconnected with wetlands, uplands, and living marine organisms.
The layers available within the data download include biotic, geoform, and substrate.
Partners: State of North Carolina
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:
- 1990-01-01 00:00:00 - Acquisition of metric aerial photography: Conventional color aerial photography was collected in several missions between 1985 and 1990 following the protocols described in NOAA Technical Report NMFS 123. Both film diapositives and paper prints were used for the interpretation.
- 1990-01-01 00:00:00 - Compilation of photographic information: Aerial photos were interpreted and habitats delineated on acetate overlays affixed to the film. Field information was used to guide this mapping process. The interpreted photo delineations were then transferred to hard-copy base maps using a zoom-transfer scope to fit the polygons to a planimetric base. Photointerpretation with a Wild AVIOPRET stereoscope. Photographs and data were compiled on a Bausch and Lomb stereo zoom transfer scope at a scale of 1:24,000 on USGS 7.5' topographic maps or on NOAA shoreline topographic sheets scaled to 1:24,000 (original scale 1:20,000). Data is a merge of several coverages dependent on map base, photo mission, and photographic scale.
- Digitization of compiled photographic interpretations: 1:24,000 scale bases were supplied to CGIA by the NOAA/NMFS/SEFSC/Beaufort Lab. These were used to digitize the delineated areas of SRV. All digital files were later compiled into one digital GIS data set. Checkplots were created for review by the Beaufort Lab and any corrections made.
- 2015-01-01 00:00:00 - The data were converted from a single ESRI polygon data set 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. This produced separate biotic, geoform, and substrate feature layers from the original input benthic habitat dataset. Each of the three feature layers contain respective CMECS biotic, geoform, and substrate component attributes where an "Equal" or "Nearly Equal" SCHEME value was present in the original data. Polygons for which no biotic, geoform, or substrate 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.
- 2025-08-01 00:00:00 - Standardized common design elements, cleaned up field content, repaired geometry, and projected to NAD83.
(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)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 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.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.
https://benthic-data-noaa.hub.arcgis.com/
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.
