Data Management Plan
GUID: gov.noaa.nmfs.inport:69717 | 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
Geographic Extent: This data set is consisting of lidar point cloud, classified lidar, and digital elevation model, which all pieces encompasses the Washington Resource Conservation and Development Council (WRCD) 2017 Lidar area of interest (AOI), approximately 128 square miles or 318 square kilometers. Data set Description: This data set consists of lidar point cloud LAS swath files and tiled LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Each file represents a separate swath of lidar. Lidar Base Specification 1.2
Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off
How the Withheld Points are Identified: Withheld (ignore) points were identified in the files using the standard LAS Withheld bit.
Class Code:1
Class Item:Unclassified
Class Code:2
Class Item:Ground
Class Code:7
Class Item:Low Noise
Class Code:18
Class Item:High Noise
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):
Process Steps:
- 2017-10-15 00:00:00 - Aerial Lidar Acquisition: Aerial data collection was acquired in five (5) flight missions, using the ALS70 SN#7123/7225 at an altitude of 2900 meters AGL. Airborne GPS and IMU data was collected during the acquisition. Data acquisition was completed on October 15, 2017.
- 2017-10-15 00:00:00 - Lidar Pre-processing: Airborne GPS and IMU data were merged to develop a Smoothed Best Estimate Trajectory (SBET) of the lidar system for each lift. Lidar ranging data were initially calibrated using previous best parameters for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project lifts, was reduced to 2 cm or less. Data were then block adjusted to match surveyed calibration control. Raw data NVA were checked using independently surveyed check points. Swath overage points were identified and tagged within each swath file
- 2017-10-16 00:00:00 - Initial processing of the GPS data was processed using Inertial Explorer. The solution file was generated and CloudPro software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines). The data from each line were combined and automated classification routines run to determine the initial surface model. This initial surface model was then verified to the surveyed test points.
- 2017-10-30 00:00:00 - Lidar Post-Processing: The calibrated and controlled lidar swaths were processed using automatic point classification routines in TerraSolid software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Data were then distributed as virtual tiles to experienced Lidar analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags are stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project are calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified Lidar swath files were delivered to the client.
- 2017-12-15 00:00:00 - Lidar Classification: The calibrated Lidar data was run through automated classification routines and then manually checked and edited. The data was classified into the following classes: 1-unclassified*, 2-ground, 7-low noise and 18-high noise
- 2023-04-28 00:00:00 - Classified lidar data was received by NOAA Office for Coastal Management from the U.S. Forest Service in Albers USFS region 6 projection (EPSG:9674) meters with vertical values in NAVD88 (Geoid12B) meters. For ingest into the Digital Coast Data Access Viewer, data were transformed to geographic coordinates (NAD83(2011)) and ellipsoid heights. Individual files were reorganized into the COPC varient of LAZ format to support streaming operations. (Citation: Classified lidar points)
(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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9823/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk or 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 tape and 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.