(This functionality is available with the Input / Output module)
This topic documents the operation codes that may be used when performing field surveys with Geodimeter data recorders for processing in the system.
Feature Codes and Symbols
Entering the appropriate feature code and dimensions as part of the data recording of a point will enable automatic generation of the symbol associated with that feature code at the size specified. Use of this feature dramatically increases productivity in both field and processing operations.
In the Geodimeter symbols can be entered as part of the point code or separately.
For most symbols, Height and Width refer to the height and width of the symbol. If height and width are not defined (default - i.e. not entered), the symbol will be drawn at the default symbol size entered in the code table.
If width is zero (default, i.e. not entered), width will be treated as equal to height and the symbol will be generated in proportion. If height and width are different, the symbol will be "stretched or elongated" (i.e. a circular symbol appears elliptical, a square symbol appears rectangular).
For tree symbols, height refers to the spread, and width refers to the trunk diameter. If width is zero (default, i.e. not entered), no trunk will be drawn.
The system uses the Geodimeter Pcode label block (4= ) for feature codes. This Pcode label may also contain symbol dimensions if the symbol is defined in the code table.
For example:
If feature code 201 was defined in the code table as a tree,
and,
the Settings/Code Definition command
had the feature code structure defined as CCCSS (three character code followed
by two character string identifier),
then,
entering 20100-10.0-1.0 in the Pcode field would result in a tree of 10.0
spread and 1.0 trunk diameter being created in the system.
Note:
The separator between the fields must be a minus sign (-) as shown in the above
example or a space.
The maximum size for height and width of a symbol is 32.5.
If a feature code is not entered the previously defined feature code will apply
to that point.
Line Creation Methods
The system supports the following Line Creation Methods.
- STRAIGHT LINE STRING [Default]
- CURVED LINE STRING
- CIRCLE BY CENTRE AND RADIAL POINT
- CIRCLE BY DIAMETER POINTS
- CIRCLE BY 3 CIRCUMFERENCE POINTS
- ARC BY 3 CIRCUMFERENCE POINTS
Use Information Label (0=) with operation code 3 to define a Line Creation Method. For example, 0=32 tells the system to create a spline.
Note that when using information label (0=) in the Geodimeter, you must enter or clear a value in the information field to cause the data to be recorded.
The system reduction process will make the following assumptions:
- After setting Line Creation Method 1, strings will be processed as straight lines until the Line Creation Method is changed.
- After setting Line Creation Method 2, strings will be processed as splines until the
- Line Creation Method is changed or a new code is entered.
- After setting Line Creation Method 3, the current point will be treated as the centre and the next point as the radial point in constructing the circle.
- After setting Line Creation Method 4, the current point and the next point will be treated as the extremities of the diameter in constructing the circle.
- After setting Line Creation Method 5 the current point and the next two points will be treated as circumference points in constructing the circle.
- After setting Line Creation Method 6 the current point and the next two points will be treated as circumference points on the arc.
- Following any Line Creation Method from 3 to 6, system will default to Line Creation Method 1 until a new Line Creation Method is entered.
Field Operation codes
All field operation options are defined via information label (0=). The options are detailed below:
| Option | First Character | Full Character | Example |
| Point Symbol | 1 | 1Feature Code-dim1-dim2 | 120100-10.0-1.0 |
| [Symbol assigned to feature code 201 with height 10.0 and width 1.0; code structure CCCSS assumed] | |||
| Offset Left | 2 | 21dist | 211.2 |
| [Left 1.2] | |||
| Offset Right | 2 | 22dist | 221.2 |
| [Right 1.2] | |||
| Move Forward | 2 | 23dist | 231.2 |
| [Forward 1.2] | |||
| Move Backward | 2 | 24dist | 241.2 |
| [Back 1.2] | |||
| Move Up | 2 | 25dist | 251.2 |
| [Up 1.2] | |||
| Move Down | 2 | 26dist | 261.2 |
| [Down 1.2] | |||
| Line Creation Method | 3 | 3methodv 33 | |
| [Line Creation Method 3] | |||
| Close String | 4 | 4 | 4 |
| [Closes current string back to its start point] | |||
| Repeat Point | 5 | 5 | 5 |
| [Repeats last point] | |||
| Remove Elevation | 7 | 7 | 7 |
| [Removes elevation from previous point] | |||
| Join 2 Points | 8 | 8-pt1-pt2-code | 8213-243-21006 |
| [Join 213 to 243 with feature code of 210; assumes code structure CCCSS] | |||
| >Circle | 9 | 9radius | 922.3 |
| [Creates a circle of radius 22.3 with centre at previous point] | |||
Note: Any item in an information label starting with a character other than 1 to 9 will be treated as a point description.
Recording Format
As the system can reduce a variety of Geodimeter field data labels contained in the same file, point codes and information data must be 'attached' to the field observations or co-ordinates.
To achieve this, the point or station identifier must be the first entry in the UDS sequence, and point codes and optional information data should follow this entry in the measurement/co-ordinate block, and occur before the next point identifier or station identifier entry.
The field UDS's recommended are as follows:-
| Station setup UDS | |||
| Station Identifier | - Stn | (2=) | |
| North Co-ordinate | - N | (37=) | optional |
| East Co-ordinate | - E | (38=) | optional |
| Elevation | - ELEV | (39=) | optional |
| Instrument Height | - IH | (3=) | |
| Reference Object | - Ref Obj | (62=) | |
| North Co-ordinate | - N | (37=) | optional |
| East Co-ordinate | - E | (38=) | optional |
| Elevation | - ELEV | (39=) | optional |
| Backbearing | - HAref | (21=) | |
| Fixed Co-ordinate UDS | |||
| Point Identifier | - Pno | (5=) | |
| Code | - Pcode | (4=) | |
| North Co-ordinate | - N | (37=) | |
| East Co-ordinate | - E | (38=) | |
| Elevation | - ELEV | (39=) | optional |
| Observation UDS | |||
| Point Identifier | - Pno | (5=) | |
| Code | - Pcode | (4=) | |
| Signal Height | - SH | (6=) | |
| Information | - Info | (0=) | (Optional - enter when required) |
| Bearing | - HA | (7=) | |
| Vertical Reading | - VA | (8=) | |
| Slope Distance | - SD | (9=) |
Note: The position of the information record is not rigid but if MUST be included AFTER the first record of the observation (which must be the Point or Station Identifier) and BEFORE the first record of the following observation or station setup.
The system also supports the data recording sequences generated by the Geodimeter program 20 (Station Definition) and program 23 (Set Out).
Example of a RAW Geodat File: Note that a feature code structure of CCCSS is assumed in this data.
Geodimeter Geodat-500- Header Line
50=241093 - Job Description
2=1- Station Identifier
3=1.550- Instrument Height
62=100- Reference Object
21=0.0000- Backbearing
5=2- Observed Point Identifier
4=60101- Code (code 601 string 01)
6=1.500- Signal height
0=220.1- Offset right 0.1
7=253.2530 - Bearing
8=90.3008 - Vertical Reading
9=18.52 - Slope Distance
5=3
4=60101
6=1.500
7=345.3608
8=90.4638
9=8.07
5=4
4=40101
6=1.500
0=5
7=349.1700
8=91.0236
9=7.01
5=5
4=40101
6=1.500
0=610101
7=260.5838
8=90.5526
9=12.04
5=9
4=10201
6=2.000
7=250.1456
8=89.0004
9=18.05
0=TPEG- Description
5=46
4=10204
6=1.500
7=280.4456
8=93.2930
9=2.33
5=47
4=10204
6=1.500
7=295.5508
8=92.0832
9=3.69
5=48
4=10204
6=1.500
7=345.3932
8=90.3436
9=3.67
5=49
4=10204
6=1.500
7=358.3344
8=90.5244
9=2.44
0=4 - Close String (46-47-48-49-46)
5=50
4=20100-5.0-0.2- Dimensioned Symbol
6=1.500
7=213.3304
8=94.2450
9=2.51
5=51
4=20100-0.2- Dimensioned Symbol
6=1.500
7=221.3906
8=94.1030
9=4.93
>
Note: The Geodimeter re-formatter re-orders the observed East/North co-ordinates to conform to the current system settings.