Surpac data recorder format
You can use this function to process a data recorder text file, using Surpac's comma delimited file format. This is useful to make third-party surveying data recorder instruments interface with Surpac. You can also use the Surpac format file to enter survey observation data directly into Surpac from a text file, or a spreadsheet. Surpac data recorder format files must have an .sdf extension.
Prerequisites: A survey database is open in Surpac.
To run this function: Choose Survey > Data recorders > Surpac format, or...
Functionality supported by the Surpac data recorder format:
- Creating points in a string file from a standard surveying pickup with horizontal angle, vertical angle, and slope distance observations. example.
- Creating new points in a string file by directly entering x,y,z coordinates. example.
- Creating new stations by single face horizontal angle, vertical angle, and slope distance observations. more information on this option as used by other data recorders. example.
- Creating new stations by multiple face horizontal angle, vertical angle, and slope distance observations. more information on this option as used by other data recorders.
- Creating new stations by directly entering x,y,z coordinates. example.
- Creating new stations by single face resection. more information on this option as used by other data recorders. examples.
- Creating new stations by double face resection. more information on this option as used by other data recorders. examples.
- Drill hole surveys by the extended rod method. more information on this option as used by other data recorders. example.
- Offsetting points in a standard surveying pickup. See here and here for more information on this option as used by other data recorders. example.
- Backsight station checks in a standard surveying pickup. more information on this option as used by other data recorders. example.
- Prism monitoring. See here and here for more information on this option as used by other data recorders.
Note the following points when using the Surpac data recorder format:
- Station names are alpha numeric. For example STN, STN123, and 123 are all valid station names.
- Station names must be in upper case. For example TEST1 is valid, but test and Test1 are not valid.
- Station names (backsight stations, instrument stations, any other known stations, or any new stations created by the job) can contain a maximum of 12 characters.
- Station names must not contain commas.
The station errors table is an optional table in the survey database that allows you to set up a quality assurance regime for new stations entering the survey database. For more information on the station errors table see here.
Fields on the Inputs tab of the Select Surpac format file form
| Field | Description |
|---|---|
| Surpac format file | Enter the name of the Surpac data recorder format (.sdf) file to process. |
| Archive survey | If you have chosen Process input file, you can select this check 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, you can use this field to specify the directory to use for archiving. A new subdirectory is created in the specified 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). |
Fields on the Options tab of the Select Surpac format file form
Note: The options for this function are relevant only if the .sdf file contains a resection. Otherwise the function does not use these values.
| Field | Description |
|---|---|
| Instrument type |
An Instrument type is a set of accuracies for a survey instrument in a particular surveying environment. This box lists the instruments that have been defined. When you select an instrument, the Accuracies for Resection fields show the accuracies for that instrument. To create a new instrument, type a new name, fill in the accuracy fields, and then click Apply. To overwrite an existing instrument, select its name in the Instrument type field, and enter new accuracies.
|
| Accuracies for Resection | |
| Angle standard deviation | Angle standard deviation (seconds). |
| Distance standard deviation | Distance standard deviation. You should enter this value in the same units as the measured distances (for example, metres or feet). |
| Distance error (ppm) | This is the distance parts per million error. It is a ratio value, and so has no units. |
| Instrument height standard deviation | Instrument height standard deviation. This is the error associated with measuring the height of the instrument. This value should be entered in the same units as the measured distances (for example, metres or feet). |
| Instrument centring standard deviation | Instrument centring standard deviation. You should enter this value in the same units as the measured distances (for example, metres or feet). |
| Target height standard deviation | Target height standard deviation. This is the error associated with measuring the height of the target. You should enter this value in the same units as the measured distances (for example, metres or feet). |
| Target centring standard deviation | Target centring standard deviation. You should enter this value in the same units as the measured distances (for example, metres or feet). |
Click Apply on the Select Surpac format file form to start processing the entered .sdf file. See here for information on defining the name of the output string file. Subsequent forms that appear when processing the .sdf file, will depend on the content of the particular .sdf file. See here for information on the forms that appear when processing a typical data recorder file (some examples for the Geodat data recorders).
Output
The result of this function is a string file. One or more report files can be created depending on the content of the particular .sdf file being processed. The survey database is updated with any new stations that have been created by the function.
If you typed a new Instrument type, that instrument is saved to Instruments.ssi.
Surpac file format codes
The following table gives details of the various codes that constitute the Surpac data recorder file format:
| 0 | Used to indicate the start of a new job in the data recorder. An optional job name may follow the code. The job name should be at most 50 characters long. For each new job a string file may be created. Examples of valid lines would be "0" or "0,test_job" |
| 1 | The name of the backsight station. An example of a valid line would be "1,ST1" |
| 2 | The name of the instrument station. An example of a valid line would be "2,ST2" |
| 3 | The target height. A similar positive/negative sign convention is used as for the instrument height detailed above. For each new job, the target height must be entered before at least the first observation line. The same target height is used for all subsequent observations in the same job, until a new target height is entered. An example of a valid line would be "3,1.620" |
| 4 | The height of the instrument axis above the station. The convention used is that distances measured up to the axis are positive while distances measured from the station down to the axis are negative. Therefore, if the station is in the back of the drive, the instrument height will be negative. An example of a valid line would be "4,1.541" |
| 5 | Reference angle to the backsight station. The angle must be entered in DDD.MMSS format. An example of a valid line would be 5,144.1144" |
| 6 | Backsight station check. This option does a check on the entered backsight station. The backsight station check is very useful in underground surveying applications, as confusion regarding station marks and station identification is much easier than for surface surveying. See here for more information on checking the backsight station. The format of this line is "6,slope distance to backsight,horizontal reference angle to backsight,vertical angle to backsight,height of the target at the backsight". The angle values must be entered in DDD.MMSS format. Code 6 can be used in place of code 5, when the extra checking is required. An example of a valid line would be "6,319.984,144.1144,90.3505,1.625". When you wish to do a backsight station check the 1, 6 and 4 codes must appear before the code 2 line when defining the pickup. Note: If the "slope distance to backsight" value on the code 6 line is equal to 0.0, then the backsight station check will not be done. In this case the "horizontal reference angle to backsight" will be read from the line and the line will be treated as though it where a standard backsight reference angle code 5 line. |
| 7 | The string number. This value must be a positive integer. This defines the number of the string for new points in the string file. If a string number is never entered in a job, then points will go into string 1 by default. Once a string number is entered in a job, all subsequent points will go into that string number until a new string number is entered. An example of a valid line would be "7,2" |
| 10 | The standard observation line. This line contains the angle and distance observation data required to calculate a new point. The format of this line is "10,point number,slope distance,horizontal angle,vertical angle,point descriptions". When a new point is created, the "point description" values become the description fields for the point in the string file. The "point description" values must be at most 64 characters in length. Usually "point number" should be a positive integer, although character values are allowed. When a new point is created the "point number" value is added to the point descriptions in the string file at the end of the "point descriptions" for the point. The "point number" is only used by Surpac calculations when performing Prism Monitoring (where it is used as the prism identifier), otherwise it can be set as a counter for the points in the job. ie 1 for the first point, 2 for the second and so on. The "point number" value must not contain commas. The "point number" should be at most 16 characters long. The horizontal and vertical angles entered in the line must be in DDD.MMSS format. An example of a valid line would be "10,1,3.134,196.0024,91.1040,gold" |
| 11 | The new station by single face standard observation line. The appearance of this line determines that the next code 10 standard observation line will be used to calculate a new station in the survey database. The format of this line is "11,name of new station". The "name of new station" becomes the name of the new station that is inserted into the database. The next code 10 line found will be used to calculate the coordinates of the new station. You have the option of entering a new code 3 target height line and a new code 7 string number line between the code 11 line and the corresponding code 10 line. No other codes can be entered between the code 11 line and the code 10 line. An example of a valid line would be "11,NEWSTAT12". |
| 12 | This line indicates the start of a code block for a drill hole survey by the extended rod method.
See here for more information on drill hole surveys by the extended rod method.
The format of this line is "12,drillhole ID,distance of the first point from the collar (along the rod), distance between the two surveyed points (along the rod), the dip of the rod (measured by clinometer)".
Note:
An example of a valid line would be "12,100,2.020,1.400,-60.0000". The next two code 10 lines will be taken to be, respectively, an observation to the point closest to the hole collar, and then an observation to the point furthest from the hole collar. You have the option of entering a new code 3 target height line and a new code 7 string number line between the code 12 line and the two corresponding code 10 lines. No other codes can be entered between the code 12 line and the code 10 lines. |
| 20 | The start of creating a new station by multiple face observations, line. See here for more information on creating a new station by multiple face observations. There are two options for the format of this line, depending on whether you wish to store the height from the floor to the target (see herefor more notes on this option). If you do not wish to store the height, the line has the format "20,name of new station to be created". An example of a valid line would be "20,NEW1". If you do wish to store the height, the line has the format "20,name of new station to be created,height from the floor to the target". Important: The "height from the floor to the target" is divided by 1000.0 when processed by Surpac. This means that if your normal coordinate units are metres, then the "height from the floor to the target" value must be entered in millimetres. An example of a valid line would be "20,NEW1,1500.00", (this corresponds to a "height from the floor to the target" value of 1.5 metres). The code 10 observation lines between the code 20 line and the next code 21 line, are taken to be the multiple face observations to the new station. The only code lines that should appear between a code 20 line and the corresponding code 21 line, are code 10 lines and code 3 (target height lines) and code 7 (string number lines). The target height should remain constant within a new station by multiple face observations code block. |
| 21 | The end of creating a new station by multiple face observations, line. See here for more information on creating a new station by multiple face observations. This line simply marks the end of the multiple face observations, and has the format "21" |
| 24 |
A face left, face right observation pair for creating a new survey station. This code can occur within the survey. After code 24, the next two observation lines expected are the face left and face right to the forward station. The point number for each observation must be the station name (station_id). The format of the new code is shown by the following example:
|
| 30 | The xyz coordinates line. This line contains direct x,y,z coordinate data required to calculate a new point. The format of this line is "30,point number,x coordinate,y coordinate,z coordinate,point descriptions". When a new point is created, the "point description" values become the description fields for the point in the string file. The "point description" values must be at most 64 characters in length. Usually "point number" should be a positive integer, although character values are allowed. When a new point is created the "point number" value is added to the point descriptions in the string file at the end of the "point descriptions" for the point. The "point number" is only used by Surpac calculations when performing Prism Monitoring (where it is used as the prism identifier), otherwise it can be set as a counter for the points in the job. ie 1 for the first point, 2 for the second and so on. The "point number" value must not contain commas. The "point number" should be at most 16 characters long. An example of a valid line would be "30,1,5033.381,13794.039,357.674,silver" |
| 31 | The new station by xyz coordinates line. This line is similar to a code 30 xyz coordinates line, except the new point is inserted into the survey database as a new station. The format of this line is "31,point number,x coordinate,y coordinate,z coordinate,name of new station". Usually "point number" should be a positive integer, although character values are allowed. The "point number" is only used by Surpac calculations when performing Prism Monitoring (where it is used as the prism identifier), otherwise it can be set as a counter for the points in the job. ie 1 for the first point, 2 for the second and so on. The "point number" value must not contain commas. The "point number" should be at most 16 characters long. The "name of new station" becomes the name of the new station that is inserted into the database. An example of a valid line would be "31,1,5033.381,13794.039,357.674,NEWSTAT12" |
| 40 | The resection observation line. See herefor more information on creating a new station by resection. This line contains observation data taken from the unknown resection station, to a known station. The format of this line is "40,point number,slope distance,horizontal angle,vertical angle,name of known station". Usually "point number" should be a positive integer, although character values are allowed. The "point number" is only used by Surpac calculations when performing Prism Monitoring (where it is used as the prism identifier), otherwise it can be set as a counter for the points in the job. ie 1 for the first point, 2 for the second etc. The "point number" value must not contain commas. The "point number" should be at most 16 characters long. The horizontal and vertical angles entered in the line must be in DDD.MMSS format. The "name of known station" is the known station to which the observations on the line are being taken. It must currently exist in the survey database. An example of a valid line would be "40,1,3.134,196.0024,91.1040,STN1" |
| 41 | Resection adjustment to the backsight reference angle, line. See herefor more information on performing a resection adjustment to the backsight reference angle. This line contains data on adjusting the backsight reference angle to account for a resection adjustment to the horizontal circle. The format of this line is "41,adjustment to backsight reference angle". The angle must be in DDD.MMSS format. An example of a valid line would be "41,144.1144". exampleNote: This is quite a technical option, and will not be required for resections in general. |
| 42 | The start of creating a new station by resection using the second resection coding scheme, line. This line simply marks the start of the resection observations, and has the format "42". See here for more information on the second resection coding scheme. |
| 43 | The end of creating a new station by resection using the second resection coding scheme, line.
The format of this line is "43,name of new station,instrument height".
The instrument height is the of the instrument axis above the new resection station.
The convention used is that distances measured up to the axis are positive while distances measured from the station down to the axis are negative.
Therefore, if the station is in the back of the drive, the instrument height will be negative.
An example of a valid line would be "43,RESECT1,0.000".
See here for more information on the second resection coding scheme.
Note: When a code 43 line appears in a job, Surpac changes some internally stored values, to help facilitate a typical surveyor's work flow.
After a code 43 line has appeared, Surpac will treat the job as a standard pickup with:
This means that after the code 43 line, you can just enter more code 10 observation lines without having to go through the process of entering new instrument and backsight station codes. See here for an example of this. This, of course, means that if you do not want to use these default values in your pickup, you will have to enter new code lines (instrument station, backsight station etc) to describe the new pickup, before the next code 10 lines appear. |
| 90 | The name of the surveyor. This value will be stored in the database if a new station is created in this job. The format of this line is "90,surveyor name". The surveyor name should be at most 25 characters long. An example of a valid line would be "90,ras". Code 90 is an optional code in a job. Note: Codes 90 and 91 are the only two codes that can appear before the first 0 start of job code at the start of the .sdf file. If any other codes appear before the first 0 code, Surpac will exit. |
| 91 | The date/time of the survey. This value will be stored in the database if a new station is created in this job. This value is also used when performing Prism Monitoring. The format of this line is "91,survey time". Valid values of "survey time" must be of the form yyyy-mm-dd hh:mm:ss The date component must appear, the time component is optional. So for example, 2005-12-29 13:25:22 and 2005-12-29 are both valid values. So examples of valid lines would be "91,2005-12-29 13:25:22" and "91,2005-12-29". Code 91 is an optional code in a job. Note: Codes 90 and 91 are the only two codes that can appear before the first 0 start of job code at the start of the .sdf file. If any other codes appear before the first 0 code, Surpac will exit. |
| 92 | Temperature value for the survey. This value is only used when performing Prism Monitoring. The format of this line is "92,temperature". The "temperature" value must be a number with decimals. An example of a valid line would be "92,30.3". Code 92 is an optional code in a job. |
| 93 | Pressure value for the survey. This value is only used when performing Prism Monitoring. The format of this line is "93,pressure". The "pressure" value must be a number with decimals. An example of a valid line would be "93,120.62". Code 93 is an optional code in a job. |