[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 hamish):

 as MarkusM asked, what does `g.region -p` say?

 can you turn debug level to 2? (`g.gisenv set="DEBUG=2"`, then back to 0
 to turn it off)

 for a 3000x3000 computational region and method=mean it should use
  3000*(3000+1)*4 * 2 / 1024000 = 70.3 MB
 of RAM to hold the data, and complete in just a few seconds.

 does `las2txt | r.in.xyz input=-` work? (see LIDAR page in the grass wiki
 for correct usage)


 Hamish

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