I have a question that... well, I think it is simple, but maybe not. I have several terrains in a single DGN. I'm using ORD 2021 R1 on Windows 11. The terrains were generated from imported survey from a CSV.
Many of the terrains include curbing... which includes the front face of curb and also the flowline (front bottom face of curb). These two lines are about six inches (the height of the curb) apart vertically, but only and inch or less horizontally. Because the way these features' points connect to each other, there are very minor albeit overlaps in the top and bottom faces. Since it's known what these are it's not a huge deal, but we want to correct them. So, we choose Terrain-->Analysis-->Reporting-->Report Crossing Features. The TCF report opens up and shows all the overlaps. I select one, or two, or all entries (the number does not matter), right-click, and choose the method "Insert a Point into both Features at an average Elevation". No matter which terrain I use, or how many entries I select, I see ORD calculate the elevations for each point. But aside from that, the command does nothing. At all. No entries disappear. No entries change.
The exception to this were the methods that did resolve the issue: "DeleteFeature1" or "DeleteFeature2." However, since I only have two features to define the face of curb, I need both features and cannot delete either of them. But a "nondestructive" method did not work, and changed nothing.
I have confirmed all terrains are editable and have no rules active. I've seen the various methods demonstrated in YouTube videos; once the crossing features' entries on the TCF report are selected, and a right-click used to select the method to resolve the crossing features, the entries disappear immediately. Thinking it may be specific to terrains imported from survey, I quickly drew two rectangles that overlapped one another: one at elevation 5, and one at elevation 10. I then selected both and opted to create a terrain from selected elements. I then chose to Report Crossing Features... and as expected, two overlaps were reported in the TCF Report. But just like the terrains imported from Survey, I could not resolve the crossing features - unless I chose to delete one or both features. The nondestructive methods calculated points, but changed nothing.
So... am I missing something? A setting maybe? Or have I discovered a bug?
Just a different 2 cents...
When the DOT I work at started using data collectors, they found it was too difficult to collect a flow line and a top face of curb and not get crossing breaklines. This is compounded when collecting curves. So, we adopted the practice of collecting only the flow line and the top back of curb. While it is less accurate, everyone understands that the sloped face is a representation of the actual curb.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page