Wildsoft Operation Codes

(This functionality is available with the Input / Output module)

This topic lists the Wildsoft data collection codes that can be read by the system. For more detailed information, consult the Wildsoft documentation.

New users who are familiar with the Wildsoft data collection codes may prefer to use these in preference to the Normal Wild Operation Codes.

Please note that if you are using a TC-600 total station, do not use these operation codes but refer instead to the TC-600 Field Operations topic.

In the list below, optional info block entries are shown in (Italic).

CODE	FUNCTION	INFO1,2,3,4
1	Start Job	Start Point ID (Reference Azimuth) (BS Point ID) (Job Number)
11	Assign Co-ordinates	Point ID X co-ordinate Y co-ordinate (Z Co-ordinate)
	Whether information blocks 2 and 3 are interpreted as East co-ordinate then North co-ordinate, or North co-ordinate then East co-ordinate by the system depends on the setting in the Utilities/Configure/Co-ordinates command. Ensure that this command is set for East first, or North first to suit your RAW file before creating the field file.
12	Co-ordinate Offset	X offset Y offset
	Whether information blocks 1 and 2 are interpreted as East offset then North offset, or North offset then East offset by the system, depends on the setting in the Utilities/Configure/Co-ordinates command. Ensure that this command is set for East first, or North first to suit your RAW file before creating the field file.
13	Target Height	Height of FS
14	Add to Target Height	Height to Add
15	Add to Distance	Distance to Add
2	Occupy a Point	(Point ID) (Instrument Height) (BS Point ID)
21	Occupy Saved Point	Point ID or Temp Point ID (Instrument Height) (BS Point ID)
NOTE:	All angle observations must be taken in rounds with the order of points observed being reversed on the second face. For example three points would be observed as follows: Face Left: BS to first point FS to second point FS to third point Face Right FS to third point FS to second point BS to first point
3	FS to Traverse Point	(Point ID) (Target Height) (BS Target Height)
31	FS to Single Point	(Point ID) (Target Height)
32	Radial Sideshots	(Point ID) (Target Height) (BS Point ID)
33	Sets of Angles	Number of FS Points Number of Sets (Point ID)
4	Closing Pt/Line	Point ID Reference Azimuth Point on Reference Line
41	Closing Angle
60	Save Point	Temporary Point ID
61	Recall Point	Temporary Point ID
63	Remark	(Optional) (Optional) (Optional) (Optional)
NOTE:	If the feature code definition in the Field Transfer/Settings/Code Definition command does not contain a string component, then the following Operation Codes 70 to 84 will be used by the system to generate the line work and contourable attributes. If the feature code definition does contain a string component, it will be used to generate the line work and contourable attributes in conjunction with the code table, and operation codes 70 to 84 will be ignored. For example if the code definition is CCC, then the operation codes 70 to 84 will be used to control the stringing and contourable attributes. However, if the code definition is CCCSS, then the operation codes 70 to 84 will not be used and stringing will be determined according to the string identifiers in conjunction with the code table settings. Refer to the Code Definition command for information about using string identifiers.
70	Start Line	(Line type) (Pen Number) (Tic Number)
71	Interrupt Line
72	Continue Line
73	3 Points for Arc
74	Start Smooth Spline
80	Start Breakline	Breakline ID (range of 1 to 99 only) Breakline type
81	Interrupt Breakline
82	Continue Breakline	(Breakline ID)
83	Start Masspoints
84	Interrupt Masspoints
100	Descriptions	OFF
NOTE:	The Codes 101 and above will be interpreted according to the Code table used. These codes will be matched to the corresponding Feature Code in the code table during the reduction process and the point and line attributes set accordingly, subject to the code definition being used (See next paragraph). The Line and contourable attributes will be generated according to the string identifiers and code table settings if the feature code definition in the Field Transfer/Settings/Code Definition command contains a string component. If the code definition does not contain a string component, then the line work and contourable attributes will not be generated according to the code table, but according to operation codes 70 to 84. Refer to the Concepts/Tables topic for more information about using code tables. The Information Blocks for Codes 101 and above may be interpreted in two ways depending on whether the feature code in the code table has a symbol defined. If the feature code has a symbol, the Information Blocks are interpreted as follows:
101 +	Feature Codes	(Symbol Dimension 1) (Symbol Dimension 2) (Description 1) >(Description 2)
	If the feature code does not have a symbol, the Information Blocks are interpreted as follows:
101+	Feature Codes	(Description 1) (Description 2) (Description 3)
	The following rules apply to how the descriptions are used. If the description in the code table contains the wild cards #1, #2, or #3, the corresponding description in the Wild file will replace the wild card. e.g. Code table description:#1 Tree #2 feet high Description 1Palm Description 250 Final point descriptionPalm Tree 50 feet high If there are no Wild cards in the code table description, and there is a Description 1 in the Wild file, it will be used in preference to the description in the code table.

ADDITIONAL CODES SUPPORTED BY THE SYSTEM when using WILDSOFT CODING

CODE	FUNCTION	INFO1,2,3,4
16	Measured Offset	(Offset +ve right, -ve left as viewed from instrument) (Added Distance +ve away from instrument, -ve towards) (Height Difference +ve up, -ve down)
90-98	Define Field Templates	First Feature Code Second Feature Code Third Feature Code Fourth Feature Code
	The Operation Code may be repeated another 4 times to define up to 20 feature codes in a field template. Up to 9 field templates, each using one of the operation codes 90 to 98, and each containing as many as 20 feature codes, may be defined and retrieved during a field session. Using the operation code after the field template is defined recalls the field template for use. Do this after observing the first point in the field template.
99	End Field Template Definition