Dear all,
I would like to share some general thoughts from my own experience with
topo-bathy lidar, which mainly is with inland, running water bodies
(i.e. rivers).
As Jörg already pointed out the main challenge in bathymetric lidar (and
the main difference to topgraphic lidar) is: (i) reconstruction of the
water surface and (ii) range and refraction correction. Refraction
correction is pretty straight forward (Snells' law) but keep in mind
that the flight trajectory is required as the refraction correction
relies on the beam direction (to be more precise: the incidence angle
between the laser beam and the water surface normal direction vector).
Identifying and reconstructing the water surface is often not trivial.
And there is no "one-for-all" solution to this problem: Why?
(a) Depending on the roughness of the water surface, the number of
air-water-surface echoes depends on and varies with the surface
roughness. More interface returns can be expected from rough surfaces
(wavy coastal waters), but Jörg has already pointed out the "white cap"
problem which is is not limited to coastal waters but may also occur at
fast-runnning streams. Considering that most bathymetric scanners employ
a constant off-nadir angle of 15-20° (Palmer scanner) the high degree of
specular reflection at smooth (water) surfaces results in many laser
echo drop-outs. This means, that only a few points are available for
water surface reconstruction. The good news: In this case only a few
points are necessary as the surface is smooth anyway.
(b) The water surface may either be dynamic (costal waters, mountain
streams, etc) or rather static (lowland rivers, lakes in case of no or
moderate wind). In the dynamic case the water surface reconstruction
needs to be carried out for each flight strip independently and for
static water surfaces data from all overlapping flight strips can be
used for reconstructing the air-water-interface. In the ideal case
return from the surface and the bottom is available for each laser
pulse. However, in practice this is an illusion and there may well be
pulses delivering an interface echo but no bottom return and vice versa.
I just mention it, as one might think that refraction correction could
be done on a per-pulse basis (without explicitly modeling the water
surface). From my experience this is infeasible. Another argument for
the necessity of modeling the water surface that the assumption of
horizontal water surfaces is no longer state-of-the-art, but proper
refraction correction takes the local water surface slope into account.
This having said, I strongly belief that different procedures are
required depending on the actual state of the water body.
To come back to the main thread of this discussion (available data),
there is sample data (trajectory and raw point cloud, Riegl VQ-880-G)
and the respective workflow available as a use case example of the TU
Wien software OPALS at:
http://geo.tuwien.ac.at/opals/html/useCase_ALB_Pielach_River.html
Data is courtesy of Riegl but can be freely used for non-commercial
purposes.
Kind regards,
Gottfried
PS: Most of my research is "open access", so in case you are interested
just google for: Mandlburger lidar bathymetry
--
Dr. Gottfried Mandlburger
Tel.:
+43 1 58801 12235
Fax.:
+43 1 58801 12299
http://www.ipf.tuwien.ac.at
_____ _____ _____
/____// ___// / Vienna University of Technology
// __ / /__ / // / Department of Geodesy and Geoinformation
//__/// /__ / // / Research Groups Photogrammetry and Remote Sensing
/____//____//____/ Gusshausstrasse 27-29, A-1040 Vienna
>
coast.noaa.gov/digitalcoast <
http://coast.noaa.gov/digitalcoast>
>
>
> On Wed, Jun 7, 2017 at 8:17 AM, Jorg Hacker
> <
jorg....@airborneresearch.com.au <javascript:>> wrote:
>
> Hello Kirk,
>
> As I have never before seen bathymetric Lidar data except the
> one that I collected myself with our Riegl VQ820-G around
> Australia, I downloaded a sample from the NOAA Digital Coast.
> It's nice, but I am wondering if it would be possible to access
> the uncleaned pointcloud data before anything was done to it.
> That would be really interesting. Our own data is available in
> any form from totally uncleaned to cleaned and classed (for
> cases where we did that).
>
> Regards,
> Jorg.
>
> On Wednesday, June 7, 2017 at 8:35:11 PM UTC+9:30, Kirk Waters
> wrote:
>
> There are a number of topobathy data sets freely available
> the on NOAA Digital Coast,
https://coast.noaa.gov/dataviewer
> <
https://coast.noaa.gov/dataviewer>. Most of the newer ones
> have been classified, but there are still some from
> mid-2000s that are really just classified as green-laser
> returns (we used class 11). Lidar cleaning and
> classifications is a topic on the agenda tomorrow at the
> JALBTCX Airborne Coastal Mapping and Charting Technical
> Workshop (JALBTCX is Joint Airborne Lidar Bathymetry
> Technical Center of eXpertise). You could always unclassify
> the data to play with if you wanted. There are at least 60
> datasets with bathy available.
>
> Kirk Waters, PhD | NOAA Office for
> Coastal Management
> Applied Sciences Program | 2234 South Hobson Ave
>
843-740-1227 | Charleston, SC 29405
>
coast.noaa.gov/digitalcoast <
http://coast.noaa.gov/digitalcoast>