Point import very different in processing time...

[c-r-o-n-o-s]

Hello.

I have several LAS files here.
If I import them as "Local coordinate system" the import is VERY fast.
Unfortunately, you can`t switch to the "correct" system after import.

If I load the file directly with the correct specification of the system, the import takes longer than average.
So long that it is impractical.

Is there not another way for the import?

[Alexey Pasumansky]

Hello c-r-o-n-o-s,

Which coordinate systems you are typically using, do they use geoid height? And what is the approximate number of points in the files being imported, so that we could try to reproduce the problem on our side for similar point clouds?

[c-r-o-n-o-s]

The LAS data are in ETRS89 / UTM zone 32N with "own" vertical coordinate system. (DHHN2016)
30.069.456 Points.

[c-r-o-n-o-s]

I see that the "error" goes back to possibly something else.
I had to create the LAS from multiple LAZ in CloudCompare.

The problem was when I load in multiple point clouds (tiles) in Metahshape and merge them into one, all the classifications are thrown together when I merge.
I will think of something else to do there.