Point Cloud coordinate problem.

[Sunalcredo]

Hi everyone!
 I need some help. So I import a .las* file to VW 2024. And the coordinates are loaded in a row. How can I fix this problem? (26.508.164 points*)

Thanks,

[Tom W.]

I have experienced the same when importing a point cloud into a georeferenced file. If I import it instead into a 'normal' file where the User Origin + Internal Origin are coincident + ensure that 'Center Import on Internal Origin' is enabled in the Import Point Cloud Options then everything is fine: all the points are present + correct + you don't get the bands where they're missing.

 

Note: in my experience it is not simply a matter of ensuring your Internal Origin is in the right place relative to the location of the point cloud. The only way to eradicate the stripy (missing) points phenomenon is to ensure that the point cloud is also centred on the User Origin. Basically you have to choose between georeferencing or having the point cloud display correctly. You aren't able to have both. That was my experience at least.

 

User origin:

 

Internal origin:

[Anders Blomberg]

Unfortunately this seems to be a current flaw in VW. When importing georeferenced point clouds they always turn out this way. The very unfortunate solution for those of us who are absolutely dependent on proper georefencing is to import on internal origin and move it as well as you can manually afterwards. 

 

[Tom W.]

2 minutes ago, Anders Blomberg said:

Unfortunately this seems to be a current flaw in VW. When importing georeferenced point clouds they always turn out this way. The very unfortunate solution for those of us who are absolutely dependent on proper georefencing is to import on internal origin and move it as well as you can manually afterwards. 

 

Good to have it confirmed by someone else. I have complained to VW about this but never got anywhere.

 

I get my friendly surveyor to include a special datum point with known coordinates off to the side of the scan, allowing me to georeference the file after import then move the point cloud to that location. At it ends up at the exact correct location but crazy you have to go to these lengths. Defeats the whole point of georeferencing.

[Anders Blomberg]

I've spoken to them about it as well and am under the impression that it might be fixed during a larger point cloud-revision. Agreed that it's an absolute pain as it is currently though.