[pdal] [pgpointcloud] ply and laz

[Howard Butler]

The ply write code is using %g (shortest representation) for double output for fprintf for the ASCII output [1]. I wonder if %e would be acceptable, but I don't know much about ply.

[1] https://github.com/PDAL/PDAL/blob/master/vendor/rply-1.1.3/rply.c#L1340

> On Sep 27, 2015, at 3:14 PM, Rémi Cura <remi.cura at gmail.com> wrote:
> 
> Hey,
> I also use RPly,
> the precision is limited in ascii output,
> but nowhere near 3 digits.
> It's an easy tweak to the C code to change output precision
> Cheers,
> Rémi C
> 
> 2015-09-25 21:29 GMT+02:00 <Dean.Hand.ctr at nga.mil>:
> Classification: UNCLASSIFIED
> ======================================================
> 
> We are using PDAL.  There is a writers.ply, but did doesn't say what readers it will support.  We are using something similar to this xml:
> 
> <?xml version="1.0" encoding="utf-8"?>
> <Pipeline version="1.0"><Pipeline version="1.0">
>   <Writer type="writers.ply">
>     <Option name="filename">outputfile.ply</Option>
>     <Option name="storage_mode">little endian</Option>
>     <Reader type="readers.pgpointcloud">
>       <Option name="connection">dbname='lidar' user='user'</Option>
>       <Option name="table">lidar</Option>
>       <Option name="column">pa</Option>
>       <Option name="spatialreference">EPSG:26910</Option>
>       <Option name="where">
>         PC_Intersects(pa, ST_MakeEnvelope(560037.36, 5114846.45, 562667.31, 5118943.24, 26910))
>       </Option>
>     </Reader>
>   </Writer>
> </Pipeline>
> 
> -----Original Message-----
> From: Howard Butler [mailto:howard at hobu.co]
> Sent: Friday, September 25, 2015 2:21 PM
> To: Hand Dean NGA-II USA CTR
> Cc: pgpointcloud at lists.osgeo.org; pdal
> Subject: Re: [pgpointcloud] ply and laz
> 
> 
> > On Sep 25, 2015, at 2:04 PM, Dean.Hand.ctr at nga.mil wrote:
> >
> > Classification: UNCLASSIFIED
> > ======================================================
> >
> > Hi Howard,
> >
> > When trying to pgpointcloud to write as either a ply we're experiencing an issue.  For ply files, the x and y coordinates are only 3 digits in length. I don't see anything in our docs to explain this...
> >
> > Can you please help?
> 
> I don't think pgpointcloud supports writing natively as ply? Are you using PDAL?
> 
> If so:
> 
> * What do you mean by "digits"? Do you mean digits after the decimal point?
> * What was original source data format before it went into pgpointcloud? LAS
> * It is possible that the PDAL ply driver could be modified to support overriding the output precision, but some investigation would need to be done into the rply code that PDAL uses to read/write PLY. Quickly looking at the PDAL source. this feature doesn't appear to exist yet.
> 
> Howard
> 
> 
> ======================================================
> Classification: UNCLASSIFIED
> 
> _______________________________________________
> pgpointcloud mailing list
> pgpointcloud at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pgpointcloud
>