Print

Data recorder

You can use the data recorder functions to convert observations — angles and distances recorded using a total station data recorder — into coordinates in a string (.str) file. You can also load set out (design) coordinates into some data recorders, either by direct communications or by copying a file onto a supported storage device.

In addition to converting angle and distance observations to co-ordinates, some data recorder interface functions allow co-ordinates recorded in the data recorder file to be saved directly to the resultant string file.

Note: For details of the data recorders which have this capability, please see the data recorder specific documentation.

To run this function: Choose Survey> Data recorders > <a specific data recorder>.

Data Recorder Function

Select the data recorder processing function you wish to use:

• Download to file
• Process input file
• Download & Process
• Upload co-ordinates
• Configuration

Configuration File

The name of a data recorder configuration file. The data recorder configuration file contains communication and coordinate transformation information for each data recorder. The data recorder configuration file also contains instrument accuracy parameters which are used in the resection calculations. This input field is only active if one of the down load or up load data recorder functions is chosen.

Job/Area Name

Some data recorders maintain a concept of job or area names. Of those that do, some also allow data to be down loaded using an externally transmitted command that specifies the job or area to down load. If the data recorder does support this you specify the job or area name here.

Location

Enter the location of the input file (.inp) which is to be created or processed.

Archive survey

If you have chosen Process input file, you can check this box to create a copy of the input file, .sdf file, and any string and report files generated by the function in the Archive directory.

Archive directory

If you have selected the Archive survey check box, specify the directory to use for archiving. A new subdirectory is created in this directory with the same name as the input file being processed. Copies of the input file, .sdf file, and any string or report files generated by the function are stored in this subdirectory. If the subdirectory already exists, a version number is appended to the name, starting with (1).

Complete the DATA RECORDER form and choose Apply to execute the chosen data recorder function.

Down Load To File

Before you can use this processing option, you must first down load data from the data recorder device to your computer. The down loaded file is termed an input file and it must have the extension .inp in order to be used by the Process Input File function.

You can create an input file in a number of ways.

• Use the down load function to extract the data. Unfortunately this function is not available for all data recorders. The specifics of down loading using this function are described in the individual data recorder sections later.
• Use the data recorder manufacturers supplied software to transfer data and create the .inp / .gsi / .job / .raw file
• Use a simple communications program like XTALK or KERMIT to transfer the data from the device to an .inp file.
• Where available, use an appropriate operating system command to copy a file from the data recorder storage device (PCMCIA card) to the computer.
• With the Sokkia SET4C2 you can retrieve data from a job by entering the data output menu on the recorder and entering download in surpac just before applying data output.

Result

After processing is complete a file with a .inp / .gsi / .job / .raw extension is created .

A number of different data recorders are available each with its own unique method of recording the data. During the course of processing, these different data formats are reduced to a common format which is then converted into coordinates and stored in a string file.

Process Input File

Before choosing this function you must have previously created an input file using one of the methods described above.

The data recorder file may contain a number of separate surveys for each of which a different string file may ultimately be created.

After processing is completed, the common format file (.sdf) that is created in the course of processing may be deleted if it is not required. The file is not deleted automatically as it can assist in determining the cause of errors arise in the conversion process.

The method of processing all the data recorders is identical and will be described once. The data formats for each data recorder will be described in detail at the later in this section.

The information which is retrieved from the data recorder file includes:

• Job name
• Backsight station identification and reference angle
• Setup station identification and height of instrument
• Target height
• Environmental data which is recorded by some data recorders but not all. Check the data recorder specific details to determine if your data recorder supports these features.This data includes:
  • Temperature if available in the data recorder
  • Pressure if available in the data recorder
  • Date if available in the data recorder
  • Time if available in the data recorder
• Observed point data which includes
  • String number
  • Point identification
  • Horizontal angle
  • Vertical angle
  • Slope distance
  • Optional point offset data
  • New station identification
