Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
ADD A NEW IDEA

All ideas

Enable scaling of .3sm reality meshes attached via the Reality Mesh Attachments tool in ORD

In OpenRoads Designer 2025, .3SM reality meshes attached using the Reality Mesh Attachments tool cannot be scaled. Currently, users must rely on Transform Element or attach the .3SM as a reference to apply datum adjustment scaling. Users request n...
2 months ago in Modeling 0 Needs review

Civil labeler-label slope along element between vertices for profiles and cross sections

Need ability to label slope along element between vertices for profiles and cross sections.
over 3 years ago in Annotation / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Future consideration

Complex Terrain - Rename "merge" and "append" to something more descriptive

Suggest renaming the "merge" and "append" functions when creating a complex terrain to something more descriptive of the action being performed. For instance, merge could be renamed to "overwrite" and append could be renamed to "use both". Users h...
about 1 month ago in OpenRail Designer / OpenRoads Designer / Terrain / User Interface 0 Future consideration

Need Named Boundaries or Multi-Point Cross Sections that can turn for secondary alignments

Currently, when secondary alignments are used, the cross sections are always based perpendicular to the primary alignment. We need the ability for named boundaries (or some other means of creating multi-point cross sections) to understand when sec...
almost 3 years ago in Drawing Production / OpenRail Designer / OpenSite Designer 4 Future consideration

Annotate Cross Section Locations In Plan

We often want to show the location of cross section in plan which can be done using the named Boundary Lines but they need to be annotated so you know what each represents e.g. stations/chainages or section names such as letters etc. There is a wo...
about 3 years ago in Annotation / OpenBridge Designer / OpenBridge Modeler / OpenRail Designer / OpenRoads Designer / OpenSite Designer 6 Future consideration

Add a tool (or an option to the existing place point tool) to compute the traverse using a deflection angle instead of an absolute angle.

The existing Locate Point tool using the Traverse and Radial methods functionally does something similar, but must have 180 degrees added manually to the deflection angles to get the absolute angle.
about 1 year ago in OpenRoads Designer 0 Future consideration

Curve ID in Plan and Profile

Should able to modify curve IDs in horizontal and vertical geometry. And we able to have text faviroaite for annotate horizontal/vertical Curve ID in plan and profile.
over 2 years ago in Drawing Production / OpenRail Designer / OpenRoads Designer / OpenSite Designer 1 Future consideration

Export Drainage Model to 2D Linework

It would be nice to be able to export a drainage network into 2D linework that can be edited for plan sheets. Currently, we don't use our modeled files directly in our plan sheets as we cannot adjust the conduit line styles and it takes longer to ...
over 1 year ago in Drainage and Utilities / OpenRail Designer / OpenRoads Designer / OpenSite Designer 3 Needs review

Ability for Cross Sections to be split or have match lines if the Model Extend Outside of Default limits

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.
almost 3 years ago in Drawing Production / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Future consideration

Control how Explorer sorts items

It would be really nice if we could organize items in the explorer by differently than it does by default. Adding the ability to control how the Explorer sorts items, whether it's something typical like alphabetically by name or something differen...
over 3 years ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / User Interface 3 Future consideration