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 lines representing coastal hydrography features that are not captured in the HYDROP polygon data layer. Typically, the features found in the HYDROL data layer are piers, breakwaters, and inland rivers and creeks.
This data set is a portion of the ESI data for Florida. 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 HYDROP (Hydrography Polygons) 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.
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-05-01 00:00:00 - The shoreline locations and features were derived from the integration of the following digital data: National Oceanic and Atmospheric Administration (NOAA) Continually Updated Shoreline Product (CUSP) (9 Aug 2011); the U.S. Fish and Wildlife Service (USFWS) National Wetlands Inventory (NWI) dataset (1 Oct 2014); the Florida Fish and Wildlife Conservation (FFWCC) Florida Shoreline (1:12,000 scale) dataset (1 Feb 2006); the South West Florida Water Management District (SWFWMD) Tarpon Springs to Boca Grande Seagrass dataset (2014) and Springs Coast Seagrass dataset (2012); the U.S. Geological Survey (USGS) National Hydrography Dataset (NHD) Best Resolution for Florida 20151030 State or Territory dataset; and manual digitization at approximately 1:1,000 scale using ortho-rectified aerial imagery resources from the Florida Department of Revenue (2012-2014), the Florida Department of Transportation (2013), SWFWMD Springs Coast Seagrass (2012) and Tarpon Springs to Boca Grande Seagrass (2014), and NOAA Cedar Key, FL Mean High Water (MHW) Integrated Ocean and Coastal Mapping (IOCM) Digital Sensor System (DSS) Natural Color 8 bit imagery (2015). See the Lineage section for additional information on the type of source data for this data layer. The HYDROL data layer contains select lines also captured in the ESIL data layer. The HYDROL layer contains only piers, breakwaters, groins, hydrographic centerlines, and the area of interest (AOI) extent of the atlas. All piers, breakwaters, and groins 24 meters (m) or greater in length were manually digitized at approximately 1:1,000 scale using the ortho-rectified aerial imagery (prioritized by currency, spectral resolution, and tidal coordination where available). Hydrographic centerlines were found in the NHD dataset. The vector source data for each HYDROL feature were recorded in the [SOURCE_ID] field in the attribute table. After the initial shoreline 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 HYDROL 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.