• Calculated co-ordinates. Not all data recorders support the recording of calculated co-ordinates. Check the data recorder specific details to determine if your data recorder supports this feature.
  • String number
  • Point identification
  • Y coordinate of point
  • X coordinate of point
  • Z coordinate of point
  • New station identification

The survey stations are identified by their unique name by which they are known in the survey database. To be able to successfully process a data recorder file, the stations which are used in a survey must be stored in a survey database. The survey database must have been created using either the surface surveying or underground surveying functions. When the coordinates for each of the observed points are calculated, the coordinates for the survey stations are retrieved from the database. This avoids the necessity of recording the station coordinates in the data recorder and hence minimises the possibility for error.

It is your responsibility to ensure that the data which are recorded in the data recorder file are stored in a logical manner to allow the conversion to coordinates to be successful. For example, all setup information such as backsight station identification, reference angle, setup station identification, instrument height and target height must be defined before any observed points are recorded in the data recorder file.

New Stations

Most data recorders support the identification of observed points as new survey stations which are to be stored in the database. The method used to identify these points differs and depends upon the data recorder. This is described in the appropriate section on data recorders.

Note:To be able to use the new station capability you must indicate when processing the data recorder file that you wish to use point descriptions as the new station codes are stored in the description field.

Resection

Resection is a method used for determining the unknown 3D position of an occupied station by measuring angles and distances to stations whose 3D coordinates are known. The data recorders for which resection is supported in Surpac are the following:

• Geodat 400
• Geodat 600
• Leica GRE3
• Leica GRE4
• Leica GIF10
• Leica TPS1000
• Leica TPS1100
• Sokkia SDR33
• Topcon GTS700(FC6)
• Trimble 3300

When the new resection point has been calculated you are given some options regarding the creation of the resected station. This is done via the Options for Resected Station form, see here for more details. The method used to implement resection depends upon the data recorder. This is described in the appropriate section on data recorders.

Offsetting Points

All data recorders permit the definition of offset codes to allow the observed point to be offset from its surveyed position to some offset position. The Leica GRE3 is the only data recorder which does not permit you to record characters. Instead, it uses a numerical coding method to define the offset codes. This is discussed in the section pertaining to that data recorder. All other data recorders use the same method which is described below.

Note: To be able to use the point offsetting capability you must indicate when processing the data recorder file that you wish to use point descriptions as the offset codes are stored in the description field.

In the point description field of the data recorder file codes of the form

D(+/-)n.nnO(+/-)n.nnV(+/-)n.nn

are used to define the offset direction and amount from the observed position of the surveyed point. The offset definition consists of three parts and these are:

• The offset direction which is defined by a letter which may be either `D' or `O' or `V'
• The sign which indicates whether the offset is a positive or a negative value. Note that the sign must be explicitly defined even for positive offsets
• The amount of the offset which is a number that defines how far the observed point is to be moved. Note that the decimal point is only required if you define a fractional shift in the required direction.

The letters which are used to define the offset codes MUST BE upper case or the offsets will not be recognised. Any reasonable combination of the offset codes is valid and any subset of the complete range of offset codes is also valid, i.e. you do not need to define all the offset codes each time you wish to offset a point.

Below are some examples.

D+2

V-1.4O-1

O+2V+2D-1

If you define an offset code twice, the second occurrence of it is ignored. In the following example the `D+1.2' will be ignored and `D+2' will be used.

D+2V-0.5D+1.2

String Numbers

Because of the variety of the data recorders a number of different methods are used to define the string number for the observed points. These are described at the end of this section for each data recorder. If you never define the string number for any of the points in the data recorder file then all points will be assigned to string number 1.

Using Data Recorders with an Underground Survey Database

Surveying in underground mines presents some unique problems caused by the frequent occurrence of very short lines of sight. The bearings which are subsequently calculated using the known station coordinates on these very short lines are likely to deviate significantly from the bearings obtained by successively adding the horizontal angles to the bearing from the setup station to the backsight station. To resolve this problem, the underground survey database has a field rev_brng in which the carried bearing is stored. Any survey function which accepts input of survey observations to calculate the coordinates of new points will use this stored bearing, if appropriate, to calculate the coordinates of the new points.

