Custom Linestyles Drawn in a Profile View do not scale
When Drawing a Custom Linestyle in a Profile view. The linestyle is scaled with the vertical exaggeration. This makes the linestyle unreadable, and therefore cannot have custom linestyles in profile view unless re-drawn in the drawing model, which...
ASCII elevation data from hydrosurveys is delivered in positive depths making for an embankment instead of a channel. A function to multiply elevations by -1 would save a trip through Excel or a GIS program.
Being able to delete more than one point at a time within template creation.
Currently, you can click the delete components within templates and draw a line through any component(s) to delete it(them). It would be nice to have a similar function to delete points by encircling them so you do not have to delete them using th...
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 ...
Ability to select lines for cross sections like in Geopak and to be able to import /export said lines for use. When you have miles of data and your sections are not perpendicular, selecting 2 end points per section is very time consuming.
Calculating Multiple Polygon Volumes using Analyze Volume from Terrain Model
The calculate volume tool only works on a single target polygon. If multiple polygons are present it's quite tedious to calculate one-by-one and manually sum the totals. For example in a bathy survey of a channel it's common to have different area...
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...
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.