[pdal] pgpointcloud : is pdal compressing pcpatch before sending them to database?

[Paul Ramsey]

Pgpointcloud lets you extract compressed results. If you don't apply
the PCUncompress function, you get the compressed version, as it lives
in the disk serialization. I didn't make this a standard thing for
PDAL driver because I didn't want people to get into the habit of
copying the comressor/decompressor code everywhere. If we had a
standard compression like laszip in use, so standard decompressors
could handle it, that would be better.

On Thu, Apr 28, 2016 at 5:50 AM, Howard Butler <howard at hobu.co> wrote:
>
>> On Apr 28, 2016, at 6:52 AM, Rémi Cura <remi.cura at gmail.com> wrote:
>>
>> According to
>> https://github.com/PDAL/PDAL/blob/master/plugins/pgpointcloud/io/PgWriter.cpp#L483
>> and
>> https://github.com/PDAL/PDAL/blob/master/plugins/pgpointcloud/io/PgReader.cpp#L138
>>
>> It seems that the compression/decompression is always done by the database,
>> correct?
>
> Remi,
>
> I think the comments on line Writer#483 are a little inconsistent. Writer looks like it always inserts uncompressed, hex-encoded data to PostgreSQL and lets the extension do what it wants with it for compression. On the PgReader side, it looks like it always asks for  PC_Uncompress which presumably has no impact when the patch is actually uncompressed.
>
> Maybe Paul can chime in with more detail on the intent of how this is supposed to work.
>
> Howard
> _______________________________________________
> pdal mailing list
> pdal at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pdal