Something very much needed to aid in productivity and efficiencies in live projects is the ruling of Named Boundaries to Geometry to make them dynamic.
Some ideas include:
XS Named Boundaries are linked to Alignment station and alignment 3d origin point so update on Geometry change based on original parameters (individual named boundary overrides for L/R offset, top/bottom distances, etc. could be added to the Named Boundary properties and be set like the Annotation Whitespace Management so they are remembered on change or reset on update)
Similar to above, Plan and Profile Named Boundaries could work the same way, but have the start of Named Boundaries linked to the end of the previous ones and remember if the user has locked to the start and end of the geometry and keep that link on alignment change.
As a minimum, addition of editable offset, height, etc. would be much better than the clumsy update methods now - perhaps with graphical manipulators like MicroStation Clipping Boundaries but with editable values.
Also a dialog informing the user that base geometry has changed with something like “Do you want to reannotate Drawings for Named Boundary Group XYZ?” and a “Named Boundary XYZ has lost link to its Base Geometry link” would be very helpful and maybe a “Named Boundary Base Geometry Reattach” tool to relink it
| Civil Product Used | OpenSite Designer, OpenRoads Designer, OpenRail Designer, OpenBridge Modeler |
0
Future consideration
Yes to all!
For XS, two ideas.
if we cannot drag the limits of a named boundary, at least allow us to edit the parameters in the properties box. This would allow us to create all boundaries on a project at one width, then adjust the ones that need to be wider to either side, etc. Vertically as well too!
If manual adjustments are not possible, then be able to define a target for the left and right offsets. Just like a point control on a corridor. We can draw lines along a project to define XS limits, even make a linear geometry if needed, then the named boundaries limits can automatically extend to this geometry.
To include adding some non-plotting flat "terrains" to define upper and lower limits to allow all XS to stack in an orderly fashion. This would include clipping visible project terrains if they extend too far above/below the desired control terrains.
Absolutely, I agree with all of the above. This addition/change will enhance the user experience.