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

GRASS GIS trac at osgeo.org
Tue Aug 7 16:46:56 PDT 2012

#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):

 please check your region resolution, what does g.region say about the
 number of rows and columns? memory use is directly tied to the region
 resolution and the statistical aggregation method used. (which method?)
 See the r.in.xyz man page for discussion about it.

 on a positive note, I'm happy to see that the G_alloc() calculation for
 how much memory it needs seems to handle & printf into the exabyte range
 without overflowing..
 for some future time when the datasets are actually that big :)


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

More information about the grass-dev mailing list