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 sensitive biological resource data for sea turtles, estuarine turtles, and T/E herps in Chesapeake Bay and the Outer Coasts of Maryland and Virginia. Vector polygons in this data set represent herpetofauna distribtution and nesting areas. Species specific abundance, seasonality, status, life history, and source information are stored in relational data tables (described below) designed to be used in conjunction with this spatial data layer. This data set comprises a portion of the ESI data for Chesapeake Bay and the Outer Coasts of Maryland and Virginia. ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil. The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources.
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):
This atlas supersedes two separate first edition atlases, Virginia (2005, #25) and Maryland (2007, #47).
- 2016-09-01 00:00:00 - Nesting and in-water distribution data for diamondback terrapins were provided by VIMS (in-water data set), USGS (nesting data set), and USFWS (pers. comm.). The VIMS data set was based on 2012 and 2013 spring-summer surveys at 165 sites and was conducted to study the relationship between terrestrial-aquatic connectivity and the distribution of an estuarine turtle. The results of the survey included predicted probability of occupancy of diamondback terrapins in the Chesapeake Bay, and the "high" and "low" probabilities of occupancy that were determined during the study were adapted for inclusion and represented as likely terrapin distribution polygons in the ESI. The USGS nesting data set was based on the results of the Patuxent Wildlife Research Center investigation of over 3,000 kilometers of Chesapeake Bay shoreline in 2002 for terrapins, tracks, and active and disturbed nests. Green (FT/MD ST, VA ST), Kemp's ridley (FE/MD SE, VA SE), leatherback (FE/MD SE, VA SE) and loggerhead (FT/MD ST, VA ST) sea turtles were mapped in this atlas. Many barrier island, and some mainland, outer sand beaches are important nesting habitat for loggerhead sea turtle, and potential (but very rare) nesting habitat for Kemp's ridley and green sea turtles. Nesting typically occurs in Virginia and Maryland from May to August with hatching from June-October (loggerhead sea turtle). Data that represent documented nesting in Virginia from 1970-2015 were provided by VDGIF. The concentration values were based on the range of nest counts observed on a particular stretch of beach over time (e.g., 0-8 nests, <10 nests). Beach buffers were used rather than point locations due to the potential for beaches adjacent to known nest sites to also provide suitable nesting habitats. Green sea turtle and Kemp's ridley sea turtle were documented as having 'false crawls' only and no nest counts. Additional nesting and general distribution and seasonality information were provided during interviews with NPS, USFWS, and the VA Aquarium. Distributions for the barking treefrog (VA ST) and chicken turtle (VA SE) were mapped using data provided as part of VDGIF's Wildlife Environmental Review Map Service (WERMS) database. Records of both species were pulled from survey dates between the years 1996 and 2013, with 2013 being the most recent surveys for herpetofauna in the database. The above digital and/or hardcopy sources were compiled by the project biologist to create the HERP data layer. 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 HERP 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.