For now, the annotation of High and Low Points is very limited:# only one Low Point is detected - multiple low points are ignored# its is a linear3D annotation, and snaps on the annotations are not ruled (this intent is to be able to place drainag...

The OBM-OBD BIM workflow may work fine for standard style bridges, but when odd geometry is encountered, it would be helpful to be able to make modifications within the LEAP Concrete OBD file for analytical reasons, without affecting OBM geometry,...

In order to comply with the Kansas State Board of Technical Professions "Minimum Standards", the Kansas Department of Transportation is asking for an enhancement to OpenSite Designer CONNECT Edition software for Right of Way workflows as follows: ...

My state agency commonly uses gutters with a 4% cross slope. The maximum superelevation rate is 7%. The gutter slope stays at 4% in this situation. Spread does not compute in this scenario because "A depressed gutter must have a Gutter Cross Slope...

We need the software to have capability in reporting to interpolate lift and slew values between regression points. Because currently when a complex alignment end point is between regression points the reporting only picks up the lift and slew val...

Whenever you have a Geometry and used shared line (e.g. Lots), There should be a tool to remove duplicate/overlapping lines. Its problematic if we use a special linestyle with gaps and when the two line on top of each other it will look like a sol...

​​There appears to be a feature in OpenRail and previously was in InRoads where you could specify in the Annotation Group to have the annotation shift if there was an overlap with another annotation but can't find the same feature in OpenRoads Des...

When a custom line style is updated in the workspace, it does not update existing files that have used the previous line style (of the same name). The only workaround is to: Manually delete all of the line styles you want to update Remove the defi...

Please add the support to import an .laz file directly to a terrain. If it ORD can read an laz into a point cloud it seems like a pointless extra step where I have to convert an laz into a pod or las before I can import it into a terrain.

The "Set Feature Definition" Tool should be added to the Feature Definition Tool Bar rather than having to go digging around to find it. It coincides with "Match Feature Definition" which is already part of the tool bar.