<br><font size=2 face="sans-serif">Pierre,</font>
<br><font size=2 face="sans-serif"> 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 :-( )</font>
<br>
<br><font size=2 face="sans-serif"> 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.</font>
<br>
<br><font size=2 face="sans-serif"> </font>
<br>
<br><font size=2 face="sans-serif">Doug</font>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">Doug Newcomb
<br>
USFWS<br>
Raleigh, NC<br>
919-856-4520 ext. 14 doug_newcomb@fws.gov<br>
---------------------------------------------------------------------------------------------------------<br>
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.</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Pierre Roudier <pierre.roudier@gmail.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: grass-dev-bounces@lists.osgeo.org</font>
<p><font size=1 face="sans-serif">07/13/2011 03:05 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Markus Metz <markus.metz.giswork@googlemail.com></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">grass-dev <grass-dev@lists.osgeo.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [GRASS-dev] Segmentation fault using
v.in.lidar</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Thanks for the quick answer Markus,<br>
<br>
That would be a nice feature to add though. A lot of the LAS files are<br>
coming "tiled", and it'd be nice to be able to do something like:<br>
<br>
v.in.lidar in=*.las out=test_input_lidar -trb<br>
<br>
or<br>
<br>
v.in.lidar in=zone_32_*.las out=test_input_lidar -trb<br>
<br>
to import a special subset of LAS files.<br>
<br>
I've very few coding abilities, so this is just meant as another line<br>
on the wishlist ;)<br>
<br>
Thanks heaps for your work on *.in.lidar, it is working well otherwise,<br>
<br>
Pierre<br>
<br>
2011/7/13 Markus Metz <markus.metz.giswork@googlemail.com>:<br>
> On Wed, Jul 13, 2011 at 2:08 AM, Pierre Roudier<br>
> <pierre.roudier@gmail.com> wrote:<br>
>> Hi,<br>
>><br>
>> I've been trying to use v.in.lidar. It yields good results on
one LAS<br>
>> file, but I get a segfault when trying it on several files:<br>
>><br>
>>> v.in.lidar in=BD32_1610.las,BD32_1611.las out=test_input_lidar
-trb<br>
>> Segmentation fault<br>
>>> v.in.lidar in=BD32_161*.las out=test_input_lidar -trb<br>
>> Segmentation fault<br>
>><br>
>> Am I missing something, or is it a bug?<br>
><br>
> v.in.lidar takes only one input file at a time.<br>
><br>
> Markus M<br>
><br>
<br>
<br>
<br>
-- <br>
Scientist<br>
Landcare Research, New Zealand<br>
_______________________________________________<br>
grass-dev mailing list<br>
grass-dev@lists.osgeo.org<br>
</font></tt><a href="http://lists.osgeo.org/mailman/listinfo/grass-dev"><tt><font size=2>http://lists.osgeo.org/mailman/listinfo/grass-dev<br>
</font></tt></a>
<br>