Global shift back when saving PCD using command line
Posted: Wed Oct 05, 2016 3:45 pm
Hi,
I am trying to save a point cloud to a pcd file using cloudcompare command line, but I am having issues with the global shift. It doesn't seem to shift back to the original coordinates when saved. I have tried setting -GLOBAL_SHIFT AUTO but it still outputs the wrong coordinates. This is the command line I am using at the moment:
CloudCompare -SILENT -C_EXPORT_FMT PCD -o -GLOBAL_SHIFT AUTO /home/chris/Documents/ResearchArea.las -NO_TIMESTAMP -SAVE_CLOUDS
Using asc as output like this:
CloudCompare -SILENT -C_EXPORT_FMT ASC -o -GLOBAL_SHIFT AUTO /home/chris/Documents/ResearchArea.las -NO_TIMESTAMP -SAVE_CLOUDS
does give me the right coordinates. Any idea how I can fix this?
I am trying to save a point cloud to a pcd file using cloudcompare command line, but I am having issues with the global shift. It doesn't seem to shift back to the original coordinates when saved. I have tried setting -GLOBAL_SHIFT AUTO but it still outputs the wrong coordinates. This is the command line I am using at the moment:
CloudCompare -SILENT -C_EXPORT_FMT PCD -o -GLOBAL_SHIFT AUTO /home/chris/Documents/ResearchArea.las -NO_TIMESTAMP -SAVE_CLOUDS
Using asc as output like this:
CloudCompare -SILENT -C_EXPORT_FMT ASC -o -GLOBAL_SHIFT AUTO /home/chris/Documents/ResearchArea.las -NO_TIMESTAMP -SAVE_CLOUDS
does give me the right coordinates. Any idea how I can fix this?