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
This digital elevation model (DEM) is a part of a series of DEMs produced for the National Oceanic and Atmospheric Administration Office for Coastal Management's Sea Level Rise and Coastal Flooding Impacts Viewer. The DEMs created for this project were developed using the NOAA National Weather Service's Weather Forecast Office (WFO) boundaries. Because the WFO boundaries can cover large areas, the WFO DEM was divided into smaller DEMs to ensure more manageable file sizes. The Seattle (WA) WFO DEM was split into three smaller DEMs. They are divided along county lines and are: 1. Seattle (WA) WFO - Grays Harbor County 2. Seattle (WA) WFO - Clallam, Jefferson, Kitsap, Mason, Pierce, and Thurston Counties 3. Seattle (WA) WFO - Whatcom, San Juan, Skagit, Island, Snohomish, and King Counties This metadata record describes the DEM for Seattle (WA) WFO - Grays Harbor County. The DEM includes the best available lidar data known to exist at the time of DEM creation for the coastal areas of Grays Harbor County, that met project specifications. The DEM is derived from LiDAR datasets collected for the Puget Sound LiDAR Consortium (PSLC), United States Geological Survey (USGS) and the Oregon Department of Geology and Mineral Industries (DOGAMI), available from the NOAA Digital Coast. Hydrographic breaklines used in the creation of the DEM were delineated using LiDAR intensity imagery generated from each constituent dataset. The DEMs are hydro flattened such that water elevations are less than or equal to 0 meters. The DEM is referenced vertically to the North American Vertical Datum of 1988 (NAVD88) with vertical units of meters and horizontally to the North American Datum of 1983 (NAD83). The resolution of the DEM is approximately 5 meters.
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):
- 2012-01-01 00:00:00 - 1. Lidar source data and hydrographic breaklines were obtained and imported into an ESRI ArcGIS file geodatabase for each constituent county within the WFO boundary. Only ground classified lidar (Class 2) points were used to reflect a bare earth surface. Hydrographic features were assigned elevation values at or below 0 meters. An ESRI Terrain was then generated from these source data. 2. The ESRI Terrain was converted to a DEM (Erdas Imagine .img file format) with a cell size of 3 meters. The DEM was reviewed in Global Mapper for incorrect elevations and artifacts introduced from source inputs or during the raster creation process. Corrections were applied to the DEM and reprocessed for further review. 3. All DEMs for the entire study area (WFO) were loaded into Global Mapper for a final review. The constituent DEMs were then checked to ensure complete coverage within the study area and that no issues existed along the boundary between adjacent DEMs. Once it was determined all DEMs were seamlessly edge-matched and no other artifacts were present, the constituent DEMs were mosaiced together, resampled to 5m and reprojected to the NAD83 geographic coordinate system. (Citation: Puget Sound LiDAR Consortium lidar data holdings)
(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.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.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.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?
(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.