Data Management Plan
GUID: gov.noaa.nmfs.inport:47993 | Published / External
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
In June 1995, the Columbia River Estuary Study Taskforce (CREST) acquired 295 true color aerial photographs (1:12,000) of Willapa Bay, Washington, from the State of Washington Department of Transportation (WDOT), suitable for the interpretation of submerged rooted aquatic vascular plant populations. In August 1995, field surveys were conducted by a team composed of staff from Oregon State University, CREST, and the Washington Department of Natural Resources, for spectral signature development and verification as well as habitat observation. The submerged plant populations were interpreted and mapped from the photographs and transferred onto State of Washington 1:12,000 Orthophoto maps (USGS 7.5' quadrangle). The interpretations were digitized into a geographic information system (GIS) for the creation of a habitat polygon map. All interpretation, digitization and photography acquisition were according to stringent parameters detailed in the Coastal Change Analysis Program (C-CAP) Protocol (NMFS Technical Document 123). Two datasets were used as ancillary information to complement the interpreted habitat polygons. In 1996, color aerial videography was obtained from WDOT for post mapping verification and accuracy assessments. Marine Resources Consultants, Inc. and the University of Washington collected videography from 29 underwater transects to verify the deep-water edge of selected seagrass beds in the southern portion of the bay. The date, time, geographic coordinates and depth were updated every 2 to 4 seconds and recorded directly on the videotape images. Latitude and longitude were provided by a differentially corrected global positioning system (GPS). The initial presence/absence map of SAV produced by CREST was later segmented by depth to discriminate between two very different seagrass communities and support field accuracy assessment. Final field verification of the data by personnel from CREST and the NOAA Office for Coastal Management was conducted in the Summer of 1997. The benthic data is classified according to the System for Classification of Habitats in Estuarine and Marine Environments (SCHEME). This system is fully described in "Development of a System for Classification of Habitats in Estuarine and Marine Environments (SCHEME) for Florida, Report to U.S. EPA - Gulf of Mexico Program, Florida Fish and Wildlife Conservation Commission, Florida Marine Research Institute. Review Draft 12/04/02."
Original contact information:
Contact Org: NOAA Office for Coastal Management
Phone: 843-740-1202
Email: coastal.info@noaa.gov
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.
4. Resources
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):
(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.
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.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?
(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.
None
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.
Contact NOAA Office for Coastal Management's Clearinghouse Manager and request a copy of "Benthic Habitats of Willapa Bay, Washington, 1995, CD-ROM." Alternatively, fill out a OCM Product Request Form at https://coast.noaa.gov/clearinghouse/;
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.