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

OpenRoads Designer

Showing 1144

Ability to use Cross Section Named Boundaries across references

We would like to be able to create cross section sheets by referencing previously created boundaries in a similar manner to how we currently are able to use Plan and Profile Named Boundaries across references.
almost 3 years ago in Modeling / OpenRail Designer / OpenRoads Designer 1 Future consideration

Tool to convert Parametric Cell to a 2D Civil Cell

Civil Cells are often difficult to create due to it's use of parent-child relationships. I find it easier to create what I'm looking for by using constraints and variables for Parametric Cells. I think most Parametric Cells act similar to how a Ci...
over 1 year ago in Modeling / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Will not implement

Forcing Tangency in Geometry Builder by element

The Geometry Builder allows us to force tangent restrictions. In some cases there might be some lines/arcs that are tangent and some that are not. It would be an improvement to have the ability to force tangent where needed instead of on all eleme...
over 1 year ago in Geometry / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Future consideration

Ability to reference in Navisworks model files

Currently our only option is to bring in Navisworks Simulate models is find the .DWGs that possibly populate it and bring each one in individually. The individual reference option misses out on any files from other software (such as smartplant) su...
almost 3 years ago in All Other / OpenRail Designer / OpenRoads Designer / OpenSite Designer 2 Future consideration

Provide a property for Corridors that shows the associated ITL

Corridors may use a variety of template drops that come from a non-default ITL (i.e. the one defined by the configuration variable CIVIL_ROADWAY_TEMPLATE_LIBRARY). A property of the corridor could be shown that identifies any of the ITLs associate...
over 1 year ago in Modeling / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Future consideration

Key Station with civil rule

Key stations can now solely be places with a station input. In many cases the location of your Key Stations depends on the position of other elements, like geometry for example. Being able to give key stations a civil rule - like the Persist Snap ...
over 2 years ago in Modeling / OpenRail Designer / OpenRoads Designer 3 Already exists

Import Geometry from Imodel

Add the ability to import/export geometry elements from an imodel into your file. Similar to land xml or gpk. Then you retain the ability to archive files without worrying about their civil schema.
over 1 year ago in Import/Export / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Future consideration

Filter Features by Name

The graphical filter is limited to feature element symbology and feature definition. Multiple, redundant, feature definitions must be created in order to import features to multiple surfaces. The feature names, assigned in the template, can be use...
almost 3 years ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Terrain 0 Future consideration

Define Template Library Name and Location from Workset creation

Add capability to define Template Libray's Name and Location through Workset creation. See attached image. This information could be populate Workset.cfg file.
almost 3 years ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Workspace 0 Future consideration

Create multiple field books w/o terrain connecting

The ability to create multiple field books without the terrain connecting to each. This would be necessary when surveying multiple sites for one given road project. Currently, this is done by importing the data and then going to the survey setti...
almost 3 years ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Survey 0 Future consideration