|
As a rule, elevations get computed automatically in TPC. When you inverse a mid-point, TPC assigns the average elevation of the end points to the mid-point. When you compute terrestrial observations with zenith angle and slope distance, TPC computes an elevation. When you compute a point in the Compute Coordinate dialog, TPC gives you options to accept the computed elevation or enter an elevation to hold. So you get the picture. Elevations are computed pretty much everywhere.
Computing Elevations in a Traverse
As you enter terrestrial data (angles and distances) in a traverse, TPC automatically carries elevations. TPC discusses traverses and elevations in Carrying Elevations in a Traverse.
Via COGO
Most COGO routines compute elevations of the points they compute. Often with options about how to hold or compute thoese elevations just the way you want.
Multiple Points
TPC gives you the option to specify a vertical spacing the the points it creates or if you choose horizontal spacing instead, you can choose to interpolate the resulting elevations based on that horizontal spacing.
Compute Coordinates
If you have an elevation you want to hold for the point being computed (like the elevation of a building floor), you can enter it or let TPC compute the elevation based on the input data.
Station Offset
TPC gives you the option to carry the centerline elevation at a station to the offset point being computed at that station.
Inserting a Midpoint
When you insert a midpoint in TPC, TPC automatically computes an average elevation for the inserted point.
Related Topics
Elevations
Editions
Personal, Premium, Professional
|
