LAS timestamp field size
LAS timestamp field size
Our scanning device records time in UNIX time, currently 1.45E9, and outputs data in LAS format. CloudCompare appears to be unable to read timestamps this large and retain precision. Is this something that could be fixed?
Re: LAS timestamp field size
What version are you using?
Since version 2.6.2 we shift the time values (using the first one as reference). Then values should be properly restored at export time.
Since version 2.6.2 we shift the time values (using the first one as reference). Then values should be properly restored at export time.
Daniel, CloudCompare admin
Re: LAS timestamp field size
Anyway I updated the code so as to split the Time field on two scalar fields (one 'low' with values below 1e6 and one 'high' with multiples of 1e6).
There's no better choice for now as scalar fields are 32 bits to save memory.
And most importantly, the values are merged together at export time so as to restore the original time value/ precision.
There's no better choice for now as scalar fields are 32 bits to save memory.
And most importantly, the values are merged together at export time so as to restore the original time value/ precision.
Daniel, CloudCompare admin