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:
Seagrasses
1.2. Summary description of the data:

These data show aquatic vascular vegetation beds dominated by submerged, rooted, vascular species or submerged or rooted floating freshwater tidal vascular vegetation. This is not a complete collection of seagrasses on the seafloor, nor are the locations to be considered exact. The presence and location of the seagrasses have been derived from multiple state and federal sources.

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
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: -166.28616, E: 145.78099, N: 60.386899, S: 13.237632
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.)
No information found
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:
No information found
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:
No information found
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:
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):

Process Steps:

  • 2013-10-01 00:00:00 - 1) Acquire original source data 2) IMPORT each shapefile into a File Geodatabase 3) PROJECT into NAD83 4) DISSOLVE each state feature class based on all fields except Object ID, Acres, Shape Length, and Shape Area to remove data overlap 5) EXPLODE all multipart features in each state feature class 6) APPEND all state feature classes into a single feature class 7) Check for overlapping features and MERGE into a single feature 8) RENAME field names to match the the proposed data dictionary 9) DELETE all superfluous fields 10) Execute the CHECK GEOMETRY function
  • 2019-01-01 00:00:00 - 1) Acquire data from sources by URL download or email. Determine if the new source data supersedes existing national data set. DELETE the older, superseded features and replace with the newer source data 2) MERGE new data sets and features into the former national data set, carrying over values from the necessary source fields that match the current data's schema 3) For ShoreZone polyline features within the Washington state DNR data, features were buffered five feet in order to generate the polygon format required of this data set. In this case, coverage was denoted as 'Present', since the polygon does not represent the footprint of the seagrass here, just that it was present somewhere along this shoreline segment 4) Convert the multipart layer to singlepart and then project into an equal area projection (example: USA Contiguous Albers Equal Area Conic). Add a new field called Acreage and calculate the geometry of the features. (Special note for the Washington state DNR data: per request of the source, the acreage values for the ShoreZone features were set to Null, and the acreage values for the SVMP features were derived from the source and not calculated separately.) Project the data back into NAD83 5) Remove all unnecessary fields and populate others according to data dictionary 6) Visually inspect older features for overlap with newer data. For example, if data from the 1970s within a small estuary is immediately adjacent to and overlapping data from 2016, remove the data from the 1970s 7) Execute the REPAIR GEOMETRY function PLEASE NOTE: Per request of the Washington state DNR, the acreage values for the ShoreZone features were set to Null, and the acreage values for the SVMP features were derived from the source and not calculated separately
  • 2015-03-01 00:00:00 - 1) Acquire source data PLEASE NOTE: For Washington state, a large percentage of the state's coastline was designated as having seagrass based on a crosswalk between survey units (polygons) and shoreline seagrass status (polylines). Where polylines that were attributed as "seagrass present", polygons that intersected these line segments were extracted. While the resulting polygons (i.e. survey units) express that seagrass is found therein, it does not represent the footprint of the seagrass extent. Conversely, in some cases seagrass footprints were provided, such as in: Willapa Bay, Padilla Bay, and areas of Snohomish County. [Survey units originated from the Submerged Vegetation Monitoring Project (for Puget Sound and Strait of Juan de Fuca) and the Washington Marine Vegetation Atlas (for the Pacific coast). Shoreline status was provided by Washington state's ShoreZone inventory.] 2) Polygon to polyline crosswalk (noted above) performed in Washington state 3) Shoreline data (denoting seagrass presence) from California DFW was buffered by 20 meters to create polygons (i.e. generalized footprints) 4) PROJECT each data set in NAD83 GRS 80 5) ADD fields (date, provider, location) to each data set then populated 6) ERASE data sets that overlap, and retain the newer data or data determined to be preferential to another 7) MERGE all data sets 8) Removed unnecessary fields and populated others according to data dictionary 9) SPLIT merged data by UTM (zone 10 and 11), explode features, and CALCULATE area of polygons in acres 10) MERGE data from both zones then execute the CHECK GEOMETRY function
  • 2022-06-26 00:00:00 - 1) Execute the REPAIR GEOMETRY function to remove null features and fix non-simple features 2) Modify field names for usability, and to avoid common controlled vocabulary
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.6. Type(s) of data
  • 1.7. Data collection method(s)
  • 2.1. Point of Contact Name
  • 2.4. Point of Contact Email
  • 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.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.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:
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):
Partial information found
Charleston, SC
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