Data Management Plan
GUID: gov.noaa.nmfs.inport:69919 | 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
Product: Digital Elevation Model
Lidar elevation was collected for the eastern portion of the Colville National Forest in Washington State for the United States Forest Service (USFS), Region 6. This digital elevation model was created from the classified lidar point cloud. This dataset is part of a larger collection detailed in the data report. The dataset was received by NOAA from USFS without metadata. This metadata was created based upon the data report from Atlantic, LLC.
Aerial lidar data for this task order was planned, acquired, processed and produced at a nominal pulse spacing (NPS) of 0.5 meters and nominal pulse density of 4.2 pulses per square meter.
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:
- 2016-08-21 00:00:00 - Aircraft and Sensor Information and Flight Plan Execution Atlantic operated a Cessna T210L (N732JE) and a Partenavia S.P.A. P 68 C/TC (N775MW) outfitted with Leica ALS70-HP lidar systems during the collection of the project area. Onboard differential Global Navigation Satellite System (GNSS) unit(s) recorded sample aircraft positions at 2 hertz (Hz) or more frequency. Lidar data was only acquired when a minimum of six (6) satellites were in view (10 degrees above the horizon) and with a PDOP of less then or equal to 4 when the laser was online.
- 2020-10-22 00:00:00 - Lidar Point Cloud Generation Atlantic used Leica software products to download the IPAS ABGNSS/IMU data and raw laser scan files from the airborne system. Waypoint Inertial Explorer is used to extract the raw IPAS ABGNSS/IMU data, which is further processed in combination with controlled base stations to provide the final Smoothed Best Estimate Trajectory (SBET) for each mission. The SBETs are combined with the raw laser scan files to export the LAS (*.las) formatted swath point clouds
- 2020-10-22 00:00:00 - Lidar Classification The calibrated point cloud data from the laser sensor was merged to produce processed (*.las) file(s) including but not limited to 3D position, intensity, and time-stamp. A filtering methodology was utilized to produce a multi-return surface elevation model dataset with bare-earth conditions. GeoCue, TerraScan, and TerraModeler software was used for the initial batch processing and manual editing of the (*.las) point clouds. 1 Processed, Unclassified 2 Ground 7 Low Point (Noise) 18 High Noise
- 2023-05-16 00:00:00 - Digital elevation models were received from USFS by NOAA Office for Coastal Management in Albers USFS Region 6 coordinates (EPSG:9674) and NAVD88 meters on Geoid12b in Imagine (*.img) format. Data were converted to cloud optimized GeoTiff format for ingest into the Digital Coast Data Access Viewer and to allow streaming. (Citation: digital elevation models)
(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://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9835/details/9835
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.