[GRASS-dev] [GRASS GIS] #1694: r.in.lidar tries to allocate way too much memory

[GRASS GIS]

#1694: r.in.lidar tries to allocate way too much memory
------------------------+---------------------------------------------------
 Reporter:  torsti      |       Owner:  grass-dev@…              
     Type:  defect      |      Status:  new                      
 Priority:  normal      |   Milestone:  7.0.0                    
Component:  Raster      |     Version:  svn-trunk                
 Keywords:  r.in.lidar  |    Platform:  Linux                    
      Cpu:  x86-64      |  
------------------------+---------------------------------------------------

Comment(by mmetz):

 Replying to [comment:5 torsti]:
 > The region the las file covers is 3000 by 3000 (meters) and the
 resolution was 1x1.

 Can you provide the current region settings for the 1x1 resolution, i.e.
 the output of g.region -p?

 What matters is not the resolution alone but the number of rows and
 columns in the current region, which are determined by the region extents
 and the resolution. That is, you probably need to check and adjust the
 region extents.
 >
 > The command:
 >
 {{{
 r.in.lidar -o --overwrite input=R4133C4.laz output=R4133C4.las method=mean
 }}}

 You might try the percent option. By default the whole map is kept in
 memory (percent=100)

 >
 > My issue is not that r.in.lidar can't be used on large datasets on
 underpowered computers, I'm just wondering whether the 64 exabytes can be
 the right amount of memory needed for cell sizes of 1x1 to 10x10 for a
 total area of 3000mx3000m with an average point density a bit over 1 point
 per square meter (11000000 points/ 9000000 m^2).

 With the right region settings and making use of the percent option it
 should be possible to import this dataset in no time. Instead of changing
 only the resolution, you can try r.in.lidar on a subregion and here figure
 out the resolution that provides the desired results. Then set the region
 to cover the full input dataset (adjust extents, align to desired
 resolution) and import the full dataset.

 HTH,

 Markus M

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1694#comment:6>
GRASS GIS <http://grass.osgeo.org>