Search Help Show/Hide Menu
This is a deprecated version of the NOAA Data Management Plan template.
InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.

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:
NCCOS Assessment: An Aquaculture Opportunity Atlas for the State of Alaska, 2023-06-01 to 2025-06-31
1.2. Summary description of the data:

Geospatial data representing the Aquaculture Opportunity Area (AOA) study developed during 2024 for the State of Alaska. Included in this dataset are:

(1) Study areas in State of Alaska waters developed based on maximum sea ice coverage, distance from coastal populated places, existing and active aquaculture sites, and the Alaska state water boundary. Ten distinct study areas were identified (Cordova, Craig, Juneau, Ketchikan, Kodiak, Petersburg, Seward, Sitka, Valdez, and Wrangell).

(2) Suitability modeling results for the ten study areas. Results between each study area should not be compared relative to outputs of another study area, as each study area was run as a discrete model and thus the outputs of the analysis cannot be compared between study areas.

(3) Precision siting outputs from the Aquaculture Opportunity Atlas for the State of Alaska. Clusters were identified within each of the ten study areas (Cordova, Craig, Juneau, Ketchikan, Kodiak, Petersburg, Seward, Sitka, Valdez, and Wrangell) for two scenarios: intertidal and subtidal mariculture.

(4) Final AOA Options for the state of Alaska based on selection of highest ranking polygons from the precision siting outputs for each of the ten study areas for both scenarios.

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:
2023-06-01 to 2025-06-30
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: -154.504748, E: -130.920252, N: 61.148115, S: 54.92603
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.)
Other
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:

  • Study areas within Alaskan state waters were identified using maximum sea ice coverage, distance from coastal populated places, active aquatic farming sites, and the Alaska state water boundary to narrow down the spatial coverage of the study region. The results were ten distinct study areas encompassing southeast, southcentral, and southwest Alaska. Travel distance from major towns and harbors, as well as a maximum depth were used to further narrow down the final study areas.
  • Study area polygons with a 5 acre hexagonal grid were created from the ten distinct study areas identified.
  • Each data layer was scored on a 0 to 1 scale, with scores approaching 0 representing low suitability and 1 representing high suitability relative to the other grid cells for continuous data and a constant downscore value for categorical data. Any grid that contained a data layer considered a constraint was given a 0 score (i.e., constraints data layer) and was deemed unsuitable for aquaculture and therefore not considered further in the analysis. Next, an overall suitability score was calculated for each submodel (i.e., national security, industry, natural or cultural resources, fisheries) by taking the geometric mean of all scores within each grid cell that was not considered a constraint. The geometric mean of the five submodels was used to calculate an overall suitability score on the same 0 to 1 scale.
  • The resulting suitability scores were used as inputs for the cluster analysis, which uses the Local Index of Spatial Association (LISA) analysis (further referred to as a cluster analysis) to identify statistically significant clusters and outliers of the final relative suitability modeling results. Two scenarios were applied to the suitability model outputs in order to filter the data to attain distinct outputs for both intertidal and subtidal mariculture. The intertidal scenario only retains grid cells in areas which are classified as marine or estuarine wetlands according to the NWI dataset, whereas the subtidal scenario only retains model outputs in areas which are in depths of 15ft to 200ft.
  • A precision siting model was developed using custom rules and an adapted version of Techniques for Order of Preference by Similarity to Ideal Solutions (TOPSIS) to identify the most suitable potential AOA Options within each study area scenario. The TOPSIS analysis used a number of characterization parameters to score the clusters defined by the cluster analysis that were larger than 50 acres (i.e. minimum AOA size requirement). In order to both refine individual clusters and select from all potential options, the precision siting model approach applied both a within-cluster and among-cluster approach. The within-cluster precision siting approach refined the clusters in size by running a TOPSIS analysis on each grid cell within a cluster in order to find the highest ranking cells for each cluster independent of the others in a given study area. The among-cluster precision siting approach refined the total number of clusters considered a final AOA option by comparing the entire clusters within a study area against each other and getting scores for each of the clusters after they had been refined using the within-cluster approach.
  • Final AOA options were selected from the precision siting process using a combination of the among-cluster TOPSIS scores and manual inspection. A subset of clusters were chosen for each study area to try and meet the goal of maximum 4,000 acres of subtidal, and 100 acres of intertidal area per study area.
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:

Draft Data - Subject to Change

This dataset is being made available for visualization and review during an active comment period. The data are provisional and may be updated, modified, or removed at any time based on feedback, ongoing data validation, or project needs. While public access is provided through REST web map services, direct data downloads may not be available during this review phase. Users should not rely on this data for authoritative decision-making. Please refer to the associated draft report or StoryMap for additional details on the review process and how to provide feedback.

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:

These data are accessible via REST web map services for visualization within the NOAA Geoplatform via ArcGIS Online and associated web applications, including a StoryMap. Direct data downloads may not be available at this time.

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 - Beaufort, NC
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