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
The Oregon Department of Geology & Mineral Industries (DOGAMI) contracted with Watershed Sciences, Inc. to collect high
resolution topographic LiDAR data for multiple areas within the state of Oregon. The areas for LiDAR collection have been designed
as part of a collaborative effort of state, federal, and local agencies in order to meet a wide range of project goals.
This LiDAR data set was collected in 17 delivery areas from August 31, 2008 through July 1, 2009. See below for the specific date
of collection and total area covered for each delivery. This data set covers 3157 square miles (2,020,760 square acres) and falls in
portions of the following counties in northwestern Oregon: Benton, Clackamas, Clatsop, Columbia, Lane, Linn, Polk, Marion, Washington,
and Yamhill. This data set consists of bare earth and unclassified points. The average pulse density is 8.14 points per
square meter over terrestrial surfaces. In some areas of heavy vegetation or forest cover, there may be relatively few ground points
in the LiDAR data. Elevation values for open water surfaces are not valid elevation values because few LiDAR points are returned
from water surfaces. LiDAR intensity values were also collected.
This LiDAR data set was collected on different dates and organized into 17 deliveries. To determine which delivery or deliveries are in
your area of interest, download the Delivery Area graphic at:
The specific date of collection and total area covered for each delivery are listed below.
Delivery 1: Acquisition Date: 20081022-20081024 Total Area = 32,150 sq acres
Delivery 2: Acquisition Date: 20080831-20090222 Total Area = 67,377 sq acres
Delivery 3: Acquisition Date: 20080831-20080914 Total Area = 89,974 sq acres
Delivery 4: Acquisition Date: 20080831-20090222 Total Area = 136,997 sq acres
Delivery 5: Acquisition Date: 20080831-20080914 Total Area = 136,424 sq acres
Delivery 6: Acquisition Date: 20080831-20080921 Total Area = 157,904 sq acres
Delivery 7: Acquisition Date: 20080831-20080921 Total Area = 65,249 sq acres
Delivery 8: Acquisition Date: 20080831-20090405 Total Area = 155,491 sq acres
Delivery 9: Acquisition Date: 20080914-20090315 Total Area = 147,742 sq acres
Delivery 10: Acquisition Date: 20081005-20090315 Total Area = 125,480 sq acres
Delivery 11: Acquisition Date: 20081005-20081111 Total Area = 89,804 sq acres
Delivery 12: Acquisition Date: 20080928-20090315 Total Area = 89,161 sq acres
Delivery 13: Acquisition Date: 20080917-20090701 Total Area = 177,375 sq acres
Delivery 14: Acquisition Date: 20090518-20090616 Total Area = 96,010 sq acres
Delivery 15: Acquisition Date: 20081010-20090607 Total Area = 191,635 sq acres
Delivery 16: Acquisition Date: 20080907-20090627 Total Area = 151,037 sq acres
Delivery 17: Acquisition Date: 20081019-20090609 Total Area = 110,950 sq acres
Original contact information:
Contact Name: Ian Madin
Contact Org: DOGAMI
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):
- 2009-01-01 00:00:00 - The LiDAR data was collected between August 31, 2008 and July 1, 2009. The survey used a Leica ALS50 Phase II laser system mounted in a Cessna Caravan 208B. The system was set to acquire greater than or equal to 105,000 laser pulses per second (i.e. 105 kHz pulse rate)and flown at 900 meters above ground level (AGL), capturing a scan angle of plus or minus 14 degrees from nadir. These settings were developed to yield points with an average native density of > or = 8 points per square meter over terrestrial surfaces. The native pulse density is the number of pulses emitted by the LiDAR system. Some types of surfaces (i.e. dense vegetation or water) may return fewer pulses than the laser originally emitted. Therefore, the delivered density can be less than the native density and lightly variable according to distributions of terrain, land cover, and water bodies. The completed areas were surveyed with opposing flight line side-lap of greater than or equal to 50 percent (greater than or equal to 100 percent overlap) to reduce laser shadowing and increase surface laser painting. The system allows up to four range measurements per pulse, and all discernible laser returns were processed for the output dataset. During the LiDAR survey of the study area, a static (1 Hz recording frequency) ground survey was conducted over monuments with known coordinates. After the airborne survey, the static GPS data are processed using triangulation with CORS stations checked against the Online Positioning User Service (OPUS) to quantify daily variance. Multiple sessions are processed over the same monument to confirm the antenna height measurements and reported position accuracy. Multiple DGPS units are used for the ground real-time kinematic (RTK) portion of the survey. To collect accurate ground surveyed points, a GPS base unit is set up over monuments to broadcast a kinematic correction to a roving GPS unit. The ground crew uses a roving unit to receive radio-relayed kinematic corrected positions from the base unit. This method is referred to as real-time kinematic (RTK) surveying and allows precise location measurement (sigma less than or equal to 1.5 cm (0.6 in)).
- 2009-01-01 00:00:00 - 1. Laser point coordinates are computed using the IPAS and ALS Post Processor software suites based on independent data from the LiDAR system (pulse time, scan angle), and aircraft trajectory data (SBET). Laser point returns (first through fourth) are assigned an associated (x, y, z) coordinate along with unique intensity values (0 to 255). The data are output into large LAS v. 1.1 files; each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z (easting, northing, and elevation) information. 2. These initial laser point files are too large to process. To facilitate laser point processing, bins (polygons) are created to divide the dataset into manageable sizes (less than 500 MB). Flightlines and LiDAR data are then reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 3. Once the laser point data are imported into bins in TerraScan, a manual calibration is performed to assess the system offsets for pitch, roll, heading, and mirror scale. Using a geometric relationship developed by Watershed Sciences, each of these offsets is resolved and corrected if necessary. 4. The LiDAR points are then filtered for noise, pits, and birds by screening for absolute elevation limits, isolated points, and height above ground. Each bin is then inspected for pits and birds manually; spurious points are removed. For a bin containing approximately 7.5 to 9.0 million points, an average of 50 to 100 points are typically found to be artificially low or high. These spurious non-terrestrial laser points must be removed from the dataset. Common sources of non-terrestrial returns are clouds, birds, vapor, and haze. 5. The internal calibration is refined using TerraMatch. Points from overlapping lines are tested for internal consistency and final adjustments are made for system misalignments (i.e., pitch, roll, heading offsets and mirror scale). Automated sensor attitude and scale corrections yield 3 to 5 cm improvements in the relative accuracy. Once the system misalignments are corrected, vertical GPS drift is then resolved and removed per flight line, yielding a slight improvement (less than 1 cm) in relative accuracy. At this point in the workflow, data have passed a robust calibration designed to reduce inconsistencies from multiple sources (i.e. sensor attitude offsets, mirror scale, GPS drift) using a procedure that is comprehensive (i.e. uses all of the overlapping survey data). Relative accuracy screening is complete. 6. The TerraScan software suite is designed specifically for classifying near-ground points (Soininen, 2004). The processing sequence begins by 'removing' all points that are not 'near' the earth based on geometric constraints used to evaluate multi-return points. The resulting bare earth (ground) model is visually inspected and additional ground point modeling is performed in site-specific areas (over a 50 meter radius) to improve ground detail. This is only done in areas with known ground modeling deficiencies, such as: bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation. In some cases, ground point classification includes known vegetation (i.e., understory, low/dense shrubs, etc.) and these points are manually reclassified as non-grounds.
- 2011-01-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained LiDAR elevation and intensity measurements. The data were in Oregon Lambert (NAD83), International Feet coordinates and NAVD88 (Geoid 03) vertical datum. OCM performed the following processing to the data to make it available within the Digital Coast: 1. The data were converted from Oregon Lambert (NAD83), International Feet coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The vertical units of the data were converted from International feet to meters. 4. The data were sorted by latitude and the headers were updated.
(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.6. Type(s) of data
- 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.
This data can be obtained on-line at the following URL:
This data set is dynamically generated based on user-defined parameters.
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.