When creating a new point in a Survey field book using the “New Point” command, allow an option to hand-enter the coordinates.
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.
Configuration variable to control default path for .tiw files
When working in a fieldbook in survey, we want to set the default file path to a specific location for .tiw files. As it stands, ORD remembers the last location from which a .tiw was imported, but we want to set a file path for all users.
Updating XS annotation group w/o resetting annotation placement
The XS annotation group will place annotations in text conflicting locations. Once the user resolves the text conflicts there is a chance that the annotations may have to be revised when the model is updated. Therefore, it would be helpful if ther...
Ability to switch the priority of other end conditions within the end condition editor as an override.
Currently there is no way to use end condition exceptions and as an override switch between other end conditions within a certain station range. A simple addition to the override feature where you could temporarily change the priorities of the end...
Calculate the area of survey chains if they are enclosed shapes
Survey chains (when enclosed) have a reported area value of zero. This is seen in the properties for the geometry, and also if you try to read the area through an item type using the expression This.GetElement().EnclosedArea. Our construction staf...
Users would like the ability to create multiple field books without the terrain connecting to each. This would be necessary when surveying multiple sites for one given road project. Currently, this is done by importing the data and then going to t...
Annotate Slope between 2 Linear Geometries in Cross Section
2 x 3D linear geometries are created with the existing terrain. In cutting cross section, 2 points are displayed in a section. However, the slope value between 2 points are not able to annotated under annotation group.
"Terrain Substitute” command that would swap all links from one Terrain to another, and also swap Parent Terrains for Surface Templates ( without breaking rules/relationships).
Export multiple terrain models as a single XML file
We deliver terrain models for top/bottom surfaces of a roadway. Due to gaps in project data we often have multiple top surfaces and multiple bottom surfaces. It would be nice to export all surfaces as a single XML file similar to alignments.