Hi Andreas
I have seen this and looked into that some time ago. If I remember
correctly, sometimes the indexing algorithm when constructing the octree
decides to merge the more detailed "bucket" of points into the parent
"bucket" (that has bigger spacing), resulting in this kind of artifacts
where
Thank you!
On Wed, 9 Dec 2020 at 02:37, Nyall Dawson wrote:
> On Tue, 8 Dec 2020 at 23:59, Andreas Neumann wrote:
> >
> > Hi Martin,
> >
> > Thanks for the explanation.
> >
> > I confirm that reducing the maximum error helps to remove the artefacts.
> WIth 0.5 mm I could still see them at one p
On Tue, 8 Dec 2020 at 23:59, Andreas Neumann wrote:
>
> Hi Martin,
>
> Thanks for the explanation.
>
> I confirm that reducing the maximum error helps to remove the artefacts. WIth
> 0.5 mm I could still see them at one particular zoom level, but with 0.4 mm
> it was completely gone.
In https:/
Hi Martin,
Thanks for the explanation.
I confirm that reducing the maximum error helps to remove the artefacts.
WIth 0.5 mm I could still see them at one particular zoom level, but with
0.4 mm it was completely gone.
Thanks a lot,
Andreas
On Tue, 8 Dec 2020 at 13:15, Martin Dobias wrote:
> H
Hi Andreas
The artifacts you are seeing are caused by the fact how the Entwine tool
works in the default configuration. When creating the octree index of point
cloud data, points are organized in a hierarchy of nodes (each containing
usually tens of thousands of points), with each level of the hie
Hi,
When testing the 2D point cloud renderer I noticed that in certain
scales / zoom levels one can clearly see point cloud tile borders:
see screenshot at
https://www.carto.net/neumann/temp/point_cloud_artefacts.png
There seem to be different densities involved in certain regions here,
bu
