All Attributes are currently treated as text. Some attributes are recorded as numeric data and are being assigned a decimal precision. When these are read to generate labels, there is no option to round those values to a different precision. For e...

Corridor design input report provides much of what we need to reconstruct the corridor, but not a list of linework listed in the corridor attachments.

Creating an Annotation Group for the Crossings --> Annotate with CellPlacement - Rotation Option: here is missing the option, that we have for the turnouts, to place the cell "Element Aligned"...Because of this you need to create 2 different an...

ORD needs a pay item tool to manage all pay items and quantities for a project. This would help with keeping up with pay items that do not have elements in a file, especially in regard to digital delivery. PowerGeopak had a quantity manager that c...

Rather than creating a new cross sectional named boundary, it would be convenient for the saved views to synchronize with 3D reference window and level display. There could even be a feature to toggle this feature on and off for a saved view.

A feature to define within the Annotation Group for plan alignment annotation and vary the text favourite used based on element length. For example, I would like to use a text favourite with transition geometry text on 1 line for elements greater ...

One of the factors prohibiting the use of civil geometry in plan production is that it can often feel cumbersome to implement design changes without 'breaking' your previous work. Let's say you have an intersection designed using civil geometry, a...

Object Properties - Feature Definition of a pipe is top level, its description is a pick list of diameters (TxDOT), but Utilities Properties has three different locations. This complexity is unnecessary.

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 ...

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