TPC's COGO routines can work with appropriate combinations of distance and direction types. If you choose geodetic types, TPC computes geodetic foresights and inverses for the dialog. If you use non-geodetic types, TPC computes non-geodetic foresights and inverses.
For the most part, you don't even think about this. You just go to a COGO dialog, compute the information you need and move on. So this topic is for those of you who may need to dig a little deeper. Typically because you are doing geodetics or PLSS and need to make sure a COGO routine is doing a geodetic computation or you need to relate a COGO routine back to grid.
The Problem With Mismatched Types
The problem with mixing distance and direction types centers around geodetic vs non-geodetic types. When you compute a geodetic foresight, you use a geodetic distance and geodetic direction. TPC then computes a geodesic, the end of which is the requested foresight. Non-geodetic computations are all grid based trigonometric computations, even if they include scaling and convergence based on the CRS (Coordinate Reference System).
So mixing a non-geodetic distance with a geodetic direction in a foresight computation, for instance, will not produce the correct foresight. This is the issue we are discussing in this topic.
Examples
The Random Inverse dialog is a great example of this. You might recall two survey points and want their grid inverse or you might want their geodetic inverse. TPC can give you both.
The Translate dialog lets you translate by distance and direction. To do this the distance and direction types must be of the same type (geodetic vs non-geodetic) or you could get unexpected results.
Identifying Distance and Direction Types in a COGO Dialog
TPC displays information about the distance and direction type so you never have to guess at which it is using.
Title Bar
The title bar of each dialog displays the distance and direction types used and the units, such as feet, meters or chains.
Summary
Most COGO dialogs include a Summary button. This button copies the computations to the current Report view so you have a record of them. These summaries all include the distance and direction type information used in the dialog.
Fields
Some fields change their name to match the distance and direction types. In the Random Inverse dialog for example, changing from a grid distance to a geodetic distance changes the distance field from GeoDist to GridDist.
Setting the Distance and Direction Types in a COGO Dialog
When you open a COGO dialog, it is preset to a specific distance and direction type depending on how they were opened. In addition to the pre-set types, some COGO dialogs allow you to over-ride the pre-set distance and direction types. These dialogs include a Show Options button that expands this section of the dialog.
Survey
If you open a COGO dialog from the TPC Desktop, either the COGO menu or the COGO toolbar, TPC initiates the dialog to use the survey's distance and direction types. These can be found in Tools, Survey Information, Project Factors.
Traverse
You can open most of the COGO dialogs from a Traverse view or by selecting a traverse in the Traverses Manager. Either way, TPC looks at the traverse when it opens the COGO dialog and pre-sets the distance and direction types to match the traverse.
Each dialog knows whether or not the distance and direction types require a match. So if you initiate a COGO dialog from a traverse in which the two do not match, TPC will display a warning and ask if you want to continue. The choice is yours. TPC just identifies the potential conflict.
As a rule, COGO dialogs retain their computation data even when you close them. So you can re-open the dialog and continue right where you left off. However, if you re-open a COGO dialog from a different location, TPC is free to reset the dialog contents accordingly. As a result, the dialogs distance and direction types may change.
Mismatch Warnings
If the distance and direction types do not match, some dialogs will warn you as follows.
•When you open the dialog from a traverse and the traverses's types do not match.
•When you choose to Compute or Save from the dialog.
•When you add a Summary of the computations to the current report.,
In each case, TPC will warn you that the types do not match, but allow you to continue if you choose to.