[pdal] [pgpointcloud] ply and laz

[Andrew Bell]

On Tue, Sep 29, 2015 at 10:16 AM, <James.V.Greenlee.ctr at nga.mil> wrote:

> Classification: UNCLASSIFIED
> ======================================================
>
> Thanks for highlighting the "precision" option in  the source!  It's not
> in the online documentation (http://www.pdal.io/stages/writers.text.html).
>
> Since my interest in the ascii version of PLY was for troubleshooting
> ingest into MeshLab, I can easily construct the PLY ascii using the headers
> from PLY binary and the CSV output from writers.text.  I agree with Pete
> that PLY ascii isn't very efficient and in most cases shouldn't be used,
> but it's very useful for troubleshooting.  Also, the PDAL implementation of
> PLY ascii is actually more efficient than the other text outputs because it
> alters the precision depending on if the value is an integer (no decimal
> places if it's an integer).
>

I'm almost finished with the precision option for ply output.


> Ideally, there would be a uniform "precision" option across all the
> textual outputs that allows for either a per field precision that matches
> the field order such as:
>
> '<Option name="order">X,Y,Z,Intensity,Red,Green,Blue</Option>'
> '<Option name="precision">7,7,3,0,0,0,0</Option>'
>
> Or a simpler single definition of precision for all fields (as currently
> implemented in writers.text) such as:
>
> '<Option name="precision">6</Option>'
>

I did this simple thing.  It just applies to X, Y and Z right now.

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