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

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

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.

Currently we are only import points and alignments in a .CSV format. I would like the ability to import lines and shapes also.

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.

When labeling civil geometry (alignments for example), whichever annotation group that is utilized is copied from the DNGLIB and saved with the active DGN. This is only the case when the geometry being annotated is stored within the active DGN, no...

The prompt for compressing the drainage database needs some work: It really should be removed. Salvaging anything marked for deletion but not compressed isn't really feasible in OpenRoads environment. Do not prompt me twice. It should be assumed t...