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.
1. General Description of Data to be Managed
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.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(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.)
2. Point of Contact for this Data Management Plan (author or maintainer)
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.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
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.
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.
Programs must identify resources within their own budget for managing the data they produce.
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.
(describe or provide URL of description):
- 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
(describe or provide URL of description):
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.
- 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?
(describe or provide URL of description):
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.
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.
Notes: This field is required if a Distributor has not been specified.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Notes: This field is required if applicable.
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.
(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)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.