[GRASS-dev] [GRASS GIS] #1694: r.in.lidar tries to allocate way too much memory
GRASS GIS
trac at osgeo.org
Wed Aug 8 06:48:11 PDT 2012
#1694: r.in.lidar tries to allocate way too much memory
----------------------+-----------------------------------------------------
Reporter: torsti | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.0.0
Component: Raster | Version: svn-trunk
Resolution: invalid | Keywords: r.in.lidar
Platform: Linux | Cpu: x86-64
----------------------+-----------------------------------------------------
Changes (by mmetz):
* status: new => closed
* resolution: => invalid
Comment:
Replying to [comment:8 torsti]:
> So memory allocation is based on the extent of the region and not the
bounding box of the LAS data, that explains a lot.
I have added a paragraph to the manuals of r.in.lidar and r.in.xyz that
emphasizes that.
>
> Sorry for the most likely unfounded & inaccurate bug report.
Let's say it was unclear documentation.
Closing ticket.
Markus M
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1694#comment:9>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list