Ask A Question I

Thu, 02 Jul 2020 02:23:31 GMT

Ask a question in a forum.

Point cloud imports for terrain model resulting in strange Z-values almost like segments (Cloudcompare to microstation)

Simon Ene — Thu, 02 Jul 2020 16:30:41 GMT

Hi,

I'm using microstation V8i and cloudcompare v2.11.0.
I've been using cloudcompare with LiDAR data to make terrain models of an area (mesh/surface). I wanted to have certain areas of more refined detail and some areas that didn't need it.

I saved the finished pointcloud i was happy with as both LAS and ASCII and continoued to attach as point cloud in microstation.

For some reason the LAS file didn't import correctly and I have no idea why that is because I also tried the same thing in recap + Civil 3d and that worked fine.

Anywas, the ASCII import went fine and, but the points looked segmented between heights which I of course dont want.

I also tried to do everything trough recap and civil3d, then export back to microstation with a landXML, but still the same thing happens.

I've included a picture of what i got (surfaces) from autodesk (to the left and what I want), and microstation (to the right).

For a smaller area I tried to attach as reference and drop element, then triangulate in inroads and that worked fine, but for larger areas the drop element on such a big terrain makes microstation freeze/crash.

Are there any solutions to this?

ASCII point cloud:

communities.bentley.com/.../4137.ASCII_5F00_Pointcloud.txt

Regards,
Simon

Simon Ene's Activities

Ask A Question I

Point cloud imports for terrain model resulting in strange Z-values almost like segments (Cloudcompare to microstation)