Better default value for spacing about potreeconverter HOT 4 CLOSED

Hi. Do you mind if I work on this? I need it.

Thank-you.

from potreeconverter.

Yes, please, this would be a much needed feature!
You'd have to account for different scenarios, though, like

• Small point clouds with a uniform extend in all axes, like the lion point cloud that is included in the potree resources.
• Large scale LIDAR data that has large length and width but relatively small elevation.
• Different point densities. The number of points relative to the volume may or may not have to be taken into account as well.

Idealy, the default spacing should be choosen so that no or very few nodes are larger than 1mb. Larger nodes have a negative impact on load times but also culling efficiency and therefore rendering performance. At the same time, the spacing must not be too large or there will be too much nodes with a small number of points in it which also negatively affects performance.

from potreeconverter.

Nice. At a first stage I'll let the user decide the point quantity per linear dimension, so that the spacing value will be computed from that.

For example:

PotreeConverter -a 1000

will compute spacing as 1/1000 of the diagonal of the bounding box. I think that using the diagonal will accomodate both the first and the second point.

from potreeconverter.

Fixed: #76

from potreeconverter.