Ability to insert a series of event points, e.g., every 25 m along axis, in a single shot at once

A SWITCH/CASE function would be easier to use than having to nest multiple IF functions.

For large scale projects, earthwork volumetric meshes cause considerable deficits in navigation performance due to the high count of vertices and faces to be calculated with each navigational operation. Use of scalable meshes for these components ...

It could be useful for different purposes to be able to create component meshes of defined length (construction, pre cast slab). I suggest to add at least 3 parameters to any component: length of the component: the question is then, where to measu...

The RIM Elevation is a stagnant number once you enter an elevation it does not update in relation to any surface changes. RIM Elevation would be better suited for use if it can be defined with an offset. Another field would be needed: RIM Depressi...

Similar to the new Station/Offset Expressions, it would be great to query a terrain in an item type on an element and return the elevation. It would be used primarily for point cells, but I could also see it being useful for linework.

Currently, annotation groups are limited to certain feature definition categories. This limits our ability to automatically annotate point features such as signs or geotech borings or drainage/utility nodes. It would be desirable to extract data f...

When applying a point control, users should have the ability to choose the individual point name when there is also a Feature Name Override on the point. As of now only the override name shows up in the point control pick list, and it currently do...

There are tens of thousands of barrier inlets on barrier medians throughout the US. Spread needs to be calculated on both sides, with the overall flow being added to the storm sewer system. Currently, the only way to do this is to create to halves...

This would enable users to quickly edit the component feature definitions for templates in the library.