[GRASS-dev] Segmentation fault using v.in.lidar

[Doug_Newcomb at fws.gov]

Pierre,
        I think the main issue with doing *.las would be that although LAS 
data is coming in tiled but is also available as overlapping swaths.  I 
imagine to impliment the option for multiple las files you would need to 
build an internal index of the "footprint" of each input  las file that 
tells r.in.lidar and v.in.lidar  which file(s) to draw the input las data 
from to create the output.  In the case of r.in.lidar, you would need to 
specify which files to simultaneously open to gather the point values to 
calculate the statistics that are the  value of the output cell. You would 
need something like the way gdaltindex builds a polygon shape file from a 
list of input georeferenced images. ( Now if I only had some skill with C 
to throw together some code :-( )

        In the short term, use the las2las command from liblas.org  to 
merge your .las files into a single las file and then process the one 
file.  You will have to watch out for the 4 billion point limit that is 
currently in the LAS file format, but for most folks that's not an issue.

 

Doug
 
Doug Newcomb 
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb at fws.gov
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the 
official policy of the U.S.Fish and Wildlife Service or Dept. of the 
Interior.   Life is too short for undocumented, proprietary data formats.



Pierre Roudier <pierre.roudier at gmail.com> 
Sent by: grass-dev-bounces at lists.osgeo.org
07/13/2011 03:05 AM

To
Markus Metz <markus.metz.giswork at googlemail.com>
cc
grass-dev <grass-dev at lists.osgeo.org>
Subject
Re: [GRASS-dev] Segmentation fault using v.in.lidar






Thanks for the quick answer Markus,

That would be a nice feature to add though. A lot of the LAS files are
coming "tiled", and it'd be nice to be able to do something like:

v.in.lidar in=*.las out=test_input_lidar -trb

or

v.in.lidar in=zone_32_*.las out=test_input_lidar -trb

to import a special subset of LAS files.

I've very few coding abilities, so this is just meant as another line
on the wishlist ;)

Thanks heaps for your work on *.in.lidar, it is working well otherwise,

Pierre

2011/7/13 Markus Metz <markus.metz.giswork at googlemail.com>:
> On Wed, Jul 13, 2011 at 2:08 AM, Pierre Roudier
> <pierre.roudier at gmail.com> wrote:
>> Hi,
>>
>> I've been trying to use v.in.lidar. It yields good results on one LAS
>> file, but I get a segfault when trying it on several files:
>>
>>> v.in.lidar in=BD32_1610.las,BD32_1611.las out=test_input_lidar -trb
>> Segmentation fault
>>> v.in.lidar in=BD32_161*.las out=test_input_lidar -trb
>> Segmentation fault
>>
>> Am I missing something, or is it a bug?
>
> v.in.lidar takes only one input file at a time.
>
> Markus M
>



-- 
Scientist
Landcare Research, New Zealand
_______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20110713/4aa27635/attachment-0001.html