[GRASS-dev] [GRASS GIS] #1694: r.in.lidar tries to allocate way too much memory
GRASS GIS
trac at osgeo.org
Wed Aug 8 00:02:33 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 torsti):
The region the las file covers is 3000 by 3000 (meters) and the resolution
was 1x1.
The command:
{{{
r.in.lidar -o --overwrite input=R4133C4.laz output=R4133C4.las method=mean
}}}
After setting the resolution to 10 by 10 (g.region res=10) it still wants
almost the same amount of memory:
{{{
ERROR: G_calloc: unable to allocate 18446744072977286712 * 4 bytes of
memory at main.c:528
}}}
With cellsize 20x20:
{{{
ERROR: G_calloc: unable to allocate 1964475953 * 4 bytes of memory at
main.c:528
}}}
This is in the range of mortal computers, I just happen to be testing on a
machine too weak for this kind of processing ;-)
With bigger cell sizes it runs, but the result is not really useful.
For small areas it runs fine on higher resolutions, e.g. a 100 by 100 area
with cellsize 1 by 1.
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).
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1694#comment:5>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list