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 <[email protected]>: > On Wed, Jul 13, 2011 at 2:08 AM, Pierre Roudier > <[email protected]> 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 [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
