How to save the cloud with Global Shift (Scale).

[aquariumbg]

First of all, I am impressed from this software - so many unique possibilities.
I am using it only 3 days and I have an issue. I tried to find the answer in the forum, but without success.
The problem:
I have PTX files with big coordinates – let say 630 000 m in X direction. I want to scale the whole cloud to 630.000. I am importing the PTX file in cloud compare and then Edit --> Global shift with scale 0.001. All works perfect.

Now I want to export the scaled cloud in format, which is possible to import to LFM Server (E57).
Export is OK but when I import the E57 file back in cloudcompare the coordinates are no scaled.
IF I export the cloud in BIN format and import back, coordinates are CORRECT!?

Unfortunately, I can use only PTX, PTZ, ASTME57 and FLS formats.
Where I am wrong? Probably this is not the correct workflow. Thank you in advance.

[daniel]

Indeed, BIN files are storing the current 'project' (or at least the highlighted elements) and everything should stay consistent in CloudCompare when you reload them.

When exporting to E57, the Global Shift and Scale will be simply 'reverted' and things may not stay consistent. Well, in the general case it should (if you use a recent version of CC, and stick to the default process), but I can imagine some tricky cases where the scale is not applied where you would expect it, for instance if you set the Global Scale after loading a file with a Global Shift already applied.

So the right workflow should be:
- use the latest version of CC (2.9.1)
- load the cloud with the 'Global Shift' translation as suggested by CloudCompare
- use the 'Edit > Multiply / Scale' method (http://www.cloudcompare.org/doc/wiki/in ... iply/Scale)
- make sure the 'Rescale Global shift' option is checked
- export to E57

I hope it works. Otherwise don't hesitate to post a new message or send me a message directly (cloudcompare [at] danielgm.net).

[aquariumbg]

I will check this as soon as possible and I will post the result here.
Thank you for the quick answer.

Yes, the scale is applied AFTER loading the file, because there is a bug ( at least on my computer) – the Global shift window appear for a few seconds and then Cloudcompare starts to import the PTX file without to wait for my answer (I am using the last version of the program, Win10 x64t). So I just agree with the proposal of the program (quick) and then applying the Global Scale shift.

[daniel]

Hum, I'm not sure I ever encountered a PTX file with large coordinates, but the 'dialog closing itself' issue is a bit weird (as it should work the same as with the other formats). Don't you have an issue with your keyboard ? :D.

By the way do you load the file via the 'File > load' menu, or by dragging it on the 3D view?

[aquariumbg]

Your method to export the cloud with changed coordinates WORKS!
Thank you. I will try tomorrow to import the E57 file in LFM server.

The big exist, my keyboard is OK :) But this is not a big problem, i am quick enough :)
Thank you again for the perfect program.

[juacarri]

Indeed, BIN files are storing the current 'project' (or at least the highlighted elements) and everything should stay consistent in CloudCompare when you reload them.

When exporting to E57, the Global Shift and Scale will be simply 'reverted' and things may not stay consistent. Well, in the general case it should (if you use a recent version of CC, and stick to the default process), but I can imagine some tricky cases where the scale is not applied where you would expect it, for instance if you set the Global Scale after loading a file with a Global Shift already applied.

So the right workflow should be:
- use the latest version of CC (2.9.1)
- load the cloud with the 'Global Shift' translation as suggested by CloudCompare
- use the 'Edit > Multiply / Scale' method (http://www.cloudcompare.org/doc/wiki/in ... iply/Scale)
- make sure the 'Rescale Global shift' option is checked
- export to E57

I hope it works. Otherwise don't hesitate to post a new message or send me a message directly (cloudcompare [at] danielgm.net).

Daniel, could you let me know if there is something similar to be applied via command line? I want to open a .Las file and save the cloud with the coordinates shifted.

[juacarri]

Indeed, BIN files are storing the current 'project' (or at least the highlighted elements) and everything should stay consistent in CloudCompare when you reload them.

When exporting to E57, the Global Shift and Scale will be simply 'reverted' and things may not stay consistent. Well, in the general case it should (if you use a recent version of CC, and stick to the default process), but I can imagine some tricky cases where the scale is not applied where you would expect it, for instance if you set the Global Scale after loading a file with a Global Shift already applied.

So the right workflow should be:
- use the latest version of CC (2.9.1)
- load the cloud with the 'Global Shift' translation as suggested by CloudCompare
- use the 'Edit > Multiply / Scale' method (http://www.cloudcompare.org/doc/wiki/in ... iply/Scale)
- make sure the 'Rescale Global shift' option is checked
- export to E57

I hope it works. Otherwise don't hesitate to post a new message or send me a message directly (cloudcompare [at] danielgm.net).

Daniel, could you let me know if there is something similar to be applied via command line? I want to open a .Las file and save the cloud with the coordinates shifted.

I was sure that Daniel thought in this before. In order to preserve the global shift, it should be used the command "-DROP_GLOBAL_SHIFT". Following you can find an example of usage in a folder which contains hundred of .Las files:

Code: Select all

for %%f in (*.las) DO CloudCompare -SILENT -C_EXPORT_FMT LAS -o -GLOBAL_SHIFT AUTO %%f -DROP_GLOBAL_SHIFT -NO_TIMESTAMP -SAVE_CLOUDS 

[daniel]

Yes, exactly ;)