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?
Jeff, here's my 2 cents. ... I've never used any type of 'auto-correction' on survey data. If the collection pushes the Face of Curb shot out over the gutter FL shot then that needs to be corrected in the field book by pulling that FC shot back into its correct position. Of course you know, Ffield collected survey data should not have crossing break lines. The Crossing Features Report, just like the InRoads Resolve Crossing Breaklines tool, is used to locate those crossing problems. ... but in my opinion, those crossing need to be corrected in the field book. I've been teaching / preaching that methodology for decades... and stand by it going into ORD.
Now, regarding whether or not the auto-correction in that tool works or not ... you may be right. It might be broken, and I'd have to test that. (And it looks like you've tested it and probably should log it with Bentley). But since I don't use it, it's a low priority on my list of things to check.
If the terrains are "survey generated", are your Survey Processing Rules activated?
Mark, thanks for your response! I agree with you that updating the source data is the best way to go about a fix. I guess the ability to easily tweak one specific point on a surface - as was the case back in SS2 - was something I was hoping to see in ORD. If that functionality was built into ORD, I've not been able to locate it. I'll file the SR with Bentley; I'm curious what they will say.
Jonathan, thanks for your reply! All rules are deactivated (i.e. the terrains are editable).
If you surface is built from your survey data can't you just move that point using the properties?