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:
Nassau Grouper (Proposed)
1.2. Summary description of the data:

This sections provides the Simplified Geographic Description for each of the Proposed Units.

The 19 Proposed Critical Habitat Units for Nassau Grouper include:

Navassa Island Unit. Waters surrounding Navassa Island. Area = 2.468 sq. km.

Puerto Rico Unit 1 - Mona Island. Waters off the west and south coast of Mona Island. Area = 18.344 sq. km.

Puerto Rico Unit 2 - Desecheo Island. Waters off the southwest coast of the island. Area = 0.468 sq. km.

Puerto Rico Unit 3 - Southwest. Waters off the southwest coast of the Puerto Rico main island. Area = 112.393 sq. km.

Puerto Rico Unit 4 - Northeast. Waters off the northeast coast of the Puerto Rico main island. Area = 48.754 sq. km.

Puerto Rico Unit 5 - Vieques Island. Waters off the west and northeast, east, and southeast coasts of the island. Area = 9.488 sq. km.

Puerto Rico Unit 6 - Culebra/Culebrita Islands. The Culebra area consists of waters off the southeastern Culebra coastline. The Culebrita area consists of waters off the western and southern coasts of the island. Area = 4.149 sq. km.

United States Virgin Island Unit 1- St Thomas. Waters off the east coast of St. Thomas Island and waters off the southwest, south, and southeast coast of the Water Island. Area = 9.183 sq. km.

United States Virgin Island Unit 2- St. John. Waters off the east coast of the island. Area = 6.552 sq. km.

United States Virgin Island Unit 3- St. Croix. Waters off the east end of St. Croix Island and waters off the north coast of Buck Island. Area = 50.35 sq. km.

Florida Unit 1 – Biscayne Bay/Key Largo. Waters south of Rickenbacker Causeway, including portions of waters from the coastline into Biscayne Bay, and waters off the eastern coastline to 80°29'21" W, 25° 01' 59" N. Area = 1279.696.

Florida Unit 2 - Marathon. Waters off the southern shoreline approximately between Knights Key to 80°55'51"W, 24° 46' 26" N. Area = 172.379.

Florida Unit 3 - Big Pine Key to Geiger Key. Waters off the south side of coastline and US 1 from approximately Geiger Key to Big Pine Key. Area = 372.369 sq. km.

Florida Unit 4 - Key West. Shoal waters south of Woman Key. Area = 127.078 sq. km.

Florida Unit 5 - New Ground Shoal. New Ground Shoal waters. Area = 31.042 sq. km.

Florida Unit 6 - Halfmoon Shoal. Halfmoon Shoal waters. Area = 33.615 sq. km.

Florida Unit 7 - Dry Tortugas. Waters encompassing Loggerhead Key and waters surrounding Garden Key and Bush Key. Area = 4.437 sq. km.

Spawning Site Unit 1 - Bajo de Sico. All waters encompassed by 100m isobath bounded in the Bajo de Sico spawning area bound within the following coordinates: A) 67°26’13”W, 18°15’23”N, B) 67°23’ 08”W, 18°15’26”N, C) 67°26’ 06”W, 18°12’55”N, and D) 67°26’ 13”W, 18°12’56”N. Area = 10.738 sq. km.

Spawning Site Unit 2 - Grammanik Bank/Hind Bank. All waters which make up the Hind Bank and the Grammanik Bank, interconnecting waters between these banks, and waters extending out to the 200 fathom line directly south from Grammanik Bank. Area = 59.6907 sq. km.

Source of Base Data Creating these Units:

The shoreline was created using Acropora critical habitat data (from NOAA NCCOS Benthic Habitat Mapping 2000-2002 - land and mangrove attribute combined for shoreline) https://coastalscience.noaa.gov/project/benthic-habitat-mapping-puerto-rico-virgin-islands/. Contours were derived from the National Geophysical Data Center’s 2004 U.S. Coastal Relief Model https://www.ngdc.noaa.gov/mgg/coastal/crm.html. The NCCOS Benthic Habitat Mapping program provides data and maps at http://products.coastalscience.noaa.gov/collections/benthic/default.aspx, which was used to pull in substrate data. Benthic data was also used from The Nature Conservancy and can be found and downloaded here: https://sites.google.com/view/caribbean-marine-maps

Standardized metadata has been prepopulated for the Fields and Values and the standard spatial reference is the World Geodetic System 1984 geographic coordinate system (GCS_WGS_1984, EPSG well-known identifier 4326).

Attribute Values:

Shape = Feature Class, Polygon Data.

ID = Species ID

Scientific Name = Genus species

Common Name = Common Name of species

Listing Status = Federal status of a taxon under the federal Endangered Species Act.

Critical Habitat Status = Status of Critical Habitat Designation (i.e. Proposed or Designated)

Unit = Location of Identified Critical Habitat

Taxon = Taxon

Lead Office = NMFS Regional Office

Federal Register Rule = Public official notice of Rule

Publication Date = Publication Date of Federal Register Notice

Effective Date = Effective Date of Rule

Area SqKm = Area of Unit in Square Kilometers

Create Date = Last Date Polygon and Attribute Data were Modified

Notes = notes

InPort URL = MetaData URL Link (InPort)

Habitat Type = general location of critical habitats

eCFR = Link to designated critical habitat regulatory text and maps published in the eCFR.

Shape_Length = dynamic geodatabase field. Automatically calculated in the units of the output coordinate system specified by the Spatial Reference parameter by ESRI.

Shape_Area = dynamic geodatabase field. Automatically calculated in the units of the output coordinate system specified by the Spatial Reference parameter by ESRI.

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:
2022-10-17 00:00:00+0000
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: -82.9275, E: -64.562313, N: 25.7482, S: 17.686503
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:
Jonathan Molineaux
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:
jonathan.molineaux@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:
301-427-8440
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:
No information found
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):
No information found
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)
  • 3.1. Responsible Party for Data Management
  • 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.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
  • 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.3. Data access methods or services offered
  • 7.4. Approximate delay between data collection and dissemination
  • 8.1. Actual or planned long-term data archive location
  • 8.2. Data storage facility prior to being sent to an archive facility
  • 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:
No information found.
7.2. Name of organization of facility providing data access:
NMFS Office Of Protected Resources (OPR)
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:
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:
No information found
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):
No information found
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