[pdal] Debugging std::bad_alloc

[James Harrison]

On 13/05/2017 21:42, Andrew Bell wrote:
> Yes. That may help depending on the memory requirements of the points
> and that of the raster. You do need to specify bounds if you use
> writers.gdal in stream mode.
> 
> On May 13, 2017 3:31 PM, "Smith, Michael ERDC-RDE-CRREL-NH CIV"
> <Michael.Smith at erdc.dren.mil <mailto:Michael.Smith at erdc.dren.mil>> wrote:
> 
>     Couldn't this be run in stream mode to reduce the memory usage?  Try
>     adding --stream
> 

Didn't know about stream mode - having said that I'm seeing that in my
dataset this is actually being caused by fragmented point cloud data
containing geographically dispersed chunks of points - in other words,
my .las has two chunks of road with a big 5km gap in the middle. No
problem in the vector world but a real pain for raster generation.

I've tried using the cluster filter and the groupby filter in
combination to emit segmented LAZ files I can then iterate over, but the
groupby filter complains the ClusterId dimension is invalid. Is this the
right approach to take? I've considered using the chipper with a
reasonably high point count but I think this would create visual
discontinuities in the output.

-- 
Cheers,
James Harrison

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20170514/25dec098/attachment.sig>