Currently, Drainage and Utilities feature definitions get captured via the CIVIL_CONTENTMANAGEMENTDGNLIBLIST variable within the workspace. Many configurations often use wildcards and file names that lump together features of D&U with road, ra...

One of my biggest pain points about ORD is if the horizontal geometry is dropped or broken, the vertical is consequently lost as well. This creates significant rework from a design and plan production standpoint (connected named boundaries). One w...

Interface Currently, writing expressions in expression builder is only slightly better than writing code in notepad. The interface could be enhanced similar to Visual Studio with colorized classes, methods, and properties, colorized brackets with ...

It would be extremely helpful, if we were able to programmatically create Feature Definitions and Feature Symbologies so that automation of the creation of new 'Custom Drainage Features' every time a drainage structure had a different bottom box (...

Currently for drawing model annotation groups, if the user wants to update the annotation, they would need to remove the outdated annotation group, which would removal all annotation groups, and then reapply all annotation groups. It would be nice...

In the Deed Writer tool (accessed via Geometry > Reports > Deed Writer), after selecting the reference alignment, the next step prompts the user to identify the Right of Way boundary. Currently, the tool only accepts closed shapes for this b...

We would appreciate an enhancement that keeps Civil Labeler open when switching files or models. If we are labeling cross sections, it closes every time we switch to every individual xsec model.

In the previous Bentley software our DOT used, the software was able to connect the cut and fill lines when transitioning from cut and fill between template drops. Currently the only way that is possible is to have a feature name override on the c...

I propose to add the possibility of dividing corridors with the retention of all attributes and elements such as point controls, feature definitions, keystations, etc. It can be seen in the programme files that such an intention to introduce a fea...

I'm not sure how best to implement it, but it's not uncommon to have multiple people working on a project with multiple corridor files. Having just one itl for the project would cause a lot of conflict and possible erros so multiple itl files are ...