[GRASS-dev] r.in.lidar: read multiple LAS files in one run

Newcomb, Doug doug_newcomb at fws.gov
Fri Oct 30 05:03:47 PDT 2015


Vaclav,

I have successfully  processed  a county with 966 laz files with well over
4.2 billion points, using a base elevation raster with 2.4 billion pixels (
Hyde county, NC  5 ft resolution DEM , about half water).  It is a bit
slower, but it does solve several of my issues.  Well done!

Will this be backported to 7.0 ?  :-)

Doug

On Mon, Oct 26, 2015 at 3:00 PM, Vaclav Petras <wenzeslaus at gmail.com> wrote:

>
> On Mon, Oct 26, 2015 at 1:20 PM, Newcomb, Doug <doug_newcomb at fws.gov>
> wrote:
>
>> multiple files at the 4.2 point las 1.2 limit! I can live with slow, just
>> concerned about the memory demands working with larger areas.
>
>
> The processing goes by row chunks. By default everything is in the memory.
> You can say that only half of rows will be in the memory at a time by
> percent=50 (you have to guess how much memory it will take). It will be
> (much) slower because it will iterate over the files (twice in this case).
> I was not able to do any tests with large amounts of points but the only
> problem will be capacity of some counters for percentage and report. The
> actual processing takes one point at a time, so there shouldn't be any
> limit. This is by the way still the same as before, I haven't changed
> anything in the way how this is handled. Let me know if this doesn't
> address your concerns.
>



-- 
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.
As a federal employee, my email may be subject to FOIA request.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20151030/8e0d7e2c/attachment.html>


More information about the grass-dev mailing list