Note: The following discussion only has relevance if you are using an underground database. If you are using a surface database then bearings are ALWAYS calculated using the known station coordinates.

With respect to underground survey databases, connections between stations are defined by the contents of the station_fr field for each station in the database.

The following logic is employed by the calculation module to obtain the bearing from the setup station to the backsight station.

1. If no connection exists between the setup and backsight stations then a form is displayed advising that the backsight/setup station pairing may be unsuitable. The reason why the pairing may be unsuitable is that, due to a mistake in recording the backsight or setup station names, there may be no line of sight between the two stations due to intervening solid rock. If this situation occurs the INCONSISTENT BACKSIGHT/SETUP STATION COMBINATION form is displayed.

   Choose Apply to obtain the bearing from the setup station to the backsight by calculating it from the known coordinates of the stations.

   Choose Cancel to abort the coordinate calculation process completely. You would make this choice if you wish to check on the backsight and setup station names before proceeding.

2. If a connection between the setup and backsight stations exists, then the stored bearing from the database and the calculated bearing obtained by using the known coordinates of the two stations are compared.

   If the difference between the bearings is less than 2 minutes then the calculation of coordinates will continue and the stored bearing will be used.

   If the bearings differ by greater than 2 minutes then the INCONSISTENT DATABASE REVERSE BEARING VALUE form is displayed.

   The stored and calculated bearings between the setup and backsight stations are displayed. You must choose one of three possible actions by choosing the appropriate button to determine how you should proceed from this point.

   Choose Use stored bearing to proceed with coordinate calculations using the bearing obtained from the database as the bearing from the setup station to the backsight station.

   Choose Use Calculated bearing to proceed with coordinate calculations using the bearing obtained from the known coordinates of the setup station and the backsight station.

   Choose Cancel to abort the coordinate calculation process completely. You would make this choice if you wish to check on the backsight and setup station names before proceeding.

   If the point being surveyed is a new survey station, the reverse bearing from the new survey station to the station from which it was surveyed is stored in the rev_brg field.

Floor Elevations of New Stations

The height from the floor to target for newly surveyed stations may now be recorded in the data recorder file for newly surveyed stations. The height from floor to target is only recorded for Leica, Geodometer 126, Geodometer 400, Sokkia and Topcon data recorders. The value is recorded in millimeters in the data recorder file. The method of recording varies between data recorders. Please read the appropriate section for more details.

The floor elevations of newly surveyed stations is now stored in the z_floor field.

Backsight station check

The Leica data recorders permit a backsight station check to be performed to ensure that the backsight station identified is the correct station. At this time this feature is only supported for the Leica data recorders.

Processing

Choose a data recorder from the SURVEYING menu to display a DATA RECORDER form.

For example, choose Collectech to display the COLLECTECH DATA RECORDER form.

Location, ID number.

