LAS format give only 0.01 scale pointcloud.

Hi Niko-Petteri,

The scale is automatically set by ContextCapture based on the resolution of the input, and this can't be specified when creating a production. If this is a very important feature for you, you can suggest it here. It will be evaluated by Product Management. In the meantime, instead of using MicroStation if it is not available for you, you can use lastools' las2las tool to rescale the points, using las2las.exe -i "input.las" -o "output.las" -rescale 0.001 0.001 0.001

- Cyril

Cyril,

We have a 3D pointcloud production based from a block that contains 3 flights of UAS imagery.  The flights were at 100 feet, 200 feet, and 400 feet AGL.  Tiling for memory usage required 7 tiles.  The resulting .las files have two scales, some tiles are at 0.01 feet and some at 0.001 feet.  In this case we would prefer a fixed scale.  Also please fix the warnings from the LASInfo.exe tool.  You are applying an offset X Y Z to the 10th decimal place.  Seeing 10 decimal places in the "offset X Y Z" tells us that you could allow end users to specify the precision they want or need.  I do like the idea of setting the Synthetic flag once precision falls below the GSD of the UAS Imagery.  However, as you well know precision along the Z axis is different than the precision in the XY axis'.  

Can you check if any flags are set for these points? 

Synthetic flag should be set for all points but those which are from sparse point cloud could be calssified as model keypoints other points with different class and only then densified points below GSD as separate class. 

We checked with LASInfo.exe.  No Flags found.  We are on ContextCapture version 16.

We checked with LASInfo.exe.  No Flags found.  We are on ContextCapture version 16.