<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Hey,<br></div><div class="gmail_default" style="font-family:monospace,monospace">I also use RPly,<br></div><div class="gmail_default" style="font-family:monospace,monospace">the precision is limited in ascii output,<br></div><div class="gmail_default" style="font-family:monospace,monospace">but nowhere near 3 digits.<br></div><div class="gmail_default" style="font-family:monospace,monospace">It's an easy tweak to the C code to change output precision<br></div><div class="gmail_default" style="font-family:monospace,monospace">Cheers,<br></div><div class="gmail_default" style="font-family:monospace,monospace">Rémi C<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-09-25 21:29 GMT+02:00 <span dir="ltr"><<a href="mailto:Dean.Hand.ctr@nga.mil" target="_blank">Dean.Hand.ctr@nga.mil</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Classification: UNCLASSIFIED<br>
======================================================<br>
<br>
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:<br>
<br>
<?xml version="1.0" encoding="utf-8"?><br>
<Pipeline version="1.0"><Pipeline version="1.0"><br>
<Writer type="writers.ply"><br>
<Option name="filename">outputfile.ply</Option><br>
<Option name="storage_mode">little endian</Option><br>
<Reader type="readers.pgpointcloud"><br>
<Option name="connection">dbname='lidar' user='user'</Option><br>
<Option name="table">lidar</Option><br>
<Option name="column">pa</Option><br>
<Option name="spatialreference">EPSG:26910</Option><br>
<Option name="where"><br>
PC_Intersects(pa, ST_MakeEnvelope(560037.36, 5114846.45, 562667.31, 5118943.24, 26910))<br>
</Option><br>
</Reader><br>
</Writer><br>
</Pipeline><br>
<span class=""><br>
-----Original Message-----<br>
From: Howard Butler [mailto:<a href="mailto:howard@hobu.co">howard@hobu.co</a>]<br>
Sent: Friday, September 25, 2015 2:21 PM<br>
To: Hand Dean NGA-II USA CTR<br>
Cc: <a href="mailto:pgpointcloud@lists.osgeo.org">pgpointcloud@lists.osgeo.org</a>; pdal<br>
Subject: Re: [pgpointcloud] ply and laz<br>
<br>
<br>
> On Sep 25, 2015, at 2:04 PM, <a href="mailto:Dean.Hand.ctr@nga.mil">Dean.Hand.ctr@nga.mil</a> wrote:<br>
><br>
> Classification: UNCLASSIFIED<br>
> ======================================================<br>
><br>
> Hi Howard,<br>
><br>
> 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...<br>
><br>
> Can you please help?<br>
<br>
I don't think pgpointcloud supports writing natively as ply? Are you using PDAL?<br>
<br>
If so:<br>
<br>
* What do you mean by "digits"? Do you mean digits after the decimal point?<br>
* What was original source data format before it went into pgpointcloud? LAS<br>
* 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.<br>
<br>
Howard<br>
<br>
<br>
</span>======================================================<br>
Classification: UNCLASSIFIED<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
pgpointcloud mailing list<br>
<a href="mailto:pgpointcloud@lists.osgeo.org">pgpointcloud@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/pgpointcloud" rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/pgpointcloud</a><br>
</div></div></blockquote></div><br></div>