[pdal] 'PDAL: vector<T> too long' error when Using writers.gdal with bounds option in PDAL 2.3.0

[Peter Lim]

Hi Andrew,

 

I’m using 64-bit windows system.  This error did not occur when I was using PDAL 2.1.0.

When I removed the “bounds” option, the error is gone, but took much longer time to process than before.

So I was wondering is there any changes to the “bounds” option from 2.10 to 2.3.0 that might cause this.

 

Please advise.

 

Thank you.

 

Best Regards,

 

Peter Lim

GPS Lands (S) Pte Ltd

 

From: Andrew Bell [mailto:andrew.bell.ia at gmail.com] 
Sent: Friday, 3 September 2021 7:36 pm
To: Peter Lim
Cc: pdal
Subject: Re: [pdal] 'PDAL: vector<T> too long' error when Using writers.gdal with bounds option in PDAL 2.3.0

 

I'm guessing you're on a 32-bit windows system. For all practical purposes this is an "out of memory" error. In order to process the data the GDAL writer needs to create at least one raster that handles your bounds / resolution * sizeof(data_type). Windows is reporting that this memory is unavailable. If you going to process large amounts of data, you should consider using a 64-bit system.

Other than this, I have no ideas. The GDAL writer has been used successfully with very large datasets and rasters, so I'm not sure what else the problem might be.

 

On Fri, Sep 3, 2021 at 2:25 AM Peter Lim <peter.lim at gpslands.com> wrote:

Hi,

 I’m trying to generate a GeoTiff image from a LAS file using PDAL 2.3.0 (git-version: Release) and pipeline as follows:

 [

    {

        "type":"readers.las",

        "filename":"input.las"

    },

    {

        "type":"writers.gdal",

        "resolution": 0.05,

        "data_type":"uint16",

        "output_type":"mean",

        "dimension":"Intensity",

        "gdalopts":"COMPRESS=ZSTD,ZSTD_LEVEL=1,NUM_THREADS=ALL_CPUS,TILED=YES",           

        "bounds":"([372595,374062],[140751,142246])",

        "filename":"output.tif"

    }                          

]

 

There is an error: PDAL: vector<T> too long.

 

This error was not there when I used PDAL 2.1.0.

 

When I removed the “bounds” option, the error is gone, but took much longer time to process than before.

 

Please advise. 

 

Thank you.

 

Best Regards,

 

Peter Lim

GPS Lands (S) Pte Ltd

 

 


 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 

Virus-free.  <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> www.avast.com 

_______________________________________________
pdal mailing list
pdal at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/pdal




 

-- 

Andrew Bell
andrew.bell.ia at gmail.com



-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20210906/ccefbd70/attachment.html>