[pdal] pgpointcloud selector filter and max_capacity

[Oscar Martinez Rubi]

Good idea to try to purge boost!

At some point I though that the selection of dimensions could be done 
when I insert the point cloud format in the DB (I only insert a format 
with X,Y,Z) but I found out that after running PDAL the one I inserted 
is ignored and a new format with all the dimensions is used. So, we 
definitively need a way to tell the writter which columns are desired.

Just to be clear, the scale_x..., is supposed to be specified in the 
PDAL pipeline XML or in the point cloud format inserted in the DB or in 
both?

Well, I attach the sql file I execute to set the DB
and the pipeline xml I am using to run pdal pipeline.

With these ones I get a PDAL: ERROR:  unterminated quoted string at or 
near "....
Looks like mismatch between expected format and the actual block format

O.


On 04-02-15 16:04, Andrew Bell wrote:
> On Wed, Feb 4, 2015 at 7:37 AM, Oscar Martinez Rubi 
> <o.martinezrubi at tudelft.nl <mailto:o.martinezrubi at tudelft.nl>> wrote:
>
>     Hi,
>
>     About the capacity I found out that i need to specify the capacity
>     in both writter and chipper.
>
>     Still do not know how to select only x,y,z?
>
>
> Hi Oscar,
>
> Thanks for giving the code a try.
>
> Right now there isn't a way to select dimensions for write.  I'll add 
> some option to the writer to select the dimensions.
>
>     I was also trying to use scale_x,y,z but it crashes when inserting
>     the patch. Did somebody managed to do this?
>
>
> Please report the bug with some detail if things aren't working for 
> you.  I'm not sure that the postgres driver has gotten much of a 
> workout since the scaling code was added.  I'll try your pipeline.
>
>     <?xml version="1.0" encoding="utf-8"?>
>     <Pipeline version="1.0">
>         <Writer type="writers.pgpointcloud">
>             <Option name="connection">
>                  dbname='pf20' user='oscar'
>             </Option>
>             <Option name="table">patches</Option>
>             <Option name="compression">dimensional</Option>
>             <Option name="capacity">3000</Option>
>             <Option name="srid">28992</Option>
>             <Option name="scale_x">0.01</Option>
>             <Option name="scale_y">0.01</Option>
>             <Option name="scale_z">0.01</Option>
>             <Filter type="filters.chipper">
>                 <Option name="capacity">3000</Option>
>                 <Reader type="readers.las">
>                     <Option
>     name="filename">/home/oscar/ahn_minibench.laz</Option>
>                     <Option name="spatialreference">EPSG:28992</Option>
>                 </Reader>
>             </Filter>
>         </Writer>
>     </Pipeline>
>
>
> Also, I don't think anyone has tried boost 1.57 that I'm aware of.  
> We're trying to purge boost from our code because of issues like this, 
> but we haven't gotten there yet.  I'll build it and try.
>
> -- 
> Andrew Bell
> andrew.bell.ia at gmail.com <mailto:andrew.bell.ia at gmail.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20150204/b86cab65/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: init.sql
Type: application/sql
Size: 1720 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20150204/b86cab65/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pdal_pipeline.xml
Type: text/xml
Size: 740 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20150204/b86cab65/attachment.xml>