You must define the data recorder file which is to be processed by entering its Location and ID number. The file is assumed to have an extension of `.inp' and it is generally referred to as an input file.

Complete the DATA RECORDER form and choose Apply to display the SURVEY JOB INFORMATION form.

This form allows you to enter details of the surveyor and the date which apply to the survey in the data recorder file.

Surveyor

Enter the name of the person responsible for conducting the survey. When a new station is created in the survey database the surveyor name is written to the surveyor field in the survey_stations table in the database.

Survey Date

Enter the date on which the survey was conducted. Note: When a new station is created in the survey database the date on which the station was surveyed is written to the survey_date field in the survey_stations table in the database. If an appropriate survey date is found in the data recorder input file then this date is written to the database, if not then the date input here as the Survey Date is written to the database.

Complete the SURVEY JOB INFORMATION form and choose Apply to display the CONFIRM PROCESSING OF SURVEY JOB form.

Job name

The description of the survey, retrieved from the data recorder file is displayed for reference. It may be altered if necessary to correct errors. The value displayed/entered is recorded in the reformatted .sdf file for future reference. In the case of the Leica GRE3 data recorder, since characters cannot be stored you will always be presented with a blank value.

The CONFIRM PROCESSING OF SURVEY JOB form will be displayed for each discrete job in the data recorder input file to allow you to review and modify if necessary the job title of each of the surveys in the file.

After the CONFIRM PROCESSING OF SURVEY JOB form has been displayed for each job in the input file, you will be prompted, for each of the jobs in the input file, whether you want to continue processing.

If you choose to continue processing a job, then coordinates will be calculated. If you skip a job then the survey will be ignored. This feature is intended for use when a survey which has already been processed has been found to be in error and the error subsequently fixed and the survey must be reprocessed to get the correct coordinates.

New Survey form

This form is displayed for each survey from the input file. If you choose Apply, processing of the identified survey will continue. If you choose Cancel the job identified will be ignored. This form will be redisplayed until there are no more jobs to be processed.

Location, ID number

You must define the .str file which will be created by entering a Location and ID number.

Report file format

The file format of the report that is output.

Purpose

The purpose is stored in the header recorder of the .str file which is created.

First vert angle for all points

This is a rather obscure option and has limited use. It is intended for use when surveying a decline in an underground mine where the inclination of the decline is consistent, and you want all points surveyed to use the vertical angle of the first point in the survey. This therefore provides an artificial adjustment to the vertical angle.

Stability monitoring prism table

If the survey being processed is to be used for stability monitoring purposes, you may wish to load the observations and co-ordinates into a Prisms table for later analysis using the Stability Monitoring module.

You may choose to ignore this feature by leaving the input field blank. This will ensure no data is loaded into the database. If you choose to load the data into the prisms table, the observation data, the calculated co-ordinates and a datetime stamp are saved for later analysis.

When data is loaded into the monitoring prism table each entry requires a date/time value. Many data recorders do not provide a special means of recording the date/time of the survey. In this instance the date/time which is entered at the commencement of processing the data recorder file is used.

For those data recorders which provide date/time values from the data recorder file, the recorded values will be used as the date/time for the records stored in the prism table whenever a date/time value is encountered in the data recorder file.

Area for monitoring prisms data

If you have chosen to load the observed data into a prisms table, you must supply an area to permit grouping of the prism data after it has been loaded into the database. The prism_area field of the prisms table permits grouping of the prisms in a manner similar to the Area/Level fields in the Surface and Underground databases.

If the .str file to be created already exists then the following form will be displayed to allow you to determine the action to be taken.

File

The name of the file which you are about to create is displayed.

(A)ppend or (R)eplace

You must define the action to be taken with regard to the existing file. If you respond with `A' then the new data will be appended to the existing file. If you respond with `R' then the existing file will be replaced with the new data.

Result

For each survey job that is processed, a string file is created containing points at the surveyed locations of each of the observed points in the data recorder file.

Each point in the string file will have the point description/code from the data recorder file in the D1 field and the point number from the data recorder file in the D2 field of the point description.

Errors

