System Maintenance Notice, Monday, December 5, 2022 @ 1pm-5pm Eastern. The Operations Team will be performing system maintenance. During this scheduled downtime, InPort will not be available.
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:
Puerto Rico Land-Based Threat to Benthic Habitats
1.2. Summary description of the data:

This data set describes the potential threat of sediment delivery and land-based sources of pollution to benthic habitats. This dataset is derived from NOAA's study, the Benthic Habitats of Puerto Rico and the U.S. Virgin Islands. The Benthic Habitats data is the result of a cooperative effort between NOAA's National Centers for Coastal Ocean Science (NCCOS), U.S. Geological Survey, National Park Service, and the National Geophysical Data Center, to produce benthic habitat maps and georeferenced imagery for Puerto Rico. This project was conducted in support of the U.S. Coral Reef Task Force.

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:
1990-01-01 to 2001-01-01
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: -67.966627, E: -65.212517, N: 18.551281, S: 17.81293
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.)
vector digital data
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:
NCCOS Scientific Data Coordinator
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:
NCCOS.data@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:
NCCOS Scientific Data Coordinator
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:

  • 2005-10-01 00:00:00 - Ground control points, camera calibration data, and USGS DTM data were used to orthorectify 500 dpi scans of the aerial photos using Socet Set Version 4.2.1. Orthorectified images were then loaded into ArcView 3.2 with the Image Analyst and Habitat Digitizer Extensions activated. This allowed the photointerpreter to interpret features, delineate and attribute benthic habitat directly into a digital reference system. The data were saved as ArcView shapefiles.to estimate the potential threat to each polygon, the following methodology was employed:Step 1) The first step of the analysis involves estimating likely relative erosion rates for each 30 m resolution grid cell using a modified, simplified form of the Revised Universal Soil Loss Equation (RUSLE) (USDA, 1989). Information on slope, land cover type, precipitation, and soil porosity were integrated to develop an indicator of relative erosion potential (REP) for all land areas within Puerto Rico. Inputs: (REP relies upon four input data sets, three of which were described under the analysis of vulnerability to erosion, above.) 4. Slope (percentage) - for each 30m grid cell, derived from the (raw) DEM (without hydrologic correction.)5. Relative erosion rate by land cover type. Relative erosion rates for each land cover type were calculated using a look-up table. Land cover categories from NASA Geocover-LC products covering Puerto Rico (http://www.MDafederal.com/geocover/geocoverlc/) were reclassified to relative erosion rates, ranging from 15 (for forest) to 220 for barren land. (below) These relative erosion rates are based on published work involving conversion factors. 6.Precipitation during the peak rainfall month (in millimeters) - Long-term average monthly precipitation values for the peak rainfall month of the year is an interpolated grid based on data for climate stations from NOAA's National Climate Data Center (NCDC). This variable was chosen because it is more indicative of the rainy season and more extreme events during the year.7.Soil erodibility factor (K-ffactor) - the K-ffactor was obtained from the SSURGO database of the USDA.Land Cover Type, Grid Code, Relative Erosion RateDeciduous Forest, 1, 15Evergreen Forest, 2, 15Shrub/Scrub, 3, 50Grassland, 4, 125Barren, 5, 220Urban, 6, 210Agriculture, 7, 200Permanent Wetland, 9, 80Mangrove, 10, 80Water, 11, 5Cloud/No Data, 13, 0Equation 2:Relative Erosion Potential (REP) = Slope(%) x precip (mm for peak rainfall month) x soil k-ffactor x relative erosion rate for land cover type / 1000The grid is divided by 1000 and converted to integer for a better data range and easier display.The analysis was implemented in ESRI ArcView 3.2 software, using the map calculator function of Spatial Analyst, which is also available in ArcMap. The raster analysis was done at 30 m resolution in UTM projection (Zone 20N, WGS84.) (continued...)
  • 2005-10-01 00:00:00 - (continued from above) Two indicators indicative of erosion within the watershed were calculated for each basin:mean REP for the basin (an indicator of average erosion rates for the basin) (REP_MEAN), and total relative erosion within the basin (REP_SUM).Step 2) An indicator of relative sediment delivery at the river mouth was estimated by multiplying total relative erosion in the basin (REP_SUM) by the sediment delivery ratio (SDR) for the basin, which is a function of watershed size. SDR reflects the percentage of erosion within the basin (REP_SUM) which reaches the river mouth.Equation 3:Sediment Delivery Ratio (SDR) = 0.41 x basin area (in sq km)*-0.3. This factor comes from published research on watersheds in the Caribbean. Equation 4:Sediment delivery at the river mouth (SED_DELIV) = REP_SUM x SDR8. The point density tool (Spatial Analyst, ArcGIS) was then used to create a threat layer, using the sediment delivery at the outflow point as input, and a kernel radius of 5 km. 9. This threat layer was then averaged for every benthic habitat polygon (NOAA Benthic Habitats of Puerto Rico and the U.S. Virgin Islands, Kendall et al., 2001) using a zonal function to determine the mean threat. Sources used were NOAA Benthic Habitats Data http://ccma.nos.noaa.gov/products/biogeography/benthic/, Geocover LC http://www.MDafederal.com/geocover/geocoverlc/, USGS National Elevation Dataset http://ned.usgs.gov/, NRCS Soils Database http://www.nrcs.usda.gov/wps/portal/nrcs/site/national/home/, NOAA Monthly Surface Data http://www.ncdc.noaa.gov/oa/climate/climatedata.html. (end continuation)
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.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.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:
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):
National Centers for Coastal Ocean Science - Silver Spring, MD
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