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 the coastal shoreline and hydrography used in the creation of the Environmental Sensitivity Index (ESI) for North New York and Long Island Sound. 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 HYDROL (Hydrography Lines), HYDROP (Hydrography Polygons), ESIL (ESI Shoreline Types - Lines) data layer for additional shoreline/hydrography information.
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 Long Island Sound 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 shoreline and classifications were fully updated using the sources and methods described below. The shoreline and intertidal habitats were delineated using a mapped sequence of Light Detection and Ranging (LiDAR) and high resolution digital orthophotography datasets. The LiDAR data was acquired in 2014 as part of a post-Super Storm Sandy contract for the United States Geological Survey (USGS). This task required the LiDAR data be collected at a nominal pulse spacing (NPS) of 0.7 meters. The window for tidally impacted waters within the area of interest was mean low water (MLW) +/- 2 hours exclusive of neap tide. Seven (7) missions were flown between April 3, 2014 and April 21, 2014, as part of the USGS project.The base shoreline was compiled at Mean Higher High Water (MHHW) first by LiDAR extraction, then refined within a Geographic Information System (GIS) utilizing high resolution digital orthophotos. After the shoreline was delineated, digital ortho-imagery from various sources was used to classify shoreline segments using the nationally, standardized ESI scale (see below). Imagery from the New York State Office of Information Technology Service (2013 and 2011), the New Jersey Office of Information Technology (2013), Connecticut Department of Transportation (2012), as well as various imagery sources for Google Earth and Bing Maps (2014) was used during the classification phase. Imagery was produced by Woolpert as part of the ESI data collection effort; however, schedules dictated that shoreline classification must occur prior to the completion of imagery collection and processing. Therefore, the new imagery was not used for the shoreline classification.Shoreline features of 10 meters (m) or greater in length were classified. In addition, wetland polygon datasets originally created by the United States Fish and Wildlife Service National Wetland Inventory (NWI) were modified and updated to be used in conjunction with the ESI shoreline. The data was visually reviewed and classified against the aerial imagery and adjusted where necessary to allow for proper classification. All classifications were determined by the specifications outlined in the Environmental Sensitivity Index Guidelines version 3.0 (2002). Where necessary, multiple types were described for each shoreline segment. GIS quality control measures were implemented to ensure that all data met the required specifications. (Citation: NYS Digital Ortho-imagery Program)
(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.