Global shift back when saving PCD using command line

[clucas]

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?

[daniel]

The current implementation of the PCD filter uses 32 bits floating point values to save coordinates in PCD files. Which means that you can't save large coordinates in such files.

I don't know if PCD files can handle 64 bits float values (I'm not the one who implemented this filter, and I don't know much about PCL).