[pdal] pgpointcloud selector filter and max_capacity

[Andrew Bell]

On Wed, Feb 4, 2015 at 9:11 AM, Howard Butler <howard at hobu.co> wrote:

>
> > On Feb 4, 2015, at 3:37 AM, Oscar Martinez Rubi <
> O.MartinezRubi at tudelft.nl> wrote:
> >
> > 2 - There seems to be a hardcoded maximum of 400 points per patch in the
> pgpointcloud writer. I know that is the recommended patch size but for
> massive point clouds I use larger number which use to be possible with
> older PDALs but not anymore.
>
> > About the capacity I found out that i need to specify the capacity in
> both writter and chipper.
>
> Because of the way PDAL used to work, you needed to specify the patch size
> on both the writer and the filters.chipper. That doesn't have to be the
> case anymore (but still is). The issue that's left is how to communicate
> the filter's capacity down to the pgpointcloud writer...
>

We can eliminate the capacity option on the pgwriter, since it assumes
things are already chipped/split.  If we wanted to remove that assumption,
we'd have to do something else.

-- 
Andrew Bell
andrew.bell.ia at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20150204/c8621351/attachment.html>