[pgpointcloud] Importing to pgpointcloud

Howard Butler hobu.inc at gmail.com
Wed Jul 17 17:11:31 PDT 2013


A few things to check

* Are you built in Release or RelWithDebInfo mode? PDAL defaults to debug mode.
* What does your PostgreSQL configuration look like?

On my 15" Retina MacBook Pro, a pipeline that chips this data at 400 points per chip and outputs to a LAS file instead of PostgreSQL only takes 13 seconds using PDAL/PDAL:master. That includes the reprojection.

<Pipeline version="1.0">
  <Writer type="drivers.las.writer">
    <Option name="filename">output.las</Option>
    <Filter type="filters.chipper">
      <Option name="capacity">400</Option>
      <Filter type="filters.cache">
        <Option name="max_cache_blocks">1</Option>
        <Filter type="filters.inplacereprojection">
          <Option name="out_srs">EPSG:4326</Option>
          <Option name="offset_x">-104</Option>
          <Option name="offset_y">33</Option>
          <Option name="offset_z">0.0</Option>
          <Option name="scale_x">0.00000001</Option>
          <Option name="scale_y">0.00000001</Option>
          <Option name="scale_z">0.001</Option>
          <Reader type="drivers.las.reader">
            <Option name="filename">36096a8_NW_C.las</Option>
          </Reader>
        </Filter>
      </Filter>
    </Filter>
  </Writer>
</Pipeline>

Howard

On Jul 17, 2013, at 1:26 PM, Paul Ramsey <pramsey at cleverelephant.ca> wrote:

> If we're talking 8M features per file, that's still blisteringly slow. 
> 
> P 
> 
> -- 
> Paul Ramsey
> http://cleverelephant.ca
> http://postgis.net
> 
> 
> On Wednesday, July 17, 2013 at 11:24 AM, Roger Bedell wrote:
> 
>> Hello Howard,
>> Update on this. I transferred the program to another machine (without Visual Studio), and all four files worked fine, at a more reasonable speed of around 15 minutes per file. 
>> 
>> Roger
>> 
>> 
>> On Wed, Jul 17, 2013 at 4:04 PM, Roger Bedell <rbedell at coordinatesolutions.com (mailto:rbedell at coordinatesolutions.com)> wrote:
>>> Here are four of them I'm using for testing.
>>> 
>>> http://ogi.state.ok.us/ogi/Downloads%5CLidar%5C36096a8_NW_D.zip
>>> 
>>> I was using 36096a8_NW_C.las and the above pipeline xml. It is a 32 bit build of PDAL on Windows. If you can point me in the right direction, I can run in debug mode in Visual Studio and maybe see something. 
>>> 
>>> Roger 
>>> 
>>> 
>>> On Wed, Jul 17, 2013 at 3:36 PM, Howard Butler <hobu.inc at gmail.com (mailto:hobu.inc at gmail.com)> wrote:
>>>> 
>>>> On Jul 17, 2013, at 8:21 AM, Roger Bedell <rbedell at coordinatesolutions.com (mailto:rbedell at coordinatesolutions.com)> wrote:
>>>>> 
>>>>> The problem is I get this error:
>>>>> 
>>>>> C:\Users\roger>c:\dev\pdal\pcpipeline.exe -i C:\dev\pdal\ImportLASFile.xml
>>>>> Requested to read 8072702 points
>>>>> Requested to write 8072702 points
>>>>> Buffer capacity is 8072702
>>>>> 0Caught exception: bad allocation
>>>>> 
>>>>> Any suggestions?
>>>> 
>>>> Something's overflowing, but I don't have any idea where. Can you post the file available for download, and I'll give it a test locally on my osx box with gdb?
>>>> 
>>>> Thanks,
>>>> 
>>>> Howard
>>> 
>>> 
>>> 
>>> -- 
>>> Roger Bedell
>>> Coordinate Solutions Inc.
>> 
>> 
>> 
>> 
>> -- 
>> Roger Bedell
>> Coordinate Solutions Inc.
>> _______________________________________________
>> pgpointcloud mailing list
>> pgpointcloud at lists.osgeo.org (mailto:pgpointcloud at lists.osgeo.org)
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pgpointcloud
> 
> 
> 



More information about the pgpointcloud mailing list