I was hoping not to have to add to my long list of posts on here regarding Terrain Model but alas, here I am again, this time with pictures and mock-able examples of probably what not to do, and looking forward to some of your awesome responses that have helped me so many times before. Looking back on my previous posts, I think it is no surprise that I find Terrain Modeling in ORD somewhat like Drainage Calc spreadsheets, voodoo magic. I have spent the better part of the last few months, off and on, trying to multi-corridor, multi-modeling method terrain models, both Existing and Proposed for various tasks, with none of them coming out to caliber in which does not raise end user eyebrows with spikes to zero, un-ruled boundaries, etc.
The above example, is an existing ground terrain model in which I ran the gauntlet or back door tricks, YouTube video workflows, Bentley Forum suggestions, Bentley Training work ups, etc. and CAN NOT for the life of me figure out why I still have spikes to zero, boundary issues, erroneous contours, etc.
If any body spots any red flags that I may not be doing correctly or didnt mention a workflow that you may have, please share! My new years resolution was to minimize my Terrain Model ORD posts.
Hey Shawn, thank you. This is all great feedback. I need to break your message down a bit and think about if I am doing what you are suggesting. The one feature I wish I could get a result out of within the Terrain Filter world would be the elevation rules. I know the elevation extents of my FG and to be able to get the zero elevation spikes to knock it off with that rule seems ideal. However, have had no luck with it in my testing.
Actually the best approach to "Edit" and create graphical filters is to only have the Civil Features checked and no other attributes selected when building those filter groups. For some reason, the process gets confused by too many search parameters. I know that method tends to work regardless what point names are applied to Corridor templates. If it's set to any one of those Top features, it will find them. It also seems to utilize the boundary type better than just setting the graphic to the typical terrain "boundary" type. It is my assumption the Boundary Option tool shown in the video uses the same method used by the Filter boundary type version. However, I think the Boundary Option tool gives more control in the local terrain file that may be reading across referenced Features.
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com
Thanks for the video Shawn. I had not seen that one previously. Do you have any experience with creating your own Graphical Filters and Utilizing them for creating Boundary Edge Methods? Just curious if that might be a good approach on this or not?
Hey Matt, Yes, I am using Graphical Filters to create. No Sir, there is no Elev 0 features within this particular model.
Hey Matt! Old video here, but the logic still applies...as the tools still exist in ORD... Check it out ... Video: Boundary Options He actually steps through some of the issues you've faced and how to tame them!