Coordinates length

[celamk]

Hi!

While doing demo of CC to some people from geodesy they pointed out issue/feature related to coordinates. According to them global coordinates sampled from LIDAR cloud are not accurate enough as they are too short. Number preceding coma is ok, but there is not enough data after the separator... But this refers to X and Y data only. Z values have more content despite same length in terms of the symbols.


Is this a limitation of the CC with this regards? Can it store and export data in 13/14-sign (digits + separator) only?
If not - which setting of the CC should I modify to uncover full coordinates of the measured point?

[daniel]

This is related to the 'Global Shift' mechanism. CC stores only 32bits values to reduce the memory consumption. If you reject the Global Shift at loading time, and keep global coordinates, you'll indeed lose accuracy.

You should accept the (temporary) Global shift while working on the cloud. It will be restored at saving time.

[celamk]

Yup, thats it.
Thanks Daniel