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
Watershed Sciences, Inc. collected Light Detection and Ranging (LiDAR) data of the Deschutes Study Area for the Oregon Department of Geology and Mineral Industries (DOGAMI).The dataset covers portions of Deschutes, Crook, Jefferson, Klamath, Lake, and Lane counties in Oregon. The study area totals 2899 square miles (1,855,159 acres). The data were collected in 17 deliveries, from 2009 through 2011.
The bare earth digital elevation model (DEM) represents the earth's surface with all vegetation and human-made structures removed. The bare earth DEMs were derived from lidar data using TIN processing of the ground point returns. The DEM grid cell size is 3 feet. Some elevation values have been interpolated across areas in the models where there is no elevation data (e.g. over water, over dense vegetation).
In addition to the bare earth DEMs, the topobathy lidar point data are also available. These data are available for custom download here: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8397
Original contact information:
Contact Name: Don Haines
Contact Org: Nature of the Northwest
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):
- Watershed Sciences, Inc. has collected Light Detection and Ranging (LiDAR) data of the Deschutes Study Area for the Oregon Department of Geology and Mineral Industries (DOGAMI). The area of interest (AOI) totals 3,001 square miles (1,920,429 acres) and the total area flown (TAF) covers 3,053 square miles (1,953,949 acres). The TAF acreage is greater than the original AOI acreage due to buffering and flight planning optimization (Figure 1.1 below). DOGAMI data are delivered in OGIC (HARN): Projection: Oregon Statewide Lambert Conformal Conic; horizontal and vertical datum: NAD83 (HARN)/NAVD88 (Geoid03); units: International Feet. The LiDAR survey utilized Leica ALS50 Phase II and ALS60 sensors mounted in multiple Cessna Caravan 208Bs. The Leica systems were set to acquire greater than or equal to 105,000 laser pulses per second (i.e. 105 kHz pulse rate) and flown at 900 and 1300 meters above ground level (AGL), capturing a scan angle of plus or minus 14 degrees from nadir. These settings are developed to yield points with an average native density of 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 vary according to distributions of terrain, land cover and water bodies.
- Processing. 1. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Laser point return coordinates were computed using ALS Post Processor software and IPAS Pro GPS/INS software, based on independent data from the LiDAR system, IMU, and aircraft. 3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate. 4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment. 5. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency. 6. Noise (e.g., pits and birds) was filtered using ALS postprocessing software, based on known elevation ranges and included the removal of any cycle slips. 7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area. 8. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical and horizontal accuracies. 9. Points were output as laser points, TINed and GRIDed surfaces.
- 2017-10-10 00:00:00 - The NOAA Office for Coastal Management (OCM) received the data in the proprietary ESRI grid format from DOGAMI. The bare earth raster files were at a 3 ft grid spacing. The data were in Oregon Statewide Lambert (NAD83 HARN) International feet coordinates and NAVD88 (Geoid03) elevations in International feet. OCM did the following processing to the data for Digital Coast storage and provisioning purposes: 1. Converted the raster files from the proprietary ESRI grid format to floating point GEOTIFF format 2. Converted the raster files from elevations in international feet to meters using gdal_translate from GDAL version 2.1.1. 3. Copied the raster files to database and https (Citation: DEM files)
- 2023-08-17 00:00:00 - Files were converted to cloud optimized geotiff format to support streaming and the vertical units were reverted to feet to match the horizontal units.
(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:
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.