[GRASS-user] LiDAR interpolation (v.surf.bspline)

[Rebecca Bennett]

Hamish wrote
>if you don't like the gridding aspect of it, and the lat/lon for
>all 4 retuns is identical, a small python or awk script could do
>the pre-processing for you in a simple and clear way.

Just to add my experience - I use awk to get a handle on the lidar xyz files 
(number of points, min, max, outliers etc) and filter for return (or scan angle 
etc) before importing into GRASS or any other software for that matter. Works 
like a dream and much faster than importing through software for the same 
information.

Carlos, if you want any pointers just let me know (though I am sure you're 
probably much more experienced than a noobie like me!)

Cheers,
Rebecca
Post-graduate Researcher
Bournemouth University, UK




________________________________
From: Hamish <hamish_b at yahoo.com>
To: Carlos Grohmann <carlos.grohmann at gmail.com>; Markus Metz 
<markus.metz.giswork at googlemail.com>
Cc: GRASS user list <grass-user at lists.osgeo.org>
Sent: Sun, 30 January, 2011 22:08:00
Subject: Re: [GRASS-user] LiDAR interpolation (v.surf.bspline)

Carlos Grohmann wrote:
> > Also, the wiki page and man pages for v.lidar.* cite
> > examples of lidar data with two returns. How well should
> > the commands run with 4 returns? Any big changes in th
> > procedure explained in the wiki?
Markus M:
> It is possible that the lidar toolchain does not work with
> 4 return because it classifies points into first or last
> return, nothing in between. In theory, it would suffice to
> identify the first and the last return, independent of the
> number of returns, in order to get a DSM and a DTM. The lidar
> filtering toolchain should work if you could remove 2. and 3.
> returns first.

set the resolution fine enough and r.in.xyz will allow you to
deal with the 4 returns any way you like.

if you don't like the gridding aspect of it, and the lat/lon for
all 4 retuns is identical, a small python or awk script could do
the pre-processing for you in a simple and clear way. maybe you
have to pipe it through `sort -n` first (but hopefully not).


Hamish



      
_______________________________________________
grass-user mailing list
grass-user at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20110131/af886b65/attachment.html