2012 OLC Bathymetric Lidar DEM: Sandy River (OR)
OCM Partners
Data Set
(DS)
| ID: 56855
| Published / External
Created: 2019-07-10
|
Last Modified: 2024-01-10
Project (PRJ) | ID: 49404
ID: 56855
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2012 OLC Bathymetric Lidar DEM: Sandy River (OR) |
---|---|
Short Name | or2012 sandy river bathy dem m8696 |
* Status | Completed |
Creation Date | 2012 |
Revision Date | |
• Publication Date | 2012 |
* » Abstract |
Airborne topobathymetric lidar point cloud collected for the Sandy River, Oregon in 2012. The Sandy River flows through areas of steep terrain and dense tree canopy and is home to Chinook and Coho salmon and Steelhead trout. The Sandy River is further distinguished by the 2007 removal of the Marmot Dam (river mile 30) and has been the focus of ongoing monitoring to understand the impacts of dam removal on downstream morphology and fish habitat. The nature of the river makes it challenging for traditional transect or boat-based bathymetric surveys. |
* Purpose |
The data were collected to map channel and floodplain morphology and to evaluate the effectiveness of new topo-bathymetric LiDAR technology in a Pacific Northwest riverine environment. The project was conducted through the Oregon LiDAR Consortium (OLC) with contributions from DOGAMI, the Federal Emergency Management Agency (FEMA), and the Bureau of Land Management (BLM). |
Notes | |
Other Citation Details | |
• Supplemental Information | |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > SEAFLOOR TOPOGRAPHY |
ISO 19115 Topic Category | elevation |
None | Oregon |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > LAND SURFACE |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords | LIDAR > Light Detection and Ranging |
Platform Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Platform Keywords | Airplane > Airplane |
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | Elevation |
• Maintenance Frequency | As Needed |
Maintenance Note | |
» Data Presentation Form | Model (digital) |
• Entity Attribute Overview |
Point cloud with points classified as unclassified (1) or ground (2) |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability | |
Data Set Credit | Oregon Lidar Consortium; Watershed Sciences, Inc; DOGAMI; FEMA; BLM |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2019-03-22 |
Date Effective To | |
Organization | Office for Coastal Management (OCM) |
Address |
2234 South Hobson Avenue Charleston, SC 29405-2413 |
Email Address | |
Phone | |
Fax | |
Mobile | |
URL | https://www.coast.noaa.gov/ |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2019-03-21 |
Date Effective To | |
Organization | Office for Coastal Management (OCM) |
Address |
2234 South Hobson Avenue Charleston, SC 29405-2413 |
Email Address | |
Phone | |
Fax | |
Mobile | |
URL | https://www.coast.noaa.gov/ |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2019-03-22 |
Date Effective To | |
Organization | Office for Coastal Management (OCM) |
Address |
2234 South Hobson Avenue Charleston, SC 29405-2413 |
Email Address | |
Phone | |
Fax | |
Mobile | |
URL | https://www.coast.noaa.gov/ |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -122.410523 |
---|---|
* » E° Bound | -121.934087 |
* » N° Bound | 45.57894 |
* » S° Bound | 45.336942 |
* » Description |
Area includes the Sandy River and a buffer of land around it. |
Extent Group 1 / Vertical Extent 1
EPSG Code | EPSG:5703 |
---|---|
Vertical Minimum | 0.0 |
Vertical Maximum | 860.0 |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-09-22 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | EPSG:3717 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure | |
• » Data Access Constraints |
None |
• Data Use Constraints |
Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | 2019-03-21 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8696 |
Distributor | Office for Coastal Management (OCM) (2019-03-21 - Present) |
File Name | |
Description |
Application to create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. |
File Date/Time | |
File Type (Deprecated) | Multiple formats |
Distribution Format | |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2019-03-21 |
---|---|
End Date | Present |
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/OLC_sandy_river_dem_2012_8696/index.html |
Distributor | Office for Coastal Management (OCM) (2019-03-21 - Present) |
File Name | |
Description |
Bulk download of data files in GeoTiff format, |
File Date/Time | |
File Type (Deprecated) | GeoTIFF |
Distribution Format | GeoTIFF |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8694/supplemental/Sandy_River_LiDAR_final.pdf |
---|---|
Name | Data set report |
URL Type | Online Resource |
File Resource Format | |
Description |
Report by WSI that formed the basis for this metadata. Contains additional information. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8694/supplemental/2012_sandy_river_m8694.kmz |
---|---|
Name | Data set extent |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
graphic showing the extent of the data set. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8694/supplemental/Sandy_River_2012_Bathymetric_Survey_Delivery_LIDAR_QC_Report.pdf |
---|---|
Name | QC report |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy | |
Vertical Positional Accuracy |
Bare earth topography: 0.060 meters at 95% confidence High confidence bathymetry areas: 0.347 meters at 95% confidence Low confidence bathymetry areas: 0.779 meters at 95% confidence Low confidence areas have a low point density. See report for details. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report | |
Conceptual Consistency | |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
Lidar was flown from two instruments over the Sandy River in Oregon. Data were processed to point clouds and classified as ground or unclassified. |
---|
Sources
Citation Title | DEM files |
---|---|
Contact Role Type | Originator |
Contact Type | Organization |
Contact Name | Watershed Sciences Inc |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
Planning: The airborne survey was designed to collect a point density of 4-5 pulses/m2 for the topo-bathymetric LiDAR. The flight was planned with a scan angle of ±20o and 50% side-lap. The 50% side-lap was used to ensure uniform coverage and to minimize laser shadowing due to vegetation and terrain. The flights were conducted in the late fall during base flow conditions to maximize water clarity and ensure shallow depths (Figure 2). The flight lines were developed using ALTM-NAV Planner (v.3.0) software and Leica Mission Pro Flight Planning and Evaluation (FPES) software. Efforts were taken to optimize flight paths by minimizing flight times while meeting all accuracy specifications. The WSI acquisition staff considered all factors such as air space restrictions, private property access, and GPS quality in the planning of this mission. |
Process Date/Time | 2012-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Lidar Survey: Two lidar instruments were flown. A Riegel VQ-820-Q for bathymetric collection and a Lieca ALS60 for topographic collection. The Riegl VQ-820-G uses a green-wavelength (μ = 532 nm) laser that, in addition to collecting vegetation and topography data, is able to penetrate the water surface with the 532-nm wavelength which provides for minimal spectral absorption. The sensor also collects both discrete returns (similar to the NIR data) and full-waveform data (every other pulse) for more rigorous feature extraction and evaluation of point returns. The recorded waveform enables range measurements for all discernible targets for a given pulse. The typical number of returns digitized from a single pulse ranged from 1 to 7 for the Sandy River project area. The Leica ALS60 uses a NIR wavelength (μ =1,064nm) laser that has been proven to provide high value terrestrial topography data. The NIR wavelengths do not penetrate the water column and thus provide water surface returns for received pulses off of water surface. The Leica system collects 8-bit intensity information and does not store waveform information. To accurately solve for laser point position (geographic coordinates x, y, and z), the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Position of the aircraft was measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll, and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft/sensor position and attitude data are indexed by GPS time. |
Process Date/Time | 2012-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Lidar Processing: Prior to the mission, a boresight calibration flight was conducted in Corvallis, OR and processed by WSI to ensure accurate initial sensor alignment. An individual mission calibration was also performed on the Sandy River data set using Riegl’s RiProcess software. RiProcess was then used by WSI to further refine line-to-line calibration of the topo-bathymetric LiDAR dataset to match collected hard surface RTK control points. Upon completion of calibration, Dewberry processed the LiDAR returns with a combination of manual and automated techniques using both the Riegl software and in-house proprietary software to differentiate the bathymetric and terrestrial data. WSI processed NIR LiDAR and the orthorectified digital imagery, which were also used to facilitate the processing of the bathymetric returns. Once bathymetric points were differentiated, they were spatially corrected for refraction through the water column based on the angle of incidence of the laser. Dewberry refracted water column points and classified the resulting point cloud. The resulting data was sent back to WSI for further review and product creation. Figure 4 shows the various datasets used in the bathymetric analysis while Table 7 summarizes the steps used to process the bathymetric LiDAR data. |
Process Date/Time | 2012-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
Point Classification: As with standard NIR LiDAR data, bathymetric (green) LiDAR returns are classified into categories according to whether the points are considered above ground, ground, or water. Additional LiDAR classifications were created for bathymetric processing by adding categories for channel bottom, water surface, and water column points. |
Process Date/Time | 2012-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
Full Waveform Processing: Initial echo analysis is accomplished with Riegl’s online waveform processing. In online waveform processing, discrete returns are digitized from the echo signal based on the amplitude and pulse deviation of returning energy. To facilitate discrimination of ground points versus water column points and bathymetry points, the Riegl VQ-820-G uses the online waveform processing system that generates a discrete point cloud dataset at time of capture (“online”) from the full waveform signal. The system also records geo-referenced waveforms for a subsample of the data (configured for every other pulse). The waveforms are used in determining accurate bathymetry in shallow submerged environments. The separation of the water surface and bottom return in shallow depths requires further analysis and customized methods to ‘decompose’ or ‘deconvolve’ the waveform. Furthermore, certain parameters such as attenuation coefficients need to be set when processing data in various depth ranges and water column parameters. Information derived from the waveforms is used to set these parameters. The determination of the bottom return also needs to be corrected for the change in speed of light through the water column and the refraction of light at the air/water interface. The processed waveforms are used to validate the online digitization of the initial point cloud data. |
Process Date/Time | 2012-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 6 |
---|---|
» Description |
The NOAA Office for Coastal Management received the lidar data from the Oregon Lidar Consortium. There were two sets of DEMs, one labeled as bare earth and one labeled as topobathy. They cover the same area, but the topobathy set appears to have more noise and/or variance. Only the bare earth DEMs were kept. The data report indicates that the data were collected and delivered in NAD83(CORS96) UTM Zone 10. The GeoTiff files indicated NAD83(HARN) UTM Zone 10. The data report is believed to be correct. The data were likely coded with HARN because there was no EPSG code for CORS96 UTM Zone 10 to use for the encoding. Note that the metadata system housing this metadata does not have either the HARN or CORS96 UTM Zone 10 codes, so the closest option (NSRS2007) was used in the metadata.
Metadata was not delivered with the data. This metadata was created from the WSI report. |
Process Date/Time | 2019-03-22 00:00:00 |
Process Contact | Office for Coastal Management (OCM) |
Phone (Voice) | |
Email Address | |
Source | DEM files |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Data Set (DS) | Cross Reference |
2012 OLC Bathymetric Lidar: Sandy River (OR) Point cloud used to create this data. |
Catalog Details
Catalog Item ID | 56855 |
---|---|
Metadata Record Created By | Kirk Waters |
Metadata Record Created | 2019-07-10 06:47+0000 |
Metadata Record Last Modified By | Kirk Waters |
» Metadata Record Last Modified | 2024-01-10 19:05+0000 |
Metadata Record Published | 2024-01-10 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|