How can a Microstation Terrain be given civil rules i.e. turned into a ORD Terrain? For context the Terrain has come from a STM.
I've tried to follow the official documentation i.e. Set Feature Definition, select Terrain category: https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/21738/use-scalable-terrain-models-in-openroads
But nothing happens, no errors etc., just says as a Terrain. Tried changing the Terrain resolution and extents but no difference. Also tried leaving it as no feature definition.
Any ideas?
It might be necessary to "dumb down" the terrain to remove its link to the STM. The STM tools use advanced terrain capabilities that are not directly supported by ORD or MicroStation. They support a level-of-detail display, thinning points and contours on the fly as you zoom in and out. Once the terrain is just a terrain, the number of points and contour display will be constant and you should be able to assign Civil Rules and a Feature Definition.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Thanks. I tried this but it didn't work hence I thought I might be missing something, must have been a problem with the specific Terrain. In the end I just ended up dropping it down into a mesh (from memory) and creating a Terrain from that.
Answer Verified By: Ken Bagnall
Hi Ken,
Sorry for late response,
In order to make the MS Terrain legit for ORD you have to Featurize it.Apply a Feature definition and it will be ok with ORD.
Vincent RAULT [Bentley]
Thanks for the response. I did try doing that after reading it somewhere online by using the set feature definition tool but it wouldn't work. I suspect it didn't like something about the Terrain, maybe part of it's geometry, maybe it's size, never figured it out....
Ok, it should work on 2022 R1.
I had issues in the past and had to use workaround : export MS Terrain ans LandXML and import LandXML, but again I worked on my last use cases, so you may give a try next time...
I did do it on 2021 so you may be correct. I'm on 2022 now so will try it when it comes up again. Otherwise I'll give your workaround a try. Thanks.