surtac

Process Help

SURTAC - reduce survey measurements using tachometric method

Process Name	Menu Path	Link to Command Table
SURTAC	Command line only	Click here

Introduction
Files, Fields and Parameters
Notes
Example
Errors

Introduction

SURTAC is a survey measurement reduction process.

How to use

This command will compute the three-dimensional coordinates of points located by angle and distance measurements from a coordinated survey station. This constitutes the second stage in survey data processing. The user will have created a file containing the survey measurements, prior to running this process, by one of the following methods:-

AED

Editor for file creation and modification.

The AED process may be used to input survey observations from the keyboard, from data written in a field note book.

SURLOG

Input of survey data from a character system file.

The SURLOG process is used to input a file of measurements that has been transferred from a digital data recorder.

The user can assign display elements of symbol, color and line style for point and strings of points, according to the descriptive code recorded in the survey.

The output files of coordinated points and string segments will then be used as input to the interactive survey editor, in order to visualize and edit the survey in three-dimensions and update the survey database.

SURVIG Interactive graphic survey data editor.

File Handling

SURTAC requires three files as input data to the process. These may be summarized as:-

A file containing the coordinates and identification of survey stations that will be used in the survey.
A file containing the measurements made to excavation points from a coordinated survey station.
A file containing graphic attributes to be assigned to the descriptive code to be found in the survey measurement file for each of the surveyed points.

Control survey station file (&CONTROL)

This file may be created by the AED process (Advanced file edit), or by process SURCAL (Computation of survey station coordinates).

Compulsory fields

The survey station coordinates must be stored in numeric fields X, Y and Z.

Compulsory key fields

*STATION

The station is identified by a numeric or alpha-numeric field, as defined by the *STATION field supplied by the user. If this field is not supplied, a numeric field STATION must be present in the file. It is important to note that the type and length of field *STATION must be the same as field INSTSTN in the input survey measurement file, &IN. If the file is to be used as input to process SUROBS and SURCAL, for the reduction of survey measurements to establish new survey stations (Option SV2 in the SRV module), the field STATION must be alphanumeric and eight characters in length.

Point and string attribute file (&ATTRIBUT)

This file may be created by the AED editor process.

Compulsory fields

The numeric fields PTYPE, PSYMBOL, PSYMSZE, PCODE, P must exist in the file.

Compulsory key fields

*STYPE

An additional numeric or alpha-numeric field *STYPE may be present, as supplied by the user, and identifies a string of points with a common type. If this field is not supplied by the user, the numeric field PTYPE will be used and must exist in the file. This is the key field on which the attributes are assigned, and so the name, type and length of the field in the attribute file (&ATTRIBUT) must also occur in the input survey measurement file (&IN).

Survey measurements file (&IN)

This file may be created by the AED process, if the data was entered from a keyboard, or by the SURLOG process (input of survey data from a character system file), where survey measurements have been transferred from a digital data recorder into your application.

Compulsory fields

The fields required in this file will depend on the method of survey, and this is selected by the user by setting the @OBTYPE parameter value at run time. The @OBTYPE may be one of four acceptable values:-

@OBTYPE = 1

Horizontal and Vertical circle direction on theodolite
Slope distance theodolite axis to target
Instrument axis height (negative if set below a point)
Target/prism height (negative if set below a point)

@OBTYPE = 2

Horizontal circle direction on theodolite
Vertical difference in height theodolite axis to target
Horizontal distance theodolite to target
Instrument axis height (negative if set below a point)
Target/prism height (negative if set below a point)

@OBTYPE = 3

Horizontal and Vertical circle direction on theodolite
Upper stadia staff intercept
Mid stadia staff intercept (optional)
Lower stadia staff intercept
Instrument axis height (negative if set below a point)

@OBTYPE = 4

X coordinate of the point
Y coordinate of the point
Z coordinate of the point

The fields expected, according to each @OBTYPE value are as follows:-

