Descartes - 3SM from Corridor-Clipped Terrain

Hi Mike,

Voids should be supported.

Could you provide your dataset for investigation? 

Thanks,

Mathieu

Having troubles uploading here. Will look for alternate host and send link, but you should be able to find more info on SR#7000766574 if you can access it.

Edit: Here's a link: Example.dgn

Yes, exporting to an external file and using that to create the 3SM doesn't fail outright, but the voids are not properly honored regardless of zoom level.

Official response from SR is, "The tool cannot be used in the way that you wish. You can only convert 3MX realty meshes to 3SM format". I suppose I could be misusing the tool, but there appears to be a lot more functionality included than just 3MX conversion.

Thank you for your suggestions.

-Mike

Hi Mike,

Importing TM element from .dgn should work, so I have entered the following defect in Descartes backlog :

Defect 877635:[DC][3SM] Error when importing TM from user's DGN

As for the voids not properly honored it might be some limitation.

If you could provide me your .tin file I could check the status with our latest internal build.

Thanks,

Mathieu

Thank you for the capability confirmation and for the defect information.

Here is a link to the TIN file you requested:

https://studio.bluebeam.com/share/nvywg5

Thanks,

-Mike

Hi Mike,

Haven't time yet to check your TIN yet but if what you want to do is clip out the terrain where a road is passing you could try the Mask capability in the Reality Mesh manager dialog (work but only for mask with limited amount of vertices).

The real solution would probably be to integrate the clipping solution we create for OpenRoads ConceptStation (which would mask automatically the corridor where a road is passing) but this is not yet available in Descartes or MicroStation based Civil products.

HTH,

Mathieu

that's a good point. I may do some experimentation in ConceptStation as well.

I tried masking the 3SM, but it must have had some odd geometry to the shape or too many vertices. It just caused the mesh not to display at all.

Any idea where the vertices' count falloff is? I may be able to simplify the mask geometry enough to keep the low LOD mesh from popping into my proposed roadway in the distance for the most part.

Thanks,

-Mike

that's a good point. I may do some experimentation in ConceptStation as well.

I tried masking the 3SM, but it must have had some odd geometry to the shape or too many vertices. It just caused the mesh not to display at all.

Any idea where the vertices' count falloff is? I may be able to simplify the mask geometry enough to keep the low LOD mesh from popping into my proposed roadway in the distance for the most part.

Thanks,

-Mike

Hi Mike,

I have tried your .tin file and I am also seeing some problem with the application of the void.

In any case you would be better using some non-destructive clipping.

As for the number of vertices I would say a few hundred max. The mask shape should also not have any overlapped.

Well the limitation is for the Reality Mesh manager dialog mask only. The mask technology developed for ConceptStation can have as many vertices as you want (i.e. : scalable clipping).

HTH,

Mathieu