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 for locations of historical sites; vector lines or locations of natural gas and intrastate pipelines, bridges, rail routes, and tunnels; and vector points depicting airports, abandoned vessels, beaches, EPA facilities, heliports, historical sites, NOAA facilities, waste disposal, and wash over sites in Chesapeake Bay and the Outer Coasts of Maryland and Virginia.
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. The entirety of the ESI Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons, Points; NAVIGATION-MARINE Polygons, Points, Lines; POLITICAL-JURISDICTIONAL Polygons, Points, Lines; RESOURCE MANAGEMENT Polygons, Points; SOCECON Polygons, Points, Lines; and NATURAL HAZARD Polygons.
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 Chesapeake Bay and Outer Coasts of Maryland and Virginia 2016 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-09-01 00:00:00 - This atlas is the second edition of two separate first edition atlases, Virginia (2005, #25) and Maryland (2007, #47). Due to imagery inconsistencies and data precision the spatial accuracy of socioeconomic point data could appear skewed. Sources of data used to depict human-use resources in this data layer include: 1) Locations of airports, airfields, landing strips, heliports, etc. were downloaded from the National Transportation Atlas Databases maintained by the Federal Aviation Administration; 2) Data on locations of abandoned and derelict vessels comes from NOAA\x92s Office of Coast Survey Automated Wrecks and Obstructions Information System (AWOIS); 3) Locations of recreational beaches used for activities such as swimming, sun-bathing, fishing, etc. were mapped from expert knowledge; 4) U.S. Environmental Protection Agency (EPA) facility locations represent facilities that maintain risk management plans describing their hazards and prevention activities as required by the EPA Risk Management Plan (RMP), facilities that manufacture, process, or use certain chemicals in amounts above established levels regulated by the EPA Toxic Release Inventory System (TRIS) program, facilities with permits from the National Pollutant Discharge Elimination System (NPDES), and facilities that the EPA has identified and monitors for storing certain quantities of oil (OIL). The data were provided by EPA to NOAA's Emergency Response Division; 5) Historical sites were depicted from sites in the National Park Service (NPS) National Register of Historic Places (2007) and Maryland State Historic Preservation Office (The Maryland Historical Trust); 6) Locations of NOAA facilities were digitized as points from address matching and verified with Google Earth imagery; 7) Locations of ocean disposal sites for dredged material removed from the bottom of waterbodies in order to maintain navigation channels and berthing areas were provided by NOAA\x92s Ocean Service, Office of Coastal Management; and 8) Washover locations are represented by points that were digitized from ESRI World Imagery by Research Planning, Inc. at a scale of 1:8,000. A washover, or washover fan, is a relatively flat surface on the top of a barrier spit complex that slopes gently landward. It is usually created when water, forced landward by breaking waves, flows across the top of the barrier spit during high spring tides or storms. This process creates a flattened-off surface along which sand is transported across the top of the spit into the standing water (lagoon) or marsh landward of the spit. The resulting deposit usually has a fan-like shape. The above digital and/or hardcopy sources were compiled by the project biologist to create the SOCECON_POINT data layer.
- 2016-09-01 00:00:00 - Sources of data used to depict human-use resources in this data layer include: 1) Natural gas inter/intrastate lines were provided by the U.S. Energy Information Association (USEIA); 2) Bridges were provided by NOAA Department of Commerce (DOC) National Ocean Service\x92s (NOS) Continually Updated Shoreline Product (CUSP) and also NOAA National Geodetic Survey\x92s (NGS) Composite/National Shoreline Product; 3): Locations of railways were downloaded from the National Transportation Atlas Databases, maintained by the Department of Transportation; and 4) Locations of tunnels were digitized as lines from information provided by Virginia Department of Transportation and Maryland Transportation Authority and verified with Google Earth imagery by Research Planning, Inc. The above digital and/or hardcopy sources were compiled by the project biologist to create the SOCECON_LINE data layer.
- 2016-09-01 00:00:00 - Historical sites were derived from locations in the National Park Service (NPS) National Register of Historic Places (2007) dataset and the Maryland State Historic Preservation Office (The Maryland Historical Trust). The above digital and/or hardcopy sources were compiled by the project biologist to create the SOCECON_POLY data layer.
- 2016-09-01 00:00:00 - Depending on the type of source data, three general approaches are used for compiling the data layer: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:24,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. See the Lineage section for additional information on the type of source data for this data layer. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the SOCECON_POINT data layer are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are 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.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.