When I import features from graphics into a field book, the program does not set the correct level (match level) for most features. If we can get it to match the level correctly, it would save a lot of time. To take it a step further, it would be ...

We need improved stroking control for corridors. Currently stroking for corridors is defined by configuration variables i.e. CIVIL_DEFAULT_CURVE_STROKING and CIVIL_DEFAULT_PROFILE_STROKING, for horizontal and vertical curves respectively, which ta...

Within the Survey Field Book of ORD, the right-click context menu offers a “Zoom” option. This should, I presume, fit all the selected survey features into view. It doesn’t work but would be very useful if it did. (Please see the attached image)

Inroads allowed the user to toggle a tick mark, such as a plus symbol (+), to show the position of any survey point in the fieldbook. Very useful. ORD allows the toggling of many different attributes of a point by using Survey Decorators. Please a...

U.S. surveyors traditionally work in Northing & Easting, in that order. When working with Microstation V8i, AND with Inroads loaded, the user could perform precision drafting by using the “NE= “ key-in to enter the exact northing/easting coord...

When using the “New Point” command for a survey point, the user must screen-pick the coordinates. There are times when it would be extremely useful to hand-enter the Northing, Easting, Elevation.

With Inroads Survey, whenever XYZ coordinates needed to be entered for a particular purpose, a screen-pick option was always available. (see attached image) This was extremely useful. However, with ORD, changing the XYZ coordinate of any points in...

Add ability to cross reference the sheet numbers of plans that are in the sheet index. IE: referencing the profile sheet number on the plan sheet and vice versa.

In 10.11 R1, the Best Match Field Code survey setting option changed from a True/False option only to a more extensive dropdown list. However, when older survey files are upgraded, there is no way to control which best match option is to be used. ...

Is there a way to add constructed length and constructed slope to a conduit flex table? I can build annotation for these fields for plan production, but I haven't found these fields to add to a conduit flex table. This would allow for more options...