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

Functional Areas

Showing 1223

External model checking process - by possibly running a report to identify where 3d conduit string lines have been placed - i.e soffit, centre, invert, crown or base, this will ensure all output data of conduits are consistent for construction.

This is useful to enable a) - checks to be carried out, b) - to identify possible conduits that require amending - to align with all others. This will enable consistent and accurate output data to be produced, that can be used to construct from.
11 months ago in Drainage and Utilities / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Future consideration

Ability to turn off Mesh (components) in reference files

There should be a way to turn off Mesh (components) in reference files. Currently, if you untick the "Mesh" Feature Definition from ORD Standards in explorer, it only turns off Mesh Components within the active model. The Mesh components that use ...
almost 2 years ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / User Interface 2 Future consideration

Best Match Field Code Option

In ORD 10.11 and beyond the Best Match Field Code Option is now a drop-down of the following: Match exact: Feature Must equal an Alpha Code, only exact matches. For example if there is a Feature Definition with Alpha Code set to AP (Asphalt Paveme...
6 months ago in OpenRail Designer / OpenRoads Designer / OpenSite Designer / Survey 0 Future consideration

Allow spread sections to be read directly from a terrain model or Corridor Model

Geopak Drainage could read a TIN file to establish the cross slopes for spread. This functionality should still existing in Drainage and Utilities by reading corridor models and terrain models. Users should be allowed to define an infinite number ...
over 1 year ago in Drainage and Utilities 1 Already exists

Have LandXML export support b-spline curves as a geometry type

This would benefit users who are trying to export their geometry using LandXML as the export format. Currently, bspline curves in an alignment are not supported by LandXML export and have to be manipulated to export the geometry.
over 2 years ago in Import/Export / OpenRail Designer / OpenRoads Designer / OpenSite Designer 0 Will not implement

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.
over 2 years ago in Modeling / OpenRail Designer / OpenRoads Designer 1 Future consideration

add distance between VPI to annotations in profiles

We need this to label our profiles optimally there'd be two values, once the horizontal (projected) distance and once the true (slanted) distance between to VPI's
almost 2 years ago in Annotation / OpenRail Designer / OpenRoads Designer / OpenSite Designer 2 Future consideration

Ability to Report on and See Superelevation Info When Referenced

I would like to see the following capabilities added for use when a superelevation file is attached as a reference: The ability to generate a superelevation report. The ability to see the control lines (obviously read-only). Basically, it would be...
almost 2 years ago in Superelevation 1 Already exists

feature match tool to limit entire feature path in the .CSV

When importing data with a .CSV format use a feature match tool so I don't have to have the entire feature definition path in the .CSV. Also add a best match option.
almost 2 years ago in Import/Export 1 Future consideration

Import Line and Shape geometry in a .CSV format.

Currently we are only import points and alignments in a .CSV format. I would like the ability to import lines and shapes also.
almost 2 years ago in Import/Export 0 Future consideration