Compass Tool's Trace Tool - gap tolerance

[jmcnabb]

I've been using the Compass Tool's Trace Tool for some time and find it very useful. However, I often have point clouds with variable point density and I find that the Trace Tool will fail to bridge between points when the space between them reaches some threshold distance. It would be very useful to know 1) what is that set distance beyond which the tool will not bridge between points, and 2) if there any way to adjust (increase) that distance. The second point is the most important. If there were a way to increase the gap tolerance, this tool would be far more useful and a lot of time would be saved. Thank you

[daniel]

Maybe the best way to get an answer would be to contact the author of the plugin directly: https://www.samthiele.science/ (you can find an email address on this webpage - if it doesn't work, you send me an email (to admin [at] cloudcompare.org) and I can give you the author's personal email address).

[daniel]

Another option is to dig in the code, but that will depend on how good is your C++ ;)
https://github.com/CloudCompare/CloudCo ... ceTool.cpp

[jmcnabb]

Thanks for the reply. I'll reach out to the plugin author. That's a far better bet than me digging into the code!

[Zetly_Casper]

The PCP export can definitely be a bit of a headache when the orientation doesn't line up perfectly with the physical site. I've found that doing a quick real-world check helps troubleshoot those 'flipped' axes before I even start the export. I usually just pull up https://123compass.org/ on my phone to verify my physical heading relative to the scan (old habits die hard, haha).
By the way, are you seeing any specific error in the rotation matrix, or is it just the translation coordinates that are off? I'd love to know if there's a simpler way to handle the offset directly in CloudCompare without jumping into a spreadsheet later!