[pdal] pdal pipeline giving garbage in postgres

[Tom van Tilburg]

1) I'm not sure what you mean with "seed" file. Do you mean create it in a
postgres table? Or more like a config file that is read by pdal pipeline?
It would be nice if the pipeline file/lasreader could deal with a directory
instead of a file.
So in de pipeline.xml file it would look like:
<Reader type="readers.las">
                    <Option name="directory">/tmp/mylasfiles</Option>
All files have the same schema, I don't have to worry about that.

2) Exactly

I'm not unhappy with the way I'm doing it now by the way, but people with
less skills in batch processing could be saved a lot of worries if it could
be all handled from the pdal pipeline command.

On Mon, 28 Sep 2015 at 16:10 Howard Butler <howard at hobu.co> wrote:

> To clarify, the workflow you desire is:
>
> 1) Create a table with a "seed" file that contains the schema/items you
> wish to load
> 2) Load up 1000s of files into that single table
>
> If so, maybe we should modify the pgpointcloud writer to make that
> scenario easier to achieve. I don't think it would be too difficult.
>
> Howard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20150928/d1c2f2de/attachment.html>