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 data set contains vector polygons representing coastal habitats of North Carolina, classified by their susceptibility to oiling. The Environmental Sensitivity Index (ESI) classification system, developed by NOAA, considers several natural and biological factors when ranking an intertidal range's sensitivity and persistence of oil impacts. As a whole, the ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil, and include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. See also the ESIL (ESI Shoreline Lines) data layer for additional information about shorelines and intertidal habitats.
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.
This reflects the extent of all land and water features included in the overall North Carolina ESI study region. The bounding box for this particular feature class may vary depending on occurrences identified and mapped.
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):
- 2016-01-01 00:00:00 - The intertidal shoreline habitats as well as inland wetland habitats were derived from the integration of the following digital data: the U.S. Fish and Wildlife Service (USFWS) National Wetlands Inventory (NWI) dataset (2010) and manual digitization at approximately 1:1,000 scale from ortho-rectified aerial imagery resources from the North Carolina Center for Geographic Information and Analysis (2012), Environmental System Research Institute (ESRI) World Imagery (2014), and the NOAA Ortho-rectified Mosaic of Eastern Coastline - Hurricane Sandy Impact Area (20141023). See the Lineage section for additional information on the type of source data for this data layer. To create the base ESIP data layer, the NWI vector dataset was used as a base in a file geodatabase feature class. The vector source data for each ESIL feature were recorded in the [SOURCE_ID] field in the attribute table. The physiographic environment recorded in the [ENVIR] field was determined using the NWI dataset. The feature topology was checked for slivers and overlap before manual clean-up and classification of the polygons began. First, the NWI classifications were cross-walked to the ESI classification system. Next, manual digitization efforts consisted of reshaping polygon extents and correcting crosswalked ESI codes, as needed, at approximately 1:1,000 scale using the ortho-rectified aerial imagery (prioritized by currency, spectral resolution, and tidal coordination where available) which were recorded in the [ESI_SOURCE] field of the ESIP layer. For shoreline segments photo-interpreted as having an adjacent tidal flat that was not present in the source data, new tidal flat polygons were digitized. A minimum mapping unit (mmu) of 0.1 acres was used for polygonal features. All wetland and tidal flat polygons adjacent to the ESIL shoreline were snapped to ESIL shoreline segments using a series of both automated and manual steps. After the initial habitat classification, the data were checked for logical consistency errors and re-checked for topology errors. The ESI, biology, and human-use data were compiled into the standard ESI digital data format. A QA/QC period for NOAA and participating resource experts was conducted and, as needed, edits to the ESIP data layer were made based on the recommendations of the experts, and final hardcopy maps and digital data were created.
(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)
- 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.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.
Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).
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.