Some improvement suggestions
Posted: Thu Sep 11, 2014 11:09 pm
Hi Daniel,
I really love CloudCompare and I use it a lot! I have a few suggestions which I think would improve my CloudCompare experience (even more!):
1. Rotate/Translate Handles.
For me, one of the most commonly used functions in CloudCompare is the translate/rotate tool. This is a really quick way of coarsely aligning two point clouds or a point cloud and a mesh. I think this tool could be improved if there were some on screen 'handles' that a user can manipulate to push/pull the object in 3D space. This would then leave the left and right mouse buttons free to orientate the view, and eliminate the need for the pause button.
Here's a screenshot from a typical 3d application which employs this technique 2. Recording and saving transformations
Quite often, I find myself transforming a point cloud from one orientation to another in several steps. For example, I might use the translate/rotate tool to coarsely align two point clouds, then perform a fine registration. These two operations currently produce two separate 4x4 transformation matricies in the console. If I want to repeat the process on a new point cloud, I either need to apply the two transformations individually (in the correct order), or combine them into one matrix somehow (currently I use Excel or matlab to do this). This can get quite messy if you move an object multiple times and you want to keep track of where it is!
I think it would be awesome if a transformation matrix was stored in the object properties. By default it would be a 4x4 identity matrix when you first import the object, each time you move it, the matrix would update.
It would also be useful if you could export this matrix to a text file
and for bonus points... maybe you could apply a matrix during import either by defining it manually or by applying a previously saved text file.
3. Dynamically changing point display settings
There are times when I need to deal with very large point clouds and for one reason or another, I don't want to sub-sample them. It would be nice to be able to reduce the amount of points which are actually displayed on screen without having to decimate the point cloud. Perhaps this could be at set intervals like 25%, 50%, 75% etc.
4. Have another go at getting the Faro SDK!
Native support for Faro .fls files would be awesome! I've managed to get my hands on the Faro SDK simply by contacting their customer service representative (ata.artuerk@faroeurope.com). Unfortunately, I can't share the SDK with you due to the NDA they make you sign, but it was a straight forward process for me. Maybe I'm just lucky!
I really love CloudCompare and I use it a lot! I have a few suggestions which I think would improve my CloudCompare experience (even more!):
1. Rotate/Translate Handles.
For me, one of the most commonly used functions in CloudCompare is the translate/rotate tool. This is a really quick way of coarsely aligning two point clouds or a point cloud and a mesh. I think this tool could be improved if there were some on screen 'handles' that a user can manipulate to push/pull the object in 3D space. This would then leave the left and right mouse buttons free to orientate the view, and eliminate the need for the pause button.
Here's a screenshot from a typical 3d application which employs this technique 2. Recording and saving transformations
Quite often, I find myself transforming a point cloud from one orientation to another in several steps. For example, I might use the translate/rotate tool to coarsely align two point clouds, then perform a fine registration. These two operations currently produce two separate 4x4 transformation matricies in the console. If I want to repeat the process on a new point cloud, I either need to apply the two transformations individually (in the correct order), or combine them into one matrix somehow (currently I use Excel or matlab to do this). This can get quite messy if you move an object multiple times and you want to keep track of where it is!
I think it would be awesome if a transformation matrix was stored in the object properties. By default it would be a 4x4 identity matrix when you first import the object, each time you move it, the matrix would update.
It would also be useful if you could export this matrix to a text file
and for bonus points... maybe you could apply a matrix during import either by defining it manually or by applying a previously saved text file.
3. Dynamically changing point display settings
There are times when I need to deal with very large point clouds and for one reason or another, I don't want to sub-sample them. It would be nice to be able to reduce the amount of points which are actually displayed on screen without having to decimate the point cloud. Perhaps this could be at set intervals like 25%, 50%, 75% etc.
4. Have another go at getting the Faro SDK!
Native support for Faro .fls files would be awesome! I've managed to get my hands on the Faro SDK simply by contacting their customer service representative (ata.artuerk@faroeurope.com). Unfortunately, I can't share the SDK with you due to the NDA they make you sign, but it was a straight forward process for me. Maybe I'm just lucky!