Re: Cloud-To-Cloud Issue
Posted: Tue Nov 21, 2017 7:01 pm
Hey Daniel, sorry it took so long. I have uploaded the LAS files to that same Dropbox folder. From more testing with 2.9.1 command line, I've learned the following:daniel wrote:Hum, with the E57 files, I can't reproduce the issue. I get the same result in the GUI and the command line mode.
I guess the issue do come from the LAS files. Can you send them to me?Code: Select all
CloudCompare.exe -silent -auto_save off -O Compared_201701031_Outside.e57 -O Reference_201701027_Outside.e57 -C2C_DIST -max_dist 0.5 -C_EXPORT_FMT E57 -no_timestamp -save_clouds
Note: regarding your command line, it would be more efficient to use the '-C_EXPORT_FMT E57 -no_timestamp' options before the -C2C_DIST option, and remove the '-auto_save off' and '-save_clouds' options. This way you'll get only one file (the compared cloud). Apart if you want both files as E57 files of course ;)
- Any number of uses of Global_shift AUTO breaks the cloud-to-cloud comparison when using LAS files
Or
Code: Select all
CloudCompare.exe -silent -O -GLOBAL_SHIFT AUTO Compared_201701031_Outside.las -O -GLOBAL_SHIFT AUTO Reference_201701027_Outside.las -C_EXPORT_FMT E57 -no_timestamp -C2C_DIST -max_dist 0.5
OrCode: Select all
CloudCompare.exe -silent -O -GLOBAL_SHIFT AUTO Compared_201701031_Outside.las -O Reference_201701027_Outside.las -C_EXPORT_FMT E57 -no_timestamp -C2C_DIST -max_dist 0.5
Code: Select all
CloudCompare.exe -silent -O Compared_201701031_Outside.las -O -GLOBAL_SHIFT AUTO Reference_201701027_Outside.las -C_EXPORT_FMT E57 -no_timestamp -C2C_DIST -max_dist 0.5
- Using default Global Shift & Scale triggering limits, cloud-to-cloud comparison works fine LAS files
Code: Select all
CloudCompare.exe -silent -O Compared_201701031_Outside.las -O Reference_201701027_Outside.las -C_EXPORT_FMT E57 -no_timestamp -C2C_DIST -max_dist 0.5
Code: Select all
Max absolute coordinate: 10^6
Max entity diagonal: 10^4