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

[Pierre Roudier]

Doug, Markus,

Thanks for the interesting discussion,

> 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.
>

Yes at the moment, my workflow is:

ls ID_*.las > las_list.txt
lasmerge -i las_list.txt -o out.las
v.in.lidar in=out.las out=lidar -trb

Works very well. I was just wondering how difficult it would be to use
wildcards directly in the input=... option. Obviously it requires some
significant amount of work.

> 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.
>

Indeed, not an issue for me (unfortunately!),

> In all GRASS versions, the limit with topology is at  2^31 -
> 1 (about 2 billion) features.

I usually never build the topology of my LiDAR point clouds. Should I do it?

Cheers,

Pierre

> 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
>



--
Scientist
Landcare Research, New Zealand