I'm using ORD 10.08.01.33. I quickly made two dummy DGN files to test some weird behavior that I was seeing on a project:
The shape & region are shown below:
If I'm in a.dgn, the area of the gray region is 17763.434 SF, measured using both the element properties and the Measure Area -> Element tool.
If I'm in b.dgn, the area of the gray region is also 17763.434 if the a.dgn reference is not clipped. If I draw a random fence safely outside the shape and Clip Boundary to the fence, the area (measured with the Measure Area tool) changes to 17601.550 SF!
No Clip: (17763 SF)
With Clipped Boundary: (17601 SF)
I tried to duplicate this behavior in PowerInRoads SS10 and could not. The area of the region was the same, regardless of whether the boundary of the reference was clipped.
Why does Clip Boundary affect the output of the Measure Area tool?
a.dgn b.dgn
While I can't be certain, You may be seeing the same thing discussed in this post: https://communities.bentley.com/products/microstation/f/microstation-forum/191138/surface-area-discrepancies/564623#564623
It might be a good idea to save off these drawings as examples. File a Service Ticket, and send them these files. If it is related to the defect, they will be able to tell you so and you will have contributed toward the fixing. If it is not related to that specific defect, they will be able to help you figure out what is going on, or they can file a new defect for you.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Answer Verified By: Steven Vander Giessen
Thanks! That does appear to be the exact same issue & bug. Somehow that post evaded my searching.
You're welcome. I thought I'd seen something like that, so I knew what I was looking for.Some days the search mojo is flowing, and some days I can't search my way out of a paper bag...
I hope they'll be able to get you in the loop with that defect.