InPort Release 5.2.0 Downtime: Thursday, May 19 @ 2:00pm - 3:30pm Eastern. InPort and its associated services will be under maintenance and unavailable for the deployment of InPort Release 5.2.0. Downtime Schedule Thursday, May 19, 2022 1:00pm - 2:30pm Eastern / 10:00am - 11:30am Pacific / 7:00am - 8:30am Hawaii Impacted Areas - InPort Website: https://www.fisheries.noaa.gov/inpor...
View All
Search Help Show/Hide Menu

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
Northwest Peninsular Florida 2016 ESI REPTILE & AMPHIBIAN Polygons, Points
1.2. Summary description of the data:

This data set contains sensitive biological resource data for sea turtles and other federally and/or state endangered, threatened, or rare reptiles and amphibians in Northwest Peninsular Florida. Vector polygons and points in this data set represent federally and state protected reptile and amphibian concentration areas, nesting areas, vulnerable occurrences, and general use areas. Species-specific abundance, seasonality, status, life history, and source information are stored in associated data tables (described below) designed to be used in conjunction with this spatial data layer. This data set is a portion of the ESI data for Northwest Peninsular 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.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2016 to 2018
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -84.8957, E: -82.2746, N: 30.0422, S: 26.4897
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Map (digital)
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
ESI Program Manager
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
orr.esi@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
No information found
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
ESI Program Manager
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
No information found
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Process Steps:

  • 2016-12-01 00:00:00 - Overview: A large portion of the data for herpetofauna were received and mapped as point locations. These point locations represent the most accurate spatial data available, but do not represent the full extent of species' ranges. Seasonality information presented with point locations is meant to represent all life stages potentially present within the full (unmapped) species range. Several species mapped in this atlas were masked for data sensitivity purposes. These species are mapped as "Rare reptile/amphibian" and "Rare amphibian".
  • 2016-12-01 00:00:00 - Sea Turtles: Five species of sea turtles use Florida beaches for nesting during the spring and summer months: loggerhead, hawksbill, leatherback, green, and Kemp's ridley. The loggerhead sea turtle (state and federally threatened) is the most numerous. A federally designated critical habitat area in nearshore waters west of Siesta and Long Boat Keys close to Sarasota has been designated to protect this species. This critical habitat was designated due to its importance as a nearshore reproductive habitat for this species. Mapped nesting locations for green, Kemp's ridley, and loggerhead sea turtles were based on a data from FWRI. The FWRI coordinates the collection of sea turtle nesting data through the annual Statewide Nesting Beach Survey Program. Nest density and locational information are summarized as a vector digital data set ranking the nesting locations under the density classes "low", "medium", or "high". These density classes were determined based on the average nest densities in relation to the number of nests per kilometer of surveyed nesting beach habitat. The range of density values are broken at 25% and 75. Density classes were created where "low" corresponds with a density that is less than or equal to the lower 25%, "medium" corresponds with a density that is greater than 25% but less than or equal to 75%, and "high" corresponds to nest density values greater than 75%. Only nesting beaches with density classes of "low" and "medium" were encountered in this region, and these values are included in the concentration field. The following narrative was provided by Robert Hardy and Anne Meylan of the FWC/FWRI on sea turtle nesting, seasonality, and in-water distribution.
  • 2016-12-01 00:00:00 - Sea Turtles Nesting: FWRI coordinates the data collection for Florida's sea turtle nesting beaches. Beaches are surveyed annually as part of the Statewide Nesting Beach Survey Program. We provide data on nest density for the most recent five years and nest occurrence, since 1979. Sea turtle nest density and occurrence data are summarized and provided by FWRI at the following website: http://myfwc.com/research/wildlife/sea-turtles/nesting/nesting-atlas/. These data may be downloaded from FWRI's GIS data catalog at the following website: http://geodata.myfwc.com/ (enter "sea turtle nesting" as the search term). Please refer to these data for detailed nesting information. A brief summary of sea turtle nesting is provided below. Within the west-peninsular Florida (WPFL) plan area, sea turtle nesting beach habitat ranges from Anclote Key to Casey Key (from north to south). Sea turtle nesting within this region typically begins during mid-April and extends through the end of October. Mapped nesting locations for hawksbill and leatherback sea turtles were included based on documentation in Eaton et al. 2008, Hardy et al. 2014, and Witherington et al. 2012. These species less commonly nest in the region, so "rare" was added to the concentration values. Loggerhead: Loggerhead sea turtle nesting occurs on all seaward-facing sandy beaches throughout the WPFL ESI region. The highest loggerhead nest density occurs in the southern portion of the plan area. Green: Green sea turtle nesting has been documented on most seaward-facing sandy beaches throughout the WPFL ESI region with the highest nesting density occurring in the southern portion of the plan area. Leatherback: Leatherback sea turtle nesting is rare within the WPFL ESI region. Leatherback nesting has been observed on Longboat Key. Hawksbill: Hawksbill sea turtle nesting is rare within the WPFL ESI region. Hawksbill nesting has been observed on Longboat Key. Kemp's ridley: Kemp's ridley sea turtle nesting is rare within the WPFL ESI region. Kemp's ridley nesting has been observed on beaches of Anclote Key State Park, Caladesi Island State Park, Middle and Northern Pinellas County, and Siesta Key.
  • Sea Turtles In-water: The potential presence of sea turtles within south Florida waters was determined based on an examination of all available in-water sea turtle research information (Eaton et al. 2008). We evaluated the in-water presence of loggerhead, green, leatherback, hawksbill and Kemp's ridley sea turtles. We also incorporated occurrence information derived from Sea Turtle Stranding and Salvage Network records from 1986 through present; these data may be downloaded from FWRI's GIS data catalog at the following website: http://geodata.myfwc.com/ (enter "sea turtle stranding" as the search term). Potential presence of sea turtles is described by species and life stage (adult or non-adult, categories described by Eaton et al., 2008). Loggerhead: Loggerhead sea turtles of all life stages may be present in nearshore and offshore waters of WPFL throughout the year. A major residence area exists within deep reef and hardbottom habitats of the West Florida Shelf, particularly from 35 - 70 m depth (Hardy et al. 2014). Surface-pelagic juvenile loggerheads occur in offshore waters of this area (Witherington et al. 2012). Green: Non-adult green sea turtles are present in inshore waters, particularly within seagrass habitats, throughout the year. Adult green sea turtles are not often documented but do occur during the nesting season. Surface-pelagic juvenile green sea turtles occur in offshore waters of this area (Witherington et al. 2012). Leatherback: Leatherback sea turtles may be encountered in offshore waters throughout the year. Hawksbill: Non-adult hawksbill sea turtles have been documented throughout the region in stranding records. Adult hawksbills are not often documented in WPFL although they may occur. Surface-pelagic juvenile hawksbills occur in offshore waters of this area (Witherington et al. 2012). Kemp's ridley: Kemp's ridley sea turtles may be present throughout the WPFL plan area during all months. Surface-pelagic juvenile Kemp's ridleys occur in offshore waters of this area (Witherington et al. 2012).
  • 2016-12-01 00:00:00 - American alligator and American crocodile: The American alligator is federally listed as threatened due to its similarity in appearance to the American crocodile. The data presented in this atlas show some occurrences and a known nesting area for American alligator, but this species is likely more widespread throughout the region. In contrast, the range of the American crocodile does not typically extend to this region, although there was one documented observation of this species near Tampa.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

  • 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?
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
No information found
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
No information found
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
No information found
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

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).

7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
No information found
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office of Response and Restoration - Seattle, WA
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank