To enhance productivity and efficiency in live projects, we need dynamic Named Boundaries linked to Geometry. This includes the ability to update the shape or location of a named boundary after creating a sheet model, with the changes reflected in...

Summary: When users turn levels off in the Default 3D models, that display state does not carry into cross section drawing/sheet models without opening them more than once. This creates unexpected sheet output where items that are intentionally hi...

Looking at creating cross section named boundaries so there is a variable left and right offset and would be good if it could follow an offset line. Can use the 2 point cross section option but takes additional time to cut individual sections. Thi...

Currently users need to remove all annotation per drawing or in all drawings with no control. An additional "Delete Drawing Annotation" with the same options as the annotate drawings one but with an additional "All Drawing Annotation Groups" optio...

Plan-Profile[LT]-Profile[RT] (and Profile[LT]-Profile[RT]) sheet creation for LT/RT split/bifurcated profile grade lines has been requested more frequently by our internal designers and our consultant designers. We have a workflow that can accompl...

Currently, vertical geometry can ONLY be displayed within the profile model of its parent horizontal alignment. On complex roadway projects, this profile view often contains numerous overlapping elements, such as: Northbound and southbound PGLs ...

Add ability to create XS by selecting multiple Line String containing more than 2 points.

OpenSite Designer currently displays terrain contours as dynamic, rule-based graphics that remain associated with the terrain model. While this workflow is suitable during design development, some users require permanent contour graphics during dr...

we should be working from 3D space to place drawing our model. being able to place lines on or offset from a known point elevation to another. When looking at a point in a view window if moving that point in that orientation moves it along that pl...

Currently our DOTs require that if elements are outside the width of the default limit, the user needs to create a matchline and/or split the cross sections. Currently this is a very manual process. This should be more automated.