(This functionality is available with the Input / Output module)
Extended Operation Codes function by allowing users to hardwire specific Operation Codes to specific Point Codes thus eliminating both keystrokes and time in the field. To utilise extended coding functionality, a user defined character, such as #, is placed against the desired code(s) in the codelist.
One example would be to hardwire Operation Code 14 (Description) to Point Code TREE. Every time a TREE is coded in the field, Operation 14 would also be automatically run, allowing the user to add additional descriptive information about the TREE, such as Species, Height etc. There is no need to record the point code and then record an additional Operation Code.
This code would be setup in the codelist as follows;
Code: TREE
Attribute1: String
Attribute2: Spread
Attribute3: Trunk
Attribute4: OpCode (Value: #14) # is the user defined character which is set in the registry.
Attribute5: Species
Attribute6: Height
If the Operation Code that is being used involves the use of more than one point, such as Operation Code 35 (Create a symbol from 2 edge points and an offset point), the OpCode attribute will need to be in the following format; #OpCode#NumPts where NumPts refers to the number of additional points used for the Operation (i.e. NumPts = Number of points used in the operation less 1).
Example: Using Operation Code 35 with Point Code CAR. Operation Code 35 involves the use of 3 points and this
would therefore be setup in the codelist as follows;
Code: CAR
Attribute1: String
Attribute2: OpCode (Value: #35#2)
Attribute3: Feature Code
Attribute4: Elevation Flag
Note: In the above example, you must ensure that the code set in the "Code" attribute does not have a symbol
assigned to it in the LISCAD Code Table used for reduction into LISCAD.
Care must be taken to ensure that the codelist is setup correctly.
The value for the user defined character that you wish to use is held in the registry. Note that the setting is held in: HKEY_CURRENT_USER\Software\LISTECH\LISCAD\8.x\SEE\Field Transfer\Code Settings .
| Setting | Used to |
| SYS1200ExtendedCodeChar: | This defines the character which is to be used if the user wishes to implement extended coding on the instrument. |
Leica System 1200 Codelist Setup
When using a codelist onboard the System 1200, it is common to have a descriptive name for the code being used.
Example: Operation Code 8/6 - Arc By 3 Pts. This would be setup in the codelist as follows;
Code: Arc3Pts
Attribute1: OpCode
Attribute2: Line Type
If this descriptive name is used in the codelist and the registry setting is set to 1, it will be included
in the RAW file and created as;
*41....+000000000Arc3Pts 42....+0000000000000008 43....+0000000000000006
To ensure that this descriptive name is not placed in the RAW file and reduces correctly, the registry setting will need to be set to 0.
This will create the RAW file as follows;
*41....+0000000000000008 42....+0000000000000006
| Setting | Used to |
| SYS1200FreeCodeUsage: | If this is set (value set to 1 in the registry), then when free coding is used, the first attribute will be sent out to the raw file. If this is set to 0, the first attribute will be ignored and all other attributes will go out to the raw file. |
Attribute Type Settings In System 1200 Code List
When creating a Leica System 1200 Codelist in Leica Geo Office (LGO), users must set the Attribute Type for each attribute of every code. The available options for the Attribute Type are Normal, Fixed or Mandatory.
Choosing Normal means the value for the attribute can be edited in the field but a value is not required.
(See Note # 1)
Choosing Mandatory means that the user will be prompted to enter a value for the attribute in the field.
Choosing Fixed means that the value for the attribute is fixed in LGO. It cannot be edited in the field.
Note # 1: If LISCAD encounters an empty attribute value, it will set the value to 00.
Dependant on the specific code, the Attribute Type setting will vary. Below are some typical settings for different code types.
Example #1: Point Code TOE; This code would be strung in the field and has no additional attributes.
| Code Settings | Leica Geo Office / Properties / Attribute Type |
|
Code: TOE Attribute1: String |
Mandatory |
Example #2: Point Code TREE; This code would not be strung in the field and has two additional attributes for the Tree spread and Trunk size.
| Code Settings | Leica Geo Office / Properties / Attribute Type |
|
Code: TOE Attribute1: String Attribute2: Spread Attribute3: Trunk |
Fixed Mandatory Mandatory |