@OBTYPE	1	2	3	4
FIELDS	INSTSTN	INSTSTN	INSTSTN	INSTSTN
	INSTHT	INSTHT	INSTHT	INSTHT
	RO	RO	RO	RO
	HZTARG	HZTARG	HZTARG
	VATARG		VATARG
	SDTARG
	TARGET	TARGET	TARGET	TARGET
	TARGHT	TARGHT	TARGHT	TARGHT
		VDTARG
		HDTARG
			UPPERS
			MIDDLES
			LOWERS
			MFACTOR
			VFACTOR
			AFACTOR
				XO
				YO
				ZO
	*STYPE	*STYPE	*STYPE	*STYPE
	*SVALUE	*SVALUE	*SVALUE	*SVALUE

*SVALUE

An additional numeric or alpha-numeric field *SVALUE may be present, as supplied by the user, and identifies a string of connected points. If this field is alphanumeric, it must be less than eight characters in length. If this field is not supplied by the user, the numeric field PVALUE will be used and must exist in the file.

*STYPE

An additional numeric or alpha-numeric field *STYPE may be present, as supplied by the user, and identifies a string of points with a common type. If this field is not supplied by the user, the numeric field PTYPE will be used and must exist in the file. This is the key field on which the attributes are assigned, and so the name, type and length of the field in the input survey measurement file (&IN) must also occur in the attribute file (&ATTRIBUT).

Note that the type and length of the fields INSTSTN and RO, must coincide to that found in the survey station file (&CONTROL) for the symbolic field *STATION.

Optional fields

The optional fields that may be used during computation also depend on the method of survey, as selected by the user in the @OBTYPE parameter.

@OBTYPE	1	2	3	4
FIELDS	HZRO	HZRO	HZRO
	VARO		VARO
	SDRO
	ROHT	ROHT
		VDRO
		HDRO
	UP	UP
	DOWN	DOWN
	LEFT	LEFT
	RIGHT	RIGHT

Mathematical Algorithms

The following simple equations are used to compute the horizontal distance and vertical component from the survey instrument to the target position, according to the measurements made:-

@OBTYPE=1

Firstly, the vertical circle reading and slope distance have to be adjusted if offsets have been measured. The offsets are first processed to assign a positive or negative sign.

@VOFFSET=1 (UP/DOWN offsets are vertical)

SMD	is the slope measured distance
VMA	is the measured vertical circle reading (0 is Zenith)
SAD	is the slope adjusted distance
VAA	is the adjusted vertical circle reading
VMO	is the vertical measured offset

OA = 180-VMA (@ANGLE=1)
or OA = 200-VMA (@ANGLE=2)

