Terrain Models from Point Clouds Issues

Hi,

There are some issues with Point Clouds and Terrain Models and I believe it is not WAD.

1) When we create Terrain from Point Cloud our source *.pod file is imported to temporary Point Cloud.xyz file in the background (behind the scene). This will lead us to problems when we have several terrain models created from Point Clouds. The Point Cloud.xyz file is overridden every time we create Terrain from Point Cloud. Hence, when we have a few Terrain Models created from Point Clouds (not even within single dgn file, but in many dgn files stored at single PC as well), the temporary Point Cloud.xyz file refers to the last terrain model we created.  Then try to Update your Terrain Models from the source - all terrain models will be updated to the temporary PointCloud.xyz file while should be updated to adequate Poind Clouds files (*.pod). Now as a result when updated  all different Terrain Models are overridden with the last one we created. Am I right or my workflow is incorrect.

2) When Creating Terrain Model from Point Cloud, the terrain model will not inherit its name from Point Cloud name. Again when we are working with multple Point Clouds attached to a single dgn file, we can not control which Point Clouds were converted to terrain models.

3)Multiple Point Clouds are attached to a single dgn file. We need to create a few terrain models from these Point Clouds and then we want to create Complex Terrain Model. How can we choose single Point Cloud to create Terrain Model? Is the  only way to control that is to attach ore display on/off Point Clouds one by one as we create terrain models. Combine that with issue I described in 1) and 2) and imagine how many inconveniences that makes.

I hope I am clear enough. If incorrect, please correct my workflow when working with complex terrain model created from multiple terrain models created from multiple  point clouds.

thank you in advance

.

  • Hi Adam,

    1 - your assumptions here are correct but the temp file should get regenerated on 'update from source' but it's currently not. This is a known defect.

    2 - The name for the terrain model is user definable at creation time but ideally if working with a single point cloud that name could be inherited.  In the instance of  several point clouds perhaps this generic name is appropriate but again the user can redefine but perhaps we could list all point cloud names being imported in the left had tree view.  I will raise an enhancement to cover this.

    3 - the control for which point cloud is imported is done via the display management . Each terrain should retain  its source but as you've found with 1 it's looking to the xyz file. So yes there would be a problem.

    Have you considered creating a graphic shape representing the boundary  and setting this as the active fence. This allows importing from many attached terrains in the active fence and it simplifies the many to a complex terrain situation. By retaining these fences there is also a route to overcome problem described in 1 as the appropriate fence can be selected to generate the temp file before updating from source again.

    Regards

    Ian



    Answer Verified By: Adam Wieczorek 

  • Thanks Ian,

    Can you expand your idea regarding boundary shapes and fences. I am afraid I don't catch your point here.

  • This video may help with your workflow on combining and creating new clouds from a given shape (i.e. fenced area)

    www.youtube.com/watch

    HTH

    Michael Barkasi

    Application Engineer 

    Reality Modeling