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
No metadata record was provided for this data set. This record was created by the NOAA Office for Coastal Management (OCM) using information from the Aero-Graphics, Inc, Lidar Data Collection report. A link to this report is provided in the URL section of this metadata record.
This GIS dataset contains Bare Earth (BE) raster grids depicting lidar-derived elevation data for USDA Forest Service Malheur National Forest (LC West) project area. The BE raster dataset encompasses 206,724 acres (323 square miles) within Grant County in Oregon. The nominal pulse density is nine points per square meter. The bare earth (BE) digital elevation model (DEM) raster grid cell size is 1 meter. The native projection was UTM Zone 11, units are in meters. The native horizontal datum is NAD83 and the native vertical datum is NAVD88 (Geoid03). Aero-Graphics, Inc. collected the lidar and created this data set.
In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data are available for download at the link provided in the URL section of this metadata record.
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):
- 2010-01-01 00:00:00 - Airborne Acquisition – Equipment and Methodology LiDAR acquisition of LC West was performed with an Optech ALTM Orion sensor. Aero-Graphics flew at an average altitude of 3280 ft AGL (above ground level) and made appropriate adjustments to compensate for topographic relief. The PRF (pulse rate frequency) used for collection was 100 kHz, scan frequency of 70 Hz, and scan angle of +/- 11 degrees from the nadir position (full scan angle 22 degrees). The ALTM Orion features roll compensation that adjusts the mirror to maintain the full scan angle integrity in relation to nadir, even when less than perfect weather conditions push the sensor off nadir. Acquisition was performed with a 50% side lap and yielded >12.5 points per square meter throughout the project boundary. The Optech ALTM Orion is capable of receiving up to four range measurements, including 1st, 2nd, 3rd, and last returns for every pulse sent from the system. The ALTM Orion is also equipped with a GPS/IMU unit that continually records the XYZ position and roll, pitch and yaw attitude of the plane throughout the flight. This information allows us to correct laser return data positions that may have been thrown off by the plane’s natural movement. The ALTM Orion LiDAR sensor is equipped with ALTM-Nav Flight Management System Software. ALTM-Nav is not only used to guide the airborne mission in flight, but our office flight planning is performed using a combination of Nav and traditional flight planning practices. The smooth transition from flight planning to aerial operations eliminates discrepancies between the flight plan and what is actually acquired. The use of ALTM-Nav helps ensure an accurate and consistent acquisition mission with real-time quality assurance while still airborne. The system operator can monitor the point density and swath during the mission to confirm adequate coverage within the area of interest Ground Survey – Equipment and Methodology Aero-Graphics used survey data to differentially correct the aircraft’s trajectory data and to ensure that the LiDAR data maintained its true geographic integrity. Using our own static base stations at strategic points in the project area, with data collected during the time of the LiDAR mission, we used Multi-Base processing in Applanix’s POS GNSS software to accurately correct the aircraft’s real-time GPS trajectory.
- LiDAR Processing Workflow and Software a. Absolute Sensor Calibration. The absolute sensor calibration is defined as the difference in roll, pitch, heading, and scale between the raw laser point cloud from the sensor and surveyed control points on the ground over two separate sites. Software: Dashmap 4.1801; ACalib 126.96.36.199. b. Kinematic Air Point Processing. Differentially corrected the 1-second airborne GPS positions with ground base stations; combined and refined the GPS positions with 1/200-second IMU (roll-pitch-yaw) data through development of a smoothed best estimate of trajectory (SBET). Software: Applanix POSPac 5.3.3664.28463. c. Raw LiDAR Point Processing. Combined SBET with raw LiDAR range data; solved real-world position for each laser point; produced point cloud data by flight strip in ASPRS v1.1 .LAS format; output in WGS84 UTM Ellipsoid Heights. Software: LiDAR Mapping Suite 1.0. d. Relative Calibration. Tested relative accuracy; performed relative calibration by correcting for roll, pitch, heading, and scale discrepancies between adjacent flightlines. Results presented in Section 4.1. Software: LiDAR Mapping Suite 1.0. e. Tiling & Long/Short Filtering. Cut data into project-specified tiles and filtered out grossly long and short returns. Software: TerraScan 10.011. f. Classification. Ran classification algorithms on points in each tile; separated into ground, unclassified, high outliers and low outliers; revisited areas not completely classified automatically and manually corrected them. Software: TerraScan 10.011. g. Absolute Accuracy Assessment. Performed comparative tests that showed Z-differences between each static survey point and the laser point surface. Results presented in Section 4.2. Software: TerraScan 10.001. h. Datum Transformation. Transformed all .LAS tiles from WGS84 UTM 11N Ellipsoid Heights into NAD83 UTM 11N, adjusted for orthometric heights on NAVD88 (Geoid03). Integrity of the .LAS file format was maintained throughout the process. Software: Blue Marble Desktop 2.1. i. DEM Creation. Generated 2-meter first-return DEMs and 1-meter ground surface DEMs in ESRI Raster Grid format, tiled according to project specifications. Software: TerraScan 10.011. j. Intensity Image Creation. Generated 1-meter pixel intensity images in GeoTIFF format, tiled according to project specifications. Software: TerraScan 10.011.
- 2020-03-02 00:00:00 - The NOAA Office for Coastal Management (OCM) received 57 raster DEM files in ESRI ArcGrid format from DOGAMI. The data were in UTM Zone 11, NAD83, meters coordinates and NAVD88 (Geoid03) elevations in meters. The bare earth raster files were at a 1 m grid spacing. No metadata record was provided for this data set. This record was created by the NOAA Office for Coastal Management (OCM) using information from the Aero-Graphics, Inc., Lidar Data Collection report. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used internal script to assign the vertical EPSG code (5703) and convert to GeoTiff format. 2. Copied to the files to https.
(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.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.
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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.