On Mon, May 19, 2014 at 6:30 AM, Hamish hamish.webm...@gmail.com wrote:
[ wish for r.in.lidar: ]
...
filter Only import points of selected return type
If not specified, all points are imported
options: first,last,mid
which would be great for r.in.lidar
On 5/17/14, Newcomb, Doug doug_newc...@fws.gov wrote:
I pulled the latest 71 trunk ( 60278) , applied the patch, and the
intensity option appears to work.
Just for the record: added in trunk in r61480.
Markus
___
grass-dev mailing list
[ wish for r.in.lidar: ]
...
filter Only import points of selected return type
If not specified, all points are imported
options: first,last,mid
which would be great for r.in.lidar as well to avoid that I need
to split the file with las2las
(back to an older topic)
On Tue, Oct 8, 2013 at 8:37 PM, Markus Neteler wrote:
On Tue, Oct 8, 2013 at 4:31 PM, Markus Metz wrote:
Markus Neteler wrote:
[ wish for r.in.lidar: ]
...
filter Only import points of selected return type
If not specified, all points are
Great! I will test when I have a spare moment!
In the long term.. Any chance of filtering the input points through an
elevation raster to subtract to get height above ground before statistics?
las file--- subtract value of elevation grid generated from ground points
-- run statistics on
I pulled the latest 71 trunk ( 60278) , applied the patch, and the
intensity option appears to work.
Doug
On Fri, May 16, 2014 at 6:02 PM, Markus Neteler nete...@osgeo.org wrote:
(back to an older topic)
On Tue, Oct 8, 2013 at 8:37 PM, Markus Neteler wrote:
On Tue, Oct 8, 2013 at 4:31
Any thoughts on applying further filtering and using the intensity of the
return for statistical analysis? For example, if one wanted to calculate
the mean/range/in/max/std_dev intensity of the last returns or first
returns.
Doug
On Tue, Oct 8, 2013 at 2:37 PM, Markus Neteler
Markus Neteler wrote:
One more wish comes to mind (indeed, I started cross-porting but :-)
v.in.lidar comes with a filter (which should perhaps be generalized to
the nth return; or, the last *is* the nth return but then mid could
be more than one in this case?):
Yes, for n returns, the
On Tue, Oct 8, 2013 at 4:31 PM, Markus Metz
markus.metz.gisw...@gmail.com wrote:
Markus Neteler wrote:
One more wish comes to mind (indeed, I started cross-porting but :-)
v.in.lidar comes with a filter (which should perhaps be generalized to
the nth return; or, the last *is* the nth return
Markus Neteler wrote:
PS: if the LAS file is not accessible, r.in.lidar happily segfaults.
My attempts to fix that were yet unsuccessful.
Fixed in r57951,2 for [r|v].in.lidar
Markus M
___
grass-dev mailing list
grass-dev@lists.osgeo.org
On Mon, Oct 7, 2013 at 8:28 AM, Markus Metz
markus.metz.gisw...@gmail.com wrote:
Markus Neteler wrote:
PS: if the LAS file is not accessible, r.in.lidar happily segfaults.
My attempts to fix that were yet unsuccessful.
Fixed in r57951,2 for [r|v].in.lidar
Thanks!
One more wish comes to
Hi,
I have ported the -p Print LAS file info and exit from v.in.lidar to r.in.lidar
I have also made a major rewrite of the manual which was too much
cloned from r.in.xyz:
http://grass.osgeo.org/grass70/manuals/r.in.lidar.html
Further improvements are welcome (in SVN or as SVN diff).
cheers
12 matches
Mail list logo