Leica DBX Extended Operation Coding

(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.

Also refer to LEICA DBX Code Lists