Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:73668 | Published / External
This is an outdated 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. Please see the Data Management Plan Help Guide to learn more.
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
Original Product: Hydroflattened Digital Elevation Model (DEM) data covering the Washington DNR 3DEP Processing project area.
Geographic Extent of Original Data: This dataset and derived products encompass an area covering approximately 562,137 acres of Eastern Washington.
Original Dataset Description: The Washington DNR 3DEP Processing Lidar project called for the planning, acquisition, and processing of lidar data collected to Quality Level 1 (QL1) standards. Project specifications are based on the U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 2.1. The data was developed based on the NAD83 2011 horizontal datum and the NAVD88 Geoid 18 vertical datum. Data was projected in Washington State Plane North, U.S. feet. Lidar data was delivered as calibrated and classified LAS 1.4 files. Lidar flight line swaths were processed to create 1,097 classified LAS 1.4 files delineated in 5,000ft x 5,000ft tiles. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create 1,097 2.0 foot hydro-flattened Raster DEMs delineated in 5,000ft x 5,000ft tiles. Non-Vegetated Vertical Accuracy (NVA) was assessed using 64 check points located on bare earth in clear, unobstructed areas. Vegetated Vertical Accuracy (VVA) was assessed using 43 check points in Tall Grass, Forest, and Shrub landcover types. Additional products include classified LAS files, intensity images, highest hit surface models, and 3D breaklines of rivers and lakes within the study area.
Ground Condition of Original Data: Ground condition was free of snow and acquisition occurred free of smoke, fog and cloud cover.
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the USGS GeoTiff files hosted by USGS on Amazon Web Services.
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):
Lineage Statement:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS GeoTiff files that are hosted on Amazon Web Services (AWS), into the Digital Coast Data Access Viewer (DAV). The DAV accesses the raster data as it resides on AWS under the usgs-lidar-public-container.
Process Steps:
- 2021-01-29 00:00:00 - Lidar Pre-Processing: 1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las format. Convert data to orthometric elevations by applying a Geoid 18 correction. 5. Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 6. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 7. Adjust the point cloud by comparing ground classified points to supplemental ground control points.
- 2021-01-29 00:00:00 - Lidar Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. After completion of classification and final QC approval, calculate final NVA, VVA, and density information for the project using ground control quality check points.
- 2021-01-29 00:00:00 - Hydro-flattening Breaklines and Hydro-flattened DEM creation: Water boundary polygons were developed using an algorithm which weights lidar-derived slopes, intensities, and return densities to detect the water's edge. The water's edge was then manually reviewed and edited as necessary. Elevations were assigned to the water's edge through neighborhood statistics identifying the lowest lidar return from the water surface. Lakes were assigned a consistent elevation for an entire polygon while rivers were assigned consistent elevations on opposing banks and smoothed to ensure downstream flow through the entire river channel. These breaklines were incorporated into the hydro-flattened DEM by enforcing triangle edges (adjacent to the breakline) to the elevation values derived from the breakline. This implementation corrected interpolation along the hard edge. Breaklines were also used to classify all ground points within the identified water bodies to class 9 (water).
- 2024-10-16 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the USGS GeoTiff files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the raster data as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. This is the location of the GeoTiffs that are being accessed: https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/WA_DNR_3DEP_Processing_2019_D20/WA_DNR_3DEP_Processing_1_2019/TIFF/
(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
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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.
https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/WA_DNR_3DEP_Processing_2019_D20/WA_DNR_3DEP_Processing_1_2019/TIFF/
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk and custom downloads.
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
Data is backed up to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.