Processing of the survey cannot continue because the reference angle from the setup station to the backsight station has not been defined. You will have to use a text editor to edit the `.inp' file and enter the appropriate data.

Invalid height of instrument "text"

The instrument height which is recorded in the data recorder file is not a valid numeric value. Edit the file and correct the problem.

Invalid height of prism "text"

The target height which is recorded in the data recorder file is not a valid numeric value. Edit the file and correct the problem.

Invalid collar extension distance - accepting as normal observations

An attempt has been made to survey a drill hole using the extended rod method and an invalid collar extension distance has been entered. Points will be treated as normal observations. See the section regarding the Leica GRE3 data collector for more details.

Invalid end to collar distance - accepting as normal observations

An attempt has been made to survey a drill hole using the extended rod method and an invalid end to collar distance has been entered. The points will be treated as normal observations.

See the section regarding the WILD GRE3 data collector for more details.

Invalid hole dip - accepting as normal observations

An attempt has been made to survey a drill hole using the extended rod method and an invalid hole dip has been entered. The points will be treated as normal observations. See the section regarding the WILD GRE3 data collector for more details.

Data recorder file is empty

There are no observations in the data recorder file. You should probably make sure that the data were correctly transferred from the data recorder to the computer.

Blank station name - Unable to proceed

A surveyed point is to be stored as a new station in the database but no station name has been supplied. Edit the input file and fix the problem.

Insufficient setup information to calculate coordinates

At least one point exists in the data recorder file before all essential setup details from the survey have been defined. Edit the input file and fix the problem.

Error in offset code "text" - using ZERO

A syntax error which defines an offset code has been made. Zero will be used but you should edit the input file and fix the problem.

Down Load and Process

This function is a combination of the previous two functions simply for convenience. That is, a down load to file is performed followed by a process input file function.

Up Load Co-ordinates

Note: Not all data recorders have this capability.

• With the Sokkia SET4C2 you can upload data to a job by entering the comms menu on the recorder and entering upload co-ordinates in surpac, however a common baud rate of 9600 must be set for uploading.

After processing, a specific format file is created with a .dat extension. This file can then be directly up loaded into the data recorder using a direct transfer method or where available you can elect to copy the file to a data recorder storage device (PCMCIA card) which can later be loaded into the data recorder.

Configuration File

The name of a data recorder configuration file. The data recorder configuration file contains communication and coordinate transformation information for each data recorder. The data recorder configuration file also contains instrument accuracy parameters which are used in the resection calculations.

Job/Area Name

Some data recorders maintain a concept of job or area names. Of those that do, some also allow data to be up loaded using an externally transmitted command that specifies the job or area to load into. If the data recorder does support this you specify the job or area name here.

Location and ID Number

Enter the Location and ID Number for the string file from which strings are to be obtained for loading into the data recorder.

String Range

Enter the range of strings that contain the set out points. A blank range means all strings will be processed.

D Field for Pt Numbers

Enter the D field that contains point numbers to be loaded into the data recorder. If no D field is specified then sequential point number starting from one will be used.

D Field for Pt Descriptions

Enter the D field that contains point descriptions to be loaded into the data recorder. Please note that not all data recorders allow point descriptions to be loaded. When a data recorder does not support point descriptions then this input is ignored.

After you have processed your point data the following form is displayed. Here you can elect to upload the processed points via a serial link or copy them to a disk location which will usually be a PCMCIA card which can later be loaded into the data recorder.

Selection

You have the choice to UPLOAD, COPY, or EXIT at this field. Selecting EXIT will return you to the Survey Menu. Upload will proceed to perform a serial upload of the data into the instrument. If you select COPY the following form is displayed.

Copy Data Recorder File

This is a read only field which displays the current name of the file containing your processed point data.

To New Location

Enter the full pathname of the location to which you want to copy the point data file. This will usually be a PCMCIA card storage device. Please note that some data recorders may have a strict naming convention for files on the card.

Configuration

This function allows you to configure the data recorder communication parameters and to also set any data transformations that may be required. This function also allows you to set the instrument accuracy parameters that are required for the resection calculations.

Configuration File

The name of a data recorder configuration file. The data recorder configuration file contains communication and coordinate transformation information for each data recorder. The data recorder configuration file also contains instrument accuracy parameters which are used in the resection calculations.

After applying the form the following form is displayed.

I/O Port

Select the serial port that the data recorder is connected to.

Baud rate

Select the baud rate (must match setting in the data recorder).

Parity

Select the parity (must match setting in the data recorder).

Data bits

Select number of data bits (must match setting in the data recorder).

Stop bits

Select number of stop bits (must match setting in the data recorder)

Flow control

Specify the form of flow control to use. Can be ether software, hardware or none.

Timeout

Specify the I/O time out value in seconds. This is the amount of time in seconds to wait for I/O before aborting.

Datum shift X, Y, Z

Specify any datum shift values to be subtracted from xyz values when up loading and added to xyz values when down loading. Some data recorders cannot store large coordinate values so xyz values need to be adjusted in order to store them in the data recorder.

Scale factor X, Y, Z

Specify any scale factor to be applied to be values after down loading or before up loading. Some data recorders store an implied decimal point so values must be multiplied by a scale value on up load and divided by a scale value on down load.

Accuracies for Resection:

Angle

The standard deviation of angle readings from the data recorder. This value should be entered in seconds.

Dist

The standard deviation of distance readings from the data recorder. This value should be entered in the same units as the measured distances (eg metres or feet).

Dist ppm

The parts per million error of distance readings from the data recorder.

Inst height

The standard deviation of measuring the instrument height. This value should be entered in the same units as the measured distances (eg metres or feet).

Inst centring

The standard deviation related to the error incurred by placing the instrument over/under a station mark. This value should be entered in the same units as the measured distances (eg metres or feet).

Targ height

The standard deviation of measuring the target height. This value should be entered in the same units as the measured distances (eg metres or feet).

Targ centring

The standard deviation related to the error incurred by placing the target over/under a station mark. This value should be entered in the same units as the measured distances (eg metres or feet).

Configuration File Description

The data recorder configuration files reside in the SSI_ETC directory.

The following is a typical data recorder configuration file. Please note that the file should not be edited other than via the configuration function.

#
# This is the data recorder setup file for Geodometer GEODAT400
#
# DO NOT EDIT THIS FILE!!!!!
#
# -------------------------------------------------------------------------
# define the up/down load capabilities
#    format name       = "name of the recorder format"
#    supports upload   = "YES" if direct up load is supported
#    supports download = "YES" if direct down load is supported
# -----------------------------------------------------------------------------
#
format name="GEODAT400"
supports upload="YES"
supports download="YES"
#
# -----------------------------------------------------------------------------
# communications settings (modified from the data recorder config menu>
#    port          = serial port
#    baud          = standard baud rate
#    parity        = parity none|odd|even
#    data bits     = data bits 5|6|7|8
#    stop bits     = stop bits 1|2
#    flow control  = flow control none|software|hardware
#    cr in         = treatment of incoming CR's should always be cr_ignore
#    cr out        = treatment of out bound CR's should always be cr_ignore
#    timeout       = a pause time in seconds to wait for I/O
#    end of record = the end of record mark
# -----------------------------------------------------------------------------
#
port=com2
baud=9600
parity=none
data bits =8
stop bits =1
flow control =software
cr in = cr_ignore
cr out = cr_ignore
timeout=5
end of record="^M"
#
# -----------------------------------------------------------------------------
# down load information
#    download prompt         = contents and sequence of download prompt
#                              where
#                                 L - Literally as specified in download prompt format
#                                 J - insert Job name as entered at run time
#    download prompt format  = C style format specifier for command to begin download
#    start of transmission   = any SOT character sent
#    end of transmission     = any EOT character sent
#    send ack string         = any acknowledge string to be sent for each record
# -----------------------------------------------------------------------------
#
download prompt="J"
download prompt format="OM=%s^M"
start of transmission=""
end of transmission=">"
send ack string=""
#
# -----------------------------------------------------------------------------
# Up load information
#    upload prompt          = contents and sequence of upload prompt
#                             where
#                                L - Literally as specified in upload prompt format
#                                J - insert Job name as entered at run time
#    upload prompt format   = C style format specifier for command to begin upload
#    upload header          = contents and sequence of upload header
#                             where
#                                L - Literally as specified in upload prompt format
#                                J - insert Job name as entered at run time
#                                C - point count if required
#    upload header format   = C style format specifier for information to put at the
#                             top of up load file if required
#    upload footer          = contents and sequence of upload footer
#                             where
#                                L - Literally as specified in upload prompt format
#    upload footer format   = C style format specifier for information to place at the
#                             end of up load file if required
#    physical record        = contents and sequence of data in the physical record
#                             where
#                                R - insert Record here
#                                T - Topcon BCC (block char check)if required
#                                B - block number if required
#    physical record format = C style format specifier for physical record
#    physical record size   = size of physical record otherwise 0 
#    coordinate line        = contents and sequence of data in the coordinate line
#                             where
#                                P - Point number
#                                X - X coordination
#                                Y - Y coordination
#                                Z - Z coordination if accepted
#                                D - point Description if accepted
#    point number type      = "numeric" or "alpha" for point identifiers
#    point number format    = C style format specifier for point number
#    ycoordinate format     = C style format specifier for y coordinate
#    xcoordinate format     = C style format specifier for x coordinate
#    zcoordinate format     = C style format specifier for z coordinate
#    description format     = C style format specifier for point description
#    eol delay              = time in seconds to wait after prompt record trans
#    eor delay              = time in seconds to wait after coord record trans
#    wait for ack           = "YES" if ACK/NACK protocol otherwise "NO"
# -----------------------------------------------------------------------------
#
upload prompt ="J"
upload prompt format="LI=%s^M"
upload header = ""
upload header format=""
upload footer="L"
upload footer format=">"
physical record=""
physical record format=""
physical record size=0
coordinate line="PDYXZ"
coordinate line format="%s%s%s%s%s"
point number type="numeric"
point number format="5=%d^M"
ycoordinate format="37=%.3f^M"
xcoordinate format="38=%.3f^M"
zcoordinate format="39=%.3f^M"
description format="4=%s^M"
eol delay =1
eor delay =0.01
wait for ack="NO"
#
# -----------------------------------------------------------------------------
# Co-ordinate transformations
#    x Scale            = x scale factor to apply (usually 1)
#    y scale            = y scale factor to apply (usually 1)
#    z scale            = z scale factor to apply (usually 1)
#    x datum            = datum value to add/subtract from x value
#    y datum            = datum value to add/subtract from y value
#    z datum            = datum value to add/subtract from z value
# -----------------------------------------------------------------------------
#    
x Scale=1
y scale=1
z scale=1
x datum=0
y datum=0
z datum=0
#
# -----------------------------------------------------------------------------
# Resection information
#    Surpac allows you to enter extra observation data to calculate the
#    coordinates of an unknown set up station. Surpac calculates the
#    unknown coordinates using a least squares method. This least squares
#    method requires various error and standard deviation values. 
#
#    supports resection                   = "YES" if Resection is 
#                                           supported for this data recorder
#    angle standard deviation             = the standard deviation of angle 
#                                           readings from the data recorder. 
#                                           This value should be entered in
#                                           seconds
#    distance standard deviation          = the standard deviation of distance 
#                                           readings from the data recorder. 
#                                           This value should be entered in
#                                           the same units as the measured
#                                           distances (eg metres or feet)
#    distance parts per million           = the parts per million error of 
#                                           distance readings from the data 
#                                           recorder 
#    instrument height standard deviation = the standard deviation of measuring
#                                           the instrument height. This value 
#                                           should be entered in 
#                                           the same units as the measured
#                                           distances (eg metres or feet)
#    instrument centring error            = the standard deviation of the error
#                                           incurred by placing the instrument 
#                                           over/under a station mark. This 
#                                           value should be entered in 
#                                           the same units as the measured
#                                           distances (eg metres or feet)
#    target height standard deviation     = the standard deviation of measuring
#                                           the target height. This value 
#                                           should be entered in 
#                                           the same units as the measured
#                                           distances (eg metres or feet)
#    target centring error                = the standard deviation of the error
#                                           incurred by placing the target 
#                                           over/under a station mark. This 
#                                           value should be entered in 
#                                           the same units as the measured
#                                           distances (eg metres or feet)
# -----------------------------------------------------------------------------
#
supports resection="YES"
angle standard deviation=3.0
distance standard deviation=0.005
distance parts per million=2.0
instrument height standard deviation=0.003
instrument centring error=0.003
target height standard deviation=0.003
target centring error=0.003