While unfolding a point cloud along a polyline, I ran into a problem with the dimensions of the resulting raster.
My test cloud is about 2000 m long and is a scan of a high-voltage power line running through fairly flat terrain. There are a few ditches and small depressions, but these are the largest elevation differences along the entire test cloud. To create the unfolding line, I first used the Trace Polyline tool, but later I switched to creating a vector in QGIS and then importing it into CloudCompare.
I created two polylines:
- a 2D only vector (no Z coordinates), which later I had to align manually with the cloud I wanted to unfold,
- a 3D vector, draped over a digital terrain model that reflects the terrain breaks and depressions (this one fit the cloud perfectly).
This leaves me with a few questions:
- When using 3D profiles, does CloudCompare “stretch” the scan (viewed as a cross-section) so that the distances correspond to the length of the vector?
- Should I expect even larger differences when scanning mountainous terrain?
- Is there a risk that a vector closely following the cloud could cause the cloud to be “normalized” and displayed as a flat surface, in addition to stretching the scan?
- In mountainous terrain, where a 2D line would cross (pierce) the terrain surface multiple times, could this cause deformations in the unfolded cloud, or should it not affect it?