Bug in translation with big coordinates

If you are allergic to bug trackers, you can post here any remarks, issues and potential bugs you encounter
Post Reply
TMK
Posts: 4
Joined: Mon Apr 24, 2017 8:15 pm

Bug in translation with big coordinates

Post by TMK »

Hello, I realised that when big translations are applied (for example X:-28534195.780001, Y=-6576591.278002) to point cloud cloudcompare does not take into account those last digits and makes translation wrongly with X:-28534196.000, Y=-6576591.500. I am using version 2.9. I also confirmed those translations with Microsoft Office Excel. Can someone duplicate and verify this ?


Br,
TMK
daniel
Site Admin
Posts: 7709
Joined: Wed Oct 13, 2010 7:34 am
Location: Grenoble, France
Contact:

Re: Bug in translation with big coordinates

Post by daniel »

Indeed, the fields in the "Global Shift & Scale" dialog are not meant to be used with so much digits. Therefore they probably truncate the input value. If you want to use such values, you would need to increase the 'precision' of these fields and recompile the project. Or maybe more simple, use the command line version of CloudCompare to input the Global Shift values directly.
Daniel, CloudCompare admin
Post Reply