Add "Arc Length Chorded" to arc properties so it can be annotated in plan
Currently there is no way to annotate the chorded length for arcs that are Chord definition. Adding a new property named "Arc Length Chorded" would allow this.
We need the ability to annotate component quantities on cross sections like you can the cut/fill volumes. Information could be pulled from the Quantities Report by Named Boundary.
Improve and simplify the named boundary drawing/sheet seed creation workflow
The way it is now, It's just too complex to create and custum the seeds for each client. Too many files, too many things to control and in too many folders/.cgf. You have to create many seeds with different specifics for each sheet size/scale/plan...
The create new survey linear tool needs to have the ability to name the element and set the field code. Currently, you have to select the new linear and enter the name and field code in the properties after it's created.
Need the ability to flood/fill the shape of the border selected (hexagon, rectangle, etc.) so there are no gaps / white space between text field and border.
Either add ability for multiple users to be in the same ITL and save the information. At the moment we run a separate ITL for segments of a project which leads to slight differences to similar items. It is cumbersome to use the template library or...
Allow different levels for different conduit sizes in the same catalogue.
For Conduits, on our 2D plans, we show a different linestyle for each size of pipe. In InRoads, we would enable centerline display using these different linestyles. This linestyle is a wide dashed line with solid edge lines. We cannot replicate th...
Allow option to label Terrain Contours using Lines/Linestrings to define paths
We regularly need to deliver contour plans to the client based on Terrains that constantly change as a 3d design develops. It is currently very hard to produce consistent contour outputs because of the manual nature of how the annotation is applie...
When using display rules Type it would be useful to have an option of values between A-B, not only >, = , and >=. This way you can choose between multiple versions of a component. Example absolute horizontal 0-1 Curb type F, 1-2 type A, 2-3 ...
Static Labels and Annotation - "Dumb Text" (make UX of labels more friendly/improve performance))
I would like the ability to place labels and annotate elements using static text. Meaning, once the label or annotation is place it will not update or change. I would love the comfort of placing labels and not worrying if I will lose the field inf...