OD = VMO^2+SMD^2
SAD= SQRT(OD - 2.0 * (ABS(VMO) * SMD) * COS (OA)

VAA= VMA + ASIN((SIN(OA)/SAD) * VMO

@VOFFSET=2 (UP/DOWN offsets are perpendicular)

SMD	is the slope measured distance
VMA	is the measured vertical circle reading (0 is Zenith)
SAD	is the slope adjusted distance
VAA	is the adjusted vertical circle reading
PMO	is the perpendicular measured offset

SAD= SQRT(PMO^2+SMD^2)

VAA= VMA + ATAN(PMO/SMD)

If LEFT/RIGHT offsets have been measured, the azimuth and slope distance to the measured point have to be adjusted.

AZI is the computed whole circle bearing
AAZ is the adjusted whole circle bearing (azimuth)

SAD= SQRT(PMO^2+SMD^2)

AAZ= AZI + ATAN(PMO/SMD)

@OBTYPE=3

Horizontal distances and vertical components are computed from stadia tacheometry measurements in the following manner:-

IAF	is the theodolite additive constant
IMF	is the theodolite multiplication factor
MUS	is the upper stadia/staff intercept measurement
MLS	is the lower stadia/staff intercept measurement
MVA	is the measured vertical circle reading (0 is Zenith)
CAE	is the computed angle of elevation
CHD	is the computed horizontal distance
CVC	is the computed vertical component instrument to target

CAE= 90.0 - MVA (@ANGLE=1)
or CAE= 100.0 - MVA (@ANGLE=2)

CHD= IMF * (MUS - MLS) + IAF * COS(CAE)^2

CVC= 0.5 * (IMF * (MUS - MLS) + IAF) * SIN(2.0 * CAE)

Where parameter @OBTYPE is a value one to three (1-3), horizontal distances and vertical components are easily computed using standard trigonometry. However, if the @PLANE parameter is not absent data, a further computation is required.

CHD	is the computed horizontal distance
CVD	is the computed difference in height between station and target
RDP	is the elevation datum to which the distance is to be adjusted
HIS	is the elevation of the instrument station
AHD	is the adjusted plane distance
WRA	is the radius of the world (6 384 100 meters)

AHD= CHD - (CHD * ((HIS + 0.5 * CVD) - RDP)) / WRA

Note that RDP is supplied as the @PLANE parameter.

Files, Fields and Parameters

Input Files

Name	Description	I/O Status	Required	Type
CONTROL	Input control survey station file. This must contain the numeric fields X, Y and Z. A field identifying the station name is required and may be of type numeric or alpha-numeric. The default station naming field is STATION of type numeric.	Input	Yes	Undefined
IN	Input tacheometry observation file. This must contain fields: INSTSTN Numeric survey station identifier of instrument location.. INSTHT Numeric instrument height. (Negative for instruments set below the survey station). RO Numeric survey station identifier of reference object. TARGET Numeric or alpha-numeric identifier of the point located. Additionally; if OBTYPE=1: HZTARG Numeric horizontal direction measured to the target. VATARG Numeric vertical direction measured to the target. SDTARG Numeric slope distance measured to the target. TARGHT Numeric target height. (Negative for target set below the target point). Optionally; check measurements to the reference survey station (RO),if OBTYPE=1: HZRO Numeric horizontal direction measured to the reference object. VARO Numeric vertical direction measured to the reference object. SDRO Numeric slope distance measured to the referenec object. ROHT Numeric target height at the reference object. Additionally; if OBTYPE=2: HZTARG Numeric horizontal direction measured to the target. VDTARG Numeric vertical distance from the survey instrument to the target. HDTARG Numeric horizontal distance measured to the target. TARGHT Numeric target height. (Negative for target set below the target point). Optionally; check measurements to the reference survey station (RO),if OBTYPE=2: HZRO Numeric horizontal direction measured to the reference object. VDRO Numeric vertical distance from the survey instrument to the reference object. HDRO Numeric horizontal distance measured to the reference object. ROHT Numeric target height at the reference object. (Negative for target set below the target point). Additionally; if OBTYPE=3: HZTARG Numeric horizontal direction measured to the target. VATARG Numeric vertical direction measured to the target. UPPERS Numeric upper stadia staff reading. MIDDLES Numeric middle stadia staff reading. LOWERS Numeric lower stadia staff reading. MFACTOR Numeric multiplication factor for the theodolite.. VFACTOR Numeric vertical difference factor. AFACTOR Numeric additive constant for theodolite. Additionally; if OBTYPE=4: XO Numeric X coordinate of the target. YO Numeric Y coordinate of the target. ZO Numeric Z coordinate of the target. IF OBTYPE=1 or 2, offset measurements may included. All measurements are taken at the measured point, in the directions indicated by the field names (LEFT,RIGHT UP,DOWN). LEFT and RIGHT offsets are taken perpendicular to the measured line, while UP and DOWN offsets may be perpendicular or vertical depending on the VOFFSET parameter. If offsets are measured, the following fields must be exist in the file:- LEFT Numeric distance left of line INSTSTN-TARGET, at SDTARG/HDTARG position. RIGHT Numeric distance right of line INSTSTN-TARGET, at SDTARG/HDTARG position. UP Numeric distance above line INSTSTN-TARGET, at SDTARG/HDTARG position. DOWN Numeric distance below line INSTSTN-TARGET, at SDTARG/HDTARG position. This file may have been created as output from the SURLOG process.	Input	Yes	Undefined
ATTRIBUT	Input attribute file. This must contain PTYPE, PTEXT, PSYMBOL, PSYMSZE, PCODE and P. May also contain an alpha-numeric string type field.	Input	Yes	Undefined

Output Files

Name	I/O Status	Required	Type	Description
POINTOU	Output	Yes	Undefined	Output point file. This will contain fields PID, X, Y, Z, PSYMBOL, PSYMSZE, P and PERIOD (numeric, explicit).
SEGOU	Output	Yes	Undefined	Output string segment file. This will contain fields PID1, PID2, PVALUE, PTYPE, PTEXT, PCODE, P and PERIOD.

Fields

Name	Description	Source	Required	Type	Default
STYPE	Optional key field in ATTRIBUT and IN file for assignment of point and string attributes. If this field is not supplied by the user, PTYPE will be used by default and must exist in the input file.	IN, ATTRIBUT	No	Any	Undefined
SVALUE	Optional key field in IN file for assignment of numeric string identifiers to the output string file. If this field is not supplied, field PVALUE will be used and must exist in the input file.	IN	No	Numeric	Undefined
STATION	Optional alphanumeric survey station identifier in the input CONTROL survey station file. If this field is not supplied the default numeric field STATION will be used.	CONTROL	No	Character	Undefined

Parameters

Name	Description	Required	Default	Range	Values
OBTYPE	Input tacheometry observation type. This will be one of: 1 = Horizontal, vertical angles and slope distance measurements. 2 = Horizontal angle and distance and vertical difference. 3 = Horizontal, vertical angles and staff/stadia intercepts. 4 = Reduced X,Y,Z coordinates. The default observation type will be (1).	Yes	1	1,4	1,2,3,4
ANGLE	Angle units used. This will be one of: 1 = Degrees, minutes and seconds; 0-360 2 = Gradians; 0-400 The default angle unit will be Degrees, minutes and seconds (1).	No	1	1,2	1,2
VOFFSET	Measurement method for UP/DOWN offsets. This will be one of:- 1 = UP/DOWN offsets measured vertically above/below distance measurement. 2 = UP/DOWN offsets measured perpendicular to the distance measurement. The default method will be vertical offset measurements (1).	No	1	1,2	1,2
PERIOD	Numeric integer period number to be stored with output point and string segment data.	No	Undefined	Undefined	Undefined
PIDSTART	Optional start point number for output to point file, field PID, if a numeric TARGET field does not exist in the input file. The default start number is 1.(1)	No	1	Undefined	Undefined
PIDINCR	Optional point number increment, if no TARGET field exists in the input file. The default increment is 1.(1)	No	1	Undefined	Undefined
PVSTART	Optional start string number for output to string file, field PVALUE, if no PVALUE field exists in the input file. The default start number is 1.(1)	No	1	Undefined	Undefined
PVINCR	Optional string number increment, if no PVALUE field exists in the input file. The default increment is 1.(1)	No	1	Undefined	Undefined
PLANE	Optional reference plane elevation to which horizontal distances will be reduced prior to computation of grid distance and point coordinates. The default is absent data [-], no futher reductions are made to the horizontal distance.(-)	No	-	Undefined	Undefined
FACTOR	Optional scale factor to be applied to the plane distance, to compute the grid distance, prior to computation of point coordinates. The default value is 1.(1)	No	1	Undefined	Undefined
ROCHECK	Optional flag = 1 to compare computed base line distance components with check measurements made. The default is 0, not to compare check base measurements, if present .(0)	No	0	0,1	0,1
UPDATE	Optional flag = 1 to append computed points to the CONTROL file, if they are subsequently occupied by the survey instrument for continuation of the detail survey during execution of the process. The default is 0, not to append any computed points to the input CONTROL file. (0)	No	0	0,1	0,1

Notes

Offset measurements

Optional fields UP, DOWN, LEFT and RIGHT may exist in the survey measurement file (&IN) representing measurements taken perpendicular or vertical to the measured point. The following points should be understood:-

The offsets are measured relative to the line from the instrument station (INSTSTN) to the target (TARGET). All values must be positive. An absent data value (-) denotes that the offset has not been measured.
A separate string identifier extension is assigned to the PVALUE field for each offset measured, and PTYPE field values are assigned by the process. This corresponds to the conventions used by the underground mine planning process DRIVES.

Offset field name	PVALUE Value	PTYPE Value
LEFT	????.04	4
RIGHT	????.05	5
UP	????.03	3
DOWN	????.02	2

In order to ensure that a string is generated when there are no offsets measured, the default value for the LEFT offset must be set to zero (0). A LEFT offset string will then be created by default, with a PTYPE value of four (4.0).

-LEFT and RIGHT offsets are always computed perpendicular to the direction of the measured line in the horizontal plane. The UP and DOWN offsets are computed according to the user-defined @VOFFSET parameter, supplied at run time:-

@VOFFSET=1 (Default setting)

UP and DOWN measurements are taken vertically above and below the point.

@VOFFSET=2

UP and DOWN measurements are assumed perpendicular to the slope of the measured line. This will often be the case in underground development with high gradients where a tape is extended between two survey stations and offsets are measured perpendicular to it at regular locations.

Many electronic total stations have the facility for entering offsets and the vertical and horizontal circle readings and slope distance are adjusted accordingly prior to storage.#12;String numbering

If the input survey measurement file (&IN) contains a numeric PVALUE field, this is copied across to the output file of string segments. If a *SVALUE field has been supplied that is alphanumeric, numbering of the strings is handled by the process and the following user- controlled parameters:-

@PVSTRT Starting value for string numbers.

@PVINCR Increment on starting value for each change in *SVALUE encountered.

Point numbering

If the input survey measurements file (&IN) contains a TARGET field that is alphanumeric, point numbers are allocated by the process and the following user-controlled parameters:-

@PIDSTRT Starting number for point numbers.

@PIDINCR Increment on starting value for each measurement record.

Limitations

A maximum of one set of measured components may be used to compute a point location (e.g. one horizontal circle measurement each to the reference station and target point, one vertical circle, slope distance, instrument and target height measurement (see note below on survey station file update). This process is therefore unsuitable for the reduction of measurements to survey stations where means of multiple measurements require computation prior to point location.

These facilities are provided by the processes in the Mine Surveying 2 Module.

A maximum of fifty (50) records can be loaded from the attributes file, &ATTRIBUT.

A maximum of one thousand (1000) records can be loaded from the survey station file, &CONTROL. If the file is larger, the stations used in the survey should be selected from the master file prior to running this process.

A maximum of one thousand (1000) records can be processed from the input survey measurement file, &IN. This represents one thousand points surveyed.

If the user has alphanumeric fields for the assignment of attributes and string numbers, the same field must not be supplied as the *STYPE field as for the *SVALUE field. When this occurs, incorrect PVALUE field string identifiers will be stored.
Survey station file update (&CONTROL)

If temporary survey stations are located in the file of input measurements (&IN) by a single set of measured components, and they are used as an instrument station location in subsequent records, the input file containing the survey station coordinates (&CONTROL) may be updated with the new point coordinates. This is achieved by setting the following parameter value when running the process:-

@UPDATE=1

Units of angle measurement

The processing of angle values found in the input file are controlled by the following parameter:-

@ANGLE

By default, this is set to process angles as degrees, minutes and seconds in the form DDD.MMSS. The user must ensure, that if angles have been recorded in Grads (Gons), this parameter is set to two (2)

Example

Processing measurements input from a TOPCON FC-5 data recorder.

The following represents the command syntax required to run the SURTAC process to process the data described below and would be the required entry in a macro of commands to process survey data.

!SURTAC

&CONTROL(TOPSTA), &IN(TOPD), &ATTRIBUT(TOPCATT),
&POINTOU(TOPCP1), &STRINGOU(TOPCS1), *STYPE(SCODE), @OBTYPE=1.0, @ANGLE=1.0, @PERIOD=1.0, @PIDSTART=1.0, @PIDINCR=1.0, @PVSTART=1.0, @PVINCR=1.0, @FACTOR=1.0, @ROCHECK=0.0, @UPDATE=0.0

The Datamine survey station file required as input to SURTAC, in OUTPUT format:-

TOPCSTA
FILE CREATED BY USING AED ON 8/4/91
4 4

X	N	1	1	0.000000E+00
Y	N	1	2	0.000000E+00
Z	N	1	3	0.000000E+00
STATION	A	1	4

14823.52	25135.0	5077.598	DC2A
14857.42	25129.03	5079.176	DC2

The Datamine file of survey measurements required as input to SURTAC, as output by process SURLOG, in OUTPUT format:-

TOPCD
FILE CREATED BY USING AED ON 30/ 1/91
18 18

JOBNUM	N	1	1	-0.100000E+31
SURVEYOR	A	1	2
INSTNUM	A	1	3
DATE	A	1	4
DATE	A	2	5
DATE	A	3	6
TEMP	N	1	7	-0.100000E+31
PRESS	N	1	8	-0.100000E+31
INSTSTN	A	1	9
RO	A	1	10
INSTHT	N	1	11	-0.100000E+31
TARGET	N	1	12	-0.100000E+31
HZTARG	N	1	13	-0.100000E+31
VATARG	N	1	14	-0.100000E+31
SDTARG	N	1	15	-0.100000E+31
PVALUE	N	1	16	-0.100000E+31
SCODE	A	1	17
TARGHT	N	1	18	-0.100000E+31

2.0 DC 28.0 790.0 DC2A DC2 1.32 100.0 225.325  89.463   97.209 1.0 C 1.42
2.0 DC 28.0 790.0 DC2A DC2 1.32 101.0 233.0545 89.5825  95.855 1.0 C 1.42
2.0 DC 28.0 790.0 DC2A DC2 1.32 102.0 241.1825 90.461  100.359 1.0 C 1.42
2.0 DC 28.0 790.0 DC2A DC2 1.32 103.0 250.044  90.283  104.962 1.0 C 1.42
2.0 DC 28.0 790.0 DC2A DC2 1.32 104.0 251.4925 90.115  109.571 1.0 C 1.42
2.0 DC 28.0 790.0 DC2A DC2 1.32 105.0 254.521  89.3335 110.808 1.0 C 1.42
2.0 DC 28.0 790.0 DC2A DC2 1.32 106.0 258.2105 88.511  106.97  1.0 C 1.42

The Datamine file of point and string display attributes required as input to SURTAC in OUTPUT format:

TOPCATT

FILE CREATED BY USING AED ON 30/1/91

6 6

PTYPE	N	1	1	0.000000E+00
PSYMBOL	N	1	2	0.000000E+00
PSYMSZE	N	1	3	0.000000E+00
P	N	1	4	0.000000E+00
PCODE	N	1	5	0.000000E+00
SCODE	A	1	6

2.0	94.0	2.0	10.0	1001.0	C
3.0	94.0	2.0	8.0	1003.0	T
4.0	92.0	1.5	6.0	1005.0	S

The output Datamine file of coordinated points created by process SURTAC, in OUTPUT format:

TOPCP

FILE CREATED BY USING AED ON 30/1/91

8 8

X	N	1	1	0.000000E+00
Y	N	1	2	0.000000E+00
Z	N	1	3	0.000000E+00
PSYMBOL	N	1	4	0.000000E+00
PSYMSZE	N	1	5	0.000000E+00
P	N	1	6	0.000000E+00
PID	N	1	7	-0.000000E+31
PERIOD	N	1	8	-0.000000E+31

14768.51	25215.14	5077.88	94.0	2.0	10.0	100.0	1.0
14780.13	25220.47	5077.542	94.0	2.0	10.0	101.0	1.0
14791.34	25230.05	5076.15	94.0	2.0	10.0	102.0	1.0
14805.41	25238.38	5076.628	94.0	2.0	10.0	103.0	1.0
14807.91	25243.45	5077.121	94.0	2.0	10.0	104.0	1.0
14813.59	25245.36	5078.35	94.0	2.0	10.0	105.0	1.0
14820.42	25241.9	5079.64	94.0	2.0	10.0	106.0	1.0

The output Datamine file of string segments created by process SURTAC, in OUTPUT format:-

TOPCS

FILE CREATED BY USING AED ON 30/1/91

7 7

SCODE	A	1	1
PVALUE	N	1	2	-0.000000E+31
PTYPE	N	1	3	0.000000E+00
P	N	1	4	0.000000E+00
PCODE	N	1	5	-0.000000E+31
PID1	N	1	6	-0.000000E+31
PID2	N	1	7	-0.000000E+31

C	1.0	2.0	10.0	1001.0	100.0	101.0
C	1.0	2.0	10.0	1001.0	101.0	102.0
C	1.0	2.0	10.0	1001.0	102.0	103.0
C	1.0	2.0	10.0	1001.0	103.0	104.0
C	1.0	2.0	10.0	1001.0	104.0	105.0
C	1.0	2.0	10.0	1001.0	105.0	106.0

Error and Warning Messages

Message	Description	Solution
*** Error - Field AAAAAAAA exceeds limit of 8 characters. A *SVALUE field must be 8 characters or less.	The symbolic field *SVALUE, used to allocate string values, has a length greater than eight (8) characters. Fatal; the process is exited.

*** Error - File &IN or &ATTRIBUT is missing field AAAAAAAA.	The symbolic field *STYPE is missing in either of the input survey measurement or string/point attribute files. Fatal; the process is exited.

*** Error - Parameter @OBTYPE must have a value in the range 1-4.

*** Error - Parameter @ANGLE must have a value in the range 1-2.

*** Error - If vertical angle and slope distance measurements are made to the RO survey station, both fields VARO and SDRO must be located in the input file &IN.	The input file &IN contains only one of the measurement fields to the Reference Object. Fatal; the process is exited.	Both vertical angle and slope distance fields (VARO and SDRO) must be added to the file &IN, using process ADDDD, or removed completely from the file, using process SELDEL.

*** Error - If vertical angle and slope distance measurements are made to the RO survey station, both fields VDRO and HDRO must be located in the input file &IN.	The input file &IN contains only one of the measurement fields to the Reference Object. Fatal; the process is exited	Both vertical difference in height and horizontal distance fields (VDRO and HDRO) must be added to the file &IN, using process ADDDD, or removed completely from the file, using process SELDEL.

*** Error - File &IN is missing essential field AAAAAAAA	A compulsory field AAAAAAAA is missing from the file &IN. Fatal; the process is exited.	Add the field AAAAAAAA to the file &IN, using process ADDDD.

*** Error - Field AAAAAAAA is missing from the input file. If offset measurements are made, the following fields must be located in the input file &IN; LEFT, RIGHT, UP, DOWN.	The input file &IN does not contain all the offset fields required. Fatal; the process is exited.	Add the missing fields, using ADDDD process, and set the default to absent data (-).

*** Error - File &CONTROL is missing essential field AAAAAAAA.	An compulsory field AAAAAAAA is missing from the input file &IN. . Fatal; the process is exited.	Add the field AAAAAAAA to the file &IN, using process ADDDD.

*** Error - Mismatch of field lengths or types: AAAAAAAA length NN type AN in file FFFFFFFF, AAAAAAAA length NN type AN in file FFFFFFFF, Survey station identities must be the same field type and length in all input files.	Survey station identities in field STATION in the input file &CONTROL and in fields INSTSTN and RO in the input survey measurements file &IN, must be the same type (Alpha-numeric or Numeric) and length. Fatal; the process is exited.	Using the Datamine Table Editor, change the field type for the required field (data column).

*** Error - File &ATTRIBUT is missing field AAAAAAAA.	The input file of string and point attributes is missing a compulsory field AAAAAAAA. Fatal; the process is exited.	Add the field AAAAAAAA to the file &IN, using process ADDDD.

*** Error - Absent data found in input &ATTRIB file.	Relate to errors encountered during the reading of data from the input files.	Check the data files.

*** Warning - Input file FFFFFFFF, record NN, contains absent data for fiel d AAAA AAAA . This record has been ignored.	The input survey measurement or string/point attributes file may contain absent data for a compulsory field that will cause errors during processing. The record will be ignored and the next record processed.	Check the data files.

*** Warning - Survey Station A, does not exist in the input file &CONTROL, and has not been computed in this process. This record is ignored.	The input survey measurement file contains reference to a INSTSTN or RO field value that does not exist in the survey station file. It has not been surveyed in the same file of measurements, and is therefore rejected and the next record is processed.	Check the data files.

*** Warning - Base line stations A-A, have coincident coordinates. This record is ignored.	The input survey measurement file (&IN) contains a record with field values for INSTSTN and RO that have coincident coordinates in the survey station file. This record is rejected and processing continues.	Check the data files.

*** Warning - Input file AAAAAAAA contains record number NN with a hori zont al dire ctio n less than 0.0 to the targ et. This record has been ignored.	The input survey measurement file (&IN) contains a record with field values for HZRO or HZTARG less than zero. Field HZRO with a value of absent data (-) is treated as 0.0, and a warning issued, but other non-positive values cause the record to be rejected and processing continues.	Check the data files.

*** Warning - Input file AAAAAAAA contains record number NN with measured distance of 0.0 to the target. This record has been ignored.	The input survey measurement file (&IN) contains a record with field values for SDTARG less than or equal to zero. The record is rejected and processing continues.	Check the data files.