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

For large projects, we need the ability to have multiple engineers working on the hydraulic model. We can achieve this by splitting the pipe network into multiple files and creating catchments in separate files. Doing so causes us to lose the abil...

The user needs a length dimension along with a leader shape that matches the measured arc. In the attached image, the white arc represents the length dimension along with the leader, which has the same shape as the measured arc (orange arc).

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

Have a variable to would control the level of the 3d cut box.

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

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.

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

We need to label this on plans.

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