[pdal] Potree writer/reader

[Connor Manning]

There is a pointsPerChunk option for entwine:
https://entwine.io/configuration.html#points-per-chunk

On Tue, Dec 19, 2017 at 11:41 PM, adam steer <adam.d.steer at gmail.com> wrote:

> Hi Daniel, all
>
> PotreeConverter exists - and is dockerised - and while not super stable it
> does the job :)
>
> I had an off-list discussion with Connor a while ago about reading entwine
> directly using the potree viewer - without greyhound, purely for removing
> one extra http interface when looking at points; and using the greyhound
> API when we want to do stuff with points.
>
> However, looking more deeply, it might just be a matter of figuring out
> how to configure my entwine build to write smaller chunks, ie topping out
> at  a few thousand or few hundred thousand points (happy to take
> assistance, I was just minutes from posting an issue on entwine and/or
> e-mailing ) - at the expense of more files… which is a neat segue to...
>
> Potreeconverter writes out very many more, much smaller files than
> entwine; and writing out potrees is really bloaty - a 240ish GB entwine
> dataset turned out to be 700+GB of potree (as LASzip)!!! So this was
> smaller than the original LAS data by a few hundred GB, bout astoundingly
> larger than the LAZ’ed data and its entwine writeout.
>
> No religious opinion about whether writers.potree should exist or not, but
> thought I’d share some notes
>
> Cheers, hope that helps!
>
> Adam
>
> On 20 December 2017 at 15:01, Daniel Kastl <daniel at georepublic.de> wrote:
>
>> Yes. Less software to install is the main reason.
>>
>>
>> On Wed, Dec 20, 2017 at 12:59 PM, Howard Butler <howard at hobu.co> wrote:
>>
>>> Is there a compelling reason to not use the Greyhound + Entwine
>>> combination?
>>>
>>>
>>> On 12/19/17 9:57 PM, Connor Manning wrote:
>>> > As far as I know, this has not previously been worked on.
>>> >
>>> > - Connor
>>> >
>>> > On Tue, Dec 19, 2017 at 7:14 PM, Daniel Kastl <daniel at georepublic.de>
>>> wrote:
>>> >
>>> >> Hi list,
>>> >>
>>> >> Before starting to add a Potree writer/reader I wanted to ask, if
>>> someone
>>> >> has already worked on this. I looked around but couldn't find
>>> anything.
>>> >>
>>> >> Best regards,
>>> >> Daniel
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Georepublic UG & Georepublic Japan
>>> >> eMail: daniel.kastl at georepublic.de
>>> >> Web: https://georepublic.info
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> pdal mailing list
>>> >> pdal at lists.osgeo.org
>>> >> https://lists.osgeo.org/mailman/listinfo/pdal
>>> >>
>>> >
>>> >
>>> > _______________________________________________
>>> > pdal mailing list
>>> > pdal at lists.osgeo.org
>>> > https://lists.osgeo.org/mailman/listinfo/pdal
>>>
>>>
>>>
>>> _______________________________________________
>>> pdal mailing list
>>> pdal at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/pdal
>>>
>>
>>
>>
>> --
>> Georepublic UG & Georepublic Japan
>> eMail: daniel.kastl at georepublic.de
>> Web: https://georepublic.info
>>
>>
>>
>>
>> _______________________________________________
>> pdal mailing list
>> pdal at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/pdal
>>
>
>
>
> --
> Adam Steer
> https://www.researchgate.net/profile/Adam_Steer
> http://au.linkedin.com/in/adamsteer
> http://orcid.org/0000-0003-0046-7236
> +61 427 091 712 <+61%20427%20091%20712>
> skype: adam.d.steer
> tweet: @adamdsteer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20171219/99b8aee6/attachment.html>