STAR*NET V6 - Circe

Chapter 5 Preparing Input Data
Regarding output of traverse observations, the individual observations are shown in the
listing file just like observations from other data type lines. However, if you have set the
option in the Project Options/Listing dialog to include traverse closures in your output,
an additional section is created in the listing file showing a summary of each traverse
along with its closure errors and precisions. See Chapter 8, “Analysis of Adjustment
Output,” for further information on this.
Data entries for the Traverse line are the same as for the Measure line, except the
traverse line contains only the “At” station name. The Traverse data line includes all the
observations required to completely define the next traverse point. The horizontal angle
is measured from the previous traverse point to the next traverse point. All other
measurements (distance and vertical observations) are taken to the next traverse point.
Traverse data may also be entered using “Bearings” or “Azimuths” rather than turned
angles using the “.MAPMODE” inline option. See “Using Inline options” later in this
chapter for details on the use of this special mode of data entry.
Example 1: (2D Data)
T 2 12-34-12 1102.42 ‘Found Iron Pipe
At station “2” we turn an angle of 12-34-12 from the previous traverse point and measure
a distance of 1102.42 to the next traverse point. No standard errors values are entered, so
global defaults are assumed. A descriptor is entered for station 2.
Example 2: (2D Data)
T 2 12-34-12 1102.42 4 .03
Same 2D data as example 1, except we have added explicit standard error values of 4
seconds for the turned angle and .03 for the distance.
Example 3: (2D Data)
T 2 12-34-12 1102.42 4 !
Same as example 1, except we have added an explicit standard error value of 4 seconds
for the turned angle and we have fixed the distance using the “!” symbol.
65