Data Collection by Eagle Point

Data Collection by Eagle Point
Information in this manual is subject to change without notice and does not represent a
commitment on the part of the vendor. The software described in this manual is furnished
under a license agreement and may be used or copied only in accordance with the terms
of the agreement.
Eagle Point has carefully prepared this program package, including research,
development, and testing to ascertain its effectiveness and accuracy. However, no
warranty of any kind is made with respect to this program package or its related material,
except as may be expressly stated in the licensing agreement or other contractual
document. In no event is Eagle Point liable for incidental or consequential damages in
connection with, or arising out of, the furnishing, performance, or use of this program
package.
The installation program used to install Eagle Point software, InstallShield, is licensed
software provided by InstallShield Software Corporation.
ColorFast™, RoadCalc™, LANDCADD™, Virtual Simulator™, as well as the ColorFast™
and Eagle Point logos, are unregistered trademarks of Eagle Point.
AutoCAD® is a registered trademark of Autodesk, Inc.
MicroStation® is a registered trademark of Bentley Systems, Inc.
Windows® and DOS® are registered trademarks of Microsoft Corporation.
Leica and the names of Leica products referenced herein are either trademarks and/or
service marks or registered trademarks and/or service marks of Leica Geosystems.
Nikon and the names of Nikon products referenced herein are either trademarks and/or
service marks or registered trademarks of Nikon Instruments Inc.
Pentax and/or Pentax Corporation products referenced herein are either trademarks or
registered trademarks of the Pentax Corporation.
Sokkia Corporation and the names of Sokkia Corporation products referenced herein are
either trademarks and/or service marks or registered trademarks and/or service marks of
Sokkia Corporation.
Trimble® and the names of Trimble Navigation Limited products referenced herein are
either trademarks and/or service marks or registered trademarks and/or service marks of
Trimble Navigation Limited.
All other registered or unregistered trademarks are the property of their respective
holders.
Copyright © Q3, 2005, by Eagle Point. All rights reserved.
DATA
COLLECTION TA B L E
OF
CONTENTS
1 Data Collection Concepts . . . . . . . . . . . .1
Introduction . . . . . . . . . . . . . . . . . . . . . . . .2
Entering Field Codes into the Collector . . .2
Field Coding Format . . . . . . . . . . . . . . . . . . . . 3
Field Entry Examples . . . . . . . . . . . . . . . . .5
Node Selection . . . . . . . . . . . . . . . . . . . . .6
2 Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Download from Collector . . . . . . . . . . . . .10
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Upload to Collector . . . . . . . . . . . . . . . . .12
QuickSteps for Uploading ASCII File . . . . . . . 13
QuickSteps for Uploading from Project . . . . . 14
Import ASCII File . . . . . . . . . . . . . . . . . . .15
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Export Nodes . . . . . . . . . . . . . . . . . . . . . .16
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Edit Instrument File . . . . . . . . . . . . . . . . .17
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Edit Formatted File . . . . . . . . . . . . . . . . .19
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Reduce Job . . . . . . . . . . . . . . . . . . . . . . .20
Preview Objects . . . . . . . . . . . . . . . . . . . . . . . 22
Display Settings . . . . . . . . . . . . . . . . . . . 24
SDMS Set-up Data . . . . . . . . . . . . . . . . . . . . 26
Manage Jobs . . . . . . . . . . . . . . . . . . . . . .28
Modify Job . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 31
Print Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table of Contents i
3 Options . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Reduction Settings . . . . . . . . . . . . . . . . . 34
Reduction Settings – Collector Tab . . . . . . . . 36
Reduction Settings – Graphics Tab . . . . . . . . 37
Reduction Settings – Line Work Tab . . . . . . . 39
Reduction Settings – Shot Averaging Tab . . . 41
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Designators . . . . . . . . . . . . . . . . . . . . . . . 44
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Line (Draw) Designator . . . . . . . . . . . . . . 49
Curve Designator . . . . . . . . . . . . . . . . . . . 50
Fitted Alignment Using a Curve
Designator . . . . . . . . . . . . . . . . . . . . . . . . 51
Close Line Designator . . . . . . . . . . . . . . . 52
Join Last Shot Designator . . . . . . . . . . . . 52
Bearing Close Designator . . . . . . . . . . . . 53
Cross-Section Designator . . . . . . . . . . . . 53
Stop Line Designator . . . . . . . . . . . . . . . . 54
Insert Description Designator . . . . . . . . . 55
Rectangle Designator . . . . . . . . . . . . . . . 55
Circle Designator (Center Point
and Radius) . . . . . . . . . . . . . . . . . . . . . . . 56
Circle Designator (Three Point) . . . . . . . . 57
Feature Line (90 Degree Angles) . . . . . . 57
Feature Line (Entered Angles) . . . . . . . . 58
Line Work . . . . . . . . . . . . . . . . . . . . . . . . 58
New Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
New Line (AutoCAD/BricsCad) . . . . . . . . 61
QuickSteps (AutoCAD/BricsCad) . . . . . . 64
New Line (MicroStation) . . . . . . . . . . . . . 65
QuickSteps (MicroStation) . . . . . . . . . . . . 68
Line Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 70
Linetype Libraries . . . . . . . . . . . . . . . . . . . . . . 71
Cross-Section Patterns . . . . . . . . . . . . . . 72
New Cross-Section Pattern . . . . . . . . . . . . . . 73
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 75
3-D Line Templates . . . . . . . . . . . . . . . . . 76
New 3-D Line Template . . . . . . . . . . . . . . . . . 77
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 78
Example . . . . . . . . . . . . . . . . . . . . . . . . . . 78
New 3-D Line Template Breakpoint . . . . . 80
ii Data Collection
4 Query . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Query Warnings . . . . . . . . . . . . . . . . . . . .84
Query Shot Averaging . . . . . . . . . . . . . . .85
Query Backup File . . . . . . . . . . . . . . . . . .86
Query File Information . . . . . . . . . . . . . . .87
Query Observations . . . . . . . . . . . . . . . . .89
Query Nodes . . . . . . . . . . . . . . . . . . . . . .92
Query Unused Nodes . . . . . . . . . . . . . . .94
Resolve Duplicate Nodes . . . . . . . . . . . .95
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 96
A SDMS Editor . . . . . . . . . . . . . . . . . . . . . .99

Introduction . . . . . . . . . . . . . . . . . . . . . .100
SDMS Editor – File Menu . . . . . . . . . . .103
Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
SDMS Editor – Edit Menu . . . . . . . . . . .105
Undo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Cut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Select All . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Find Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Global Edit . . . . . . . . . . . . . . . . . . . . . . . . . . 110
SDMS Editor – Tools Menu . . . . . . . . . .113
Insert Row . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Delete Row . . . . . . . . . . . . . . . . . . . . . . . . . 113
Add Column . . . . . . . . . . . . . . . . . . . . . . . . . 114
Find Data Collection Warnings . . . . . . . . . . 114
Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Display Settings . . . . . . . . . . . . . . . . . . . . . . 116
SDMS Editor – Help Menu . . . . . . . . . .116
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Search For Help On . . . . . . . . . . . . . . . . . . . 116
About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Table of Contents iii

B Geodat Labels . . . . . . . . . . . . . . . . . . . 117
GEODAT Labels . . . . . . . . . . . . . . . . . . 118
New/Modify GEODAT Label . . . . . . . . . . . . 119
QuickSteps . . . . . . . . . . . . . . . . . . . . . . 120
Edit Data Tags . . . . . . . . . . . . . . . . . . . . . . . 120
C Leica Codes . . . . . . . . . . . . . . . . . . . . . 123

Leica Codes . . . . . . . . . . . . . . . . . . . . . 124
New Leica Code . . . . . . . . . . . . . . . . . . . . . . 126
QuickSteps . . . . . . . . . . . . . . . . . . . . . . 127
Edit Data Tags . . . . . . . . . . . . . . . . . . . . . . . 128
D Collectors and Formats . . . . . . . . . . . 129

GEODAT . . . . . . . . . . . . . . . . . . . . . . . . 130
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Collecting Data . . . . . . . . . . . . . . . . . . . . . . . 132
UDS – 2 SETUP . . . . . . . . . . . . . . . . . . 132
UDS – 3 CONTROL CHECK . . . . . . . . . 134
UDS – 4 UTILITY WITH LINE WORK . . 134
UDS – 5 UTILITY FEATURE . . . . . . . . . 135
UDS – 6 TOPOGRAPHY
WITH BREAKLINES . . . . . . . . . . . . . . . 136
UDS – 7 TOPOGRAPHY . . . . . . . . . . . . 137
UDS – 8 CONTROL ENTRY . . . . . . . . . 138
UDS – 9 TRAVERSE AHEAD . . . . . . . . 138
UDS – 10 CROSS-SECTIONS . . . . . . . 139
UDS – 11 COMMENT . . . . . . . . . . . . . . 140
UDS – 12 ACTIVITY LABEL . . . . . . . . . 140
Line Work (Recommended
for Non-Alphanumeric Instruments) . . . . 141
Line Work (Recommended
for Alphanumeric Instruments) . . . . . . . 142
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . 143
QuickSteps . . . . . . . . . . . . . . . . . . . . . . 144
QuickSteps . . . . . . . . . . . . . . . . . . . . . . 145
QuickSteps . . . . . . . . . . . . . . . . . . . . . . 146
Leica (WILD) . . . . . . . . . . . . . . . . . . . . . 148
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Measure Block . . . . . . . . . . . . . . . . . . . . 149
Code Block . . . . . . . . . . . . . . . . . . . . . . 149
Collecting Data – Using codes based
on WILDsoft . . . . . . . . . . . . . . . . . . . . . . . . . 150
iv Data Collection
Code 1: Project Setup . . . . . . . . . . . . . . 150
Code 11: Control Coordinates . . . . . . . . 150
Code 13: New Target Height . . . . . . . . . 151
Code 2: Instrument Setup . . . . . . . . . . . 151
Code 52: Backsight . . . . . . . . . . . . . . . . 151
Code 3: Foresight . . . . . . . . . . . . . . . . . 152
Code 32: Radial Sideshot . . . . . . . . . . . 152
Code 99: Sideshot . . . . . . . . . . . . . . . . . 152
Code 100: Sideshot . . . . . . . . . . . . . . . . 153
Collecting Data – Node ID . . . . . . . . . . . . . . 153
Collecting Data – Entering Decimals
on the Instrument . . . . . . . . . . . . . . . . . . . . . 154
QuickSteps . . . . . . . . . . . . . . . . . . . . . . 154
Collecting Data – Field Codes . . . . . . . . . . . 154
Collecting Data –Temporary Shots . . . . . . . 155
Collecting Data – Traverse . . . . . . . . . . . . . 156
Collecting Data – Line Work (Recommended
for Non-Alphanumeric Instruments) . . . . . . . 158
Collecting Data – Line Work (Recommended
for Alphanumeric Instruments) . . . . . . . . . . 161
Intermediate Shots . . . . . . . . . . . . . . . . 164
Changing Field Codes . . . . . . . . . . . . . . 164
Collecting Data – Customizing Codes . . . . . 165
Numeric Activities . . . . . . . . . . . . . . . . . 165
Code 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Code 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Collecting Data – Leica Instruments . . . . . . 168
VIP Series . . . . . . . . . . . . . . . . . . . . . . . 168
TPS Series . . . . . . . . . . . . . . . . . . . . . . 168
Transferring Data . . . . . . . . . . . . . . . . . . . . . 168
Downloading from the Collector (GIF10) 169
Uploading to the Collector (GIF10) . . . . 170
Downloading from the Collector (GRE4) 172
Maptech . . . . . . . . . . . . . . . . . . . . . . . . .174
Nikon . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Download from an AP700 or 800 Series
Instrument . . . . . . . . . . . . . . . . . . . . . . . 175
Pentax and Corvallis . . . . . . . . . . . . . . .176
Downloading from the Collector . . . . . . 176
Alternative Downloading Steps . . . . . . . 178
Uploading to the Collector . . . . . . . . . . . 180
Table of Contents v
Sokkia (Lietz) . . . . . . . . . . . . . . . . . . . . 182
Collecting Data . . . . . . . . . . . . . . . . . . . . . . . 184
Downloading from the Collector . . . . . . 184
Uploading to the Collector . . . . . . . . . . . 186
Surveyor’s Module (SMI) . . . . . . . . . . . 188
Download Coordinate Information from the
SMI Data Collector . . . . . . . . . . . . . . . . . . . . 188
Download Raw Survey Information from the
SMI Data Collector . . . . . . . . . . . . . . . . . . . . 189
Upload Coordinate Information to the SMI
Data Collector . . . . . . . . . . . . . . . . . . . . . . . 190
Trimble/Tripod Data Systems (TDS) . . . 191
Downloading from the TDS HP48GX . . 191
Uploading to the TDS HP48GX . . . . . . . 192
Downloading from the TDS Ranger
(SurveyPro v3.x) . . . . . . . . . . . . . . . . . . 193
Uploading to the TDS Ranger
(SurveyPro v3.x) . . . . . . . . . . . . . . . . . . 196
Topcon . . . . . . . . . . . . . . . . . . . . . . . . . 200
Zeiss . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Collecting Data . . . . . . . . . . . . . . . . . . . . . . . 201
E Troubleshooting . . . . . . . . . . . . . . . . . 203
General Communications Problems . . . 204
Internal Modem/Digitizer with a Serial
Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . 206
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 207
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . . . 207
F EP SDMS . . . . . . . . . . . . . . . . . . . . . . . 209
Beginning of SDMS File . . . . . . . . . . . . 211
Surveying Activities . . . . . . . . . . . . . . . . 211
Project (PR) Activity . . . . . . . . . . . . . . . . . . . 212
Occupied Station (OS) Activity . . . . . . . . . . . 212
Backsight (BS) Activity . . . . . . . . . . . . . . . . . 213
Foresight (FS) Activity . . . . . . . . . . . . . . . . . 214
Sideshot (SS) Activity . . . . . . . . . . . . . . . . . . 214
vi Data Collection
Elevation Control Check (EC) Activity . . . . . 215
Other Activities . . . . . . . . . . . . . . . . . . . . . . 215
Common Data Tags . . . . . . . . . . . . . . .215
AZ: Azimuth . . . . . . . . . . . . . . . . . . . . . . . . . 215
DO: Offset Direction . . . . . . . . . . . . . . . . . . 216
DS: Slope Distance . . . . . . . . . . . . . . . . . . . 217
FE: Feature (Field Code) . . . . . . . . . . . . . . . 218
FG: Figure . . . . . . . . . . . . . . . . . . . . . . . . . . 218
GM: Geometry . . . . . . . . . . . . . . . . . . . . . . . 219
HZ: Horizontal Angle . . . . . . . . . . . . . . . . . . 220
IH: Instrument Height . . . . . . . . . . . . . . . . . . 220
LO: Length Offset . . . . . . . . . . . . . . . . . . . . 221
OF: Offset . . . . . . . . . . . . . . . . . . . . . . . . . . 222
PD: Point Description . . . . . . . . . . . . . . . . . 223
PN: Point Number . . . . . . . . . . . . . . . . . . . . 224
PO: Prism Offset . . . . . . . . . . . . . . . . . . . . . 224
PR: Project Name . . . . . . . . . . . . . . . . . . . . 225
RO: Radial Offset . . . . . . . . . . . . . . . . . . . . 226
SH: Staff Height . . . . . . . . . . . . . . . . . . . . . . 227
SS: Nominal Stationing . . . . . . . . . . . . . . . . 228
ST: Stationing . . . . . . . . . . . . . . . . . . . . . . . 228
TK: Task . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
VO: Vertical Offset . . . . . . . . . . . . . . . . . . . . 230
VT: Vertical (Zenith) Angle . . . . . . . . . . . . . 230
XC: X Coordinate Value . . . . . . . . . . . . . . . 231
YC: Y Coordinate Value . . . . . . . . . . . . . . . 232
ZC: Z Coordinate Value/Elevation . . . . . . . . 232
Reserved Eagle Point SDMS Data
Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
Minimum Setup Information . . . . . . . . . .244
Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . 244
Occupied Station . . . . . . . . . . . . . . . . . . 244
Backsight . . . . . . . . . . . . . . . . . . . . . . . . 245
Intermediate Setup . . . . . . . . . . . . . . . . . . . 247
Intermediate Occupied Station . . . . . . . 247
Intermediate Backsight . . . . . . . . . . . . . 247
Data Collection Glossary . . . . . . . . . . .249
Index . . . . . . . . . . . . . . . . . . . . . . . . . . .253
Table of Contents vii

viii Data Collection
DATA
COLLECTION CHAPTER
CONCEPTS
Data Collection runs on AutoCAD, BricsCad, and
MicroStation.
In this chapter:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Entering Field Codes into the Collector. . . . . . . . . . . . 2
Field Entry Examples . . . . . . . . . . . . . . . . . . . . . . . . . 5
Node Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1
Chapter 1: Data Collection Concepts 1

Introduction
Data Collection utilizes direct links with several supported data collectors and data
collector formats to download raw instrument and coordinate data. This information may
be previewed, error-checked and processed into the CAD graphic. Through the use of
special designators and cross-section patterns in the field, and 3-D templates within Data
Collection, existing roads, walls, gutter and sidewalk sections can be created quickly and
easily in the CAD graphic.
Information may also be exported or uploaded from your CAD graphic or database directly
to your data collector for stakeout or setout functions in the field.
Entering Field Codes into the Collector

! This section outlines how Field Code and line information are recorded for most data
collection formats. For information on how your specific data collector format is integrated
within Data Collection, including GEODAT and Leica, see Collectors and Formats, which
begins on page 129. For additional information on how to customize Data Collection for
GEODAT and Leica instruments, refer to Geodat Labels, which begins on page 117 or
Leica Codes, which begins on page 123.
One of the most important steps toward creating a project with Data Collection is taken
before you even use the software – collecting the data appropriately out in the field. You
can collect points as usual, but to take full advantage of Data Collection’s line-drawing
and symbol-manipulation abilities, you must give the program information about your
points using Field Codes and line names.
Field Codes are user-defined, alphanumeric codes that are stored in the Node (Field
Code) Library (See Node (Field Code) Library in the Eagle Point Menu manual). This
contains a library of symbols that can be placed at each coordinate point recorded with a
data collector. Each Field Code is associated with a symbol and attributes that may be
specific to the Field Code or similar Field Codes through a Node Attribute Style. Also
stored in the Node (Field Code) Library is the description, scale factor, attributes, and CAD
properties for each symbol.
When you record a shot point in the data collector, you can enter a Field Code as the first
part of the point’s description. Data Collection then inserts the corresponding symbol into
the CAD graphic at the calculated location.
You can also create line work by following the Field Code with a line work designator.
Here are some points to remember regarding Field Codes and symbols:
2 Data Collection
1. If you enter a Field Code for a shot and follow it with a description, Data
Collection Concepts
Collection places the description you entered into the CAD graphic next to the
Chapter 1: Data
symbol, e.g., MH STORM. If you do not enter a description, Data Collection uses
the description it finds in the Node (Field Code) Library, e.g., MH.
2. If you do not enter a Field Code for a point, Data Collection uses the default
Field Code set in the Reduction Settings in Data Collection.
3. Data Collection assumes that anything alphanumeric less than 10 characters at
the front of the description field is a Field Code. If it is not in the Node (Field
Code) Library, Data Collection uses the default Field Code in the settings and
displays the message “Field Code_ not found at point #” in the Warnings
dialog box after the job is reduced.
Field Coding Format

The following is the format for entering Field Codes into a collector, definitions, and
examples:
Field Code Line designator Line name Special designator <<space>> Description
Definitions for Entering Field Codes into a Collector

Option Function
Field Code One of the user-defined, alphanumeric codes defined in the Node (Field Code) Library.
Line designator A user-defined alphanumeric delimiter must be present if the point taken generates line
work. The default value is a period (.).
Line name One of the user-defined, alphanumeric line names defined in line work. The line name will
be connected to each occurrence in the job file that has the same line name.
Special You may use a special designator when shooting a point with line work to define special
designator(s) conditions in the line work.
<<space>> Required if a description is to be entered.
Description Used to describe the point taken. Data Collection places the description into the CAD
graphic next to the point. This description overrides or is combined with the description
entered for the symbol in the Node (Field Code) Library. The determining factor is the
description designator.
! The only time a space should be used is before entering the description or within a
description.

Figure 1-1 Entry Format for Field Codes
The following table lists the designators and the initial default values.
Designators System Defaults

Line . (period)
Curve - (hyphen)
Close line + (plus)
Join last shot * (asterisk)
Bearing close # (pound sign)
Cross-section = (equal sign)
Stop line ! (exclamation point)
Insert description * (asterisk)
Command indicator / (forward slash)
Rectangle R
Circle C
Feature Line FL
4 Data Collection
Collection Concepts
Field Entry Examples
Chapter 1: Data
The following examples use the default designators for line work:
Default Designators for Line Work Examples
MH.EL SEWER This entry places Field Code MH and connects any line name EL
with a line(.), and overrides the default description for symbol MH
with SEWER.
MH.EL- This entry places Field Code MH and connects any line name EL
with a curve(-), and uses the default description for Field Code MH.
DTREE This entry places symbol DTREE and uses the default description.
No line work is produced.
MH.EL.TEL This entry is a common point between lines EL and TEL. When
shooting a point that is on more than one line, you only need to
shoot the common point once. Follow the first line name entered
with a second line designator and second line name.
MH.BOX+ This entry places Field Code MH, using the default description. The
close line designator (+) closes this line to the first shot taken on line
BOX.
T.BC! This entry allows you to stop the line BC at that shot without
connecting it to the next BC line.
IP.PROP* This entry allows you to connect the last shot taken to the line
entered on the current shot. Assume the prior shot was “IP.” The
prior shot entry places symbol IP using the default description. The
Join Last Shot designator will connect the prior shot as if it were
coded “IP.PROP.”
! When customizing the designators, you cannot use the same characters as part of any
Field Code name or any other designator name. For example, the Close Line
designator cannot be “CLINE” while the Line designator is “line.”
! When collecting line work, record the information in a linear or radial fashion so that shots
are taken in order. The line work is processed in the order that it occurs in the file.

Node Selection
If you are uploading, exporting or querying the Nodes in a project, there are several
different methods that you can use to select them.
Figure 1-2 Query Nodes Dialog Box
Query Nodes Dialog Box Definitions

Option Icon Function
PIC Click on the PIC icon to graphically select a Node or Nodes based on your
selection method.
Selection Mode These options allow you to choose whether to add Nodes to the selection set or
to remove them from the selection set. If the Selection Mode is set to Select
when Apply is clicked on, the Nodes will be added to the selection set. If the
Selection Mode is set to Unselect, the Nodes will be removed from the selection
set when Apply is clicked on.
6 Data Collection
Collection Concepts
Chapter 1: Data
Selection " Single: You may select a single Node from the CAD graphic by
Method clicking on the Pick in CAD (PIC) button and picking a Node, or by
typing a Node ID that exists in the project. When a Node is selected,
the coordinates for the Node will update in the static text field next to
the coordinate label. You may continue to select Nodes and the fields
will update, but only one Node will be selected when Apply is clicked
on.
" Elevation Range: You may enter two elevation values to select all of
the Nodes that match and fall within the elevation range.
" Range: Type an interval for a range of Nodes, or select two Nodes
from the CAD graphic by clicking on the PIC button and picking two
Nodes. The range may be entered with either the larger or smaller
Node ID in either order.
" All: All valid Nodes are selected from the project.
" Name: You may type in an alpha prefix for the Nodes to be selected.
A question mark (?) denotes the place of an alpha character. An
asterisk (*) may be used as a wild card at the end of the name. All
Nodes with the portion of the alpha prefix entered will be selected.
" AutoCAD/BricsCad: Within AutoCAD/BricsCad, you can use
several methods to select Nodes (Window, Crossing, Fence, etc.).
When Apply is selected, the selection set that was built in AutoCAD/
BricsCad will be used.
" Proximity: You may select all of the Nodes within a proximity of a
Node or point in the CAD graphic. To select a Node or point, click on
the PIC button and pick a Node, type a Node ID that exists in the
project, or place the focus in a coordinate edit field, click on the PIC
button and pick a point, or type the coordinates.
! If you use the PIC button, the location of the cursor, or focus, determines
what may be selected in the CAD graphic. For example, if focus was in the
Node ID edit field before you clicked on the PIC button, then only a Node
can be selected. If focus was in a coordinate edit field before you clicked
on the PIC button, then only a coordinate value can be determined.
! You may enter a horizontal distance to represent the proximity around the
Node selected. All Nodes within this horizontal radius will be selected.

Selection " Description: You may type a description to select Nodes. An asterisk
Method (*) may be used as a wild card at the beginning or the end of the
description.
" Block: You may type the block name (AutoCAD/BricsCad) or cell
name (MicroStation) of the symbol that is used in the Nodes you want
to select. You may add an asterisk (*) as a wild card at the beginning
or the end of the name.
" Field Code: You may select Nodes by choosing a Field Code from
the drop list. The Field Codes listed are from the current Node (Field
Code) Library.
" The Prefix option will be available only if the Node ID format is set to
alphanumeric. You may type in an alpha prefix for the Nodes to be
selected. A question mark (?) denotes the place of an alpha
character. An asterisk (*) may be used as a wild card at the end of the
name. All Nodes with the portion of the alpha prefix entered will be
selected.
" Fence: Within MicroStation, you may use a fence in CAD to select
Nodes. When Apply is selected, the fence that is in the drawing will
be used for the selection. You may choose to place a fence at any
time before Apply is selected.
8 Data Collection
JOBS
In this chapter:
CHAPTER
Download from Collector. . . . . . . . . . . . . . . . . . . . 10
Upload to Collector . . . . . . . . . . . . . . . . . . . . . . . . 12
Import ASCII File. . . . . . . . . . . . . . . . . . . . . . . . . . 15
Export Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Edit Instrument File . . . . . . . . . . . . . . . . . . . . . . . . 17
Edit Formatted File . . . . . . . . . . . . . . . . . . . . . . . . 19
Reduce Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Manage Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2
Chapter 2: Jobs 9
Download from Collector
DATA COLLECTION # JOBS # DOWNLOAD FROM COLLECTOR
KEY-IN COMMAND: download
ICON:
This command allows you to download survey information from your data collector to Data
Collection.
You may select your collector format from the drop list of supported formats and download
the information.
Refer to Collectors and Formats, which begins on page 129, for additional information on
specific collector formats and file transferring steps.
Figure 2-1 Download from Collector Dialog Box
Download from Collector Dialog Box Definitions

Option Function
Job Name Enter a descriptive name for the job that is being downloaded. You are allowed up to 32
characters for the Job Name. The name of the job is used to keep track of the file within
Data Collection.
Format Specify the collector format you will be using to download data. Select a format from the
list of supported formats.
Version When one of the SMI formats is selected (SMi - Coordinate, SMi - SDMS, or SMi -
SDR2X), you may select whichever version of SMI you are using.
Serial Port Select the port where the data collector is connected. If you already have the data on disk,
use the Import ASCII File command.
Baud Rate Select the appropriate baud rate to match the settings for the data collector.
Data Bits Select the appropriate data bit size and parity setting for the data collector.
10 Data Collection
Download from Collector Dialog Box Definitions
Option Function
Create Legal Toggle on this option to create a backup of the file that is being downloaded. This file is an
Backup File exact duplicate of the downloaded file and is attributed read-only. Any modification to this
file will create a change in the date stamp of this file so that it will no longer match the time
that it was created originally.
! You may compare this file with any modifications that you make to the downloaded
instrument file, and you may revert to the original at any time.
QuickSteps
Chapter 2: Jobs
1. Open a project in Eagle Point and select Products ! Data Collection.
2. Select Jobs ! Download from Collector.
3. Type the name of the job to download.
4. Select the data collector format from the drop list of available formats.
5. If you choose an SMI data collector, select the version of software you have on
the collector.
6. Select the serial port that is connected to the collector.
7. Select the baud rate of the collector.
8. Select the data bit size and parity of the collector.
9. Choose whether to create a legal backup of the file to be downloaded and click
on OK.
10. Prepare the data collector for data transmission. See your data collector’s
documentation for more information.
11. Press any key on the computer.
The computer waits a maximum of thirty seconds for data to be received. If data is not
received, a timed-out message displays and communications are terminated.
12. Send the data from the collector.
! When everything is working properly, you will see the data scroll across the computer
screen, or the system will display a message stating the number of bytes being sent.
During this time, you may press F1 to terminate data transmission.
! If you are having problems downloading the information, see Troubleshooting, which
begins on page 203.
Chapter 2: Jobs 11
Upload to Collector
DATA COLLECTION # JOBS # UPLOAD TO COLLECTOR
KEY-IN COMMAND: upload
ICON:
This command allows you to transfer coordinate or stakeout data from the computer to the
data collector.
You may upload an ASCII file that has been created through Data Collection, Data
Transfer or other applications, or you can upload Nodes straight from the project.
Refer to Collectors and Formats, which begins on page 129, for additional information on
specific collector formats and file transferring steps.
Figure 2-2 Upload to Collector Dialog Box
Upload to Collector Dialog Box Definitions

Upload Data Type the path and file name, or select the ASCII file to upload. This ASCII file
From File may contain information created from Data Collection, Data Transfer, Site
Design (sub-strata or depth stake information), or RoadCalc™ (cross-section
information) modules. You may also create the ASCII file using a spreadsheet,
word processor, or other application. The ASCII file may be delimited by
commas or spaces.
! Make sure the communication settings are set up correctly before
selecting a file to upload.
! Depending on the format selected, you may be prompted to enter
additional information.
12 Data Collection
Upload to Collector Dialog Box Definitions
Upload Data Select Nodes from the project to upload to the collector. Select the Nodes or
From Project points using the standard methods of selection.
File Name If you select File from the drop list, indicate the path and file in this edit field.
! If you choose the SMi - Coordinate format, the file must have an .ASC
extension.
! If you choose the TDS - Coordinate format, the file must have a .CR5
extension.
Job Name If you select Project from the drop list, type the job name to upload to the
Chapter 2: Jobs
collector.
! If you choose the SMi - Coordinate format, the file must have an .ASC
extension.
! If you choose the TDS - Coordinate format, the file must have a .CR5
extension.
Format Specify the collector format you will be using to upload data. Select a format
from the list of supported formats.
Version When one of the SMI formats is selected (SMi - Coordinate, SMi - SDMS, or
SMi - SDR2X), you may select whichever version of SMI you are using.
Serial Port Select the port where the data collector is connected. If you want to send the file
to disk, use the Export Nodes command.
Baud Rate Select the appropriate baud rate to match the data collector.
Data Bits Select the appropriate data bit size and parity setting for the data collector from
the list.
QuickSteps for Uploading ASCII File

To upload an ASCII file to a data collector, complete the following steps:
1. Open a project in Eagle Point and select Products ! Data Collection ! Jobs !
Upload to Collector.
2. Select the File option.
3. Type the path and file name of the ASCII file, or select the ASCII file to upload.
4. Select the data collector format from the drop list of supported formats.
5. Select the remaining communication settings.
% Verify that the computer and the data collector’s communications parameters are
set the same and that the cable is connected properly. Failure to do so may result in
the computer and/or data collector locking up.
6. Prepare the data collector to receive the data. See your data collector’s
Chapter 2: Jobs 13
7. Click on OK in the Upload to Collector dialog box.
You will be prompted to prepare the data collector if it is not already prepared to
receive data.
8. Press any key to send the data to the collector.
As with downloading, the data will either scroll across the computer screen or display
the number of packets and the percentage of time needed to transfer during the
upload.
! You may press F1 at any time to terminate the data transmission.
! If you are having problems uploading information, see Troubleshooting, which begins on
page 203.
QuickSteps for Uploading from Project

To upload directly from the project to a data collector, complete the following steps:
2. Select the Project option from the Upload Data From drop list.
4. Select the remaining communication settings and click on OK.
% Verify that the computer and the data collector’s communications parameters are
set the same and that the cable is connected properly. Failure to do so may result in
the computer and/or data collector locking up.
5. Prepare the data collector to receive the data. See your data collector’s
6. Select the Nodes to upload using the standard methods of selection.
7. When all of the Nodes are selected, accept the listing of the Nodes generated
and click on OK.
As with downloading, the data will either scroll across the computer screen or display
the number of packets and the percentage of time needed to transfer during the
upload.
! You may press F1 at any time to terminate the data transmission.
14 Data Collection
Import ASCII File
DATA COLLECTION # JOBS # IM PORT ASCIIFILE
KEY-IN COMMAND: dcimp
ICON:
This command allows you to import a file on disk containing survey information created
Chapter 2: Jobs
from a data collector or from an external software package and process it through Data
Collection.
You may select a file that is in any of the supported formats.
! Line work, Field Codes, and special designators may be used if the imported file contains
the correct information.
Figure 2-3 Import ASCII File Dialog Box
Import ASCII File Dialog Box Definitions

Job Name Enter a descriptive name for the job that is being imported. You are allowed up to
32 characters for the job name. The name of the job is used to keep track of the
file within Data Collection.
File Name Enter the path and file name or select an ASCII file to import.
Format Specify the format the selected ASCII file is in from the drop list of supported
formats.
Create Legal You may automatically create a backup of the file that is being imported. This file
Backup File is an exact duplicate of the imported file and is attributed read-only. Any
modification to this file will create a change in the date stamp of this file, so that it
will no longer match the time that it was created originally.
! You may compare this file with any modifications that you make to the
downloaded instrument file, and you may revert to the original at any time.
Chapter 2: Jobs 15
QuickSteps
To import an ASCII file, proceed through the following steps:
2. Select Jobs ! Import File.
3. Type the path and file name of the ASCII file, or select the ASCII file to import.
4. Type the name of the job to import.
5. Select the data format of the ASCII file from the drop list of supported formats
and click on OK.
6. Choose whether to create a legal backup of the file to be imported and click on
OK.
Export Nodes
DATA COLLECTION # JOBS # EXPORT NODES
KEY-IN COMMAND: dcexp
ICON:
This command allows you to transfer coordinate or stakeout data from an Eagle Point
project to a file.
You may export Nodes using the standard methods of selection directly to a file.
Figure 2-4 Export Nodes Dialog Box
Export Nodes Dialog Box Definitions

File Name Type the path and file name to export the information to. If a file already exists,
choose an ASCII file to export to by clicking on the Select File to Export to icon
and selecting the file to export to.
16 Data Collection
Export Nodes Dialog Box Definitions
Format Specify the format for the exported points from the drop list of supported
formats.
Job ID This is the ID number that is used for your job.
QuickSteps
To export Nodes from the project to a file, perform the following steps:
Chapter 2: Jobs
2. Select Jobs ! Export Nodes.
3. Type the path and file name, or click on the folder icon and select a file to export
the Nodes to.
5. If you select a Sokkia format, type the Job ID value and click on OK.
6. Select the Nodes to upload using the standard methods of selection.
7. When all of the Nodes are selected, accept the listing of the Nodes generated
and click on OK.
Edit Instrument File

DATA COLLECTION # JOBS # EDIT INSTRUM ENT FILE
KEY-IN COMMAND: editinst
ICON:
You may edit the original instrument file information that was downloaded or imported to
Data Collection. This file may then be reprocessed in the project with the edited
information.
You may select the editor of your choice to edit the instrument file.
Chapter 2: Jobs 17
! If you have edited the formatted file before editing the instrument file, changes to the
formatted file will be lost. The formatted file is recreated from the instrument file each time
the instrument file is edited.
Figure 2-5 Edit Instrument File Dialog Box
Edit Instrument File Dialog Box Definitions

Job Name Select the name of the job that you want to edit from the current list of jobs.
Name Select the name of the editor to use. You may select DOS Edit, Notepad,
WordPad or User Defined from the drop list.
File Name For each editor, type the path and file name, or select the editor by clicking on
the Select Editor icon. You may select any editor as the user-defined option.
For example, type C:\COMMS\COMMS or C:\PCTOOLS\VIEW or
C:\MSOFFICE\WINWORD\WINWORD.
! When saving a file from a user-defined editor, save as TEXT only.
QuickSteps
To edit a raw instrument file using a user-defined editor, perform the following steps:
2. Select Jobs ! Edit Instrument File.
3. Select the job you want to edit from the drop list of current jobs.
4. Select the Name of the editor you would like to use.
5. If the path and file name of the editor do not display, select or type the path and
file name of the editor to use.
6. Click on the Edit button to launch the editor and edit the file.
18 Data Collection
Edit Formatted File
DATA COLLECTION # JOBS # EDIT FORM ATTED FILE
KEY-IN COMMAND: editformat
ICON:
You may edit the processed formatted file information that was downloaded or imported to
Chapter 2: Jobs
Data Collection. This may include changing coordinates, assumed directions, adding
descriptors, or fixing blunders. The changes may be saved and reprocessed in the project
with the edited information.
Figure 2-6 Edit Formatted File Dialog Box
Edit Formatted File Dialog Box Definition

Option Function
Job Name You may select the name of the job that you want to edit from the current list of jobs.
QuickSteps
To edit a formatted file using the SDMS Editor, perform the following steps:
2. Select Jobs ! Edit Formatted File.
3. Select the job you want to edit from the drop list of current jobs.
4. Click on the Edit button to launch the editor and edit the file.
Chapter 2: Jobs 19
Reduce Job
DATA COLLECTION #JOBS # REDUCE
KEY-IN COMMAND: reduce
ICON:
You may reduce survey information contained in a job file and place it in the current
project. The term ‘reduce’ derives from taking raw measurements and converting, or
reducing, the information to coordinates that can be placed readily in the CAD graphic.
While reducing a job, Data Collection uses the Field Codes and line names contained in
the descriptor fields of the file. Blocks (AutoCAD/BricsCad) or Cells (MicroStation) are
created in your drawing that correspond to the symbols you defined in the Node (Field
Code) Library.
You may preview the job or jobs before processing the data into the project. This will
automatically show basic points and line work generated using hard-coded defaults so
that you can see if the survey information is processing correctly. You may also edit the
file, make changes, and re-preview the file to verify the changes made. Settings can be
changed and the results of the reduction may be viewed and printed from this dialog box.
You may click on OK to process the job into the project. Data Collection may issue an
“Auto Zoom” in the CAD graphic at the end of the reduction of the job file. This setting is
the Auto Zoom toggle on the Reduction Settings dialog box – Graphics tab (Figure 3-3 on
page 37). If the toggle is set to on, the CAD graphic will automatically size to encompass
all of the information in the file. If the toggle is set to off, the current view in the CAD
graphic will remain at the same view size.
You may also reduce a file in successive iterations. The results are dependent on how the
Erase on Re-Reduce toggle is set on the Reduction Settings dialog box – Graphics tab.
When the toggle is set to on, the system removes all of the objects that are in the project
belonging to that particular job and replaces them in the project with the reprocessed
information. When the toggle is set to off, the system places the information more than
once. Since the points may be listed within the file, you can compare the results of each
point as necessary.
20 Data Collection
! If the Erase on Re-Reduce toggle is set to off and you reduce a file two times, the drawing
will contain the information twice. However, if you then set the Erase on Re-Reduce toggle
to on and reduce the file, the system overwrites the old information with the new
information.
Chapter 2: Jobs
Figure 2-7 Reduce Job Dialog Box
Reduce Job Dialog Box Definitions

Select Job(s) Select the jobs you want to reduce into the project. You may do a multi-select
on the jobs that you want to reduce by clicking on the uppermost file and
keeping the SHIFT key depressed, click on the lowermost job to reduce. To
remove a job from the multi-select, depress the CTRL key and click on the jobs
that you want to remove. Any jobs that are highlighted will be processed in the
order that they occur in the list view.
To change the order in which the job files are processed, first use the arrow
icons to move single jobs up and down the list. Highlight the job that you want
to move and click on the up or down arrow to move the job up or down the list
of jobs one position.
To clear the highlighted items in the list view, use the mouse to click off to the
side within the list view.
! Only the highlighted jobs will process.
Job Name This displays the names of the jobs that are in this project.
Format This displays the format of each job in the project.
Reduced This displays whether the file has been reduced.
Move Job Up Highlight a job and click on this icon to move it up the Select Job(s) list.
Arrow
Move Job Down Highlight a job and click on this icon to move it down the Select Job(s) list.
Arrow
Chapter 2: Jobs 21
Reduce Job Dialog Box Definitions
Settings You may establish control over how the jobs are processed into the project.
Toggle options allow you to accomplish a variety of tasks. Establish collector
specific settings, set up a custom translator, graphics settings, line work
settings, and shot averaging placement priority defaults.
For more information, see Reduction Settings on page 34.
Warnings You may view any processing errors that occur when a job is reduced. This
may include messages about missing Field Codes, incomplete line work,
unsupported data tags or functions, etc. You can print this report to a file or to
the system printer.
For more information, see Query Warnings on page 84.
Preview You may view the file in the preview screen before placing the data in the
project. This will show the basic points and line work generated so that you can
see if the information is processing correctly.
See Preview Objects below and Display Settings on page 24 for more
information.
Shot Averaging You may view the shot averaging results for the job reduced. The shot
averaging options allow you to establish the priority of multiple occurrences of
the same Node ID within a job based on how the data was recorded and in
what order the data occurs within the job file. You can print this report to a file or
to the system printer.
For more information, see Query Shot Averaging on page 85.
Preview Objects
DATA COLLECTION # JOBS # REDUCE # PREVIEW
When you click on the Preview button on the Reduce Job dialog box, the Preview Objects
dialog box (Figure 2-8 on page 23) displays. The Preview Objects command allows you to
display objects in an Open GL preview window instead of placing the objects in the CAD
graphic. The Open GL preview command allows you to zoom, pan and rotate the display.
You can dynamically zoom, zoom window, zoom extents and zoom previous. You can also
dynamically pan in the preview. The display can be rotated using the defined views of Top,
Front and Isometric or by defining the X-Axis Angle and the XY Plane Angle.
The view perspective in the preview window is stored in memory when the Preview
Objects dialog box is closed. When the Preview Objects command is opened subsequent
times within the same session of Eagle Point, the view perspective is restored. The
surface model is also stored in memory. When the command is opened subsequent times,
the surface model is also restored. The surface model is not restored in all commands.
Commands that display a specific surface model (such as the Preview Intersection
command in the Intersection Design product) do not restore the surface model. When
22 Data Collection
the Preview Objects command is opened after Eagle Point has been closed, the Preview
Objects dialog box defaults to the top view and the first surface model in the drop list.
Chapter 2: Jobs
Figure 2-8 Preview Objects Dialog Box
Preview Objects Dialog Box Definitions

Zoom Dynamic This icon allows you to zoom in the preview window dynamically. To zoom
in the preview window, click on the Zoom Dynamic icon. Click and hold the
primary button on your pointing device in the preview window and move
your cursor up to increase the size of the images in the preview window.
Move your cursor down to decrease the size of the images in the preview
window. To stop zooming, release the primary button on your pointing
device.
Zoom Window This icon allows you to zoom into an area in the preview window. To zoom
into an area in the preview window, click on the Zoom Window icon. Select
the first corner of the zoom window in the preview window and then the
opposite corner of the zoom window.
Zoom Extents This icon allows you to center all of the objects in the preview window. This
will zoom to the extents of all of the objects that are turned on for display.
For more information on the objects turned on for display, see Display
Settings on page 24.
Zoom Previous This icon allows you to restore the objects in the preview window to their
previous state.
Chapter 2: Jobs 23
Preview Objects Dialog Box Definitions
Pan Dynamic This icon allows you to pan in the preview window dynamically. To pan in
the preview window, click on the Pan Dynamic icon. Click and hold the
primary button on your pointing device in the preview window and move
your cursor in the direction you want the images in the preview to move. To
stop panning, release the primary button on your pointing device.
Restore Top View This icon will set the view for the preview window to the top view. This sets
the X-Axis Angle to 270 degrees and the XY Plane Angle to 90 degrees.
Restore Front View This icon will set the view for the preview window to the front view. This sets
the X-Axis Angle to 270 degrees and the XY Plane Angle to 0 degrees.
Restore Iso View This icon will set the view for the preview window to an isometric view. This
sets the X-Axis Angle to 315 degrees and the XY Plane Angle to 45
degrees.
X-Axis Angle This is the angle from the X-Axis. The valid entries are from 0 degrees to
360 degrees. You can enter a desired value, or use the scroll arrows to set
the angle. A single click on the scroll arrows will adjust the angle by 1-
degree increments. If you click and hold the cursor down on the scroll
arrows, the angle will be adjusted by 5-degree increments.
XY Plane Angle This is the angle from the XY plane. The valid entries are from -90 degrees
to 90 degrees. You can enter a desired value, or use the scroll arrows to set
the angle. A single click on the scroll arrows will adjust the angle by 1-
degree increments. If you click and hold the cursor down on the scroll
arrows, the angle will be adjusted by 5-degree increments.
Display Settings These allow you to specify which objects are on, the zoom ratio, pan factor
and display type for the objects. The display types that can be chosen are
wireframe, constant shading and hidden surface removal.
For more information on the display settings, see Display Settings below.
Display Settings
DATA COLLECTION # JOBS # REDUCE # PREVIEW # DISPLAY S ETTING S
The Preview Object Display Settings command allows you to specify which objects are
previewed. The list control displays all of the objects that can be previewed. Highlight the
desired object and click on the On or Off button to change whether the object is
previewed. You can also double-click on an item in the list control to change whether the
object is previewed. The zoom ratio, pan factor and display type for the objects can be
24 Data Collection
controlled by clicking on the View Tab. The display types that can be chosen are
wireframe, constant shading, and hidden surface removal.
Chapter 2: Jobs
Figure 2-9 Display Settings Dialog Box
Display Settings Dialog Box Definitions

Option Function
Display Column This displays whether the object listed in the item column will be displayed. If the column
is set to On, then the object will be displayed in the preview window. If the column is set to
Off, the object will not be displayed in the preview window. To change the display state,
highlight the desired object and click on the On or Off button. You can also change the
display state by double-clicking on an item in the list control.
Item Column This displays the objects that can be previewed. All of the objects that are listed can be
previewed. If the display column is set to On, then the object will be displayed in the
preview window of the Preview Objects dialog box. If the display column is set to Off, the
object will not be displayed in the preview window. To change the display state, highlight
the desired object and click on the On or Off button. You can also change the display state
by double-clicking on an item in the list control.
On This allows you to turn the display of an object on so it is shown in the preview window of
the Preview Objects dialog box. To turn an object on to be displayed in the preview
window, highlight the desired object and click on the On button.
Off This allows you to turn the display of an object off so it is not shown in the preview window
of the Preview Objects dialog box. To turn an object off so it is not displayed in the preview
window, highlight the desired object and click on the Off button.
Zoom Ratio The Zoom Ratio controls how much larger or smaller the object displays in the preview
window when you use the Zoom In or Zoom Out commands. A Zoom ratio of 2 increases
the size of the objects by two times in the preview window in the Preview Objects dialog
box when using the Zoom In command and decreases the size of the objects by two times
when using the Zoom Out command.
Pan Factor This controls how much the objects are displaced when using the horizontal and vertical
scroll bars.
Chapter 2: Jobs 25
Display Settings Dialog Box Definitions
Option Function
View Type This allows you to control how solid objects are displayed in the preview. The available
options are Wireframe, Constant Shading and Hidden surface removal.
" Wireframe: When this option is selected, all elements are displayed. The
elements are transparent, so hidden lines are not removed.
" Constant Shading: When this option is selected, all elements are shaded
according to their color. Any objects that are behind a solid object are not
displayed.
" Hidden surface removal: When this option is selected, only the parts of the
objects that are visible are displayed. Lines that are hidden behind other objects
are removed or not displayed.
SDMS Set-up Data

If you reduce a job that does not have enough information to process the initial or
intermediate setup locations, the SDMS Set-up Data dialog box (Figure 2-10 below)
displays.
See EP SDMS, which begins on page 209.
! This dialog box will also display if the coordinate values for the setup points are being read
from the project. Accept the coordinate values for both the occupied station and the
backsight if applicable.
Figure 2-10 SDMS Set-up Data Dialog Box
26 Data Collection
SDMS Set-up Data Dialog Box Definitions
PIC Click on the PIC icon to graphically select a Node, snap to a point, or pick a
coordinate from the CAD graphic.
Node ID Type the occupied station/ backsight Node ID used to record a measurement
for the point number specified at the top of the dialog box. Put a check in the
box next to the value to use it during reduce.
Northing Type the Northing coordinate value for the occupied station/ backsight. Put a
check in the box next to the value to use it during reduce.
Easting Type the Easting coordinate value for the occupied station/ backsight. Put a
Chapter 2: Jobs
Elevation Type the elevation value for the occupied station/ backsight. Put a check in the
Instrument Type the instrument height for the occupied point. Put a check in the box next to
Height the value to use it during reduce.
Instrument Type the instrument elevation for the occupied station. Put a check in the box
Elevation next to the value to use it during reduce.
! This value is the resultant of the elevation and the instrument height.
Modifying this value will adjust the elevation for the occupied point.
Station Type the station value of the occupied station. Put a check in the box next to the
value to use it during reduce.
Description Type the description for the occupied station. Put a check in the box next to the
Options Select the type of direction to use for entering the backsight. You may select
one of the 6 supported bearing and azimuth types from the drop list of formats.
Direction Type the direction of the backsight based on the direction type selected (either
Absolute or Geometric).
See Concepts in the COGO manual.
Vertical Angle Type the vertical angle that was recorded from the occupied station to the
backsight. Put a check in the box next to the value to use it during reduce.
Add data to file Toggle this check box on if you want to write the results from the SDMS Setup
dialog box to the formatted file.
Chapter 2: Jobs 27
Manage Jobs
DATA COLLECTION # JOBS # M ANAG E
KEY-IN COMMAND: dcman
ICON:
Each job that has been created, either through the Download from Collector or Import
ASCII File command, will be listed by job name and format in this dialog box. You may
modify, delete and print each selected job file. The status of each job associated with the
project can be determined by highlighting the job in question. The status will report if the
job has been reduced into the project, if the instrument or formatted file has been edited,
or if a legal backup exists in the project folder.
Other tools allow you to show only the objects in the CAD graphic that are contained in the
highlighted job file, or you may want to create a selection set of all of the objects in the
CAD graphic linked to the job file.
Figure 2-11 Manage Jobs Dialog Box
Manage Jobs Dialog Box Definitions

Job Name Lists the names of the jobs in the project.
Format Lists the format of each job.
28 Data Collection
Manage Jobs Dialog Box Definitions
Job Status You may determine the status of a job file by highlighting the job in the list view.
The status will update with the current status of the job.
Job Reduced: This will show whether the job file has been reduced into the
project.
Instrument File Edited: This will show whether a change has been made and
saved to the raw instrument file.
Formatted File Edited: This will show whether a change has been made and
saved to the formatted file.
Chapter 2: Jobs
Legal Backup Created: This will show whether a legal backup of the original
instrument file exists. This would have been created when the job was
downloaded or imported.
Modify Job You may modify the description of the selected job, change the format that is
used to read the job, revert to the backup file if the instrument file has been
edited, or revert to either the instrument file or the backup file if the formatted file
has been edited.
For more information, see Modify Job on page 30.
Delete Job You may delete unnecessary jobs from the project. Highlight the job to be
deleted and click on the Delete Job icon.
Print Job Use this option to print the highlighted job to a file or to the system printer. You
may print the instrument file, formatted file, a coordinate list of the file and the
legal backup file. Highlight the job you want to print and click on the Print Job
icon. Select the type of file you want to print and click on OK.
Show Only You may show only the objects within the CAD graphic that are linked to the
selected job. Highlight the job that you want to show and click on the Show Only
button. All other data in the CAD graphic will be hidden until a regenerate or
refresh is executed.
Select Objects You may automatically select all objects in the CAD graphic that are linked to the
selected job. These objects may then be used as part of a CAD selection set.
AutoCAD/BricsCad will establish a selection set so that the previous option can
be used to use the previous selection set for the current AutoCAD/BricsCad
command. MicroStation will select the elements for use by the next command
issued.
! If you have added points, lines, annotation, etc., the system will not select
the objects because they were not originally part of the file. Therefore, you
can use this command to isolate points collected on a specific day.
Chapter 2: Jobs 29
Modify Job
DATA COLLECTION # JOBS # M ANAG E # M ODIFY JOB
ICON:
You may modify the description of the selected job and, in some cases, change the format
of the job from one format to another. In addition, you can revert to a prior level of editing
and backup by reverting to the existing instrument file, or even further to the legal backup.
! Modifying the format may change the way Data Collection reads and reduces the
selected job file. Only certain formats are supported to actually change the file format of
the job.
Figure 2-12 Modify Job Dialog Box
Modify Job Dialog Box Definitions

Option Function
Job Name You may change the job name of the file by typing the new name in the edit field.
Format You may specify the collector format you want to change the job to. Select a format from
the list of supported formats.
Revert to You may revert the formatted file back to match the Instrument file. When you elect to set
Instrument File the formatted file to the instrument file, Data Collection displays an alert box warning you
that all changes made to the formatted file will be lost. If you want to set the formatted file
to the instrument file, click on the Revert to Instrument File button; otherwise, click on
Cancel to preserve the formatted file and cancel the command.
Revert to Legal You may revert the formatted file or instrument file back to match the legal backup file.
Backup
When you elect to set the formatted or instrument file to the legal backup file, Data
Collection displays an alert box warning you that all changes made to the formatted or
instrument file will be lost. If you want to set the formatted or instrument file to the Backup
file, turn on the Revert to Legal Backup toggle; otherwise, click on Cancel to preserve the
formatted or instrument file and cancel the command.
30 Data Collection
QuickSteps
The following steps show how to modify a job format.
To change the format associated with an existing job, complete the following steps:
1. Select Jobs ! Manage.
The Manage Jobs dialog box (Figure 2-11 on page 28) displays.
2. In the Manage Jobs dialog box, highlight the job you want to change.
3. Click on the Modify Job icon.
The system displays the Modify Job dialog box (Figure 2-12 on page 30).
Chapter 2: Jobs
4. Click on the on the Format field to display the supported list of formats.
5. Click on the desired format.
6. Click on OK.
After completing these steps, the Modify Job dialog box closes. The new format
displays in the list of jobs.
The following steps show how to revert to the Legal Backup.
To revert to the Legal Backup file, complete the following steps:
1. Select Jobs ! Manage.
The Manage Jobs dialog box (Figure 2-11 on page 28) displays.
2. In the Manage Jobs dialog box, highlight the job you want revert to the legal
backup.
3. Click on the Modify Job icon.
The system displays the Modify Job dialog box (Figure 2-12 on page 30).
4. Toggle on the Revert to Legal Backup option.
5. Click on OK.
6. When the system displays a dialog box warning you about your changes, turn
on the Revert to Backup File toggle to continue the process; otherwise, click on
Cancel to cancel the process and retain the current file. The system overwrites
the highlighted file with information contained in the Legal Backup file.
Chapter 2: Jobs 31
Print Job
DATA COLLECTION # JOBS # M ANAG E # PRINT JOB
ICON:
You may print the selected job files to a file or the system printer.
Figure 2-13 Print Job Dialog Box
Print Job Dialog Box Definitions

Option Function
Print Instrument This prints the instrument file.
File
Print Formatted This prints the formatted file.
File
Print Reduced This prints the reduced data.
File
Print Backup This prints the backup file.
File
32 Data Collection
OPTIONS
The Options in Data Collection allow you to establish
graphics, line work and shot averaging settings to control
CHAPTER
what data is placed in the project. You may customize the
designators to match your field procedure and create line
work that is standardized for you and your clients to
minimize drafting time. You may also enter cross-section
patterns and 3-D line templates to help minimize time in
the field collecting data.
In this chapter:
Reduction Settings . . . . . . . . . . . . . . . . . . . . . . . . 34
Designators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Line Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3
Cross-Section Patterns . . . . . . . . . . . . . . . . . . . . . 72
3-D Line Templates . . . . . . . . . . . . . . . . . . . . . . . . 76
Chapter 3: Options 33
Reduction Settings
DATA COLLECTION # OPTIONS # REDUCTION SETTING S
or
DATA COLLECTION # JOBS # REDUCE # SETTING S
KEY-IN COMMAND: dcset
ICON:
You may establish control over how the file is processed into the project. Establish what
types of information get written to the CAD graphic, such as Nodes and line work. There
are also settings to erase every associated object in the CAD graphic when re-reducing a
job, as well as an Auto-Zoom feature to see everything that has been processed.
You may specify the default Field Code to use when reducing the selected jobs. If there
are any Node ID occurrences that are the same in the project and the job, you may
overwrite, ignore, renumber, or not place duplicates as the jobs are processed.
For placing line work in the CAD graphic, there are several options. You may select the
line library to be used in the process. You may also choose to place the lines and curves in
3-D (MicroStation), place lines using the 3-D templates, use the entered Field Code to
process as a line name or place line work that was shot using a cross-section line pattern.
Finally, the shot averaging may be enabled for duplicate occurrences of the same Node ID
within the job file. Certain collectors and formats allow for the storage of repeated turns to
the same Node using forward or reverse (or face 1/ face 2) observations. If the collector
does not mean (average) these points out for you, Data Collection can average these
occurrences through shot averaging based on the type of shot or record used to store the
points. The higher priority occurrences are reported and meaned if necessary, whereby
the lower priority occurrences are just reported in the Reduction Settings dialog box – Shot
Averaging Tab (Figure 3-5 on page 41). You may define the priority of each type of record
34 Data Collection
or shot in the shot averaging options. You may also prioritize multiple occurrences of the
same occupied station to be the first, last or averaged coordinate values.
Figure 3-1 Reduction Settings Dialog Box
Reduction Settings Dialog Box Tab Definitions
Chapter 3: Options
Option Function
Collector tab This tab allows you to select the default data collector format, customize GEODAT labels
or Leica codes, or establish a custom translator to transfer information within Data
Collection.
For more information, see Reduction Settings – Collector Tab on page 36.
Graphics tab This allows you to set the toggles for drawing lines, placing Nodes, auto-zoom and erase
on re-reduce. You may also select the default Field Code to place when the Field Code
value specified in the file does not exist in the Node (Field Code) Library.
For more information, see Reduction Settings – Graphics Tab on page 37.
Line Work tab This allows you to set the toggles for using the specified line library, drawing 3-D lines,
using 3-D line templates, using the Field Code as the line name, cross-section patterning
and custom lines.
For more information, see Reduction Settings – Line Work Tab on page 39.
Shot Averaging This allows you to set the priority for Node placement when there are duplicate records to
tab the same Node ID in the job. You can set the priority of placement of keyed-in
coordinates, raw measurements, directional or azimuth information and calculated
coordinates from the data collector. You may also determine what record to use for the
setup information when the same occupied station is occupied more than once in the job.
For more information, see Reduction Settings – Shot Averaging Tab on page 41.
Reduction Settings – Collector Tab
DATA COLLECTION # OPTIONS # REDUCTION S ETTING S # COLLECTOR TAB
or
DATA COLLECTION # JOBS # REDUCE # S ETTING S # COLLECTOR TAB
Figure 3-2 Reduction Settings Dialog Box – Collector Tab
Reduction Settings Dialog Box – Collector Tab Definitions

Default Format This is a drop list of all of the supported formats. You may select one of the
formats and it will be the default format for downloading and importing new
data.
Customize If you are using a Geodimeter or a Leica instrument with a GEODAT or Leica
data collector, you may customize the settings in Data Collection to closely
match your current surveying procedures. Select a GEODAT or Leica format
and click on the Customize button.
See Geodat Labels, which begins on page 117 or Leica Codes, which begins on
page 123.
36 Data Collection
Reduction Settings Dialog Box – Collector Tab Definitions
Custom If you want to run a different application to perform the communications with
Translator your data collector, click the check box on and type the path and file name of
the application, or click on the Select A Custom Translator icon and select the
program. This program will be utilized when the Download from Collector or the
Upload to Collector commands are selected.
After the file is downloaded using the custom application, the Import File dialog
box will display for you to select the downloaded file. When you upload a file,
the custom translator you select will be launched to upload the data to the
collector.
Reduction Settings – Graphics Tab

DATA COLLECTION # OPTIONS # REDUCTION SETTING S # G RAPHICS TAB
or
DATA COLLECTION # JOBS # REDUCE #SETTING S # G RAPHICS TAB
Figure 3-3 Reduction Settings Dialog Box – Graphics Tab Chapter 3: Options
Reduction Settings Dialog Box – Graphics Tab Definitions
Option Function
Draw Line Work Determines whether or not lines are drawn in the CAD graphic.
On: Data Collection processes the line information using the current Line Work Library.
Off: Data Collection does not place lines in the CAD graphic.
Reduction Settings Dialog Box – Graphics Tab Definitions
Option Function
Erase on Re- Determines whether the objects in the CAD graphic that are linked to the selected job are
Reduce first removed on a reduce or whether the data is placed more than once.
On: Data Collection removes all of the information in the project that is linked to the
selected job and replaces the information with the modified job information.
Off: Data Collection appends the information to the CAD graphic when the file is re-
reduced.
! If this field is set to off and you reduce the job a second time, the project will actually
consist of the original data and the new data. However, if you then set this field to on
and reduce the job, Data Collection replaces the original data set with the new
information.
Auto Zoom Determines how the CAD graphic displays after it is reduced.
On: After the file is reduced, the system automatically zooms to the extents of the selected
jobs.
Off: After the file is reduced, the system does not change the current view.
Place Nodes Determines if Nodes are placed when a file is reduced.
On: Data Collection places the Nodes at the proper location when the file is reduced.
Off: Data Collection does not place Nodes when the file is reduced. However, the system
does calculate the coordinates for line work.
Default Field If you are placing Nodes, you may select a Field Code from the Node (Field Code) Library
Code to be used when a Field Code that is entered in the job file is not defined in the Node
(Field Code) Library, or if a job file record does not have a description. Select a Field Code
from the drop list of Field Codes.
! Set the Default Field Code to be one that is used the most in the job. For example, a
topography job with mostly ground shots may have a “plus” or an “X” placed most of
the time, whereby a survey with many breaklines may be set to a Field Code that
only places a point object so that a symbol is not brought in on every shot taken.
38 Data Collection
Reduction Settings – Line Work Tab
DATA COLLECTION # OPTIONS # REDUCTION SETTING S # LINE W ORK TAB
or
DATA COLLECTION # JOBS # REDUCE # S ETTING S # LINE W ORK TAB
Chapter 3: Options
Figure 3-4 Reduction Settings Dialog Box – Line Work Tab
Reduction Settings Dialog Box – Line Work Tab Definitions

Option Function
Use Line Library Determines what properties are used when placing lines.
On: You may select the line library to use for the reducing of the selected job files. Select
a library from the drop list of line libraries. Data Collection uses the properties defined on
the Line Work dialog box (Figure 3-23 on page 59) for each entered line name in the job.
Off: The CAD properties of the line work are determined by the current CAD settings.
Add Undefined This option will be disabled if the Use Line Library option is toggled off. This option allows
Lines to Line you to select whether or not to add line names to the Line Library automatically. When this
Library option is toggled off, the line names that are part of the Data Collection file but are not in
the current line library will not be added to line library. When this option is toggled on, the
line names that are part of the Data Collection file but not in the current line library will be
added to the line library with default values. You can then modify these default values to
your desired values.
For more information about modifying a line name in your line library, see Line Work on
page 58.
Option Function
Draw 3-D Lines Each line segment that is processed will pass through the point that it is placed at the
correct elevation.
On: Data Collection will create 3-D line and arc segments (MicroStation only) that pass
through the respective point shot in the field.
Off: All line work is placed at the elevation specified in the Line Work dialog box (Figure 3-
23 on page 59) for 2-D lines. The default elevation is zero (0).
! If the line work generated is to be used as breaklines to create a surface model, all of
the lines are automatically considered breaklines, even though they are at an
elevation that is not consistent with the shots recorded. Refer to Surface Modeling
for a more informative description of breaklines.
Use 3-D Line You may process any 3-D line templates that are associated with any lines in the job file.
Template The template may represent existing curb and gutter, road or other features and
structures automatically.
On: Data Collection will read each line name that is associated with a 3-D line template
and place the template lines at the correct elevations and offsets from the original
template line.
Off: All lines that would be created from templates will not be placed in the CAD graphic.
Use Field Code You may use the line name entered in the field to be processed as the Field Code as well.
as Line Name Data Collection will check both the current line library and current Node (Field Code)
Library to place the correct line and Node information.
On: Data Collection will read each Field Code as a line name for every Field Code that is
set in the Node (Field Code) Library to be placed as a line. This will allow you to enter only
the Field Code if the Field Code and the line name are the same.
Off: Field Codes are processed only as Field Codes.
% Do not toggle on both the Use Field Code as Line Name and Use Line Name as
Counter options at the same time.
Use Line Name This option allows you to specify only one line name in your line work library and have
as Counter numbered instances of the same line name placed. The Field Code that is entered will be
used as the line name in the line work library. The number that follows the draw designator
will be the counter for the line name. All counters that are the same will be connected until
a stop designator is entered. The counter allows you to increment the line name without
having the additional line names in the line work library. For example, if EP is the line
name in the line work library, you may have a series of shots coded as EP.1 and EP.2 that
are two distinct lines, but they would be placed according to the settings specified for the
EP line name.
Use Cross- You may use the cross-section line patterning when placing lines in the CAD graphic.
Section
On: Data Collection uses the cross-section line names when processing line work.
Patterning
Off: All lines that are processed with a cross-section designator will be processed as a
single line.
40 Data Collection
Option Function
Use Pattern You may choose to use custom lines defined for each line or place lines using the proper
Lines linetype or line style.
On: If the line properties include a custom line pattern created from the Pattern Line
Library, Data Collection uses the appropriate custom line pattern defined for each line
name in line work.
Off: Data Collection will only use the defined linetype or line style to place line work in the
CAD graphic.
Reduction Settings – Shot Averaging Tab

DATA COLLECTION # OPTIONS # REDUCTION SETTING S # SHOT A VERAG ING TAB
or
DATA COLLECTION # JOBS # REDUCE # SETTING S # S HOT A VERAG ING TAB
Chapter 3: Options
Figure 3-5 Reduction Settings Dialog Box – Shot Averaging Tab
Reduction Settings Dialog Box – Shot Averaging Tab Definitions
Option Function
Use Shot You may process the job file using the shot averaging options. These allow you to
Averaging establish the priority of multiple occurrences of the same Node ID within the job file based
on how the data was recorded to the file and in what order the data occurs within the job
file.
On: The coordinate values for multiple occurrences of the same Node ID are averaged
according to the shot averaging options.
Off: The first coordinate value for a point is used when placing a Node.
! Only points of the same measurement type will be averaged.
Placement You may establish the order of priority of the type of data that occurs in the job file. If two
Priority or more points exist in the file that were created by two or more different measurement
types, then the highest priority occurrences will be averaged to calculate the location of
the Node ID.
The default setting is:
" Input Coordinates
" Raw Measured Data
" Collector Reduced Data
" Collector Computed Coordinates
The four different types of records are in order of priority. That is, if the instrument data file
contains both inputted and raw measured data for a Node with the same ID value, the
reduced coordinates being used will be the inputted coordinate values because they are
of a higher priority (default = priority 1).
If the coordinates of a reduced point have been averaged, this will be reported in the view
process file. The averaged coordinate values as well as the standard deviations for the
averaged point will be reported.
If the raw instrument data file contains different measurement types for the same point,
this will be reported in the view process file. Shots of lower priority will also have the point
coordinates reported to allow for error checking.
Input You may set the priority of any coordinates that were keyed into the collector. These
Coordinates coordinates are usually identified by the data tags YC: (Northing), XC: (Easting), and ZC:
(elevation) when viewed in the formatted file. Set the priority from the drop list.
Raw Measured You may set the priority of any raw field measurement recorded in the field from an
Data occupied station. These measurements are usually identified by the data tags HZ:
(Horizontal circle reading), VT: (Vertical angle), and DS: (Slope distance) when viewed in
the formatted file. Set the priority from the drop list.
Collector You may set the priority of any raw data that has been averaged and reduced by the
Reduced Data collector. These records are usually identified by the data tags AZ: (computed azimuth) or
HH: (computed horizontal circle reading), HD: (Horizontal distance), and VD: (Vertical
distance) when viewing the formatted file. Set the priority from the drop list.
Collector You may set the priority of any coordinates that were computed by the collector. These
Computed coordinates are usually identified by the data tags YY: (Northing), XX: (Easting), and ZZ:
Coordinates (elevation) when viewed in the formatted file. Set the priority from the drop list.
42 Data Collection
Reduction Settings Dialog Box – Shot Averaging Tab Definitions
Option Function
Occupied You may select the occupied stations to use in the event of a duplicate Node ID
Station Priority occurrence from another setup location. Each occupied station can be averaged using the
prioritization stated above, but each time the same point number occurs, it is factored into
the averaging.
To prevent the occupied stations from being over averaged from other shots in the file, the
first occurrence or the last occurrence may be held without being averaged. The default
setting is Average.
Examples
Sample report 1:
----------------
Point # 3 has been averaged from 2 raw measured point occurrences.
Average Point Values: X = 274.0823 Y = 198.4019 Z = 102.4804
Standard Deviations: X = 0.0546 Y = 0.0951 Z = 0.0411
Occurrences of point # 3:
Raw Measured Point: X = 274.1210 Y = 198.3347 Z = 102.5095 (From 2)
Raw Measured Point: X = 274.0437 Y = 198.4692 Z = 102.4514 (From 2)
Chapter 3: Options
In this case, two raw measured observations of point #3 exist. The two raw measured
points will be averaged, and the average point values will be used.
Sample report 2:
----------------
Point # 3 has been averaged from 2 keyed-in point occurrences.
Average Point Values: X= 9761.0640 Y= 3250.2000 Z= 4.0000
Standard Deviations: X= 0.0000 Y= 0.1414 Z= 0.0000
Keyed-In Point: X= 9761.0640 Y= 3250.3000 Z= 4.0000
Collector Computed Point: X= 9761.0640 Y= 3250.5440 Z= 0.0000(Occupied)
Collector Computed Point: X= 9761.0640 Y= 3250.1000 Z= 0.0000(Occupied)
Raw Measured Point: X= 9760.8978 Y= 3252.9793 Z= 4.3119(From 12)
In this case, several occurrences of point #3 with different measurement types exist. The
points with the measurement type of highest priority will be averaged and used. In this
example, all the keyed-in point values will be averaged.
Sample report 3:
----------------
Raw Measured Point: X= 274.1210 Y= 198.3347 Z= 102.5095(From 2)
Collector Reduced Point: X= 274.8046 Y= 198.6972 Z= 102.4514(From 2)
Collector Computed Point: X= 274.1000 Y= 198.4000 Z= 102.4000
In this case, several occurrences of point #3 with different measurement types exist. Since
there are no multiple occurrences with the same measurement type, no points will be
averaged. The point with the measurement type of highest priority will be used. In this
example, the keyed-in point values will be used.
Designators
DATA COLLECTION # OPTIONS # DESIG NATORS
KEY-IN COMMAND: desig

You may enter the designators for recording line work in the field. Set the user-defined
codes for lines, curves, close line, join last shot, bearing close, cross-section, stop line,
insert description and command aliases including rectangle, circles and feature lines.
Each designator can be up to ten alphanumeric characters; however, you may not enter
any spaces.
! If you are using either a Leica or Geodimeter instrument, see Geodat Labels, which
begins on page 117 or Leica Codes, which begins on page 123, for additional information
on collecting line work.
44 Data Collection
! When setting up the line, curve, close line, join last, bearing close, cross-section and stop
line designators, you cannot use the same characters as part of any symbol name or any
other designator name. For example, close line designator cannot be “CL” while the line
designator is “L.”
Chapter 3: Options
Figure 3-6 Designators Dialog Box
Designators Dialog Box Definitions

Option Function
Line This is the draw line designator. This designator must occur immediately before the line
name. This signifies that a line is to be drawn at this shot. For example:
MH.EL SEWER
This entry places Field Code MH and connects any line name EL with a line(.), and
overrides the default description for symbol MH with SEWER.
! If the same line name occurs later in the file, that shot connects automatically with
the last prior occurrence of the line name. If this is not desired, use a stop line
designator at the end of the entered line name to terminate the line.
Curve This is the curve designator. You may place this immediately following the line name of a
shot that is on a curve. This signifies that a curve is to be placed through this shot. For
example:
MH.EL-
This entry places Field Code MH and connects any line name EL with a curve(-), and uses
the default description for Field Code MH.
Option Function
Close Line This is the close line designator. You may place this immediately following the line name
of the last shot on a line that is to draw a line back to the first shot on the line. This
signifies that the first shot of the same line name is connected from this shot. For example:
MH.BOX+
This entry places Field Code MH, using the default description. The close line designator
(+) closes this line to the first shot taken on line BOX.
Join Last Shot This is the join last shot designator. You may place this immediately following the line
name of a shot that was taken after a shot that did not have the line name entered. This
signifies that the previous shot taken needs to be connected with this shot. For example:
IP.PROP*
This entry connects the last shot taken to the line entered on the current shot. Assume the
prior shot was “IP.” The prior shot entry places symbol IP using the default description.
The join last shot designator connects the prior shot as if it was coded “IP.PROP.”
Bearing Close This is the bearing close designator. You may place this immediately following the line
name of a shot that you want to close the object using the directions of the first and last
courses of the line name. This signifies that the first shot on this line is connected with this
shot, but only first by projecting the first course (bearing) from this shot, and this course
(bearing) from the first shot to find a common point in between. For example:
MH.BOX#
This entry places Field Code MH, using the default description. The bearing close
designator (#) closes the line by extending the start and endpoint of the line using the
bearings or directions of the first and last courses of the line. Refer to Figure 3-15 on page
53 for a diagram representing the use of this designator.
Cross-Section This is the cross-section designator. You may place this immediately following the line
name of a shot that was collected using a cross-section pattern. This signifies that this
shot was recorded using a cross-section and all of the shots that have the same pattern
process the line work as listed in the cross-section portion of Data Collection. Shots
recorded using the same pattern have the same line name and this designator. For
example:
.XC=
This entry places the default Field Code and description, since no Field Code was entered
at this occurrence. Data Collection processes the line work listed in the order that it
exists in the cross-section pattern.
Stop Line This is the stop line designator. You may place this immediately following the line name of
the last shot on a line. This signifies that the line terminates at this shot. If the same line is
started later in the file, it starts normally. For example:
T.BC!
This entry allows you to stop the line BC at that shot without connecting it to the next BC
line.
46 Data Collection
Option Function
Insert This is the insert description designator. You may place this in the descriptor portion of the
Description Field Code entry. Typically, after a space has been entered, everything that ensues is
considered the description. If anything is entered in this portion of the descriptor, it
replaces the description for the Field Code. You may insert the description of the Field
Code by using the insert description designator. For example:
100 18” OAK *
This entry places Field Code 100 and a description with the insert description designator.
The description for Field Code 100 is TREE, and gets inserted immediately after the
entered description so that the result would be 18” OAK TREE.
Command Enter this designator in the shot description prior to entering the command alias (either a
Indicator rectangle “R,” circle “C” or a Feature Line “FL”). Information preceding the Command
Indicator (/ by default) is treated as Field Code or line information.
Rectangle The Rectangle command allows you to enter a width of rectangle to be drawn parallel to
Command Alias the shot on which the command was invoked, as well as the previous shot. A positive
width value draws the rectangle offset to the right of the line based on the direction from
the previous shot. A negative width constructs a rectangle offset to the left of the line
based on the direction from the previous shot. The resulting rectangle is a separate closed
polyline drawn with the same CAD attributes of the line name coded at the command shot.
Chapter 3: Options
For more information see Rectangle Designator on page 55.
Circle Command The Circle command allows you to enter a radius of a circle to be drawn from the center of
Alias the shot that is being recorded. This can be used to represent manhole covers with
different diameters, or to display the approximate drip line of a tree within the CAD
graphic. To record large structures or features to which the center point cannot be located,
you can record three consecutive shots along the perimeter of the feature which fit circle
geometry through each shot. This may be used to represent columns, utilities, or
cylindrical structures with a large circumference. The resulting figure is drawn with the
same CAD attributes of the line name coded at the command shot.
For more information see Circle Designator (Center Point and Radius) on page 56 and
Circle Designator (Three Point) on page 57.
Feature Line The Feature Line command allows you to enter multiple positive and negative distances
Command Alias to construct a feature line. By entering just distances, the line generated has 90-degree
corners deflected either to the right (when entering positive distances) or the left (when
entering negative distances). The initial direction established by the current shot and
previous shot is used to turn the angles from. A Close designator of “C” can also be used
to close the figure to the first shot of the figure (shot previous to the command shot). You
can also use the Angle designator “A” to specify an angle of some amount rather than
using 90-degree angles. Again, a positive/negative convention is used to determine
whether this is a deflection to the right (positive distance) or to the left (negative distance).
The resulting figure is drawn with the same CAD attributes of the line name coded at the
command shot.
For more information see Feature Line (90 Degree Angles) on page 57 and Feature Line
(Entered Angles) on page 58.
The following table lists the designators and the associated default.
Designators and Associated Defaults
Designators System Defaults

Line . (period)
Curve - (hyphen)
Close line + (plus)
Join last shot * (asterisk)
Bearing close # (pound sign)
Cross-section = (equal sign)
Stop line ! (exclamation point)
Insert description * (asterisk)
Command Indicator / (slash)
Rectangle R
Circle C
Feature Line FL
QuickSteps
To modify the designators used for line work, complete the following steps:
2. Select Options ! Designators.
3. Tab to the Line field.
4. Type a back slash (\) in the field
5. Click on OK.
The Designators dialog box closes. When you are in the field collecting data, a line is
defined by a back slash (\).
Examples
The illustrations on the following pages offer additional information about line work. The
default designators of line (.), curve (-), close line (+), join last shot (*), bearing close (#),
cross-section (=) and stop line (!) are used in the following examples.
48 Data Collection
These examples also show how line work may be entered using three different methods of
coding. The first method, or the default method, shows the Field Code and the Line Name
coded separately. This method was the only method available in previous versions of
Eagle Point. The Field Code, of course, is optional.
! When a line is recorded without a Field Code, the Default Field Code is used.
The second method represents Field Codes with the Use Field Code as Line Name in
Data Collection (FCasLN) toggle turned ON in the Node Field Code Library for the
respective Field Codes. This toggle is in the System ! Node (Field Code) Library off the
main toolbar for each Field Code. The option must also be enabled in Data Collection !
Options ! Reduction Settings ! Line Work.
The third method demonstrates the use of the line name to represent a placeholder or
counter (LNasCounter). The line name is the same as the first Field Code that was used to
record it. This option is located in Data Collection ! Options ! Reduction Settings ! Line
Work.
Line (Draw) Designator

In the following figure, the shots were all recorded using the same Field Code (EP).
Chapter 3: Options
! When coding using either the Default or the LNasCounter methods with special
designators, such as curve, close line, etc., the designators need to be accompanied by a
draw designator that precedes the line name. The FCasLN method does not require a
draw designator.
Figure 3-7 Use of Line (Draw) Designator
When shooting a point that occurs on more than one line (as shown in Figure 3-8, below),
you only need to record the common point once. Follow the first line name (EP) with
another line designator (.) and second line name (PIPE) on the shot to Node ID 2.
Figure 3-8 More Than One Line Per Shot
Curve Designator
The figure below shows an example of a single shot along a curve. Node ID 3 was
recorded on the curve portion, while Node IDs 1, 2, 4, and 5 were all recorded on straight
line segments.
Figure 3-9 Use of a Curve Designator
Figure 3-10 on page 51 shows an example of several shots recorded along a curve. Node
IDs 3, 4, and 5 were all recorded using a curve designator. Data Collection creates a
fitted curve within the CAD graphic.
50 Data Collection
! This is not a true arc segment, but an approximation of the arc that is comprised of
multiple straight-line segments that may be used to represent curb, pavement or other
types of curved breaklines.
Figure 3-10 Multiple Shots Along a Curve
Fitted Alignment Using a Curve Designator
Chapter 3: Options
A fitted alignment takes multiple shots on a curve and place a true arc segment in the CAD
graphic using the shots taken along the curve to approximate a radius. This may be used
to approximate design geometry by recording original ground features and monuments,
such as the PCs and PTs. This geometry can then be used by COGO or RoadCalc™ to
create an alignment.
Notice in the following figure, the shots recorded along the curve portion are not found to
be exactly on the arc segment. This is because Data Collection computed a true arc
segment based off the locations of the PC and the PT points. The arc is then fitted to
match the rest of the points along the curve, however, these shots may vary in location
from the arc placed.
Figure 3-11 Fitted Alignment
Close Line Designator
Figure 3-12, below, shows an example using the close line designator. When recording a
sequence that needs to be closed back to the original point with the same line name, there
is no need to reshoot the first point a second time to close the line. Place the close line
designator (+) immediately after the line name (BD) on the shot to Node ID 6.
Figure 3-12 Use of a Close Line Designator
Join Last Shot Designator

Figure 3-13, below, shows a shot to Node ID 3 that was intended to be on line EP, but was
recorded without the line information. To rectify this situation in the field, you may enter the
join last shot designator on the following recorded shot to Node ID 4.
Figure 3-13 Shot 3 Has No Line Information
52 Data Collection
Place the desired line name and the join last shot designator on the current shot (shot to
Node ID 4) and the processed lines connect to the proper locations.
Figure 3-14 Use of Join Last Shot Designator
Bearing Close Designator

Figure 3-15 (below) shows the front line of a building pad that was joined using a bearing
close designator. When shooting the corners of an existing building, the last corner may
not need to be shot using the bearing close designator.
Chapter 3: Options
The last corner of the building that was not shot is calculated by squaring the corners
using the bearing, or direction, of the first and last sides. Place the bearing close
designator (#) immediately after the line name (BD) as shown with shot #5.
Figure 3-15 Use of a Bearing Close Designator
Cross-Section Designator
Figure 3-16 on page 54 shows an existing road that was recorded using a cross-section
designator in a zigzag fashion. When you record existing road cross-sections, you may
save time in the field collecting data using the cross-section designator. Each shot taken in
the cross-section pattern is recorded using the same line name; however, each, is
processed using the correct line work once reduced into the CAD graphic.
The lines are recorded as the same name to save time entering each individual line name
in the field. You may create a pattern in the field and then add it after the survey is
complete.
! You may take a shot that is not a part of the cross-section pattern while the pattern is
being recorded. The pattern automatically picks up where the last shot in the pattern was
located.
! The Use Field Code as Line Name (FCasLN) and the Use Line Name as Counter
(LNasCounter) recording methods are not supported using a cross-section designator;
however, you may now insert a Field Code in the Cross-section line pattern. For more
information, refer to Cross-Section Patterns on page 72.
Figure 3-16 Use of a Cross-section Designator
Stop Line Designator

Figure 3-17 on page 55 shows an example of a line discontinued at Node ID 2. The line
EP was discontinued so that it could be started again at another location in the project.
You may record these points by placing the stop line designator (!) after the line name as
shown to Node ID 2.
54 Data Collection
! Entry of two draw designators performs the same effect as the stop line designator. For
example, entry of “..CL” is valid for stopping line CL.
Figure 3-17 Use of a Stop Line Designator
Insert Description Designator

Each Node that is placed in the CAD graphic has a default description that is associated
with it. You may enter a description in the field in lieu of using the default from the Field
Code, however, there may be instances where you want to append the default description
Chapter 3: Options
to one that is entered in the field. This may be done by adding the insert description
designator while entering the description.
! The insert description designator may only be entered once per description. For example,
if you have a Field Code 100 that has TREE for description, you may type 18” OAK * in
the field (* is the default insert description designator). The Node processes with a
description of 18” OAK TREE in the CAD graphic.
Rectangle Designator
This example demonstrates the use of the command indicator with the Rectangle
command alias. Node IDs 1 and 4 were recorded using the same line name (EP). Node ID
2 was recorded with a different line name to represent an inlet (IN). Node ID 3 was
recorded with the Rectangle command alias (R) and an offset value (2). This creates a
geometrically closed rectangle placed in the CAD graphic from the previously recorded
shot with the same line name (line IN from Node ID 2), and offset using a distance
immediately entered after the alias.
The dashed line in this example demonstrates that two lines are drawn in the CAD
graphic: the closed rectangle geometry, and the continuing line that connects shots 1 and
4.
Figure 3-18 Rectangle Designator
Circle Designator (Center Point and Radius)

This example demonstrates some different uses of the command indicator with the Circle
command alias. In this example, several shots were recorded using different Field Codes
(DTREE and MH) to reflect the desired geometry. Node IDs 1, 4, 5, and 6 were used to
locate existing, and the radius value was used to approximate the drip line. Node IDs 1
and 4 show a radius value of 10, while shots 5 and 6 show a radius value of 20 units.
Node IDs 2 and 3 were used to record existing manhole utilities with corresponding radius
values entered immediately entered after the alias. The radius value for both shots
entered was 2 units.
Figure 3-19 Circle Designator (Center Point and Radius)
56 Data Collection
Circle Designator (Three Point)
This example demonstrates three shots recorded along an existing cylindrical structure.
Three consecutive shots that are coded using the same line and Curve command alias
without a radius value “fit” circle geometry through each of the three recorded shots.
Figure 3-20 Circle Designator (Three Point)
Feature Line (90 Degree Angles)
Chapter 3: Options
This example demonstrates the use of the command indicator with the Feature Line
command alias. Node ID 1 was recorded at the start of the feature line. This shot only
needs to be coded with the same line name that is coded with the shot that has the feature
line information. Node ID 2 was recorded using the same line name as the previous shot,
but it is also coded with the indicator (/) and the alias (FL). In this example, the first
distance is 25 units to the right, so it was recorded as +25.
The second value is 20 units to the right, so it was recorded as +20. The third distance is
15 units to the left, so it was recorded as -15. The fourth distance is 40 units to the right, so
it was recorded as +40. The letter “C” recorded following the last distance value creates a
geometrically closed feature in the CAD graphic which connects the last leg of the feature
line with the first leg of the feature line.
Figure 3-21 Feature Line (90 Degree Angles)
Feature Line (Entered Angles)
This example demonstrates the use of the Command Indicator with the Feature Line
Command Alias and a user-definable angle value other than 90 degrees. Node ID 1 was
recorded at the start of the feature line. This shot only needs to be coded with the same
line name that is coded with the shot that has the feature line information. Node ID 2 was
recorded using the same line name as the previous shot, but it is also coded with the
indicator (/) and the alias (FL). In this example, the first distance is 25 units to the right, so
it was recorded as +25. The second value is 40 units to the right, so it was recorded as
+40. The third distance is 15 units to the left, so it was recorded as -15. The letter “A”
preceding 225 designates a 225 degree turned angle to the right. The distance was
recorded to be 28.28 and the angle is turned to the right because the distance value was
positive (+).
The letter “C” recorded following the last distance value creates a geometrically closed
feature in the CAD graphic which connects the last leg of the feature line with the first leg
of the feature line.
Figure 3-22 Feature Line Entered Angles
Line Work
DATA COLLECTION # OPTIONS # LINE W ORK
KEY-IN COMMAND: linework
ICON:
You may create line names and establish the properties of each line as it is reduced into
the CAD graphic through Data Collection. The user-definable properties of each line
58 Data Collection
include name, layer/level, color, linetype/style, pattern, width/weight, masking, type, fitted,
template, and elevation placement.
Displayed in the Line Work dialog box (below), is the active library of lines. You may create
new lines, modify lines, delete lines, print the library or select a different line library or
linetype library.
Figure 3-23 Line Work Dialog Box
Line Work Dialog Box Definitions
Chapter 3: Options
Name This displays the name of the line. This is an alphanumeric name assigned to
the line when the data was collected.
Layer/ Level This displays the layer/level on which the line is placed in the CAD graphic.
Color This displays the color assigned to the line.
Linetype/Style This displays the linetype/linestyle associated with the line.
Pattern This displays the custom line style that is used for the line. When the Use Line
Library toggle on the Line Work Reduction Settings tab is on, Data Collection
uses the line pattern defined for the line. When the Use Line Library toggle is
off, the line is placed using the default line properties in CAD.
Width/ Weight This displays the width/weight in drawing units.
Masking This displays the masking that is placed on the line when it is reduced into the
CAD graphic. Depending upon the feature the line is to represent, there are
different ways to mask the line when it is being used to generate a surface
model. The four types of masking using line work are:
" Include: This line is used as a break line when generating a surface
model. For example: An edge of pavement line would be masked as
include. The vertices as well as the line itself are read when
generating a surface model.
" Exclude: This line is ignored by the surface model. For example: A
lot line or utility line would be masked as exclude.
" No Break: This line is used when generating a surface model, but is
not used as a breakline. Only the vertices along the line are read
when generating the surface model.
" Void region: This line, when closed with the close line or bearing
close designator, forms a void region. The region bounded within the
line is ignored by the surface modeling process.
" Softbreak: The Softbreak feature allows you to change the way the
breaklines are interpreted. The breaklines are considered soft,
meaning that a smoothing factor is applied over the breaklines. A soft
breakline would be used if you want a ditch bottom to be smooth
instead of an abrupt change in grade.
Refer to Surface Modeling for a more detailed description of masking.
Type This displays the type of line to be processed. The different types are Line,
Fitted Alignment, and 3-D Line Template.
If the Type option is set to Line, Data Collection places a regular line/polyline/
complex chain. This is the default choice.
Fitted If this line is a Fitted Alignment, this displays how the line handles processing
the points at a curve. Any shots on a curve are used to “best fit” a defined arc
segment within the alignment. This means that shots that are taken along a
curve are used to create the arc without having the arc pass through the points.
Template If this line is a 3-D Line Template, this displays the 3-D line template that is
processed when the line is reduced. The line template may consist of several
lines that are already listed in the current line library.
Elevation This displays the elevation at which the line is processed.
If the elevation is not displayed, then the line is a 3-D line and is drawn through
the point shot at the appropriate elevation.
New Line You may create a line to add to the current line library. Click on the New Line
icon and enter the line properties.
For more information, see New Line on page 61.
Modify Line You may modify the line properties. Select the line name in the dialog box and
click on the Modify Line icon.
For more information, see New Line on page 61.
Delete Line You may delete a line from the active line library. Highlight the line name in the
dialog box and click on the Delete Line icon.
60 Data Collection
Line Work Print You may print the contents of the current line library to a file or the system
Options printer.
Line Libraries You may create a new library or select a different line library to use from the list
view.
Linetype You may select the AutoCAD/BricsCad linetype library file to use when creating
Libraries line work. The default library is the ACAD.LIN file stored in the AutoCAD/
(AutoCAD/ BricsCad Support folder. This option is not available when running in
BricsCad) MicroStation.
New Line
DATA COLLECTION # OPTIONS # LINE W ORK # NEW LINE
ICON:
Chapter 3: Options
The New Line option allows you to add a new line to the Line Work dialog box (Figure 3-23
on page 59) and specify the CAD properties, masking, type of line and placement.
New Line (AutoCAD/BricsCad)

You may establish the properties of each line that is reduced into the CAD graphic through
Data Collection. Displayed in the New Line dialog box (Figure 3-24 on page 62) are the
properties of the line to be added to the Line Work dialog box (Figure 3-23 on page 59).
These include line name, layer, color, linetype, pattern, width, masking, type, and
placement.
Figure 3-24 New Line Dialog Box
New Line Dialog Box Definitions

Name Type the name of the line. This may be a combination of alpha and numeric
characters not to exceed nine characters in length. This value may be entered
in the field when collecting line work.
Layer Type the name of the layer that the line is placed on when reduced into the CAD
graphic. If the layer does not exist, Data Collection creates it automatically. If
CAD is loaded, you may select the layer control button and select a pre-existing
layer from the dialog box.
Color Type the number or name, or select a color from the color palette.
Linetype Select a linetype from the available linetypes in the active linetype library.
Pattern Select a custom line pattern from the available custom line patterns defined in
the Pattern Line Library. To define a new Line pattern, click on the Library icon
to load the Custom Line Library. Pattern lines are used to insert blocks or text
along even intervals from the start of the line for features such as a fence, rock
wall or utility.
When the Use Pattern Lines toggle (check box) on the Line Work settings tab
(Figure 3-4 on page 39) is on, Data Collection uses the custom line pattern
defined for the line. When the Use Pattern Lines option is off, the line is placed
without the custom line pattern.
Width Type the numeric width value of the line.
62 Data Collection
Masking When generating a surface model with the lines created through Data
Collection, the lines may inherit different properties with regard to the role they
play in generating the model. Masking defines how the lines are to be utilized in
Surface Modeling.
Select the masking property for the line. There are different ways to mask the
line depending upon the feature the line is to represent. The four types of
masking using line work are:
" Include: This line is used as a breakline when generating a surface
lot line or power line would be masked as exclude.
" Void region: This line, when closed with a close line or bearing close
designator, forms a void region. The region bounded within the line is
ignored by the surface modeling process.
Chapter 3: Options
! Refer to Surface Modeling for a more detailed description of Masking.
Type Select the type of line that this line is to be processed as. The different types are
Line, Fitted Alignment and 3-D Line Template.
" Line: This is a standard line within Data Collection.
" Fitted Alignment: This line is processed as a fitted alignment
through all of the points along the line. Any shots on a curve are used
to “best fit” a defined arc segment within the alignment. This means
that shots that are taken along a curve are used to create the arc
without having the arc pass through the points. When this type is
selected, you may choose to hold the PC, hold the PT or hold neither
when the line is drawn.
" 3-D Line Template: This line places the 3-D line template that is
associated with the line name when reduced. The line template may
consist of several lines that are already listed in the current line
library. When this type is selected, you may select a defined 3-D line
template from the list of available templates, or click on the manager
button and load the 3-D Line Template manager dialog box.
Refer to 3-D Line Templates on page 76 for a more detailed description.
Option Select an option to use for the new line.
Placement You may place this line in the CAD graphic at a constant elevation, or place the
lines through each of the Nodes as they are reduced.
" 2-D: Each line and arc segment that is generated by Data Collection
is processed at the elevation entered. Type the desired elevation to
place the line work.
! For lines to be used as breaklines when generating a surface model, the
lines need not be at the elevation of the model. Each line endpoint only
needs to pass through a point that is at the correct elevation. For this
reason, line work that is placed at elevation zero, (0), has the desired
effect being used as breaklines. Set your minimum elevation to just above
the elevation of the lines (i.e. Minimum Valid Elevation = 1), so as not to
include them when generating your surface model. For more information
on generating surface models, refer to the Surface Modeling module.
is processed at the elevation of the Node or point that is being
placed.
QuickSteps (AutoCAD/BricsCad)
To add a line to the Line Work dialog box (Figure 3-23 on page 59), complete the following
steps:
1. From Data Collection, select Options ! Line Work.
2. Highlight the line name from the Line Work dialog box that you would like to
make a copy of and click on the New Line icon, or just click on the New Line
icon.
The New Line dialog box (Figure 3-24 on page 62) displays.
3. Type the name of the new line in the Name edit field and press the Tab key.
4. Type the layer name you want the line to be placed on in the Layer edit field or
select a layer by clicking on the Select Layer icon, and then press the Tab key.
5. Select a color from the color palette or enter the color number/name and press
the Tab key.
6. Select the Linetype of the line from the drop list of linetypes and press the Tab
key.
7. Select the Line Pattern to use with the line and press the Tab key. If you want to
create a new line pattern, click on the Custom Line Library icon to display the
Custom Line Library dialog box. You may add a pattern and use it for the new
line. If you do not want to use a custom line pattern, select None from the drop
list and press the Tab key.
8. Type the line width and press the Tab key.
9. Select the masking type from the drop list and press the Tab key.
64 Data Collection
10. Select the type of line and press the Tab key. If you select Fitted Alignment, you
may hold the curve PC, curve PT, or neither when processing and press the Tab
key. If you selected 3-D Line Template, then select a 3-D Line Template from the
drop list, or click on the Manager button to display the 3-D Line Templates
dialog box. You may add a new template, close this dialog box, and select the
created 3-D Line Template from the drop list and press the Tab key.
11. Select whether to place the line at a fixed elevation (2-D), or to place the line
through the elevations of the points processed (3-D). If you select 2-D, type the
elevation that you would like the line to be processed at.
12. Click on Apply to add the line or on OK to modify the line.
New Line (MicroStation)

You may establish the properties of each line that is reduced into the CAD graphic through
Data Collection. Displayed in the New Line dialog box (below) or Modify Line dialog box
Chapter 3: Options
(not shown) are the properties of the line to be added to the Line Work dialog box (Figure
3-23 on page 59). These include line name, level, color, style, pattern, weight, masking,
type, option, and placement.
Figure 3-25 New Line Dialog Box
Name Type the name of the line. This may be a combination of alpha and numeric
characters not to exceed nine characters in length. This value may be entered
in the field when collecting line work.
Level Type the level number (level name in MicroStation V8) that the line is placed on
when reduced into the CAD graphic.
Color Type the number, or select a color from the color palette.
Style Select a line style from the available line styles in MicroStation.
! If MicroStation is not loaded, you are not able to select a MicroStation
custom line style.
Pattern Select a custom line pattern from the available custom line patterns defined in
the Pattern Line Library. To define a new line pattern, click on the Custom Line
Library icon to load the Custom Line Library. Pattern lines are used to insert
cells or text along even intervals from the start of the line for features such as a
fence, rock wall or utility.
When the Use Pattern Lines option on the Line Work tab in Reduction Settings
is on, Data Collection uses the custom line pattern defined for the line. When
the Use Pattern Lines option is off, the line is placed without the custom line
pattern.
% If a line is placed using a MicroStation custom line style and a
custom line pattern through Data Collection, the line may not edit as
a MicroStation custom line style. This is due to the process that is
used in creating the custom line pattern.
Weight Type the numeric weight value of the line.
66 Data Collection
Masking When generating a surface model with the lines created through Data
Collection, the lines may inherit different properties with regard to the role they
play in generating the model. Masking defines how the lines are to be utilized in
Surface Modeling.
Select the masking property for the line. There are different ways to mask the
line depending upon the feature the line is to represent. The four types of
masking using line work are:
" Include: This line is used as a breakline when generating a surface
lot line or power line would be masked as exclude.
" Void region: This line, when closed with a close line or bearing close
designator, forms a void region. The region bounded within the line is
ignored by the surface modeling process.
Chapter 3: Options
Refer to Surface Modeling for a more detailed description of Masking.
Type Select the type of line that this line is to be processed as. The different types are
Line, Fitted Alignment and 3-D Line Template.
" Line: This is a standard line within Data Collection.
" Fitted Alignment: This line is processed as a fitted alignment
through all of the points along the line. Any shots on a curve are used
to “best fit” a defined arc segment within the alignment. This means
that shots that are taken along a curve are used to create the arc
without having the arc pass through the points. When this type is
selected, you may choose to hold the PC, hold the PT or hold neither
when the line is drawn.
" 3-D Line Template: This line places the 3-D line template with the
same line name when reduced. The line template may consist of
several lines that are already listed in the current line library. When
this type is selected, you may select a defined 3-D line template from
the list of available templates, or click on the Manager button and
load the 3-D Line Template manager dialog box.
Refer to 3-D Line Templates on page 76 for a more detailed description.
Option Select an option to use for the new line.
Placement You may place this line in the CAD graphic at a constant elevation, or place the
lines through each of the Nodes as they are reduced.
is processed at the elevation entered. Type the desired elevation to
place the line work.
! For lines to be used as breaklines when generating a surface model, the
lines need not be at the elevation of the model. Each line endpoint only
needs to pass through a point that is at the correct elevation. For this
reason, line work that is placed at elevation zero, (0), has the desired
effect of being used as breaklines. Set your minimum elevation to just
above the elevation of the lines (i.e. Minimum Valid Elevation = 1), so as
not to include them when generating your surface model. For more
information on generating surface models, refer to the Surface Modeling
module.
is processed at the elevation of the Node or point that is being
placed.
QuickSteps (MicroStation)
To add a line to the Line Work dialog box (Figure 3-23 on page 59) complete the following
steps:
1. From Data Collection, select Options ! Line Work.
The Line Work dialog box displays.
Figure 3-26 Line Work Dialog Box
2. Highlight the line name from the Line Work dialog box that you would like to
make a copy of and click on the New Line icon.
The New Line dialog box (Figure 3-25 on page 65) displays.
3. Type the name of the new line in the Name edit field and press the Tab key.
4. Type the level you want the line to be placed on in the level edit field and press
the Tab key.
68 Data Collection
5. Type an RGB color number or select a color from the color palette and press the
Tab key.
6. Type the style number or select the line style from the drop list of line styles and
press the Tab key.
! MicroStation must be running to access this feature.
7. Select the Line Pattern to use with the selected line style and press the Tab key.
If you want to create a new custom line pattern, click on the Custom Line
Library icon to display the Custom Line Library dialog box. You may add a
pattern and use it for the new line. If you do not want to use a custom line
pattern, select None from the drop list and press the Tab key.
% If a line is placed using a MicroStation custom line style and a custom line pattern
through Data Collection, the line may not edit as a MicroStation custom line style.
This is due to the process that is used in creating the custom line pattern.
8. Type the line weight and press the Tab key.

9. Select the masking type from the drop list and press the Tab key.
Chapter 3: Options
10. Select the type of line and press the Tab key. If you select Fitted Alignment, you
may hold the curve PC, curve PT or neither when processing. If you select 3-D
Line Template, then select a 3-D Line Template from the Template drop list, or
click on the 3-D Line Templates icon to display the 3-D Line Templates dialog
box. You may add a new template, close this dialog box, and select the created
3-D Line Template from the drop list and press the Tab key.
11. Select whether to place the line at a fixed elevation (2-D), or to place the line
through the elevations of the points processed (3-D). If you select 2-D, type the
elevation at which you would like the line to be processed.
12. Click on Apply to add the line, or on OK to modify the line.
13. Click on Cancel.
14. Click on Close in the Line Work dialog box.
Line Libraries
DATA COLLECTION # OPTIONS # LINE W ORK # LINE LIBRARIES
You may add or create new line libraries for a specific project or add a library used by a
different client and incorporate it as one of your line libraries.
Figure 3-27 Line Libraries Dialog Box
Line Libraries Dialog Box Definitions

Description This displays the description associated with each line library.
Library Name This displays the names of all established line libraries. Highlight a line library
and click on OK to make it current.
New Line Library You may enter the name and a description of the line library you want to add.
The extension LWL is attached to the name and the library is placed in the
SUPPORT folder.
To select an existing file, click on the File Open button and select the library file.
You can select an existing library file with an LWL extension.
! Line libraries that were used in an earlier version of Eagle Point (version
5.5 or 13.0 or greater) need to be converted using the Convert Previous
Installation command found in the EGPT Administration Utility program
(EPADMIN.EXE).
Modify Line You may modify the description of the line library.
Library
Delete Line Click on this icon to delete a file from the list box. An Alert box displays with this
Library command. Click on OK to remove the library or Cancel to retain the library.
% Deleting a line library deletes the library file from your hard drive.
70 Data Collection
Linetype Libraries
DATA COLLECTION # OPTIONS # LINE W ORK # LINETYPE LIBRARIES
You may add a defined linetype library to use other than the ACAD.LIN linetype library file.
! This command is not available when running with MicroStation.
Figure 3-28 Linetype Libraries Dialog Box
Chapter 3: Options
Linetype Libraries Dialog Box Definitions
Description This displays the description of the linetype library.
Library Name This displays the name of the linetype library. The extension LIN is attached to
the name. This file must be located in the AutoCAD search path.
New Linetype You may enter the name and a description of the linetype library you want to
Library add. This file must already exist and have an LIN extension.
To select an existing file, click on the File Open icon and select the linetype
library file.
Modify Linetype You may modify the description of the Linetype Library.
Library
Delete Linetype Click on this icon to delete a file from the list box. An Alert box displays with this
Library command. Click on OK to remove the library or Cancel to retain the library.
! This only removes the linetype library file from the list view, and does not
remove it from the hard drive.
Cross-Section Patterns
DATA COLLECTION # OPTIONS # CROSS-SECTION PATTERNS
KEY-IN COMMAND: dcxs
ICON:
You may associate a repetitive series of shots, or a cross-section pattern as one line
name. This means you may enter the same line name for each shot taken on a pattern.
The resultant lines that are processed are stored with the cross-section pattern and
processed in a zigzag or a side to side pattern. The cross-section patterns may be used to
complete an entire survey project such as a roadway or to record components of a project
such as curbs, gutters and sidewalks.
! If intermediate shots that are not part of the pattern are taken, such as a manhole or power
pole, you can enter the appropriate Field Code for that feature and continue taking shots
from where you left off on the cross-section pattern.
Figure 3-29 Cross-Section Patterns Dialog Box
Cross-Section Patterns Dialog Box Definitions

Pattern Name This displays the name associated with the cross-section pattern.
Method This displays the number of points or shots assigned to the cross-section
pattern (e.g. 7- PNT). If the pattern is Side to Side, an S is displayed as part of
the method. If the pattern is Zig Zag, a Z is displayed as part of the method (e.g.
7-PNT Z).
Description This displays the description associated with the cross-section.
New Cross- You may create a new cross-section pattern. Click on the New Cross-Section
Section Pattern Pattern icon and enter the pattern name, description and associated lines.
72 Data Collection
Cross-Section Patterns Dialog Box Definitions
Modify Cross- You may modify the cross-section pattern. Highlight the cross-section pattern
Section Pattern you want to modify and click on the Modify Cross-Section Pattern icon.
For more information, see New Cross-Section Pattern (below).
Copy Cross- You may copy a cross-section pattern. Highlight the cross-section pattern you
Section Pattern want to copy and click on the Copy Cross-Section Pattern icon.
For more information, see New Cross-Section Pattern (below).
Delete Cross- You may delete a cross-section pattern. Highlight the cross-section pattern you
Section Pattern want to delete and click on the Delete Cross-Section Pattern icon.
Print List Cross- You may print all of the cross-section patterns to a file or the system printer.
Section Pattern This prints the pattern name, method, description and associated lines for each
pattern.
New Cross-Section Pattern

DATA COLLECTION # OPTIONS # CROSS-SECTION PATTERNS # NEW CROSS-S ECTION PATTERN
Chapter 3: Options
ICON:
The New Cross-Section Pattern command allows you to create a cross-section pattern to
be used when collecting field data. The cross-section pattern includes a name,
description, method and associated lines. The pattern name is recorded for each shot
taken on the data collector along with the cross-section pattern designator. Depending on
how the data is collected in the field, the pattern may process the line to facilitate either a
side to side method of collection or in a zigzag fashion. Each associated line in the pattern
is processed into the CAD graphic using the specified properties defined in the Line Work
dialog box. Also, if a Field Code has been specified along with the associated line, the
specified field code is placed instead of a default field code.
For more information about the Line Work Library, see Line Work on page 58.
For more information about cross-section pattern designators, see Designators on page
44.
Figure 3-30 New Cross-Section Pattern Dialog Box
New Cross-Section Pattern Dialog Box Definitions

Pattern Name Type the name that you want assigned to the cross-section pattern. This is
the line name that is entered in the field to represent the cross-section
pattern.
Description Type a description for the cross-section pattern.
Method Select the method used when collecting points or shots. You may choose
either Side to Side or Zigzag.
" Side to Side: The list of associated lines is processed from the top
of the list down to the bottom. The line on the bottom is processed
twice to facilitate the start of the next cross-section and the list is
read from the bottom to the top, repeating in that fashion for the
length of the pattern.
" Zigzag: The list of associated lines is processed from the top of
the list down to the bottom. This is repeated for the length of the
pattern.
New Associated You may add a line to the list of associated lines at the bottom of the list.
Line Click on the New Associated Line icon and toggle on the Use Field Code
option if you want to place a specific field code with the line. Then, choose
between the From Library, Line Name and No Line options for the linework.
Select the From Library option if you want to use a line name from the Line
Work Library or click on the Line Work Library icon to create new line in the
Line Work Library. Select the Line Name option to specify a line name in the
corresponding edit field that is not in the Line Work Library. Select the No
Line option if you do not want to have any linework drawn for the shots
collected using the associated line. Click on Apply to add the line.
74 Data Collection
New Cross-Section Pattern Dialog Box Definitions
Insert You may insert a line to the list of associated lines. Highlight the line that you
Associated Line want to insert a new line before. Click on Insert and toggle on the Use Field
Code option if you want to place a specific field code with the line. Then,
choose between the From Library, Line Name and No Line options for the
linework. Select the From Library option if you want to use a line name from
the Line Work Library or click on the Line Work Library icon to create new line
in the Line Work Library. Select the Line Name option to specify a line name
in the corresponding edit field that is not in the Line Work Library. Select the
No Line option if you do not want to have any linework drawn for the shots
collected using the associated line. Click on Apply to add the line.
Modify You may modify a line in the list of associated lines. Highlight the line that you
Associated Line want to modify and click on the Modify Associated Line icon to change
anything for the associated line. Once you have made modifications, click on
the OK button.
Delete You may delete a line from the list of associated lines. Highlight the line to
Associated Line delete from the pattern and click on the Delete Associated Line icon.
QuickSteps
Chapter 3: Options
To add a cross-section pattern, complete the following steps:
1. From Data Collection, select Options ! Cross-Section Patterns.
2. Click on the New Cross-Section Pattern icon.
The New Cross-Section Pattern dialog box (Figure 3-30 on page 74) displays.
3. Type a pattern name (this name is used by the surveyor when recording a shot
on the pattern) and a description.
4. Select the method that is used in the field for this pattern. Choose either Side to
Side or Zigzag.
5. Add associated lines to the pattern. Click on the New Associated Line icon to
add a line to the pattern. The New Associated Line dialog box displays.
6. Toggle on the Use Field Code option and select a field code from the drop list.
Turn on the From Library radio button and select a line from the available list of
lines and click on Apply. Continue to add lines to the pattern until it is finished.
After you have clicked on Apply to add the final entry, click on Cancel.
7. Click on OK in the New Cross-Section Pattern dialog box.
8. Click on Close in the Cross-Section Patterns dialog box.
3-D Line Templates
DATA COLLECTION # OPTIONS # 3-D LINE TEM PLATES
KEY-IN COMMAND: linetemp
ICON:
You may associate a series of approximated geometry, or template with a single shot in
the field. This may be used to automatically generate curb and gutter sections, sidewalks,
ditches or any other existing feature that only needs to be approximated. The points and
lines for the remainder of the template are automatically drawn in the CAD graphic based
on the location of the origin shot for each template. This means you only need to collect
one shot in the field, where it would have normally called for several to accurately depict
the original ground pattern. The 3-D Line Templates may be used by themselves or used
in conjunction with a cross-section pattern to complete an entire survey project such as a
roadway or to record components of a project such as curbs, gutters and sidewalks.
Figure 3-31 3-D Line Templates Dialog Box
3-D Line Templates Dialog Box Definitions

Description This is the name of the 3-D line template. The template name may be
associated with any line name in Line Work if it is set to be a 3-D Line Template
line.
New 3-D Line You may create a new 3-D line template. Click on the New 3-D Line Template
Template icon and enter the template name, and the associated offsets, elevations, and
line names.
Modify 3-D Line You may modify the 3-D line template. Highlight the template you want to
Template modify and click on the Modify 3-D Line Template icon.
For more information, see New 3-D Line Template on page 77.
Delete 3-D Line You may delete a 3-D line template. Highlight the template you want to delete
Template and click on the Delete 3-D Line Template icon.
76 Data Collection
3-D Line Templates Dialog Box Definitions
Print 3-D Line You may print all of the 3-D line templates to a file or the system printer. This
Template Listing prints the template name and the associated offsets, elevations and line names.
and Data
New 3-D Line Template

DATA COLLECTION # OPTIONS # 3-D LINE TEM PLATES # NEW 3-D TEM PLATE
ICON:
You may add or modify the associated offsets, elevations and line names with a 3-D Line
Template. Offsets and elevations may be added, modified or deleted to more closely
resemble the existing geometry of surveyed features. After processing, you may modify
the lines associated with the template to incorporate different properties and reprocess the
job into the project.
Chapter 3: Options
Figure 3-32 New 3-D Line Template Dialog Box
New 3-D Line Template Dialog Box Definitions

Template Name Type the name of the 3-D Line Template.
! The template name is not utilized in the field, but is selected as a property
of a line through the Line Work dialog box (Figure 3-23 on page 59). See
Line Work on page 58 for more information.
New 3-D Line You may create a new offset associated with the template. Click on the New 3-
Template D Line Template icon and type the offset, change of elevation, and select a line
from the drop list of lines from the current line library, or click on the Linework
Library icon in the New 3-D Line Template Break Point dialog box (Figure 3-34
on page 80) to display the Line Work dialog box (Figure 3-23 on page 59) to
add a new line.
New 3-D Line Template Dialog Box Definitions
Modify 3-D Line You may modify an offset associated with the template. Highlight the offset you
Template want to modify and click on the Modify 3-D Line Template icon.
For more information, see New 3-D Line Template Breakpoint on page 80.
Delete 3-D Line You may delete an offset with the template. Highlight the offset you want to
Template delete and click on the Delete 3-D Line Template icon.
QuickSteps
To create a new 3-D Line Template, complete the following steps:
1. From Data Collection, select Options ! 3-D Line Templates.
The 3-D Line Templates dialog box (Figure 3-31 on page 76) displays.
2. Click on the New 3-D Line Template icon to display the New 3-D Line Template
dialog box (Figure 3-32 on page 77).
3. Type the name of the new template in the Template Name edit field.
4. Click on the New 3-D Line Template icon to add a new elevation and offset to the
template.
5. Type the offset distance from the location where the shot is actually recorded. A
negative value places the offset on the left.
6. Type the elevation difference from the location where the shot is actually
recorded. A negative value places it below the shot.
7. Select a line name from the drop list of lines in the current Linework Library, or
click on the Linework Library icon to display the Line Work dialog box (Figure 3-
23 on page 59) to add a new line.
8. Click on Apply and continue to add offsets until the template is finished. Click
on Cancel when completed.
9. Click on OK to add the template.
10. Click on Close in the 3-D Line Templates dialog box.
Example
The following example shows you how to add a template of a typical curb and gutter
section.
You first need to know the relative dimensions of the existing curb and gutter section that
is to be (or has been) surveyed. Calculate the offsets and elevations of the breakpoints
along the typical curb and gutter section. For this example, the typical dimensions are
known.
78 Data Collection
In this example, the cross-slope of the gutter is 0.05m per meter. The height of the face of
curb is 0.10 meters, and the back of curb extends an additional 0.08 meters.
Figure 3-33 Line Template Diagram
To enter this template, complete the following steps:

1. From Data Collection, select Options ! 3-D Line Templates.
2. Click on the New 3-D Line Template icon to display the New 3-D Line Template
dialog box (Figure 3-32 on page 77).
3. Type CG Right for the name of the new template in the Template Name edit
Chapter 3: Options
field.
4. Click on the New 3-D Line Template icon to add a new elevation and offset to the
template.
5. Type 0.4 in the Offset edit field and press the Tab key.
6. Type -0.02 in the Elevation edit field and press the Tab key.
7. Select a line from the drop list of line names for the gutter line. If a line name
does not exist in the Line Library, click on Open and add a line to the Line Work
dialog box (Figure 3-23 on page 59). Highlight the line that you have created in
the Line Work dialog box and click on Close.
8. The gutter or flow line portion of the curb and gutter section should be added at
this point. Click on Apply to add the breakpoint.
9. Type 0.42 in the Offset edit field and press the Tab key.
10. Type 0.08 in the Elevation edit field and press the Tab key.
11. Select a line from the drop list of line names for the top of curb line. If a line
name does not exist in the Line Library, click on Open and add a line to the Line
Work dialog box. Highlight the line that you have created in the Line Work
dialog box and click on Close.
12. The top of curb portion of the curb and gutter section should be added at this
point. Click on Apply to add the breakpoint.
13. The last breakpoint of the template needs to be added. Type 0.5 in the Offset
edit field and press the Tab key.
14. Type 0.08 in the Elevation edit field and press the Tab key.
15. Select a line from the drop list of line names for the back of curb line. If a line
name does not exist in the Line Library, click on Open and add a line to the Line
Work dialog box. Highlight the line that you have created in the Line Work
dialog box and click on Close.
16. The back of curb portion of the curb and gutter section should be added at this
point. Click on Apply to add the breakpoint.
17. Click on Cancel in the New 3-D Line Template Breakpoint dialog box.
18. The template should display in the viewer. Click on OK to add the template.
19. Click on Close to close the 3-D Line Templates dialog box.
New 3-D Line Template Breakpoint

DATA COLLECTION # OPTIONS # 3-D LINE TEM PLATES # NEW 3-D LINE TEM PLATE
# NEW 3-D LINE TEM PLATE
ICON:
You may add offsets to the template, or highlight an existing offset and modify it. The offset
and elevation values are in the working units of the project, and places points at the proper
elevations based on the insertion point of a zero (0) offset and a zero (0) elevation.
The shot that is recorded in the field needs to be processed on a line, and that shot is
assumed to be at the zero offset location. The elevation of the template is also read from
the calculated elevation value of the shot, and the associated template lines are
processed using that elevation.
Figure 3-34 New 3-D Line Template Breakpoint Dialog Box
80 Data Collection
New 3-D Line Template Breakpoint Dialog Box Definitions
Offset Type the offset value for the breakpoint. This value is measured from the base
location of the template, which occurs where the actual surveyed shot is
located.
Elevation Type the change in elevation from the base location of the template, which
occurs where the actual surveyed shot is located.
! The elevation of the offset line is processed according to the line
properties. If it is a 3-D line, then the elevations are in accordance with the
shot taken. If it is a 2-D line, then it processes at the elevation specified in
the line properties. The points, however, are at the correct, calculated
elevation based on the template.
From Library Select the From Library option if you want to use a line name from the Linework
Library, or click on the Linework Library icon to create a new line in the Linework
Library.
Line Name Select a line name from the drop list of defined lines in the current line library. If
the line does not exist, or if you need to change line libraries, click on this button
to display the Line Work dialog box (Figure 3-23 on page 59).
No Line Select the No Line option if you do not want to have linework drawn for the
shots collected using the associated line.
Chapter 3: Options
82 Data Collection
QUERY
In this chapter:
CHAPTER
Query Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Query Shot Averaging. . . . . . . . . . . . . . . . . . . . . . 85
Query Backup File. . . . . . . . . . . . . . . . . . . . . . . . . 86
Query File Information. . . . . . . . . . . . . . . . . . . . . . 87
Query Observations . . . . . . . . . . . . . . . . . . . . . . . 89
Query Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Query Unused Nodes . . . . . . . . . . . . . . . . . . . . . . 94
Resolve Duplicate Nodes . . . . . . . . . . . . . . . . . . . 95 4
Chapter 4: Query 83
Query Warnings
DATA COLLECTION # QUERY # W ARNING S
or
DATA COLLECTION # JOBS # REDUCE # W ARNING S
KEY-IN COMMAND: dcwarn
ICON:
You may query and print the warnings and error messages that may have displayed after
processing. This may include messages about Field Codes missing, incomplete line work,
unsupported data tags or other types of warning messages. You can print this report to a
file or to the system printer.
! If the list is not cleared, new results will be appended to the bottom of the results each time
the OK or Preview button on the Reduce Job dialog box (Figure 2-7 on page 21) is clicked
on.
Figure 4-1 Query Warnings Dialog Box
Query Warnings Dialog Box Definitions

Print Options You may print the information to a file or directly to the system printer.
Clear You may clear the results list to start a new project.
84 Data Collection
Query Shot Averaging
DATA COLLECTION # QUERY # SHOT A VERAG ING
or
DATA COLLECTION # JOBS # REDUCE # QUERY SHOT A VERAG ING
KEY-IN COMMAND: dcaverage

You may query and print the shot averaging that may have occurred for processing
multiple occurrences of the same Node ID within the job file. Certain collectors and
formats allow for the storage of repeated turns to the same Node using forward or reverse
(or face 1/ face 2) observations. If the collector does not mean these points out for you,
Data Collection can mean (average) these occurrences through shot averaging based on
the type of shot or record used to store the points. The higher priority occurrences are
reported and meaned if necessary, whereby the lower priority occurrences are just
reported in the Query Shot Averaging dialog box (below). You may define the priority of
each type of record or shot in the shot averaging options under Reduction Settings on
page 34.
! If the list is not cleared, new results will be appended to the bottom of the results each time
the OK or Preview button on the Reduce Job dialog box (Figure 2-7 on page 21) is clicked
on.
Figure 4-2 Query Shot Averaging Dialog Box Chapter 4: Query
Query Shot Averaging Dialog Box Definitions

Print Options You may print the information displayed in the Query Shot Averaging dialog box
to a file or directly to the system printer.
Clear You may clear the results list to start a new report.
Chapter 4: Query 85
Query Backup File
DATA COLLECTION # QUERY # BACKUP FILE
KEY-IN COMMAND: qbackup
ICON:
You may compare the data in the Instrument with that of the Backup file. If you have made
any editing changes and want to review the original copy of the file, you may verify line for
line the information in the instrument file. You may then make the necessary changes to
the instrument file by editing the instrument file, or reverting back to the backup file by
modifying the job file.
Figure 4-3 Query Backup File Dialog Box
Query Backup File Dialog Box Definitions

Job Name Select the job name from the drop list of current jobs in the project from which to
query the backup file.
Backup This displays the path and file name of the backup file.
Filename
Backup File Date This displays the date the file was created.
86 Data Collection
Query Backup File Dialog Box Definitions
Backup File Size This displays the size of the backup file.
Instrument This displays the path and file name of the instrument file.
Filename
Instrument FIle This displays the date the file was created.
Date
Instrument File This displays the size of the instrument file.
Size
Print Options You may print either the backup file or the instrument file to a file or path to the
system printer.
Query File Information

DATA COLLECTION # QUERY # FILE INFORM ATION
KEY-IN COMMAND: fileinfo
ICON:
You may query file information from any job in the project. Information includes the format
that the file is in, date, time and current file size.
Chapter 4: Query
Chapter 4: Query 87
You may also determine how many objects are in the current project from the selected job,
the path and file name of each file in the job and whether the integrity of the backup data
file has been maintained. You may print this information to a file or directly to the system
printer.
Figure 4-4 Query File Information Dialog Box
Query File Information Dialog Box Definitions

Option Function
Job Name Select the job name from which to query file information from the drop list of current jobs
in the project.
Format This displays the format filter that was used to either download or import the instrument.
Number of This displays the number of objects that have been drawn in the CAD graphic that are
current objects associated with the job file. This includes any line or arc segments that would have been
in CAD graphic drawn, as well as points/Nodes.
Created/Edited This displays the date, time and size of each of the files associated with the job.
New/Download This displays the date, time and size of each of the files associated with the job.
Instrument FIle This displays the time and date the instrument file was created or last saved and the size
of the file.
Formatted File This displays the date and time the formatted file was created or last saved and the size of
the file.
! In most cases the formatted file will be larger than the instrument file.
Backup File This displays the date the file was created and the size of the backup file.
! Since this file is attributed read-only when it is created, this date and time should
always be the same as the New/Download date and time. If they do not match, the
backup file has been altered.
Path Location This displays the path and file names of each file associated with the selected job.
Instrument File The system displays the complete path and name of the instrument.
Formatted File The system displays the complete path and name of the formatted file.
88 Data Collection
Query File Information Dialog Box Definitions
Option Function
Backup File The system displays the complete path and name of the backup file.
Print Options You may print this information to a file or directly to the system printer.
Query Observations
DATA COLLECTION # QUERY # OBSERVATIONS
KEY-IN COMMAND: dcobs

This command allows you to display, sort, and print all of the raw observations in the
selected job file. Viewing these observations may help you detect blunders or
observations that need to be corrected, commented or removed from the job file.
This dialog box is divided into two different reports.
The Observations listview displays each raw observation to a side shot or a foresight
within the job file. The observations are initially sorted chronologically. However, you may
sort the data by Node ID, Horizontal Angle, Vertical Angle and Slope Distance by clicking
on the respective column header.
The Observation Summary listview sorts all of the observations that share the same At-
From-To combination into a group. Each group is displayed in a row along with properties
of that group: Quantity of observations, meaned angles and distances, range or maximum
difference between all angles and distances, and the standard deviations.
To use this command, you can sort the groups of observations by greatest range or
Chapter 4: Query
standard deviation to determine what sets of raw observations are questionable or fail
your criteria for accuracy. Keeping this dialog box up, you can comment out the sets of
angles using the Formatted File Editor by placing a PR activity on the undesirable
observations, save the file, and refresh the Query Observations report dialog box to show
the new results.
The Refresh button will reread the formatted file to display any changes since the job file
was first selected and displayed. Any information changed in the file will be redisplayed
according to your sorting preference. If you previously selected a column header to sort
the data, this header will be used to sort the rows in the listview.
Chapter 4: Query 89
Reports may be customized. You may determine which columns to include as well as the
header for each column, the column width, and the column order of each report. Reports
will print the rows as they appear in the Query Observations dialog box.
Figure 4-5 Query Observations Dialog Box
Query Observations Dialog Box Definitions

Job Name Select the job from the Job Name list. All of the raw instrument measurements
recorded will be displayed, including the horizontal angle, vertical angle and
slope distance of each observation. When a job is selected, the Query
Observations dialog box redisplays the observations within the selected job
file.
Observations All raw instrument measurements recorded within the selected job file will be
displayed here. Initially, the observation information will be displayed in the
order that it was recorded, or chronologically. Each column header may be
clicked to sort the observations by the column selected.
" At: The occupied station used to record the observation.
" From: The backsight used to record the observation. This may
display as a direction or as a Node ID.
" To: The observed point.
" Horizontal Angle: The horizontal angle recorded during the

observation. This is generally reported as an angle right.
" Vertical Angle: The vertical angle recorded during the observation.
This is generally reported as a zenith angle.
" Slope Distance: The slope distance recorded for the observation.
90 Data Collection
Observation All raw instrument measurements recorded within the selected job file that
Summary share the same At-From-To orientation will be displayed here. There must be
at least two recorded observations that have matching orientation (At-From-
To) for the observations to appear in the Observation Summary report.
The observation information will be displayed in the order that it was recorded,
or chronologically. However, each column header may be clicked to sort the
observation combinations by the column selected to easily determine if all the
recorded sets of observations follow acceptable standards and practices. This
is done by sorting the rows to show the sets of observations with the largest
values at the top of the report. Click on the range or standard deviations
column headers to sort the horizontal, vertical and slope distances columns.
" #Obs: This displays the number of observations that have been
recorded to a point that share the same At-From-To combination.
" At: The occupied station used to record the observations.
" From: The backsight used to record the observations. This may
display as a direction or as a Node ID.
" To: The point observed.
" Mean HA: This displays the meaned or averaged value of the
horizontal angles with the same At-From-To combination.
" Range HA: This displays the range or difference between the two
angles with the greatest spread or difference with the same At-
From-To combination. The use of comparing the range of various
At-From-To combinations within a survey may be useful in
determining the area where a surveying blunder may have
occurred.
Chapter 4: Query
" Std. Dev. HA: This displays the standard deviation of all the
horizontal angles with the same At-From-To combination.
" Mean VA: This displays the meaned or averaged value of the
vertical angles with the same At-From-To combination. Vertical
angles recorded in the Face 2 or reverse position are 'normalized'
for reporting purposes.
" Range VA: This displays the range or difference between the two
normalized angles with the greatest spread or difference with the
same At-From-To combination.
Chapter 4: Query 91
Observation " Std. Dev. VA: This displays the standard deviation of all the vertical
Summary angles with the same At-From-To combination.
" Mean SD: This displays the averaged value of the slope distances
with the same At-From-To combination.
" Range SD: This displays the range or difference between the two
recorded distances with the greatest spread or difference with the
same At-From-To combination.
" Std. Dev. SD: This displays the standard deviation of all the slope
distances with the same At-From-To combination.
Print Reports This allows you to generate a report of all observations and/or generate the
observation summary. The data in the report is displayed as it is sorted in the
dialog box. There are custom print settings so you can choose the columns
and modify the headers that you want to print.
Refresh If you have highlighted certain rows, these rows will remain highlighted after
Refresh is selected. This makes it easier to measure the impact made by
editing and commenting out a set of observations to a point.
Warnings This displays the Query Warnings dialog box within Data Collection.
See Query Warnings on page 84 for more information.
Query Nodes
DATA COLLECTION # QUERY # NODES
KEY-IN COMMAND: dcnode
ICON:
The Query Nodes command may be used to build a report of selected Nodes from the
project. You can use any of the standard methods of selecting Nodes from the drawing or
the database.
For more information, see COGO Select Nodes Dialog Box in the COGO manual or help
file.
The selected Nodes will report information such as Node ID, Northing, Easting, elevation,
description, layer/level, symbol and Field Code. The report can then be printed in a user-
definable format. You may choose the information and the order in which the information
92 Data Collection
should appear in the report. You will also be able to save the printing options as a default
setting.
Figure 4-6 Query Nodes Dialog Box

Node ID This column displays the Node ID values.
Northing-(Y) This column displays the Northing or Y coordinate values of the Nodes.
Easting-(X) This column displays the Easting or X coordinate values of the Nodes.
Elevation-(Z) This column displays the Elevation or Z coordinate values of the Nodes.
Description This column displays the description values.
Layer/Level This column displays the layer (AutoCAD/BricsCad) or level (MicroStation) of
each selected Node.
Symbol This column displays the symbol name of each selected Node. This will either
be the name of the block (AutoCAD/BricsCad) or cell (MicroStation).
Field Code This column displays the Field Code associated with each selected Node.
Chapter 4: Query
Report Options You may select the Node information order for the printed report. These settings
can be saved as the default for future reports. You may print the report to a file
or the printer.
See COGO Print Options Dialog Box in the COGO manual or Help file.
Clear You may clear the list of Nodes and reselect them from the project by clicking
on this button.
Select Nodes This allows you to display the Select Nodes dialog box to select or deselect
Nodes to be reported. This is only available if the Select Nodes dialog box has
been closed.
Chapter 4: Query 93
Query Unused Nodes
DATA COLLECTION # QUERY # UNUSED NODES
KEY-IN COMMAND: dcunused

This command may be used to see what node IDs are not in use in the project.
You can report what Node ID ranges are available in the entire project or check to see
what Nodes are not being used within a specified range.
Figure 4-7 Query Unused Nodes Dialog Box
Query Unused Nodes Dialog Box Definitions

Node ID This displays the unused Node ID ranges. If the range contains more than 100
Nodes it is designated by an asterisk.
All If this option is selected, all the available Node IDs will display for the entire
project.
Range If this option is selected, specify a range of Nodes that you would like to check
for unused Node ID values.
From This is the point where the unused Nodes will start to be reported.
To This is the ending point where the unused Nodes will be reported to.
Print Unused You may print the report to a file or directly to the system printer.
Nodes
94 Data Collection
Resolve Duplicate Nodes
DATA COLLECTION # QUERY # RESOLVE DUPLICATE NODES
KEY-IN COMMAND: dcdupnode
ICON:
This command allows you to resolve duplicate occurrences of Node ID’s in the project.
These may have been caused from processing jobs that used the same Node ID’s as
those already in the project or to average multiple shots to the same Node ID.
You may select any of the six options available to resolve the duplicate occurrences in the
project. The options allow you to perform a combination of deleting, renumbering and
averaging the coordinate values of the duplicate occurrences. The selected Nodes will
report information such as Node ID, Northing, Easting, elevation, description, CAD
property (layer/level), symbol and Field Code.
The report can then be printed in a user-definable format. You may choose what
information and in the order that it is specified to appear.
Chapter 4: Query
Figure 4-8 Resolve Duplicate Nodes Dialog Box
Resolve Duplicate Nodes Dialog Box Definitions

Node ID This column displays the Node ID values.
Northing This column displays the Northing or Y coordinate values.
Easting This column displays the Easting or X coordinate values.
Chapter 4: Query 95
Resolve Duplicate Nodes Dialog Box Definitions
Elevation This column displays the Elevation or Z coordinate values.
Description This column displays the description values.
Layer/Level This column displays the layer (AutoCAD/BricsCad) or level (MicroStation) of
each selected Node.
Symbol This column displays the symbol name of each selected Node. This will be the
name of the block/cell.
Field Code This column displays the Field Code associated with each selected Node.
Resolve You may select the information and order for the printed report. You may print
Duplicate Nodes the report to a file or directly to the system printer.
Print Options
Renumber Node This will renumber the highlighted occurrence to the lowest available Node ID in
to Lowest the project. This will be shown on the dialog box in static text.
Available
Renumber Node This will renumber the highlighted occurrence to the Node ID one higher than
to Next Available the current highest number in the project.
Renumber Node This will renumber the highlighted occurrence to a user-defined number that
to Selected does not exist in the project. This defaults to the next available Node ID. If the
Value entry field is left blank and this method is applied, Data Collection will
renumber the Node to the next available Node ID value.
Delete Selected This will delete the highlighted occurrence(s).
Node(s)
Keep Selected This will delete all the duplicate Node occurrences remaining in the dialog box
Node(s), Delete except the highlighted occurrence(s).
Remaining
Duplicates
Average This will create one Node with the average Northing, Eastings, and elevation
Coordinates & values for the occurrences remaining in the dialog box and place the Node with
Elevations of the Field Code and attributes of the highlighted occurrence.
Selected Nodes
QuickSteps
To resolve duplicate Nodes, complete the following steps:
1. Select Query ! Duplicate Nodes.
The project will be searched for any duplicate Node ID values. If none are found, the
command prompt displays that no duplicate Nodes were found.
If duplicates are found, the Resolve Duplicate Nodes dialog box displays the Node IDs
that are duplicated, as well as other associated information.
2. Select one of the resolve options from the drop list.
96 Data Collection
3. Highlight one or more Nodes (depending on the resolve option selected) to be
resolved.
4. Click on Apply.
5. Once you have made all of the changes, click on Close.
Chapter 4: Query
Chapter 4: Query 97
98 Data Collection
SDMS EDITOR
In this appendix:
APPENDIX
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
SDMS Editor – File Menu . . . . . . . . . . . . . . . . . . 103
SDMS Editor – Edit Menu . . . . . . . . . . . . . . . . . . 105
SDMS Editor – Tools Menu . . . . . . . . . . . . . . . . . 113
SDMS Editor – Help Menu . . . . . . . . . . . . . . . . . 116
Appendix A: SDMS Editor 99

Introduction
The SDMS (Survey Data Management System) Editor (Figure A-1 on page 101) allows
you to edit a formatted survey file. This editor is used when editing Data Collection
formatted files, COGO batch files, and Survey Adjustment files. The editor is similar to a
spreadsheet editor with individual cells containing a piece of data or text.
Each row within the editor represents one survey activity from the information that was
recorded. Each activity is sequentially numbered along the left side of the editor and
represents the row number. You cannot change these numbers because the system has
assigned the numbers to represent the order in which the data was recorded. Within each
row are a series of columns representing a data tag and the data entered for the tag. Two
columns are always needed to define a particular piece of data. The first of the two
columns must be either a two-letter activity code or a two-letter data tag. The following
column will then contain the actual value (data) for the particular code or tag. Refer to
Reserved Eagle Point SDMS Data Tags on page 233 for additional information on the
SDMS file format.
! Row numbers are not Point Numbers (PN:).
! While focus is in any cell, you may use the F1 key to display a popup Help dialog box to
assist you in understanding the data tag or what are valid options for a particular item.
You can navigate between the cells using the Tab key, arrow keys, or mouse. Click your
mouse in a cell where there is no data to set the cell active (as shown by the rectangular
highlight around the cell) to immediately begin overwriting the data that is already there
(see Figure A-3 on page 102). Clicking in an area in a cell that contains data will place
your cursor at the location you picked (see Figure A-4 on page 102). When the cursor is
blinking, you may perform a double click to highlight the entire number or word you are
pointing at (see Figure A-5 on page 102). When entering data within a cell, you may use
the Esc key to revert to the data that was originally there before editing. As soon as focus
leaves the cell however, the Esc key will not change the data back (use the Undo
command).
An entire row or column may be highlighted by clicking on the numbered or lettered
headers on the left and top of the data area respectively. Additionally, clicking the blank
header in the upper left corner of the data area will highlight the entire file. After
highlighting certain data, you can copy the data to the Windows clipboard by using the
Ctrl+C shortcut. This makes the data available for pasting into another SDMS file or a
different application altogether.
Performing a right-button mouse click while pointing your cursor in the data area will
display a popup menu that contains the Cut, Copy, and Paste commands from the Edit
menu and the commands from the Tools menu. The editor also remembers the size and
position at which you last closed it. Each time you open the editor, it is displayed at its last
100 Data Collection

location and size. Other commands allow you to control the column widths and
spreadsheet display.
! In order for the editor to display in Data Collection using the Edit Formatted File
command, the selected file must have been downloaded and the data collector format
must be set correctly.
Figure A-1 SDMS Editor Dialog Box
SDMS Editor Dialog Box Definitions

Option Function
SDMS Editor This displays the job name of the file being edited.
Caption Bar
File Menu This menu provides access to the Save, Print, and Exit commands.
For a description of how these commands work, refer to SDMS Editor – File Menu on
page 103. Appendix A: SDMS
Edit Menu This menu provides access to the various edit commands to cut, copy, paste, search/
replace, and globally edit the data in the current file.
Editor
For a description of how these commands work, refer to SDMS Editor – Edit Menu on
page 105.

SDMS Editor Dialog Box Definitions
Option Function
Tools Menu This menu provides access to the Insert/Delete Row commands and the commands for
setting certain display options.
For a description of how these commands work, refer to SDMS Editor – Tools Menu on
page 113.
Help Menu This menu provides access to the on-line help.
For a description on how these commands work, refer to SDMS Editor – Help Menu on
page 116.
Data Area This is the area within the editor that contains the file data. The information within this area
may be edited to meet your specific needs. Type data directly into the cells or use the
commands in the Edit and Tools menus to search and replace, globally edit, or add/delete
rows.
Status Bar The area in the lower left-hand corner of the editor displays the current data tag and
definition associated with the data tag.
Figure A-2 SDMS Editor Toolbar
Figure A-3 Active Cell with Rectangular Highlight
Figure A-4 Focus in Cell with Blinking Cursor
Figure A-5 Data Highlighted in Cell
102 Data Collection

SDMS Editor – File Menu
The commands in this menu are used to save or print the current SDMS file or to exit the
editor environment.
Figure A-6 File Menu
Save
SDM S EDITOR # FILE # SAVE
ICON:
Use this command to save the current data in the editor to the active file. You will not be
prompted for the file location or warned that you are overwriting the file. Use may also use
the Ctrl+S shortcut or the Save icon on the SDMS Editor Toolbar.
Save As
SDM S EDITOR # FILE # SAVE A S
Use this command to save the current data in the editor to a specific file and location.
Upon selecting this command, you will be presented with the standard Windows Save As
dialog box. Browse to the desired location and enter a file name. If the file already exists,
you will be prompted to replace the existing file.
! The file will be saved in the Eagle Point SDMS file format.
Appendix A: SDMS
Editor

Print
SDM S EDITOR # FILE # PRINT
ICON:
This command prints the contents of the editor to the specified Windows printing device.
Select the command from the File menu, use the Ctrl+P shortcut, or click on the Print icon
on the SDMS Editor Toolbar.
The Print dialog box allows you to select the printer, page range, and number of copies.
The printout is not formatted. To print the SDMS formatted file, use the Print option on the
Data Collection Manage Jobs, COGO Manage Batch Files, or the Manage Survey
Adjustment Files dialog boxes.
Exit
SDM S EDITOR # FILE # EXIT
This command will close the SDMS Editor. You may alternatively use the X icon in the
upper right-hand corner of the editor to exit the current session. If changes have been
made to the file since the last time it was saved, you will be prompted to save changes.
Select Yes to save your current changes and exit the editor, select No to exit the editor
without saving your changes, or select Cancel to return to the editor without saving
changes.
104 Data Collection

SDMS Editor – Edit Menu
The commands in this menu are used to edit the current SDMS file. In addition to standard
Copy and Paste commands, the Find, Replace, and Global Edit commands can be used
to search for or edit selected text and data tags.
Figure A-7 Edit Menu
Undo
SDM S EDITOR # EDIT # UNDO
This command will undo the last editing action(s) performed in the editor. This includes
changing data tags, editing cell values, inserting and deleting lines, and using the Replace
and Global Edit commands.
Select the Undo command multiple times to undo successive changes. Select the
command from the Edit menu or use the Ctrl+Z shortcut.
Redo
SDM S EDITOR # EDIT # REDO
This command reverses the action of the last execution of the Undo command. You can Appendix A: SDMS
only redo the last change after an undo.
Select the command from the Edit menu or use the Ctrl+R shortcut.
Editor

Cut
SDM S EDITOR # EDIT # CUT
ICON:
This command deletes the currently highlighted text in the active cell and also copies it to
the Windows clipboard. This allows you to paste it into a different cell.
Select the command from the Edit menu, click on the Cut icon on the SDMS Editor
Toolbar, use the Ctrl+X shortcut, or right click in the editor to select the command from the
popup menu.
! To delete or cut an entire row of data, use the Delete Line command from the Tools menu.
The Delete Line command will not copy the contents of the row to the clipboard.
! Because you may be dealing with a legal document, you may want to use the DL Data
Tag rather than deleting any information from the file.
Copy
SDM S EDITOR # EDIT # COPY
ICON:
Use this command to copy the currently highlighted text in the active cell to the Windows
clipboard. An entire row or column of cells may be highlighted by clicking on the numbered
or lettered headers on the left and top of the data area respectively. Or highlight multiple
cells by dragging your mouse across the desired cells while holding down your left mouse
button. Using the Copy command or a highlighted selection makes the data available for
pasting into another SDMS file or a different application altogether.
After highlighting the desired cells/text, select the command from the Edit menu, click on
the Copy icon on the SDMS Editor Toolbar, use the Ctrl+C shortcut, or right click in the
editor to select the command from the popup menu.
106 Data Collection

Paste
SDM S EDITOR # EDIT # PASTE
ICON:
This command will insert the contents of the Windows clipboard into the active cell.
Select the command from the Edit menu, click on the Paste icon on the SDMS Editor
Toolbar, use the Ctrl+V shortcut, or right click in the editor to select the command from the
popup menu.
Select All
SDM S EDITOR # EDIT # SELECT A LL
This command highlights every cell in the active SDMS file. This allows you to copy the
entire contents of the SDMS file to the Windows clipboard.
Select the command from the Edit menu or use the Ctrl+A shortcut.
Find
SDM S EDITOR # EDIT # FIND
ICON:
This command allows you to search the active SDMS file for a specific piece of text or
data tag. Toggle on the Include Field Text option and enter a number, word, or part of a
word in the edit field to search for. The Find command is not case sensitive, meaning that
entering upper case letters may find matching lower case letters, and vice versa. You may
also enter only portions of a certain word or number and the editor will find all instances
that even partially contain the desired text. For example, entering “LINE” in the Include Appendix A: SDMS
Field Text edit field will find the text “LINE2” or “CATCHLINE” because the letters L, I, N, E
appear in sequence within both of those words.
Editor
Additionally, narrow your search by specifying to find the text only when used with a
certain data tag. Toggle on the Include Data Tag option and select the appropriate data
tag before clicking on the Find button. You may also perform a search for a specific data
tag by just toggling on the Include Data Tag option and toggling off the Include Field Text
option.

After setting the desired options, click on the Find button. The editor looks for the text from
the current cell down through the file. If the text and/or data tag is found, focus will be
placed in the appropriate cell. If the search fails, you will receive a message indicating that
the specified text cannot be found. Since the Find command is modeless, you can leave
the dialog box open while you are editing the file and return to the dialog box to perform
another search.
Select the command from the Edit menu, click on the Find icon on the SDMS Editor
Toolbar, or use the Ctrl+F shortcut.
! The Find command searches for the text/data tag down through the file from the current
cell. Make sure that the current cell is above the portion of the file you wish to search.
Figure A-8 Find Dialog Box
Find Dialog Box Definitions

Option Function
Include Field Toggle on this option to search the active SDMS file for a specific number, word, or part of
Text a word. Enter the desired text in the edit field and click on Find. By default, the text in the
current cell is placed in the Include Field Text edit field. The search engine is not case
sensitive and can also find the entered text when it is only a portion of a larger number or
word.
Include Data Tag Toggle on this option to search for a specific data tag or to narrow a field text search.
Toggled on by itself, this option will find the next occurrence of the specified data tag.
When the Include Field Text option is also toggled on, the Find command will only search
the specified data tag to locate the desired text. By default, the data tag associated with
the current cell is placed in the Include Data Tag drop list.
Find Next
SDM S EDITOR # EDIT # FIND NEXT
ICON:
This command can be used to locate the next instance of the last item searched for using
the Find command. When the next instance is found, focus is placed in the appropriate
cell. If the item is not found, a message displays, indicating that the specified text cannot
be found. For more information, refer to Find on page 107.
108 Data Collection

Select the command from the Edit menu, click on the Find Next icon on the SDMS Editor
Toolbar, or use the Ctrl+N shortcut.
! The Find Next command searches for the text/data tag down through the file from the
current cell. Make sure that the current cell is above the portion of the file you wish to
search.
Replace
SDM S EDITOR # EDIT # REPLACE
ICON:
This command allows you to search the active SDMS file for a specific piece of text and
replace it with a different piece of text. The Replace command is not case sensitive,
meaning that entering upper case letters may find matching lower case letters, and vice
versa. Also, you may enter only portions of a certain word or number and the editor will
find all instances that even partially contain the desired text. For example, entering “LINE”
in the Find text edit field will find the text “LINE2” or “CATCHLINE” because the letters L, I,
N, E appear in sequence within both of those words. Those same characters would then
be replaced by the text in the Replace with edit field. Note that this command works for
finding/replacing data input fields and data tag drop lists.
After setting the desired options, you may want to click on the Find Next button to just
locate the next occurrence of the specified text and verify whether it should be changed or
not. Focus is placed in the found cell. Click on the Replace button to replace just that
occurrence. The Replace button then performs a Find Next to locate the next occurrence.
You may alternatively just use the Replace option instead of first performing a Find Next.
Additionally, you can replace all occurrences of the specified text using the Replace All
button.
When searching for the text, the editor looks for the text from the current cell down through
the file. If the text is found, focus will be placed in the appropriate cell. If the search fails,
you will receive a message indicating that the specified text cannot be found. Since the
Replace command is modeless, you can leave the dialog box open while you are editing
the file and return to the dialog box to perform another search/replacement.
Appendix A: SDMS
Select the command from the Edit menu, click on the Replace icon on the SDMS Editor
Toolbar, or use the Ctrl+H shortcut.
Editor

! The Replace command searches for the text/data tag down through the file from the
search.
Figure A-9 Replace Dialog Box
Replace Dialog Box Definitions

Option Function
Find text Enter the desired number, word, or part of a word in the edit field and click on Find Next.
By default, the text in the current cell is placed in the Find text edit field. The search
engine is not case sensitive and can also find the entered text when it is only a portion of
a larger number or word.
Replace with Enter the number or string you wish to replace the found text with. Since the command
can find the entered text when it is a portion of a larger number or word, the Replace with
text is substituted for only the characters specified in the Find text edit field. For example,
entering “TREE” in the Find text edit field and “Bush” in the Replace with edit field will
replace “TREE12” with “Bush12.”
Find Next Use this button to locate the next occurrence of the Find text value. Focus is placed in the
cell for editing.
Replace This button performs a Find Next when the current cell does not contain the text specified
in the Find text edit field. After finding the next occurrence, focus is placed in the cell,
allowing you to click on the Replace button again to actually modify the selected value
with the specified Replace with text. After the text is replaced, it performs another Find
Next to locate the next occurrence to replace.
Replace All Click on this button once you have entered the text to find and what you want to replace it
with. All instances of the Find text value will be replaced with the characters from the
Replace with edit field throughout the entire file.
Global Edit
SDM S EDITOR # EDIT # G LOBAL EDIT
ICON:
This command allows you to modify the data tag and/or corresponding value for a
selection set of Nodes in the active SDMS file. This command is similar to the Replace
command, but offers more flexibility in identifying only certain Nodes and data tags to be
110 Data Collection

modified. Specify a single Node ID, a range of Node IDs, a Node description, or all Nodes
to be modified. From that selection set, you narrow the search by specifying a data tag
that will be modified. You can modify the data tag itself and/or the corresponding data
value. Choose to set a new value by replacing it, adding a constant amount to it, or
multiplying it by a constant amount. Toggle on the Confirm Each Replacement option to
“step through” each replacement, confirming whether or not the change should be made.
Additionally, since the Global Edit command is modeless, you can leave the dialog box
open while you are editing the file and return to the dialog box to perform another
modification.
Select the command from the Edit menu, click on the Global Edit icon on the SDMS Editor
Toolbar, or use the Ctrl+G shortcut.
! The Global Edit command is not case sensitive, meaning that entering upper case letters
for a Node description may find matching lower case letters and vice versa.
! The Global Edit command searches for the text/data tag down through the file from the
search.
Figure A-10 Global Edit Dialog Box
Appendix A: SDMS
Editor

Global Edit Dialog Box Definitions
Option Function
Selection Specify the method with which to select the Nodes. Choose from selecting a single Node,
Method a range of Nodes, all Nodes that match a description, or every Node in the file.
" Single: Select the Single method to specify a single Node ID to modify.
" Range: Select the Range method to specify an inclusive range of Nodes. The
range may be entered with either the larger or smaller Node ID first. The Prefix
option is available for Alphanumeric Node IDs so that you can enter an alpha
prefix for the Nodes to be selected. All Nodes within the range (inclusively) will
be selected.
" Description: Select the Description method to build a selection of Nodes to edit
by entering either a portion of a description or by matching the entire
description. Toggle off the Match Description Exactly option to select all Nodes
that have descriptions that contain the sequence of letters/numbers in the
Description edit field (e.g., when the text is part of a larger word). Toggle this
option on to only select Nodes where the entered text matches the entire
description entered. For example, with the toggle off, entering “TREE” will select
Nodes that have descriptions of “Tree”, “TREE14,” or “OAKTREE.” With the
toggle on, only Nodes with descriptions of “Tree” or “TREE” will be selected (not
“OAK Tree”).
" All: Select this method to perform an edit on every Node in the file.
Find Tag Enter the data tag that corresponds to the item that will be modified. You may change the
data tag for the selected Nodes and/or the cell text/number that is associated with the
data tag.
Change Tag To Toggle on this option to change the data tag for the selected Nodes. The tag specified in
the Find Tag drop list will be modified to match the data tag specified in the Change Tag
To drop list.
Change Field Toggle on this option to change the text/number in the cell associated with the data tag
Text specified in the Find Tag drop list. Use the drop list next to the edit field to control what
action is taken on the text/number. To modify the text of the selected tag, change the drop
list to the Set option. Set the drop list to Add or Multiply to perform mathematical
operations on the numerical value of a field. To subtract a number, specify a negative in
the Change Field Text edit control and set the drop list to Add. To divide by a number,
enter the decimal reciprocal of the corresponding multiplication value and change the drop
list to Multiply.
Confirm Each Toggle on this option to be prompted before any modifications are made to each of the
Replacement selected Nodes. The prompt allows you to “step through” each replacement, confirming
whether or not the change should be made. Within the Confirm Each Replacement dialog
box, you are also provided with a prompt to choose an All option that allows the
modification to be made on all of the rest of the selected Nodes without further
confirmation.
112 Data Collection

SDMS Editor – Tools Menu
The commands in this menu are used to edit the current SDMS file and set certain display
options. You may insert and delete rows or add a new column to the end of the file with
commands in this menu. The Find Data Collection Warnings command is also available in
this menu when you have invoked the editor from Data Collection.
! A right click in the cell area of the editor also displays the commands found in the Tools
menu.
Figure A-11 Tools Menu
Insert Row
SDM S EDITOR # TOOLS # INSERT ROW
ICON:
Use this command to insert a blank line after the row that currently has focus.
Select the command from the Tools menu, click on the Insert Row icon on the SDMS
Editor Toolbar, or right click in the editor to select the command from the popup menu.
Delete Row
SDM S EDITOR # TOOLS # DELETE ROW
Appendix A: SDMS
Editor
ICON:
Use this command to remove the row that currently has focus.
Select the command from the Tools menu, click on the Delete Row icon on the SDMS

! Because you may be dealing with a legal document, you may want to use the DL Data
Tag rather than deleting any information from the file.
Add Column
SDM S EDITOR # TOOLS # A DD COLUM N
ICON:
This command adds two columns to the rightmost section of the current SDMS file. The
first of the two columns added is to set the data tag and the second column is for the data
itself.
Select the command from the Tools menu, click on the Add Column icon on the SDMS
Find Data Collection Warnings

SDM S EDITOR # TOOLS # FIND DATA COLLECTION W ARNING S
ICON:
This command can be used to identify field coding problems within the active SDMS file.
Errors and warnings such as Setup data missing, Field Code not found,
Unsupported Data Tags, etc., that reference a specific Node ID can be selected on the
Find Data Collection Warnings dialog box (Figure A-12 on page 115) and used as a
means to position your cursor within the active file. After highlighting a specific warning,
click on the Goto Line button and your cursor will be placed in the first cell at the line that
contains the referenced Node ID.
Select the command from the Tools menu, click on the Find Data Collection Warnings
icon on the SDMS Editor Toolbar, or right click in the editor to select the command from
the popup menu.
! This command is only available while editing the formatted file in Data Collection.
114 Data Collection

! If the Warnings list is not cleared, new results will be appended to the bottom of the results
each time the OK or Preview button on the Reduce Job dialog box is selected.
Figure A-12 Find Data Collection Warnings Dialog Box
Find Data Collection Warnings Dialog Box Definitions

Warnings list This listing contains the warnings for all Data Collection files that have been
reduced in the current project. When a job is reduced or previewed, the SDMS
file is processed and any coding warnings or errors that exist in the file are
reported in this list. The most recent warnings/errors are appended to the
bottom of the listing.
Print Data Select this option to print the listing of warnings to a file or to your Windows
Collection system printer (according to the options set in the Eagle Point Main Menu !
Warnings File ! Print Setup command).
Clear Use this option to empty the contents of the Warnings list.
Goto Line After highlighting a specific warning/error within the current job's report, select
this option to set your cursor to the row in the editor that is referenced by the
Node ID specified in the warning.
Options
SDM S EDITOR # TOOLS # OPTIONS
This command allows you to set the default cell width of the Data Tag and Data Field Appendix A: SDMS
columns. When the editor is opened, the values specified here are used to size the
columns. Sizing the column headers will not change the default widths.
Editor

Display Settings
SDM S EDITOR # TOOLS # DISPLAY S ETTING S
This command allows you to change various settings for the editor display. Change how
the headers and gridlines appear, the color scheme of the editor, and how the active cell is
indicated.
SDMS Editor – Help Menu

The commands in this menu can assist you in finding specific help topics related to the
SDMS Editor and SDMS file format and data tags.
Contents
SDM S EDITOR # HELP # CONTENTS
Select this command to display the Table of Contents of the Help file for the SDMS Editor.
Additionally, you may use the Index or Find tabs to look up a keyword or phrase within a
help topic.
Search For Help On

SDM S EDITOR # HELP # SEARCH FOR HELP ON
Select this command to display the Index tab of the Help file for the SDMS Editor. Enter a
keyword or other topics of interest for which to display help. Additionally, you may use the
Find tab to look up a phrase or keyword within a help topic.
About
SDM S EDITOR # H ELP # A BOUT
This command displays the About dialog box for the SDMS Editor. Here you can find
version information about the SDMS Editor.
116 Data Collection

GEODAT LABELS
In this appendix:
APPENDIX
GEODAT Labels . . . . . . . . . . . . . . . . . . . . . . . . . 118
Appendix B: GEODAT Labels 117

GEODAT Labels
DATA COLLECTION # OPTIONS # REDUCTION SETTING S # COLLECTOR # G EODAT # CUSTOM IZE
The GEODAT Labels are customizable to your Geodimeter data collection system. Data
Collection provides a default list of GEODAT labels. You may add or modify labels to
meet your specific needs. The GEODAT Labels list view displays the actual value entered
recorded in the field, the associated Data Tag and the prompt on the instrument.
You may edit the data tags associated with the labels by clicking on the Edit Data Tags
button. You may also create new labels, modify or delete existing labels, or print a list of all
the GEODAT Labels and their associated information to a file or directly to the system
printer.
! For more information on field procedures and troubleshooting tips, see Collectors and
Formats, which begins on page 129.
Figure B-1 Geodat Labels Dialog Box
Geodat Labels Dialog Box Definitions

Label This displays the GEODAT label value that is stored when collecting data.
Tag This displays the data tag associated with the GEODAT label.
Prompt This displays the prompt for the GEODAT label on the collector.
Description This displays the description of the data tag associated with the GEODAT label.
New Geodat You may create a new GEODAT label to add to the list. Click on the New
Label Geodat Label icon and add the label.
118 Data Collection

Geodat Labels Dialog Box Definitions
Appendix B: GEODAT
Modify Geodat You may modify a GEODAT label to use a different data tag. Highlight the
Labels
Label GEODAT label you want to modify and click on the Modify Geodat Label icon.
Delete Geodat You may delete a GEODAT label from the list. Highlight the GEODAT label you
Label want to delete and click on the Delete Geodat Label icon.
Print Geodat You may print the list of GEODAT labels to a file or directly to a printer.
Label
Edit Data Tags You may edit the data tags by adding, modifying and deleting them. This
displays the Edit Data Tags dialog box (Figure B-3 on page 120).
See EP SDMS, which begins on page 209, for more information on supported
data tags.
New/Modify GEODAT Label

DATA COLLECTION # OPTIONS # REDUCTION SETTING S # COLLECTOR # G EODAT # CUSTOM IZE # NEW
You may add a new GEODAT label that does not already exist in the list.
Figure B-2 New Geodat Label Dialog Box
New Geodat Label Dialog Box Definitions

Option Function
Label Type the number of the new GEODAT label.
Tag This displays the data tag associated with the GEODAT label.
Prompt This displays the prompt for the GEODAT label on the collector.
Description This displays the description of the data tag associated with the GEODAT label.

QuickSteps
To add a new GEODAT Label, complete the following steps:
1. From Data Collection, select Options ! Reduction Settings.
2. Click on the Collector tab and select any of the GEODAT formats from the drop
list of formats.
3. Click on the Customize button.
This displays the Geodat Labels dialog box (Figure B-1 on page 118).
4. Click on the New Geodat Label icon.
This displays the New Geodat Label dialog box (Figure B-2 on page 119).
5. Type the label number in the Label edit field.
6. Select the data tag to associate with the GEODAT label from the list view by
highlighting it.
7. Click on Apply to add the label to the GEODAT Labels list.
8. Click on Cancel.
9. Click on Close in the Geodat Labels dialog box.
10. Click on Cancel in the Reduction Settings dialog box.
Edit Data Tags

DATA COLLECTION # OPTIONS # REDUCTION SETTING S # COLLECTOR # G EODAT
# CUSTOM IZE # EDIT DATA TAG S
You may edit the data tags used to process GEODAT raw files.
Figure B-3 Edit Data Tags Dialog Box
120 Data Collection

Edit Data Tags Dialog Box Definitions
Appendix B: GEODAT
Tag This displays the two-character data tag.
Labels
Prompt This displays the prompt of the associated data tag.
Description This displays the description of the associated data tag.
New Data Tag You may add a data tag to the list of data tags. Click on the New Data Tag icon
and add a new data tag. Enter a two-character alphanumeric code identifying
the data tag, along with the prompt on the GEODAT and the description.
Modify Data Tag You may modify a data tag. Highlight the data tag to modify and click on the
Modify Data Tag icon.
Delete Data Tag You may delete a data tag from the list. Highlight the data tag to delete and click
on the Delete Data Tag icon.
Print Data Tag You may print the list of data tags to a file or directly to the printer.

122 Data Collection
LEICA CODES
In this appendix:
APPENDIX
Leica Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Appendix C: Leica Codes 123

Leica Codes
DATA COLLECTION # OPTIONS # REDUCTION SETTING S # COLLECTOR # LEICA # CUSTOM IZE
The Data Collection module currently works in conjunction with most Leica/WILD
instruments used as total stations or data collectors. These instruments collect and store
information using the same structure, which allows you to use the same set of codes,
regardless of the type of instrument collecting the data.
The data collectors supported by Data Collection are the GRE4, GIF-10 and GIF-12
devices. Importing a GSI formatted file is supported by setting the format to any of the
mentioned collectors. The various types of total stations (VIP, TPS, etc.) are also
supported through this interface.
Data Collection provides a default listing of codes that are customizable to use with most
collection systems.
! For more information on field procedure and troubleshooting tips, see Troubleshooting,
which begins on page 203.
Figure C-1 Leica Codes Dialog Box
Leica Codes Dialog Box Definitions

Code This displays the code number that is used when collecting data. This code is
always located at the end of the first word of a code block.
Activity This displays the surveying activity associated with the code. The activity is
usually defined by the first word of the code block, although a code can change
activities within the code block (i.e. switching from occupied station to
backsight within the same code). The surveying activity may be a side shot,
occupied station, foresight, etc. The activity may be specified as continue
previous, which means that information entered in this code will be a
continuation of the last surveying activity that was entered in the file. This
information may be related to the staff height, line work, etc. The activity also
corresponds to a Field Value that may be entered when collecting data.
124 Data Collection

Leica Codes Dialog Box Definitions
Information This displays the data tags associated with each code block. The data tag for
blocks each information field will link to the information in the code block as it is
processed through Data Collection. The Leica GPC data collector and some of
the newer Leica instruments have up to eight information fields that may be
used per code block. Others have only four information fields per code block.
New Leica Code You may add a new Leica code to the list. This will display the New Leica Code
dialog box (Figure C-2 on page 126).
Modify Leica You may modify a Leica code on the list. Highlight the code that you want to
Appendix C: Leica
Codes modify and click on the Modify Leica Codes icon. This will display the Modify
Leica Code dialog box.
Codes
For more information, see New Leica Code on page 126.
Delete Leica You may delete a Leica code from the list. Highlight the code that you want to
Codes delete and click on the Delete Leica Codes icon.
Print Leica You may print the Leica code list to a file or directly to your printer. This will print
Codes each code and the associated activity and data tags for each information block.
Edit Data Tags You may edit the data tags by adding, modifying, and deleting them. This
displays the Edit Data Tags dialog box (Figure C-3 on page 128).
See EP SDMS, which begins on page 209, for more information on supported
data MS.

New Leica Code
DATA COLLECTION # OPTIONS # REDUCTION SETTING S # COLLECTOR # LEICA # CUSTOM IZE # NEW
ICON:
You may add a new Leica code that does not already exist in the list.
Figure C-2 New Leica Code Dialog Box
New Leica Code Dialog Box Definitions

Option Function
Code Type the code value in the edit field. This code is always located at the end of the first
word of a code block in the Leica raw format.
Activity Select the SDMS surveying activity for the code. You may select from any of the activities
in the drop list. The surveying activity may be a side shot, occupied station, foresight, etc.
The activity may be specified as ‘continue previous’, which means that information
entered in this code will be a continuation of the last surveying activity that was entered in
the file. This information may be related to the staff height, line work, etc. The activity also
corresponds to a Field Value that may be entered when collecting data.
See EP SDMS, which begins on page 209.
Info This displays the information block value. A code may have up to eight information blocks.
Tag This displays the data tag that is used to associate with the value in the information block.
Decimal This displays the location where the decimal point is inserted when reading a value from a
Leica raw file. This value is counted from the far right of the word to the left. For example,
21.104+10115377 is a value that may be associated with the HZ data tag (Horizontal
circle reading). The decimal location is 5, so the circle reads 101 degrees, 15 minutes,
37.7 seconds.
126 Data Collection

QuickSteps
To add a new Leica code to the list, follow the steps outlined below:
1. From Data Collection, select Options ! Reduction Settings.
2. Pick the Collector tab and select any of the Leica (WILD) formats from the drop
list of formats.
This displays the Leica Codes dialog box (Figure C-1 on page 124).
4. Click on the New Leica Code icon.
Appendix C: Leica
This displays the New Leica Code dialog box (Figure C-2 on page 126).
Codes
5. Type the code number in the Code edit field.
6. Select the surveying activity for the start of the code. You may select this from
the drop list of SDMS activities.
7. To add a data tag to an information block, highlight the information block on the
left.
8. Highlight the data tag on the right to associate with the label. Double-click on
the data tag, or click on the Add button.
9. To remove a data tag associated with an information block, double-click the
information block on the left or highlight the information block and click on the
Remove button.
10. Click on Apply to add the code to the Leica Codes list.
11. Click on Cancel when you are finished adding codes.
12. Click on Close in the Leica Codes dialog box.
13. Click on Cancel in the Reduction Settings dialog box.

Edit Data Tags
DATA COLLECTION # OPTIONS # REDUCTION SETTING S # COLLECTOR # LEICA # CUSTOM IZE
# EDIT DATA TAG S
You may edit the data tags used to process Leica raw files.
Figure C-3 Edit Data Tags Dialog Box
Edit Data Tags Dialog Box Definitions

Decimal This displays the location where the decimal point is inserted when reading a
value from a Leica raw file. This value is counted from the far right of the word
to the left. For example, 21.104+10115377 is a value that may be associated
with the HZ data tag (Horizontal circle reading). The decimal location is 5, so
the circle reads 101 degrees, 15 minutes, 37.7 seconds.
New Data Tag You may add a data tag to the list of data tags. Click on the New Data Tag icon
and add a new data tag.
Modify Data Tag You may modify a data tag. Highlight the data tag to modify and click on the
Modify Data Tag icon.
Delete Data Tag You may delete a data tag from the list. Highlight the data tag to delete and click
on the Delete Data Tag icon.
Print Data Tag You may print the list of data tags to a file or directly to the printer.
128 Data Collection

COLLECTORS
AND FORMATS APPENDIX
In this appendix:
GEODAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Leica (WILD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Maptech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Nikon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Pentax and Corvallis . . . . . . . . . . . . . . . . . . . . . . 176
Sokkia (Lietz) . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Surveyor’s Module (SMI) . . . . . . . . . . . . . . . . . . 188
D
Trimble/Tripod Data Systems (TDS) . . . . . . . . . . 191
Topcon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Zeiss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Appendix D: Collectors and Formats 129

GEODAT
Geodimeter total stations have the ability to run customized sequences to collect survey
data called User Defined Sequences, or UDS’s. These UDS’s may be used as templates
for customizing your own system to meet your specific needs.
In order to optimize the use of the raw information recorded with the Geodimeter
instrument, Data Collection requires that the sequences that are recorded are compatible
with the Eagle Point SDMS minimum requirements. See EP SDMS, which begins on
page 209.
! If you desire to record and review the raw instrument data, it is recommended that you
collect the survey information using the recommended UDS’s described in this section as
examples.
! If coordinate information is all that is desired, the default UDS’s on the GEODAT may
suffice.
Preparation
Some of the following UDS's will use programs from the Geodimeter. Listed in this
document are recommended recording sequences for the built-in programs. SetOut and
AngleMea programs need to be modified to contain information in the proper order for
processing in Data Collection.
To change the recording order to 5, 7, 8, 9, 40, 41, 42, 67, 68, 69 for P23, choose SetOut
from the program menu, then select 0 for config, then view, create, then enter the
appropriate label numbers, and add a blank at the end to finish the configuration. For more
information on the programs for the Geodimeter, refer to your Geodimeter documentation
for further explanation.
GEODAT Definitions
GEODAT Recorded Labels EP-SDMS Definition

Label # Tag Example
5 PN: 1 Node ID; Point #
7 HZ: 0.0034 Meaned Horizontal
8 VT: 89.1231 Meaned Vertical
9 DS: 1045.56 Slope Distance
67 YC: 6000.00 Northing Coordinate
68 XC: 5000.00 Easting Coordinate
130 Data Collection

GEODAT Definitions

Label # Tag Example
69 ZC: 129.235 Elevation
40 EY: 0.05 Error in the Northing
41 EX: 0.01 Error in the Easting
42 EZ: 0.008 Error in the Elevation
All activities (AC:) need to be entered as capital letters (e.g., AC:OS, not AC:os). See EP
SDMS, which begins on page 209.
To change the recording order to 7, 8, 9, 24, 25, 17, 18, 19, 16 for P22 choose AngleMea
from the program menu, then select 0 for config, then view, create, then enter the
appropriate label numbers, a blank enter at the end will finish the config.
Reordering Definitions
Appendix D: Collectors
Label # Tag Example
and Formats
7 HZ: 0.0034 Meaned Horizontal
8 VT: 89.1231 Meaned Vertical
9 DS: 1045.56 Slope Distance
24 H1: 23.0158 Horizontal in Face: 1
25 V1: 90.4051 Vertical in Face: 1
17 H2: 203.0204 Horizontal in Face: 2
18 V2: 270.3001 Vertical in Face: 2
19 EV: 0.1020 Error in Vertical
16 EH: 0.0015 Error in Horizontal
Some labels have been modified or changed so that you can collect data in the field that is
easily translated into Data Collection. The suggested labels follow. These labels are
default in Data Collection and may be modified.

Each label in the following table is denoted by an asterisk * when it is listed in one of the
sample UDS’s contained in this document. Use programs 40 and 41 to redefine the
following labels:
Suggested Labels
Prompt Label Activity (alpha) Activity (numeric)

RunP22 88
Comment 89
KeynPR 90 AC:PR AC:20
KeynOS 91 AC:OS AC:19
KeynBS 92 AC:BS AC:2
KeynCC 93 AC:CC AC:3
KeynSS 94 AC:SS AC:27
Weather 95
Descrp 96
KeynFS 97 AC:FS AC:11
Owner 98
RunP23 99
Most of these labels are used as ‘shot separators,’ or to denote a change in surveying
activity (i.e. from foresight (FS) to occupied station (OS) or to sideshot (SS)). You may use
label 61 instead of the ‘Keyn’ labels. Label 61 is a general shot separator, and could
replace the KeynXX labels within your UDS’s. This would mean that the surveying activity
taken would be defined on label 61. Refer to sample UDS 12 for further information.
Collecting Data
Provided are some sample UDS’s that may be used to integrate with Data Collection.
Before recording any information from the instrument, run UDS 1 to include basic job
information.
UDS – 2 SETUP
For entering a setup sequence, follow the example provided for UDS 2. This contains the
occupied station point number, instrument height, and backsight information. For each
sequence, or sets of angles that are recorded, UDS 2 would be utilized.
132 Data Collection

! If this were the initial setup of the job, a coordinate value of the occupied station would be
required for the job to process correctly. This value may be entered using UDS 8 Control
Entry explained below, or by having the Node ID of the occupied station exist in the
project.
Sample of UDS – 2 SETUP
Prompt Label # Label Type Note EP-SDMS Tag Example

KeyOS 91* 3 Accept “OS” AC:OS or AC:19
Pno 5 1 Occupied pnt# PN:2
IH 3 3 Enter height of HI:5.25

instrument
KeynBS 92* 3 Accept “BS” AC:BS or AC:2
Pno 5 1 Backsight Point # PN:1
HorRef 21 2 0.0 to 0 in BS AZ:0.0
HA 7 0 Shot to Backsight HZ:0.0000
and Formats
VA 8 0 Shot to Backsight VT:89.1234
SD 9 0 Shot to Backsight DS:1045.56
HA 7 8 Display Only
VA 8 8 Display Only
SD 9 8 Display Only
End 79 6 Return to P0
UDS 2 is very similar to Program 20 that may be defined as a default on the GEODAT
instrument. It is recommended that you use UDS 2 because of the addition of labels 91
and 92 that help designate what surveying activity is being performed.
Label 21 is the horizontal reference azimuth value. Depending upon your use of this
feature in the field, this may be set up in one of two ways.
If you are using Label 21 to read a true azimuth direction to a backsight, then the correct
data tag to use with this UDS is the azimuth (AZ:) data tag. You may want to set the circle
of the gun to a specific azimuth reading and sight the backsight, aligning yourself in the
field with the actual azimuth.
If you are using Label 21 to record the circle reading with out setting the circle on the gun
to zero, then the proper data tag for this purpose is the horizontal circle reading (HZ:) data
tag.

You do not need to automatically zero the instrument when sighting the backsight, as the
circle reading taken when sighting the backsight will be recorded and used for this setup.
UDS – 3 CONTROL CHECK

While recording large amounts of topography from a single setup, or if it is not known if the
setup may have been disturbed, you may run UDS 3 to confirm the backsight orientation
or a recorded measurement to a known point.
Sample of UDS – 3 CONTROL CHECK

KeynCC 93* 3 Accept “CC” AC:CC or AC:3
RunP23 99* 8 Reminder to run P23
This location will be recorded in the file, but the shot will not be used in the calculation of
the location of the shot taken. It is recorded so that a check to the known point can be
verified. If the data does not match up within a reasonable tolerance, then resurveying the
information may be in order.
UDS – 4 UTILITY WITH LINE WORK

To record power, sewer, or other service or utility lines, you may use UDS 4 to record the
information. This UDS includes recording the owner of the utility, a description, and the
line name using label 66.
Sample of UDS – 4 UTILITY WITH LINE WORK

KeynSS 94* 3 Accept “SS” AC:SS or AC:27
Pno 5 4 Use Auto PN:1004
Pcode 4 3 Point/Feature Code FE:ELMH
Lname 66 3 Figure/Line Name FG:E1
Descrp 96* 3 Point Description PD:112kv
Owner 98* 3 Owner Name OW:Iowa Partner
SH 6 3 Use Auto SH:5.000
HA 7 0 Shot to Sideshot HZ:123.2534
134 Data Collection

Sample of UDS – 4 UTILITY WITH LINE WORK

VA 8 0 Shot to Sideshot VT:91.1234
SD 9 0 Shot to Sideshot DS:245.91
Pno 5 8 Display Only
SH 6 8 Display Only
ELE 39 8 Display Only
End 79 6 Loop to start of this

UDS
! If your data collector has alpha capability, you may enter the Field Code and line
information all on label 4, Pcode and omit the need for Label 66. This would utilize the
standard method of collecting line work as outlined in Data Collection Concepts, which
begins on page 1.
UDS – 5 UTILITY FEATURE
and Formats
To record lamp posts, monuments or other features that do not need to be connected with
line work, you may use UDS 5 to record the features. This UDS is identical to UDS 4
except for the omission of label 66 (line name).
Sample of UDS –5 UTILITY FEATURE

Descrp 96* 3 Point Description PD:112kv
Owner 98* 3 Owner Name OW: Iowa Partner

Sample of UDS –5 UTILITY FEATURE

SH 6 8 Display Only

UDS
UDS – 6 TOPOGRAPHY WITH BREAKLINES

To record breaklines such as gutter lines, ditch lines, catch lines, centerline, edges of
pavement, building corners, etc., use UDS 6 to record the information.
Sample of UDS – 6 TOPOGRAPHY WITH BREAKLINES

Lname 66 3 Figure/Line Name FG:BC1-
Descrp 96* 3 Point Description PD:Brick
SH 6 8 Display Only

UDS
136 Data Collection

! Any UDS that is designed to record line work may also include label 65 (Geometry). This
will allow you to enter a numeric designator. You may set your designators to be the
GEODAT default designators in Data Collection,.1, .2, .3, and .4 respectively. You can
then record line work and features using these designators. To do so, insert the designator
label following label 66 as follows:
Sample of Label 65 (Geometry)

Lname 66 3 Figure/Line Name FG:BC1-
Desig 65 3 Line Designator GM:1
Descrp 96* 3 Point Description PD: Brick
UDS – 7 TOPOGRAPHY
To record general topographic features without lines, use UDS 7 to record the information.
and Formats
Sample of UDS – 7 TOPOGRAPHY

KaynSS 94* 3 Accept “SS” AC:SS or AC:27
Pno 5 4 use Auto PN:1007
Descrp 96* 3 Point Description PD:Oak 24*
SH 6 8 Display Only

UDS
! This UDS is identical to UDS 5 less the Owner data tag.

UDS – 8 CONTROL ENTRY
If you have a known coordinate value for the initial occupied station, backsight, or any
control points in the traverse, you may enter the coordinate values using UDS 8.
Sample of UDS – 8 CONTROL ENTRY

KeySS 94* 3 Accept “SS” AC:SS or AC:27
Pno 5 4 Use Manual PN:22
N 37 1 Northing of point YC:5000.000
E 38 1 Easting of point XC:5000.000
ELE 39 1 Elevation of point ZC:203.25
Pcode 4 3 Point/Feature Code FE:IP

UDS
! If you have not entered the coordinate value for the initial setup point, then the Node ID
may exist in the project. If not enough information is provided to process the job file, you
will be prompted to enter a Node ID, type a coordinate value, or graphically select a point
in the CAD graphic.
UDS – 9 TRAVERSE AHEAD

To record a measurement to the next setup point, run UDS 9.
Sample of UDS – 9 TRAVERSE AHEAD

KeynFS 97* 3 Accept “FS” AC:FS or AC:11
Pno 5 4 Foresight point # PN:4
Pcode 4 1 Point/Feature Code FE:IR.TRAV
RunP22 88* 8 Reminder to run P22
Immediately following UDS 9 will be UDS 2 at the new setup location to re-orient the
instrument. You may run several iterations of UDS 9 and 2 to record multiple sightings
between the foresight and the backsight.
138 Data Collection

UDS – 10 CROSS-SECTIONS
To rapidly record existing road cross-section patterns, you may utilize the Data Collection
Cross-Section Patterns.
The name of the pattern is entered as the line name in label 66.
Sample of UDS – 10 CROSS-SECTIONS
Prompt Label Label Type Note EP-SDMS Tag

KeyinSS 94 3 Accept “SS” AC:SS or AC:27
Pcode 4 3 Point Code/Feature FE:EP
Lname 66 3 Figure/Line Name FG:XC=
Descrp 96 3 Point Description PD:EPL
SH 6 3 Staff Height SH:4.5
HA 7 0 Shot to SS HZ:123.4532
VA 8 0 Shot to SS VT:91.1205
and Formats
SD 9 0 Shot to SS DS:313.07
SH 6 8 Display Only
End 79 5 Loop to start of UDS
UDS 10 uses the cross-section designator (default value is ‘=’) at the Lname prompt. You
may establish an alpha character or other character for the designator. You may also
insert label 65 immediately following label 66 to enter a numeric designator to represent
the cross-section pattern (i.e., .6).

UDS – 11 COMMENT
To enter pertinent information to the job file related to a surveyed point or points, you may
run UDS 11.
Sample of UDS –11 COMMENT

Comment 85* 1 Enter Comment CM:Station 4+50
End 79 5 Loop to Start
UDS – 12 ACTIVITY LABEL

To key-in a change of activity on the fly, or to separate shots or surveying activities, you
may run UDS 12. UDS 12 may be run instead of specifying the activity within each UDS.
This will allow you greater flexibility as to what activity you want to run, and may work
better with your current method of collecting data. This also may be advantageous when
the activity changes frequently.
Sample of UDS – 12 ACTIVITY LABEL
Activity Label # Label Type Note EP-SDMS Tag Example

Activity 61 1 Enter Activity AC:11 (foresight)
After the activity is saved you may run any built in program to produce the required results.
If label 61 is utilized as a shot separator, use the Data Collection codes to define what
activity needs to be processed. Enter the numeric activity as follows in the table below:
Numeric Values
Activity Description Geodimeter Eagle Point

OS Occupied Station 0 19
BS Backsight 1 02
FS Foresight 2 11
SS Sideshot 3 27
SR Station Resection 4 26
EC Elevation Control 7 08
140 Data Collection

Numeric Values
Activity Description Geodimeter Eagle Point

CC Control Check 9 03
PR Project Information 10 20
If you have already created files that have utilized the Geodimeter types of shot
separators, you will need to replace the following common occurrences in the Geodimeter
file:
If you are going to edit the instrument file, replace the following common changes:
61=0 replace with 61=19
By way of editing the formatted file, select Global Edit from the Options menu and change
the following:
AC:0 to AC:OS
AC:AA to AC:BS
and Formats
AC:CC to AC:S
Line Work (Recommended for Non-Alphanumeric

Instruments)
One method does not require the need for alpha or extended characters. For instruments
that are relatively difficult to enter alpha or extended characters for designators, you may
use label 66 and 65 for line work entry. Label 66 is assigned to the FG: (Figure) data tag,
and label 65 is assigned to the GM: (Geometry) data tag. See EP SDMS, which begins on
page 209.
! Both the FG: and the GM: data tags may be assigned to any label.

You may use the Geodimeter default values for designators, and set the remaining
designators as follows:
Designators
Description Designator Example

Shot on a line .1 66 = 10
65 = .1
Stop line .2 66 = 10
65 = .2
Shot on a curve .3 66 = 10
65 = .3
Close line .4 66 = 10
65 = .4
Join last shot .5 66 = 10

65 = .5
Bearing close .6 66 = 10
65 = .6
Cross-section .7 66 = 10
65 = .7
! You may change the designator to be any extended character, alpha character or even
numeric value.
! The only time a stop line designator is required is when the same line name is used to
start in a different location. The lines will automatically connect throughout the file without
the entry of a stop designator.
Line Work (Recommended for Alphanumeric Instruments)

The second method involves the used of alpha or extended characters entered on the
same label as the line name. The default label is 66, which is assigned to the FG: data tag.
The draw designator is not used with this label, as it is assumed to be a shot on a line.
Special designators may follow this line name, as well as a draw designator to signify
more than one line to be processed through the same point.
142 Data Collection

The default designators are as follows when using label 66:
Label 66 Default Designators
Description Designator Example

Shot on a line no designator 66 = 10
Stop line period “.” 66 = .10
Shot on a curve minus sign “-” 66 = 10-
Close line plus sign “+” 66 = 10+
Join last shot asterisk “*” 66 = 10*
Bearing close pound sign “#” 66 = 10#
Cross-section equal sign “=” 66 = 10=
When taking a shot on a line, type the line name with no designator.
When taking a shot to stop a line, type a period ‘.’ before the line name.
When taking a shot on a curve, type a minus sign ‘-’ before or after the line name.
and Formats
When taking a shot using any of the other special designators, type the designator after
the line name.
! You may change the designator to be any extended character, alpha character or even
numeric value. It is recommended that the draw designator remain unchanged from a
decimal ‘.’, as the stop designator is treated as a double designator, or ‘..’.
! Since a line name appearing in a FG: data tag assumes that a line is to be drawn, the
draw designator is not needed, however the stop designator is still a ‘double draw
designator.’
! If a numeric designator is used to replace one of the special designators (say “0” for
bearing close), it may be confusing to the user recording the line information.
! The only time a stop line designator is required is when the same line name is used to
start in a different location. The lines will automatically connect throughout the file without
the entry of a stop designator.
Troubleshooting
Reducing the files into Eagle Point may cause processing errors, line work not showing
up, or data placed in the project with incorrect orientation.

You can avoid all of these problems if you are using correct UDS’s for collecting raw
survey information and processing line work.
Geodimeter information can generally be read correctly using the most basic pre-installed
UDS’s. If you do not desire to change the UDS’s on your surveying equipment, you can
make the changes easily within Data Collection so that the data is reduced correctly.
Problem: Selected job does not reduce.
Solution: You may experience problems processing Field Codes that are greater than 10
characters or that have excess line work. For example, if you enter 1.1 in the Pcode edit
field (typically label 4), then what might occur is Field Code 1 will be placed and connected
up with line name 1. If you are preprocessing your Geodimeter files through a different
software package (GSS, GeoTool, etc.), this same sequence might write out
manhole.sewer to the raw file. Data Collection might not be able to handle the length of
the entry in the FE: (Pcode) edit field.
You may globally edit the FE: (Feature or Pcode) data tag in the formatted file to be a PD:
(Point Description) data tag, or you can modify label 4 and change it from a FE: data tag to
a PD: data tag. The only limiting factor is that you can have only one PD: per activity, so
you will not be able to enter a different description from the Field Code in the field.
QuickSteps
To change your FE: data tag to a PD: data tag in the formatted file, complete the following
steps:
1. Select Products ! Data Collection ! Jobs ! Edit Formatted File.
! If you have problems loading the formatted file editor, please consult the Installation guide
for suggestions on installing the Field Book Editor.
2. Select Global Edit From the Edit menu.

3. Type FE for the data tag.
4. Turn on the Change Tag To option and type PD.
5. Turn off the Field Value option and click on OK.
6. Exit and save changes. You may now reprocess any Geodimeter job back into
the project.
If the job is now able to process, you may permanently resolve the processing problem by
performing the following steps:
1. Select the Options ! Settings.
2. On the Collector tab, select a Geodimeter format and click on the Customize
button.
The GEODAT Labels dialog box (Figure B-1 on page 118) displays.
144 Data Collection

3. Highlight label 4 (Pcode) in the first column of Geodat labels and click on
Modify.
4. Highlight the PD: data tag and click on OK.
If the file is still not able to process, contact Eagle Point or your data collector’s technical
support. Be prepared to send the file via email.
Problem: Proper use of the Horizontal Reference Azimuth function needs to be defined.
Solution: If you use label 21 – Horizontal Reference Angle in the field, you may need to
modify the Data Collection label. The Horizontal Reference Angle is typically the
horizontal circle reading on the instrument when backsighting a point. If you typically leave
label 21 blank, then the instrument reads the circle reading and records it for the reference
angle reading. For this situation, you may need to change label 21 in Data Collection
from the Back Circle (BC:) data tag to the Horizontal Circle (HZ:) data tag.
If you use label 21 or other label to specify an initial backsight direction, you may use the
Azimuth (AZ:) data tag to do so. The AZ: data tag when recorded within a backsight (BS:)
data tag may be used to establish the initial orientation of a traverse.
Depending on your use of label 21, proceed through the following steps and replace the
BC: data tag with either an AZ: or an HZ: data tag.
and Formats
QuickSteps
To add the AZ: data tag to the list, proceed through the following steps:
1. Select Products ! Data Collection ! Options ! Settings.
button.
3. Click on the Edit Data Tags button.
The Edit Data Tags dialog box (Figure B-3 on page 120) displays.
4. Click on New.
5. Type (in Caps) AZ for the data tag, AZ for the prompt, and AZIMUTH for the
description and click on OK.
6. Click on OK on the Edit Data Tags dialog box.
To edit label 21, proceed through the following steps:
1. Highlight label 21 in the first column of GEODAT labels and click on Modify.
2. Highlight the HZ: or AZ: data tag (which ever is correct) and click on OK. You
may now reprocess any Geodimeter job back into the project.

Problem: Survey data not oriented properly.
Solution: The Geodimeter calculates coordinate information and stores this along side of
the raw survey information. Data Collection reads both, however, there is a priority
established for each when processed.
Files that may have been created using improper UDS’s may have processed correctly in
the past because the calculated coordinates were used to place the data in the project.
Since the coordinates were already calculated, Data Collection did not need to process
the raw data. Data Collection has since been modified to prioritize the raw data
occurrences over the coordinate data for the same shot. Therefore, if the survey data does
not process correctly, the raw data may not have been collected properly to process in
Data Collection.
! If you are not using the recommended UDS’s, it is likely that the raw information will not
read correctly within Data Collection.
To use the calculated coordinates over the raw information from the Geodimeter, you will
need to ‘demote’ the raw information for each point. To do so, you can change each
occurrence of a HZ: (Horizontal Circle reading) to a HH: (Calculated Horizontal Circle
reading).
QuickSteps
To add the HH: data tag to the list, proceed through the following steps:
1. Select Products ! Data Collection ! Options ! Settings.
button.
3. Click on the Edit Data Tags button.
The Edit Data Tags dialog box (Figure B-3 on page 120) displays.
4. Click on New.
5. Type (in Caps) HH for the data tag, HA for the prompt, and HORIZONTAL ANGLE
for the description and click on OK.
6. Click OK on the Edit Data Tags dialog box.
7. Highlight label 7 in the first column of the GEODAT labels and click on Modify.
8. Highlight the HH data tag and click on OK. You may now reprocess any
Geodimeter job back into the project.
! This will not affect keyed-in coordinate information.
146 Data Collection

Problem: Cannot download from the collector, or upload to the collector.
Solution: If you have tried the suggestions for troubleshooting data collectors, you can
verify that the communication parameters on the Geodimeter are set correctly. There are
specific parameters that need to be set on the instrument.
Run Program 51 on the Geodimeter and verify the following parameters:
Parameters
Line Parameter
1 9600
2 0
3 8
4 1
5 10 (time-out)
6 0
7 1
and Formats
8 17
9 19
10 0
11 0
12 0
13 0
14 1.13
15 0
16 1.04

Leica (WILD)
There are several different types of software that may be supported when using a Leica
instrument. If you are familiar with H.A.S.P., ETI, WILDsoft, or LISCAD, there are code
structures that are similar to what you may already be familiar with so that you can
integrate the surveying products in Eagle Point more quickly into your surveying routine.
For the purpose of demonstration, the codes that are used in the following examples
closely resemble that of the WILDsoft code structure.
Preparation
Data Collection currently works together with all the Leica/WILD instruments used as
total stations or data collectors. These instruments collect and store information using the
same structure, which allows you to use the same set of codes, regardless of the type of
instrument collecting the data.
The collectors listed in the communications include the GRE4, GIF10 and GIF12 devices.
Many of the other collectors and instruments are also supported through the GRE4 setting
in Data Collection.
The raw data in a Leica format file is structured by a series of lines of information. Each
line is termed a block, and within each block there are several smaller blocks of
information, or words.
Block: A group of information containing up to nine words, or portions of data in a raw
data file. It appears in a raw data file as one line of text. A block may be either a measure
block or a code block.
Block Example
110009+00000684 21.104+12223510 22.104+09136170 31..01+00067480 51....+0001+003
Word: A portion in a block composed of 16 characters (15 and a space) that contains a
single bit of information. This information may be a point number, horizontal angle,
instrument height, etc.
Word Example
110009+00000684
Collected information is organized into two different types of blocks: Measure blocks and
Code blocks. The measure blocks contain raw measured data collected directly from the
instrument. The code blocks contain user input information that is used as instructions for
the measure blocks. Code blocks may also be used to record information such as an
instrument height, side shot, point description, etc.
148 Data Collection

Measure Block
The number 11 in the first two positions of the first word signifies a block that contains
measurement information. The first word of a measure block also includes the point
number in the data portion of the word. The standard format of a measure block is usually
as follows:
Measure Block Example
Point Number INFO 1 INFO 2 INFO 3 INFO 4
SDMS Tag PN:684 HZ:122.2351 VT:91.6317 DS:674.80 CM:1+003
Definition Point Number Horizontal Angle Vertical Angle Slope DIstance Inst. Constant
Raw 110009+00000684 21.104+12223510 22.104+09136170 31..01+00067480 51....+0001+003

information
In this example of a block the point number is 684. The remaining words store information
as the instrument recorded a shot.
! Data Collection will set the Node ID (point number) if there is a Node ID (PN:) data tag in
the code list. If the Node ID is not set anywhere in the file using the PN:, Data Collection
and Formats
will use the Node ID value set in the first word of a measure block as shown above.
Code Block
The number 41 in the first two positions of the first word signifies a block that contains
information that was coded on the instrument. The first word of the code block also
includes the instrument code that was recorded on the instrument. The remaining words
store additional information or instructions that help describe the inputted instrument code.
The format of the code block depends upon what the code is designed to record. This
example shows Code 11, which is a record of coordinates and a description:
Code Block Example
Code/Function INFO 1 INFO 2 INFO 3 INFO 4
SDMS Tag AC:SS YC:52400 XC:500000 ZC:123000 PD:100000
Definition Code Number Northing Easting Elevation Description

Coordinate Coordinate
Raw 410002+00000011 42....+00052400 4....+00500000 44....+00123000 45....+00100000

Information

Code 11 was inputted and recorded in the first word of the block. Code 11 is listed in the
Leica Survey Codes listing as a sideshot activity (AC:SS). Each information field for code
11 also has a data tag associated with it. Data Collection will read the second word, or
information field 1, as a Northing coordinate, word three as an Easting coordinate, word
four as an elevation, and word five as a point description.
Each code is defined by a function and an association to one or more data tags in the
information fields. A data tag is a two character string that designates a specific property
to the current activity. See EP SDMS, which begins on page 209.
Collecting Data – Using codes based on WILDsoft

Eagle Point’s default code structure is based on the WILDsoft method of coding. Here is
a sample of the steps to be performed on the instrument when recording information
based on the default Leica Codes:
Code 1: Project Setup

This code is designed to record the basic project information. The information may include
the project name, operator’s name, weather, instrument ID, date, etc. If you are using
code 1 for recording backsight information, see Collecting Data – Customizing Codes on
page 165.
1. Press CODE on the instrument.
2. Type 1 and press ENTR.
3. Type the project name and press ENTR.
4. Type the operator’s name and press ENTR.
5. Type the instrument ID or serial number and press ENTR.
6. Type today’s date and press ENTR then REC.
Code 11: Control Coordinates

This code is for entering known coordinate information. You may use this code to enter the
coordinate values of your initial setup points, or other control points that may be located as
check shots or benchmarks.
3. Type the point number and press ENTR.
4. Type the easting coordinate and press ENTR.
5. Type the northing coordinate and press ENTR.
150 Data Collection

6. Type the elevation coordinate and press ENTR.
7. Type the point description (optional) and press ENTR then REC.
Code 13: New Target Height

This code is for making a change to the staff height for one or more shots. If you are
changing the staff height for the next measurement only, proceed through the following
steps:
3. Switch the setting on the instrument from a ‘+’ to a ‘-’.
4. Type the staff height (no decimals) and press ENTR.
5. Aim the instrument at the sideshot and press ALL to record measurements.
! To apply the change in staff height to more than one shot, leave the setting on the
instrument to a ‘+.’ The ‘-’ is a temporary setting so that the code block applies to the
following measurement only.
and Formats
! If you are processing a vertical offset (code 16) or a length offset (code 17), proceed
through similar steps.
Code 2: Instrument Setup

This code allows you to enter the occupied station point number and instrument height. If
you want to also enter the backsight point number, enter the value in information field 4 as
outlined in the following steps:
3. Type the point number of the occupied station and press ENTR.
4. Type the height of instrument (no decimals) and press ENTR.
5. Type the point number of the backsight and press ENTR then REC.
Code 52: Backsight

This code may be used to enter the backsight if it is not recorded in code 2.
3. Type the point number of the backsight and press ENTR.

4. Type the target height (no decimals) and press ENTR.
5. Type the point description (optional) of the backsight and press ENTR then
REC.
6. Aim the instrument at the backsight and press ALL to record measurements.
Code 3: Foresight
This code is used for traversing to the next occupied station, or to record the closing
orientation of the traverse. When entering this code, it is assumed that you are going to
follow this code with a measurement to the foresight. If you are recording a set of angles,
refer to Collecting Data – Traverse on page 156.
3. Type the point number of the foresight and press ENTR.
4. Type the target height (no decimals) and press ENTR.
5. Type the point description (optional) of the foresight and press ENTR then REC.
6. Aim the instrument at the foresight and press ALL to record measurements.
Code 32: Radial Sideshot

This code is entered at the start of a sideshot sequence. You can define the starting point
number for the recorded sideshots and the current staff height.
3. Type the point number of the first sideshot and press ENTR.
4. Type the target height (no decimals) and press ENTR then REC.
5. Aim the instrument at the backsight and press ALL to record measurements.
Code 99: Sideshot

This code is entered to record a feature in the field. You may designate a Field Code, line
name and geometry designator if applicable.
3. Type the Field Code of the sideshot and press ENTR.
4. Type the line name and press ENTR.
152 Data Collection

5. Type the geometry of the line (optional) and press ENTR then REC.
Keep pressing ALL until the Field Code, line name or geometry changes.
Code 100: Sideshot

This code may be used to change a description for the following shots. Each time Code
100 is recorded, the description is applied to each sideshot recorded until the description
is changed.
3. Type the point description and press ENTR then REC.
Keep pressing ALL until the description changes.
Collecting Data – Node ID
Data Collection will set the Node ID (point number) if through processing the file there is
and Formats
a Node ID (PN:) data tag located somewhere in the file. Data Collection automatically
increments the Node ID for each measure block recorded starting immediately following
the last code block recorded with a PN: data tag.
! When taking shots to previously recorded instances, such as recording a set of angles, be
sure to re-enter the Node ID for the shot before retaking the shot.
You may use the measure block for the point number if it is a coordinate file. Since the PN:
data tag does not exist in a coordinate file, the point number in the measure block will be
used as the Node ID value.
Node ID Example
1 110023+00000020 81..11+05331036 82..11+05325161 83..11+00006388
2 110024+00000021 81..11+05329587 82..11+05329922 83..11+00006862
3 110025+00000022 81..11+05326204 82..11+05333273 83..11+00000702
Each of these measure blocks has point number values (20, 21 and 22) as well as
coordinate values. If the entire file is made up of measure blocks, then the Node ID is read
from each measure block in the file.
! If you are bringing files in that have no record of the PN: being set in the file, Data
Collection will use the Node ID value set in the first word of a measure block.

Collecting Data – Entering Decimals on the Instrument
Typing decimal values on the instrument to designate staff heights, instrument heights or
coordinate values is not supported. Values must be entered as an integer value to be
processed correctly.
! If you are a new user to Leica, the older versions required that values be entered without a
decimal value. The decimal location was determined by the type of value being entered.
Example of a word that contains decimal values
1 410002+00000001 42....+00000999 43....+00004.74 44....+00004.72 45....+00023025
Proper method of the same word without decimals
2 410002+00000001 42....+00000999 43....+00004740 44....+00004720 45....+00023025
QuickSteps
To establish decimal location for a particular data tag, proceed through the following steps:
1. Open a project in Eagle Point and select Products ! Data Collection ! Options
! Reduction Settings.
2. On the Collector tab, select the Leica GIF10, Leica GIF12, or Leica GRE4 option
from the drop list of supported formats.
4. Click on the Edit Tags button.
5. Highlight the data tag that you want to modify. Select instrument height (IH:) as
an example.
6. Click on Modify.
The value from the Precision drop list shows the location of where the decimal point will be
located when processing a value for this data tag. For the instrument height (IH:), the data
tag will show a decimal location of +12345.678 which means that the decimal is
automatically placed three spaces from the left. The staff height (SH:) data tag is set up
the same way.
Collecting Data – Field Codes

Field Codes may be established by adding a Feature (FE:) data tag to one of the codes in
the Leica Code list (See Leica Codes, which begins on page 123).
154 Data Collection

The Field Code will then be applied to each successive shot recorded until the Field Code
value is recorded as a different value.
If a recorded code is not defined in the Leica Code list, the code value is treated as a Field
Code read from the Node (Field Code) library (See Node (Field Code) Library in the Eagle
Point Menu manual). If the Field Code does not exist in the Node (Field Code) Library,
then the default Field Code set in the Reduction Settings will be used to process the file.
Reduction Settings Example
410008+00000135
This sample code block has a code value of 135. This code value is not listed in the Leica
Code listing, so Data Collection will process Field Code 135 from the Node (Field Code)
Library for the measurement immediately following this code block. If Field Code 135 does
not exist in the Node (Field Code) Library, then the default Field Code in Data Collection
will be placed instead.
Collecting Data –Temporary Shots
At certain times it is necessary to raise or lower the staff height for only one shot. Other
and Formats
times there may be one different Field Code out of a long string of shots that have the
same Field Code or description.
If you are changing the value of a staff height, Field Code or description for only the next
shot, you may record the respective code with a minus (-) in the code block.
Temporary Shots Example
1 110035+00001520 21.324+16445343 22.324+09001437 31..20+00359823 51....+0000+000
2 410036-00000050 42....+00004150
3 110037+00001521 21.324+16606423 22.324+08943177 31..20+00360261 51....+0000+000
4 110039+00001522 21.324+16134557 22.324+08952002 31..20+00356371 51....+0000+000
5 110040+00001523 21.324+16103456 22.324+08950403 31..20+00345655 51....+0000+000
Code block 2 will change the staff height of the measurement of measure block 3. The
information field 1 of code block 2 is a new staff height value, but is only applied to the
measure block immediately following the code block. Measure block 4 will use the
previously defined staff height value.

Collecting Data – Traverse
When recording traverse information using sets of angles (such as with code 3), it is
required that the point number for each shot be recorded. For example, if you are
recording a sequence of shots that involves sighting the backsight (Face 1 or normal
orientation), turn to the foresight, inverting the scope and turning to the foresight (Face 2
or inverted position), and finally turning to the backsight, between each shot you will need
to record the point number before recording the shot.
If you are a former user of WILDsoft, you may be familiar with the operation of codes 3, 31
and 33 for recording multiple records to the same shot. WILDsoft increments the point
number on every measure shot except for those taken following a code 3, 31, or 33. Using
these codes, the point number is hard-coded not to increment.
Data Collection is entirely user-definable and does not distinguish between these codes
for the purposes of incrementing the point number. Therefore, codes 3, 31 and 33 will not
work function the way they did in WILDsoft due to this difference in the structure of the
program. When recording each measurement in a set of angles, enter a code before each
measurement to reset the point number for the shot.
The following are some examples on how the codes may be used to work within your
current method of collection:
Code 3 (foresight) is used to record measurements between a backsight and a foresight.
Code 52 is used to sight the backsight, and set the point number for the backsight. You
would input a code 3 to specify the foresight and any changes to the staff height. One set
of angles between point numbers 1 and 3 might read as follows:
Traverse Example
1 410001+00000052 42....+00000001
2 110008+00000015 21.104+00000110 22.104+09429410 31..01+00118860 51....+0000+000
3 410001+00000003 42....+00000003
4 110008+00000016 21.104+07545520 22.104+09900090 31..01+00117970 51....+0000+000
5 410001+00000003 42....+00000003
6 110008+00000017 21.104+25545010 22.104+26058460 31..01+00000000 51....+0000+000
7 410001+00000052 42....+00000001
8 110008+00000018 21.104+17959480 22.104+26529370 31..01+00000000 51....+0000+000
156 Data Collection

! Notice the slope distances were not recorded while the instrument was in face 2 (or
inverted). If you have an instrument that has an offset EDM that does not sight the laser
coaxial with the sight, you may not want to record the distance while the instrument is
inverted. The error that may result would be enhanced to shots taken to sideshots, shots
that have a fair change in elevation, or shots taken in relatively close proximity with the
gun would have the highest degree of error. Data Collection will process the shot using
the distance value recorded from the first instance of the point number in the set.
! The target height is also assumed to have already been established earlier in the file.
Code 31 (sideshot) is used for multiple turns to a single point. After each measure code
recorded, the point number needs to be reset to the previous point number.
Face 1/Face 2 Shot Sequence on Point 12 Example
1 410001+00000031 42....+00000012
2 110008+00000016 21.104+07545520 22.104+09900090 31..01+00137970 51....+0000+000
3 410001+00000031 42....+00000012
4 110008+00000017 21.104+25545010 22.104+26058460 31..01+00138060 51....+0000+000
and Formats
Code 32 (radial sideshot) is used for recording sideshots in a radial sequence. The
following is an example of six sideshots recorded first in a Face 1 position, followed by a
Face 2 position. The starting point number is 100 for both series of shots.
Six Sideshots Recorded in a Face 1 Position Example
1 410001+00000032 42....+00000100 43....+00055000
2 110008+00000015 21.104+05611000 22.104+09429410 31..01+00118860 51....+0000+000
3 110008+00000015 21.104+12311000 22.104+09431460 31..01+00118860 51....+0000+000
4 110008+00000015 21.104+15611000 22.104+09428730 31..01+00118860 51....+0000+000
5 110008+00000015 21.104+21011000 22.104+09429410 31..01+00118860 51....+0000+000
6 110008+00000015 21.104+24511000 22.104+09429410 31..01+00118860 51....+0000+000
7 110008+00000015 21.104+31211000 22.104+09429410 31..01+00118860 51....+0000+000
8 410001+00000032 42....+00000100 43....+00055000
9 110008+00000015 21.104+05611000 22.104+09429410 31..01+00118860 51....+0000+000
10 110008+00000015 21.104+12317000 22.104+09431460 31..01+00138860 51....+0000+000
11 110008+00000015 21.104+15621000 22.104+09428730 31..01+00158860 51....+0000+000
12 110008+00000015 21.104+21034000 22.104+09429410 31..01+00168860 51....+0000+000

Six Sideshots Recorded in a Face 1 Position Example
13 110008+00000015 21.104+24541000 22.104+09429410 31..01+00178860 51....+0000+000
14 110008+00000015 21.104+31255000 22.104+09429410 31..01+00138860 51....+0000+000
! It is not important what face the instrument is in when a shot is taken because it is
automatically determined by reading the vertical angle.
! Code 33, in the form that it exists in WILDsoft, is not supported in Eagle Point. You would
simply use the method outlined for Code 3.
Collecting Data – Line Work (Recommended for Non-

Alphanumeric Instruments)
The default code for a start line in WILDsoft is a code 70. Data Collection generates line
work that is not specific to any particular code, but may be inputted as any code that is not
currently listed in the Leica Codes listing.
Default Implementation for a Code Not Entered in the Current List
SDMS Tag FE: FG: GM: FG: GM:
Definition Field Code Line Name Geometry Line Name Geometry
Raw 110002+00000089 42....+00000001 43....+00000000

information
The Field Code (FE:) is read directly from the Node (Field Code) Library. The line name
(FG:) represents the line name from the Data Collection Line Work library. The Geometry
(GM:) represents the Leica numeric geometry designator.
Listing of Geometry Designators
Line 0
Curve 1
Stop 2
Close 4
Bearing close 8
Cross-section 16
Joinlast 32
158 Data Collection

To record shots along a line, information field 2 needs to be either a zero value or left
blank. To record a shot along a curve segment, the value of information field 2 should be
1. The designator value may also be a combination of designators to produce more than
one effect. For example, if you wanted to end a line that was a shot on a curve, the
recorded designator would be 3.
! The stop line designator prevents a line of the same name to be connected automatically.
Recorded Designator of 3
Line Value 0
Curve Value 1
Stop line value 2
Recorded designator = 3
To collect existing ground cross-section information, use the cross-section designator. To

stop the line work before and intersection, the stop line designator would be added to the
last shots on the cross-section just before the intersection. You would then continue to
collect data after the intersection using the same format.
and Formats
Recorded Designator of 18
Cross-section value 16
Stop line value 2
Recorded designator = 18
Sample File that Includes Line Work Using Numeric Designators
1 410001+00000001 42....+00000100 43....+00000000 44....+00000101
2 410002+00000011 42....+00000100 43....+00500000 44....+00500000 45....+00100000
3 410003+00000011 42....+00000101 43....+00500000 44....+00545960 45....+00101390
4 410004+00000002 42....+00000100 43....+00005470 44....+00000000 45....+00000101
5 410005+00000003 42....+00000102 43....+00005000 44....+00000012
6 410006+00000070 42....+00000001
7 110007+00000684 21.104+12223510 22.104+09136170 31..01+00067480 51....+0001+003
8 110008+00000685 21.104+11253470 22.104+09034000 31..01+00092970 51....+0001+003
9 110009+00000686 21.104+08225440 22.104+09103570 31..01+00086340 51....+0001+003
10 110010+00000687 21.104+08413530 22.104+09045500 31..01+00113130 51....+0001+003

Sample File that Includes Line Work Using Numeric Designators
11 110011+00000688 21.104+06133060 22.104+09016340 31..01+00128050 51....+0001+003
12 410012+00000070 42....+00000001 43....+00000004
13 110013+00000689 21.104+04312080 22.104+09011540 31..01+00083680 51....+0001+003
14 410014+00000135 42....+00000002
15 110015+00000690 21.104+17752020 22.104+09056390 31..01+00091290 51....+0001+003
16 110016+00000691 21.104+12130160 22.104+08947410 31..01+00174580 51....+0001+003
17 410017+00000135 42....+00000002 43....+00000001
18 110018+00000692 21.104+11012480 22.104+09036130 31..01+00205890 51....+0001+003
19 410019+00000135 42....+00000002
20 110020+00000693 21.104+09949060 22.104+08836230 31..01+00210860 51....+0001+003
21 110021+00000694 21.104+06040250 22.104+09016170 31..01+00238320 51....+0001+003
In the above file, the first shot on a building is in measure block 7. The line name for the
building is set in the first information field of code block 6. This line name is “1”. The
geometry for the building line is “line” because there is no value entered for information
field 2 in code block 6.
The building line is closed as designated by the second information field of code block 12,
as the value for a close line designator is 4. This will close line 1 to the following
measurement recorded in measure block 13 to the initial shot on the building line in
measure block 7.
Starting with code block 14, code 135 is not defined in the Leica Code list. Data
Collection processes any code not defined in the Leica Code list as a Field Code and line
work. Information field 1 holds the line name 2, which will process the line according to the
information in the Data Collection Line Work library for line 2. Information field 2 has a
value of 1 which designates the geometry of line 2 as being recorded on a curve.
160 Data Collection

! If a line name is not defined in the Data Collection Line Work library, the lines will be
placed in the CAD graphic using the current CAD properties.
Figure D-1 Line Work Generated Using the Standard Method
and Formats
Collecting Data – Line Work (Recommended for Alphanumeric
Instruments)
Outlined here is an alternative method to collecting line work using Leica instruments. This
method involves using Field Codes, line designators and line names all entered on the
code line.
! This method is for total stations or collection devices with extended or alpha characters
available (i.e. “.”, “+”, “-” or alpha characters other than numbers). If your surveying
equipment does not have this capability, then use the numeric method inputting line work
information.
Sample File that Contains Cross-sectional Line Work Using the Code Block
1 410001+00000001 42....+00000100 43....+00000000 44....+00000101
2 410002+00000011 42....+00000100 43....+00500000 44....+00500000 45....+00100000
3 410003+00000011 42....+00000101 43....+00500000 44....+00545960 45....+00101390
4 410004+00000002 42....+00000100 43....+00005470 44....+00000000 45....+00000101
5 410005+00000003 42....+00000102 43....+000050000 44....+000000BC
6 410006+000000.1
7 110007+00000684 21.104+12223510 22.104+09136170 31..01+00067480 51....+0001+003

Sample File that Contains Cross-sectional Line Work Using the Code Block
8 110008+00000685 21.104+11253470 22.104+09034000 31..01+00092970 51....+0001+003
9 110009+00000686 21.104+08225440 22.104+09103570 31..01+00086340 51....+0001+003
10 110010+00000687 21.104+08413530 22.104+09045500 31..01+00113130 51....+0001+003
11 110011+00000688 21.104+06133060 22.104+09016340 31..01+00128050 51....+0001+003
12 410012+00000.1+
13 110013+00000689 21.104+04312080 22.104+09011540 31..01+00083680 51....+0001+003
14 410014+0000.XC=
15 110015+00000690 21.104+17730549 22.104+09045120 31..01+00078383 51....+0001+003
16 110016+00000691 21.104+17752200 22.104+09003570 31..01+00091277 51....+0001+003
17 110015+00000690 21.104+17810448 22.104+09045500 31..01+00106857 51....+0001+003
18 110016+00000691 21.104+13548501 22.104+09013130 31..01+00109216 51....+0001+003
19 110015+00000690 21.104+14009220 22.104+09016340 31..01+00118810 51....+0001+003
20 110016+00000691 21.104+14431270 22.104+09034000 31..01+00131159 51....+0001+003
21 110015+00000690 21.104+11745126 22.104+09003570 31..01+00168197 51....+0001+003
22 110016+00000691 21.104+12130160 22.104+09045500 31..01+00174578 51....+0001+003
23 110015+00000690 21.104+12539548 22.104+09018410 31..01+00183205 51....+0001+003
24 410014+000.-XC=
25 110016+00000691 21.104+11006379 22.104+09013130 31..01+00191946 51....+0001+003
26 110015+00000690 21.104+11012480 22.104+09016340 31..01+00205878 51....+0001+003
27 110016+00000691 21.104+11321481 22.104+09000300 31..01+00217956 51....+0001+003
28 410014+0000.XC=
29 110015+00000690 21.104+10019559 22.104+09034000 31..01+00198017 51....+0001+003
30 110016+00000691 21.104+09949600 22.104+09018210 31..01+00210797 51....+0001+003
31 110015+00000690 21.104+09915377 22.104+09016340 31..01+00226247 51....+0001+003
32 110016+00000691 21.104+07813382 22.104+09000500 31..01+00199025 51....+0001+003
33 110015+00000690 21.104+07859525 22.104+09045120 31..01+00211632 51....+0001+003
34 110016+00000691 21.104+07948262 22.104+09013130 31..01+00226913 51....+0001+003
35 110015+00000690 21.104+05904408 22.104+09045500 31..01+00227157 51....+0001+003
36 110016+00000691 21.104+06040250 22.104+09064000 31..01+00238317 51....+0001+003
37 110016+00000691 21.104+06224397 22.104+09003570 31..01+00252021 51....+0001+003
162 Data Collection

In the file just shown, the first shot on a building is in measure block 7. The line name for
the building is set in the actual code of code block 6. This line name is “1.” The geometry
for the building line is “line” because there is no other special designator associated with
the value entered in code block 6. The designators may be defined in Data Collection.
This file was generated using the default designators for line (.), close line (+) and the
cross-section pattern (=).
The building line is closed as designated by a close line designator following the line name
entered in code block 12. This will close line 1 to the following measurement recorded in
measure block 13 to the initial shot on the building line in measure block 7.
Line name XC is recorded in code block 14. It represents the cross-section pattern of the
same name which contains three lines in the pattern, EPL, CL and EPR. Each shot on the
cross-section pattern is recorded with the same line name, but is processed with the
appropriate line properties defined in the pattern.
The cross-section pattern is recorded on a curve portion as designated in code block 24.
Measure blocks 25, 26 and 27 are all processed as shots on a curve. The line geometry is
then reinstated in code block 28.
! You may collect and process line work through Data Collection by also specifying the
Field Code along with the designator and the line name in the in the code block. (See Data
Collection Concepts, which begins on page 1).
and Formats
! If you find that you do not have enough special characters on your instrument to handle all
of the designators, you may use any character to represent a designator, including
numbers or alpha letters in caps.
Figure D-2 Line Work Generated Using a Cross-section Pattern

Intermediate Shots
If you want to take a shot out of sequence, say to a manhole or power pole, this may be
done by just typing the Field Code and recording a measurement to the feature.
Sample of a Shot that Does Not Fall on the Cross-section Pattern
1 410014+0000.XC=
2 110015+00000690 21.104+10019559 22.104+09000000 31..01+00198017 51....+0001+003
3 110016+00000691 21.104+09949600 22.104+09000000 31..01+00210797 51....+0001+003
4 410014+000000MH
5 110015+00000690 21.104+10115377 22.104+08912000 31..01+00296247 51....+0001+003
6 410014+0000.XC=
7 110015+00000690 21.104+09915377 22.104+09000000 31..01+00226247 51....+0001+003
8 110016+00000691 21.104+07813382 22.104+09000000 31..01+00199025 51....+0001+003
Code block 4 contains a man hole Field Code. A measurement is recorded to the man
hole in measure block 5. This is followed by resuming the cross-sectioning sequence by
re-initiating the cross-section name in code block 6 and recording the measurement to the
next shot on the pattern. The order that the shots are taken will be retained to properly
select the correct line in the sequence.
Changing Field Codes

If you want to change Field Codes along the cross-section pattern while taking shots, then
you may enter the Field Code before the line information in the code block.
Change of Field Code Example
1 410014+0200.XC=
2 110015+00000690 21.104+10019559 22.104+09000000 31..01+00198017 51....+0001+003
3 110016+00000691 21.104+09949600 22.104+09000000 31..01+00210797 51....+0001+003
4 110015+00000690 21.104+10115377 22.104+08912000 31..01+00296247 51....+0001+003
5 410014+0067.XC=
6 110015+00000690 21.104+009915377 22.104+09000000 31..01+00226247 51....+0001+003
7 410014+0200.XC=
8 110016+00000691 21.104+07813382 22.104+09000000 31..01+00199025 51....+0001+003
164 Data Collection

Code block 1 contains Field Code 200 along with the cross-section pattern name XC. The
Field Code that is placed for a shot in the pattern is changed in code block 5 to 67. The
Field Code 200 is reinitiated in code block 7. Field Code 200 might represent an edge of
pavement shot appropriate symbol, attribute style and description in the Field Code
Library. Field Code 67 might designate a centerline symbol, fence line or other desired
Field Code.
Collecting Data – Customizing Codes

! The default codes that are included with Data Collection may not be identical to your
current set of codes. You may decide to use the current codes in Data Collection or the
ones on the instrument; however, it is encouraged that you customize your collection
coding system to better match the default codes in Data Collection.
If you are familiar with the WILDsoft structure of coding, some of the codes that you are
familiar with include more than one activity per code block. Data Collection is activity
based and only processes one activity at a time. Therefore, you may need to modify the
Leica Code list to match data tags to change activities within one code block. As an
alternative, you may just perform one surveying activity per code line.
and Formats
Numeric Activities
Most EP SDMS activity’s that are supported have a numerical equivalent when using the
Leica codes of Data Collection. These numeric activity values are used to create and
process Leica codes so that the information can readily be translated into the EP SDMS
system. Use these numbers when defining new code functions, or when inserting a
change of activity within a code block.
Numeric Activities Example
Number Activity Description

02 BS Backsight
03 CC Control Check
08 EC Elevation Control
11 FS Foresight
19 OS Occupied Station
20 PR Project Information
26 SR Station Resection
27 SS Sideshot

Code 1
For example, the default WILDsoft code 1 reads a reference azimuth in information field 2
and a backsight point number in information field 3.
Code 1 Example
Code/ INFO 1 INFO 2 INFO 3 INFO 4

Function
SDMS Tag AC:20 PR:Project (Azimuth) (Backsight) (Job Number)
Definition Code Number Project name Azimuth value Backsight ID Job number
Raw 410001+00000011 42....+00001997 43....+00000000 44....+00000100 45....+01121997

information
This would have the affect of changing the surveying activity from Project (AC:20) to
Backsight (AC:02) within the same code block. Data Collection can only process one
surveying activity at a time, i.e. Backsight (AC:02), Project (AC:20), Occupied Station
(AC:19), etc.
If you typically record the starting occupied station and backsight point number in code 1,
make the following modifications to code 1:
Modifications to Code 1 (Typical)
SDMS Tag AC:20 CM:Comment AC:02 PN:Point

Number
Definition Project Activity Notes Backsight Point Number

Activity
Raw 410001+00000001 42....+00000001 43....+00000000 44....+00000002

information
The code 1 outlined above the backsight point number in information field 3. No
information is required in information field 2 because Data Collection will use that space
in the file to write backsight activity. Information field 1 may be used for notes, as the
occupied station will be read from a code 2 that typically follows a code 1 on the initial
setup. Information field 3 and all fields beyond it are then assumed to be part of the
backsight activity.
! When using this code, it is assumed that the coordinate values for both of these points
either exist in the file, in the project that they are going to be processed into, or known
coordinates that can be entered when the file is reduced.
166 Data Collection

If you typically record an azimuth value for the backsight in code 1, make the following
modifications to code 1:
Modifications to Code 1 (Azimuth)
SDMS Tag AC:20 AC:02 AZ:Azimuth PN:Point

Number
Definition Project Activity Backsight Azimuth value Point Number

Activity
Raw 410001+00000001 42....+00000000 43....+00000000 44....+00000002

information
The code 1 outlined above only includes a backsight activity and a reference azimuth in
information field 2. No information is required in information field 1 because Data
Collection will use that space in the file to write backsight activity. Information field 3 may
be optionally used as a point number if the following code is used to record a point to the
backsight.
! The minimum amount of information needed to process the initial setup is either
and Formats
coordinate values for both occupied and backsight points, or a coordinate value for the
occupied point and a reference azimuth. (See EP SDMS, which begins on page 209).
Code 2
Use code 2 to recording the backsight point number in information field 3. In order for the
backsight point number to be read correctly, a backsight activity will need to be inserted in
information field 3. The point number value, however, will need to be recorded in
information field 4. To collect data for code 2 as described, make the following
modifications to code 2:
Modifications to Code 2
Code/ INFO 1 INFO 2 INFO 3 INFO 4

Function
SDMS Tag AC:19 PN:Point IH: Inst. Height AC:02 PN:Point

Number Number
Definition Occupied Point Number Instrument Backsight Point Number

Activity Height Activity
Raw 410002+00000002 42....+00000001 43...+00001720 44....+00000000 45....+00000002

information

! To continue using code 2 without making any changes to the code on the instrument, you
can run code 52 (or similar code) to record the backsight information.
Collecting Data – Leica Instruments

Leica has developed a program that will prompt for what information to place in the code
blocks based on the code you enter. The information is stored using the default structure
for codes. Some of the earlier instruments do not have this capability, whereby some of
the newer instruments do. This can be customized, but it is far easier for you to disable its
prompt so that it does not prompt you to record information incorrectly.
The earliest series of instruments supported is the T1000/ T1600 series and the TC1000/
TC1600 series. This series of instruments does not prompt you for the information to be
placed, but leaves you empty information blocks which the user can input information. It is
recommended that you either use the default Leica codes in Eagle Point or make the
appropriate modifications to them using the rules and examples outlined previously.
VIP Series
The next series of instruments is the VIP series which includes the T/TC 1010 and 1610
instruments. These instruments have prompts on the machine. To disable, select MENU,
4, and then erase. This will delete the program from memory and the instrument will work
as the earlier series of instruments with empty information blocks to place information. To
reload this program, you will need the X Trans program and the standard RS232 transfer
cable for WILD instruments.
TPS Series
This series includes the T/TC 600, 800, 1100, and 1800 instruments. These instruments
may have a program that will prompt you for information based on what code is entered.
When the code key on the instrument is pressed, the program is activated. These prompts
may not match with the Leica codes in Data Collection. If this is confusing, then it is
recommended that the prompts on the instrument be disabled.
To disable the prompts, move or rename the CODE.HEX program on the PCMCIA card.
This will disable the prompts, and the instrument will then just have empty information
blocks without being prompted for the content. Consult your instrument manual for further
information on the CODE.HEX program.
Transferring Data
You may transfer data from the GIF and GRE data collection systems using the GSI8+
data format. There are steps outlined for each type of collection system.
168 Data Collection

Downloading from the Collector (GIF10)
In order to communicate with the GIF10 card reading device, the parameters in both
Eagle Point and on the GIF10 need to be set.
! The GIF12 card reading device is similar, but it uses a parallel port for communication.
Select the parallel port used and the power device when downloading from a GIF12 card
reader.
To prepare the collector to download, perform the following steps on the data collector:
! The following steps are outlined for the WILD GIF10 v. 2.0. These steps may vary slightly
with a different version of the firmware residing on the GIF10 card reader.
1. Press the ON button on the card reader.

2. Press the Down arrow button three times so that the cursor is blinking on the
COMM option.
3. Press the Run button.
4. Verify the following communication settings. Other parameters may work as
well, however, these represent one example that is successful:
and Formats
Communication Settings
Connected DTE
End mark CR/LF
Stop bit 1
Protocol ACK/NAK
Parity odd
Baud 9600
5. Set the baud setting. To change the rate, use the up or down arrow buttons.
Press the Left arrow button.
6. Set the connection as DTE. Press the Left arrow button.
7. Set the Endmark to CR/LF. Press the Left arrow button.
8. Set the Stopbit to 1 (one). Press the Left arrow button.
9. Set the Protocol to ACK/NAK. Press the Left arrow button.
10. Set the Parity to ODD. Press the Run button.

Perform the following steps on the computer:
Download from Collector.
12. Type the name of the Job that is being downloaded.
13. Under Communication Settings, Select Leica GIF10 from the drop list of
supported formats.
14. Select the COM port that is being used on the computer.
15. Set the baud rate to 9600.
16. Set the data bits to 7, odd.
17. Make a check in the Create Legal backup checkbox to automatically create a
backup file on download.
18. Click on OK.
This will launch a blank DOS window.
! If you are using Windows NT, you will receive the message to prepare data collector to
transmit. Press any key to continue. If you are using Windows 95 or 98, you may not
receive this message.
Perform this last step on the data collector:

19. Select the SEND option on the card reader and Press the GO button.
You should see data scroll across the screen as it is being downloaded from the collector.
You may process the downloaded job information by selecting Reduce under the Jobs
menu.
Uploading to the Collector (GIF10)

To prepare the computer to upload, perform the following steps:
2. Select File or Project to upload the information from. You may upload
coordinate information from a file, or directly from the CAD graphic and/or the
External Node Database by selecting project.
3. If you have selected File, type the path and file name of the file to upload, or
click on Open and select the file.
4. Under Communication Settings, Select Leica GIF10 from the drop list of
supported formats.
170 Data Collection

7. Set the data bits to 7, odd.
backup file on download. Click on OK.
Perform the following steps on the GIF 10:
! The following steps are outlined for the WILD GIF10 v. 2.0. These steps may vary slightly
with a different version of the firmware residing on the GIF10 card reader.
9. Press the On button on the card reader.

10. Press the Down arrow button three times so that the cursor is blinking on the
Comm option.
11. Press the Run button. Verify the following communication settings.
12. Set the baud setting. To change the rate, use the up or down arrow buttons.
Press the Left arrow button.
Connected DTE
End Mark CR/LF
and Formats
Stop Bit 1
Protocol GSI
Parity odd
Baud 9600
13. Set the connection as DTE. Press the Left arrow button.
14. Set the Endmark is CR/LF. Press the Left arrow button.
15. Set the Stopbit is set to 1 (one). Press the Left arrow button.
16. Set the Protocol is set to GSI. Press the Left arrow button.
17. Set the Parity is set to ODD. Press the Run button.
18. Click on OK on the Upload to Collector dialog box.
19. If you have selected Project to Upload Information From, you will be prompted
to select Nodes. You may use any of the standard methods of selecting Nodes
(Range, window, description, etc.).
20. Click on Apply to accept the Nodes.
The resultant list of Nodes will be listed to be accepted to upload.
21. Click on OK to accept.

22. If you are using Windows NT or Windows 3.1, you will receive the message to
Start data collector for receiving… Prepare the collector to receive. If you
are using Windows 95 or 98, you may not receive this message.
23. You should see data scroll across the screen as it is being uploaded to the
collector.
Downloading from the Collector (GRE4)

In order to communicate with the GRE4 data collector, the parameters in both Eagle Point
and on the GRE4 data collector need to be set.
! There may be slight differences on the GRE3 and GRE4 devices as far as the steps of
performing the functions described below. The information provided below is for the Leica
GRE4 data collector, but similar steps will work for the Leica GRE3 data collector as well.
1. Press the ON button on the data collector. The default starting file is file 1 (one).
2. If you are downloading file 2-5, press SET, MODE, 80 and type the number of the
file to download.
3. Press RUN twice to accept the correct file number.
4. Verify the following communication settings. Other parameters may work as
well, however, these represent one example that is successful:
SET MODE 70 9600
SET MODE 71 2
SET MODE 72 1
SET MODE 73 1
SET MODE 74 3
5. Set the communication parameters. Press SET, MODE, 70, and RUN to set the
baud rate.
6. Press 9600 and press RUN twice.
7. Press SET, MODE, 71, and RUN to set the parity. Press 2 to set the parity to
even.
8. Press SET, MODE, 72, and RUN to set the protocol. Press 1 to set it to on.
9. Press SET, MODE, 73, and RUN to set the ending characters per word. Press 1
to set it to CR/LF.
172 Data Collection

10. Press SET, MODE, 74, and RUN to set the ending characters for the file. Press 3
to set it to ACK/NAK/CR/LF.
11. Press DATA to display the file to download.
12. Press an arrow key to navigate within the file.
13. Press GOTO and press the block number at the start of the file that you want to
start downloading.
! This will most likely be block 1.
14. Press RUN to go to the specified block.
15. Open a project in Eagle Point and select Data Collection from the Products
menu.
16. Select Download from Collector from the Jobs menu.
18. Under Communication Settings, Select Leica GRE4 from the drop list of
supported formats.
and Formats
21. Set the data bits to 7, even.
22. Select the appropriate COM port.
24. Click on OK.
! If you are using Windows NT, you will receive the message to prepare data collector to
transmit. Press any key to continue. If you are using Windows 95 or 98, you may not
receive this message.

25. Press SEND, RUN on the data collector.
You should see data scroll across the screen as it is being downloaded from the
collector. You may process the downloaded job information by selecting Reduce
under the Jobs menu.

Maptech
If you are using a Maptech data collector, the file format is supported but no additional
technical information is available at this time.
Nikon
Depending upon what Nikon hardware you are using, the following solutions are available
to you for collecting and processing data through Data Collection. Use of the Nikon NS-6,
TransIT or other program may be required to download and upload information to the total
station.
If you are using a DTM-A, C-100 or a D-50 total station, use a Nikon DR-48 or other data
collector that is compatible with Data Collection to record and store raw and coordinate
data.
If you are using a DTM-300 series total station, use a Nikon DR-48 or other data collector
that is compatible with Data Collection to record and store raw and coordinate data. If
you do not desire to have an external data collector, you may use either the Nikon NS-6 or
the Nikon TransIT programs to transfer the files. The files would then have to be translated
to an ASCII coordinate file format or a different format that is in the drop list of supported
formats.
If you are using DTM-400 or 500 series total station, use a Nikon DR-48 or other data
collector that is compatible with Data Collection to record and store raw and coordinate
data. If you not desire to have an external data collector, you may use the Nikon TransIT
programs to transfer the files. The files would then have to be translated to an ASCII
coordinate file format or a different format that is in the drop list of supported formats.
If you are using DTM-700 or 800 series total station with AP-700 or 800 software, use a
data collector that is compatible with Eagle Point and your total station to record and store
raw and coordinate data. If you do not desire to have an external data collector, you may
download directly from the total station to a computer using either the Sokkia SDR data
format or the Trimble/Tripod Data Systems (TDS) data format. Refer to Sokkia (Lietz) on
page 182 or refer to Trimble/Tripod Data Systems (TDS) on page 191 for more information
on the respective format.
If you are using the card reader to transfer files, use the Nikon TransIT or other available
program as a custom translator within Data Collection. You may translate the file
information from the Nikon raw format to an ASCII coordinate file format, TDS raw format
or Sokkia SDR coordinate or raw format.
! If you are using the TDS 700 software on-board the total station, refer to Trimble/Tripod
Data Systems (TDS) on page 191.
174 Data Collection

Transferring Data
Download from an AP700 or 800 Series Instrument

To download from an AP700 or 800 series instrument, proceed through the following
steps:
On the instrument:
1. Turn the instrument ON. Let instrument boot up, tilt scope, etc.
2. On the main menu, select option 8 - Communications.
3. Select option 2 - Download.
You will have four options:
Destination
Data Format
Type of Data
Time Stamp
and Formats
4. Select Data Format and choose a desired format.
Here is a list of formats:
SDR2X
SDR33
DXF
Nikon
TDS
5. Select TDS, SDR2x, or SDR33.
On the computer:
6. From Data Collection, select Jobs ! Download from Collector.
7. Choose the desired format, set the communications parameters, and click on
OK.
8. Prepare data collector to transmit, and press any key on the keyboard to
continue.
On the instrument:
9. Download the data.

! The TDS raw format may be easier to edit as it is comma-delimited. The SDR format is
space-dependent and may be sensitive to the addition of spaces or other accidental
editing modifications.
Pentax and Corvallis

If you are using a Pentax SC-5 or a Corvallis MC-5 data collector, the information found in
this next section will apply to your data collector.
If you are using a total station that is utilizing the Pentax DC-1Z, the file format is
supported, but no additional technical information is available at this time.
If you are using the Pentax SC-105 software, or are using a Pentax total station that has
on-board data collection, you may communicate with Eagle Point directly by downloading
or uploading by setting the format to either a Sokkia format or the TDS raw format. Refer
to Sokkia (Lietz) on page 182 or Trimble/Tripod Data Systems (TDS) on page 191.
Transferring Data
The following steps are outlined for the Pentax and Corvallis data collectors that have
Surveyor’s Assistant installed on them.
The Surveyor’s Assistant software supports several formats for input and output. For
downloading information to the computer, it is suggested to either send the data using the
Lietz (Sokkia SDR2X) format (refer to Sokkia (Lietz) on page 182), or to send the data as
coordinate information using the AASHTO (SDMS) format (see EP SDMS, which begins
on page 209). To upload information back to the collector for stakeout, the Lietz (Sokkia
SDR2X) format is recommended.
Downloading from the Collector

To download from the Pentax SC-5 and Corvallis MC-V data collectors, perform the
following steps.
1. From the main menu on the data collector, select the Job option and highlight
the job that you want to download. Press the F1 or the Go button.
176 Data Collection

2. From the main menu, select the Transfer option. Here you will input the
following options:
Options
Direction OUPUT
Format LIETZ
Data ALL DATA
Port COM 1 or COM 2
CHK HOLD NO
Protocol NONE
3. Press the F5 or PORT button.

4. From the Port Setup menu, verify the following options:
Options
Baud 2400
and Formats
Parity NONE
Data Bits 8
Stop-bits 1
Handshake XON/XOFF

5. Open a project in Eagle Point and select Data Collection from the Products
menu.
6. Select Download from Collector from the Jobs menu.
8. Under Communication Settings, Select Sokkia SDR2x from the drop list of
supported formats.
11. Set the data bits to 8, none.
13. Click on OK.

Perform the last step on the data collector:
14. Press the F1 button or the GO button. You will see the data collector read Lietz
Format.
You should see information scroll across the computer screen as it is transmitting.
15. Press continue on the data collector when finished.
16. Press the Enter key or the F1 key on the computer when finished.
17. You may process the downloaded job information by selecting Reduce under
the Jobs menu.
Alternative Downloading Steps

To use a file transfer method to download information from the data collector, follow the
steps outlined below.
1. From the main menu on the data collector, select the Job option and highlight
the job that you want to download. Press the F1 button or the GO button.
following options:
Options
Direction OUTPUT
Format AASHTO
Data COORDINATE
Port COM 1or COM 2
CHK HOLD YES
Protocol KERMIT
178 Data Collection

Options
Baud 9600
Parity NONE
Data Bits 8
Stop-bits 1
Handshake XON/XOFF

5. Open a project in Eagle Point and Products ! Data Collection ! Jobs !
7. Under Communication Settings, Select Pentax SC-5 from the drop list of
supported formats.
and Formats
10. Set the data bits to 8, none.
12. Click on OK.
This will launch a DOS Kermit window.
Perform the following steps on the data collector:
13. Press the F1 or GO button.
You will see the data collector read AASHTO Format. You will see a Kermit screen
that displays the packets as the file is being transmitted.
14. Press continue on the data collector when finished.
15. Press the Enter key or the F1 key on the computer when finished.
16. Select Edit Instrument File under the Jobs menu. Verify that the Job that was
just downloaded is listed in the Job Name edit field.
17. Select an editor from the drop list of editors.

18. If the path and editor name do not display in the File Name edit field below, type
the path and file name of the editor or click on Open and select the editor of
your choice. Click on the Edit button.
19. Add the following two lines to the top of this file:
PR:JOB NAME
TK:COM
20. Both of these lines need to be in all capital letters. Save your changes and exit
from the editor.
21. Select Manage from the Jobs menu. Highlight the recently downloaded job and
click on Modify.
22. Change the format of this file from Pentax SC-5 to SDMS and click on OK. You
may now reduce this job.
Uploading to the Collector

To upload information to the data collector, perform the following steps.
To prepare the computer to upload, perform the following steps on the computer:
2. Select File or Project to upload the information from. You may upload
coordinate information from a file, or directly from the CAD graphic and/or the
External Node Database by selecting Project.
click on the Open button and select the file.
4. Under Communication Settings, select the Sokkia SDR2x format from the drop
list of supported formats.
5. Select the COM port that is being used on the computer. Set the baud rate to
2400 and set the data bits to 8, none. Before clicking on OK, prepare your
collector to receive data.
The following steps are to be performed on the data collector:
6. From the main menu on the data collector, select the Job option and create a
new job to upload, or highlight the job that you want to upload to. Press the F1
button or the GO button.
180 Data Collection

following options:
Options
Direction INPUT
Format LIETZ
Data ALL DATA
Port COM 1 or COM 2
CHK HOLD NO
Protocol NONE

Options
Baud 2400
and Formats
Parity NONE
Data Bits 8
Stop-bits 1
Handshake XON/XOFF
10. Press the F1 or GO button. You will see a heading on your data collector that
says Lietz Format.
11. Click on OK on the Upload to Collector dialog box. If you have selected Project
to upload information from, you will be prompted to select Nodes. You may use
any of the standard methods of selecting Nodes (Range, window, description,
etc.).
12. Click on Apply to accept the Nodes. The resultant list of Nodes will be listed to
be accepted to upload. Click on OK to accept.
13. If you are using Windows NT or Windows 3.1, you will receive the message to
Start data collector for receiving. Prepare the collector to receive. If you are
using Windows 95 or 98, you may not receive this message, but you will be
prompted to enter a Job ID.

14. Type a Job ID value and press the Enter key.
You should see information display across the computer screen as it is being
uploaded.
15. Press continue on the data collector and press the Enter key or the F1 key on
the computer when finished.
Troubleshooting
Problem: Backsight data not processing.
Solution: If you do not record a measurement to a backsight on a set up procedure, or if
there is not enough data in the file to set the backsight, Data Collection will not be able to
read the backsight record properly. See EP SDMS, which begins on page 209.
Edit the file so the backsight record is processed correctly by proceeding through the
steps below:
1. Open a project in Eagle Point and Products ! Data Collection ! Jobs ! Edit
Formatted File.
2. Look in the file for a record that starts as AC:SS and has coordinate information
to the backsight for the initial set up. Edit this record so that it reads as an
AC:BS.
! If you do not have a coordinate value for the backsight and are using a circle reading for
an azimuth value, then modify the activity that is associated with the azimuth value
instead.
3. Close the editor, save the changes, and select Reduce from the Jobs menu and
process the job.
! For additional troubleshooting suggestions, refer to Sokkia (Lietz) below, or
Troubleshooting, which begins on page 203.
Sokkia (Lietz)
The Sokkia data collectors send and receive data in one of two formats, that based on the
SDR2X, and that based on the SDR3X series of collectors. Both of these formats are
space dependent and are not delimited by commas or spaces. The SDR2X format is as
follows:
00NMSDR20 V03-05 Feb-03-97 10:41 122211
10NMB4745
08TP00015000.000008000.0000095.5563156BL
182 Data Collection

08KI00024665.318008515.36508135.600000BL
08TP10004665.319268515.36314135.602979BM 514
08TP10015557.772898108.9393391.2855610CLRD.CLRD
The SDR3X data structure allows 14 for the storage of the ‘point ID’ or Node ID, and for
each of the coordinate values. The SDR3X structure is better adapted for use with large
coordinate or state plane systems, and the large Node ID edit field is used by Data
Collection for recording and storing alphanumeric values instead of just numeric values.
The SDR3X format is as follows:
00NMSDR33 V04-04.02 Feb-06-97 16:11 122211
10NMHORRY CREEK 122111
06NM1.00000000
13OOCurrent view,MC
13TSFeb-06-97 09:29
13JS11000
13NMTIE PHOTO PANELS
08KI 50816711.92300000 14271.25200000 38.71000000
TRAV
and Formats
08KI 50917250.62500000 14654.09900000 36.80000000
TRAV
08KI 70218104.73100000 13592.86700000 51.56000000
TRAV
The Sokkia SDR USFT data structure is identical to the Sokkia SDR3x except that the
header contains an option field that sets the Distance Unit of the job to US Feet. When an
existing job on the data collector has Units--> Dist set to US Feet, choose the Sokkia SDR
USFT format when uploading so that the collector does not attempt to apply the
conversion to US Feet.
00NMSDR33 V04-04.00000001-Oct-00 11:36 131111
10NMYORK FACTORY F.N121111
06NM1.00000000
13TS18-May-00 13:48
13JS10000
02TP 700915337.3479 16488.9598 624.3098
5.102 NAIL
07TP 7009 70020.0000 211.4597
03NM4.872
09F1 7009 1000397.949 89.2764
148.8125 GAR. DR.

09F1 7009 1001397.949 89.2764
148.8125 GAR. DR.
09F1 7009 1002397.949 89.2764
148.8125 GAR. DR.
Collecting Data
While recording information with the Sokkia data collector, you may choose one of several
views to store the information. Each view uses a different method to calculate and store
the location of the points.
If you are recording large amounts of topography for subsequent contouring and/ or
volume calculations, record and send the data using the POS view. The POS view, or
positional, records and sends the data as coordinates only.
If you are recording precise traverse information or are using the Set Collection functions
available on the data collector, you will want to send the data using the MC, or
measurement corrected attribute only. This format is very similar to the OBS view, except
when using the Set Collection routine. The backsight information for a particular set is not
recorded in a fashion that is read correctly into Eagle Point, but the MC view stores it
correctly.
! You may control what type of shots are used in the reduction process within Eagle Point
by using the shot averaging capability in the Data Collection module. This allows you to
either read and process only the raw OBS information (Raw Measured Data) or the MC
information (Collector Reduced Data). Both forms of information will be reported in the
Reduction Settings dialog box – Shot Averaging tab (Figure 3-5 on page 41), but only the
occurrences from the highest priority type of measurement will actually be used to perform
the calculations. See Reduction Settings – Shot Averaging Tab on page 41.
Transferring Data
Downloading from the Collector

To download from the Sokkia or Lietz data collectors, verify in the communications portion
that the format is set to SDR.
! When downloading information, only have one view attribute set on. This is to ensure that
duplicate and otherwise unnecessary information will not be read or processed. On the
SDR33 data collector, send the records in one view only.
184 Data Collection

! Depending upon what data collector and what version of Sokkia is running on the
collector, the options may vary slightly.
1. Select the Communications option off of the main menu. Press OK.
2. Select the OPTNS button from the Communications menu and set the view to
send records in. Send records in either the POS view for coordinate
information, or the MC view for raw observations, and turn all other views to
NO. Press OK.
3. Select the COM button and verify the communication parameters are correct.
Here is a sample of communication parameters:
Communication Parameters Examples
Port Bottom
Modem No
Baud rate 2400
Word length 8
Parity Not set
and Formats
Stop bit 1
Output delay 0
File No
4. Click on OK.
5. Press the SEND button. Highlight SELECT JOBS and press OK.
6. Select the job that you want to send by using the arrow key.
9. Under Communication Settings, select Sokkia SDR2x or Sokkia SDR3x from the
drop list of supported formats.
2400 and set the data bits to 8, none.
12. Click on OK.

13. If you are using Windows NT, you will receive the message to prepare data
collector to transmit. Press any key to continue. If you are using Windows 95 or
98, you may not receive this message.
14. Click on OK on the data collector to send the data.
You should see data scroll across the screen as it is being downloaded from the
collector.
15. You may process the downloaded job information by selecting Reduce under
the Jobs menu.
Uploading to the Collector

To prepare the computer to upload, perform the following steps on the computer:
2. Select File or Project to upload the information from.
You may upload coordinate information from a file, or directly from the CAD graphic
and/ or the External Node Database by selecting project.
click on Open and select the file.
4. Under Communication Settings, select the Sokkia SDR2x, Sokkia SDR3x, or
Sokkia SDR USFT format from the drop list of supported formats.
! When an existing job on the data collector has Units--> Dist set to US Feet, choose the
Sokkia SDR USFT format when uploading so that the collector does not attempt to apply
the conversion to US Feet.
2400 and set the data bits to 8, none. Before clicking on OK, prepare your
collector to receive data.
Perform the following steps on the data collector:
! Depending upon what data collector and what version of Sokkia is running on the
collector, the options may vary slightly.
6. Select the Communications option off of the main menu. Click on OK.
7. Verify in the Communications portion that the format is set to SDR.
186 Data Collection

8. Press the COM button and verify the communication parameters are correct.
Here you will input the following options:
Options
Port Bottom
Modem No
Baud Rate 2400
Word Length 8
Parity Not set
Stop bit 1
Output delay 0
File No
9. Click on OK.
10. Press the RECV button.
and Formats
12. If you have selected Project to upload information from, you will be prompted to
select Nodes.
You may use any of the standard methods of selecting Nodes (Range, window,
description, etc.).
13. Click on Apply to accept the Nodes.
The resultant list of Nodes will be listed to be accepted to upload.
14. Click OK to accept.
15. If you are using Windows NT or Windows 3.1, you receive the message to Start
data collector for receiving. Prepare the collector to receive. If you are using
Windows 95 or 98, you may not receive this message, but it prompts you to
enter a Job ID.
16. Type a Job ID value and press the Enter key.
You should see information display across the computer screen as it is being
uploaded.
17. Press continue on the data collector and press the Enter key or the F1 key on
the computer when finished.

Troubleshooting
Problem: Data collector displays a “Communications Error” message when downloading
or uploading.
Solution: Verify that the communication parameters are the same for the collector as they
are on the computer. If you are still receiving the error, reduce the baud rate to a low
setting, i.e. 2400 or lower.
Problem: Data collector displays an “Invalid Input” message when uploading to the
collector.
Solution: Change the format from Sokkia SDR3x to Sokkia SDR2x. Only if you are
working in very large coordinate ranges and need to retain very high precision would you
need to upload using the SDR3x format. If this is a requirement, please contact technical
support for assistance on a possible solution.
Problem: Data collector displays an “Error Receiving Data” message.
Solution: Verify communication parameters are correct.
In all cases, if the cable is too long, or if you are using too many adapters, try reducing the
cable length and minimize adapters if possible. See Troubleshooting, which begins on
page 203.
! If problems persist and you have the Sokkia Comms, WComms, or SDR Link programs,
you may establish these programs as custom translators within Eagle Point and use them
to create files to import. When downloading, if the application is closed, Data Collection
will display the File to Open dialog box. You may select the SDR file that was created from
the Sokkia program to bring it into Data Collection.
Surveyor’s Module (SMI)
Download Coordinate Information from the SMI Data Collector

To download coordinate information from the SMI data collector, complete the following
steps.
1. To download a coordinate file to the computer, select Data Collection ! Jobs !
2. Type a job name for the job that you are going to download.
The job name is used to keep track of the file within Data Collection.
3. Select the SMI - Coordinate format from the drop list of supported formats.
188 Data Collection

4. Choose the version of the SMI software on the data collector from the drop list
of SMI versions.
5. Select the appropriate COM port from the Serial Port drop list.
6. Set the baud rate to match the baud rate of the data collector.
7. Select 8, None from the Data Bits drop list.
8. Toggle on the Create Legal Backup File option to create a backup file on
download.
9. Click on OK.
This displays the Transferring from SMI dialog box and starts the download process.
10. On the SMI Data Collector, open the job to be transferred, and press the [JOB],
{XFER}, and {SEND} buttons successively.
This transfers the selected coordinate file to the computer.
You may now edit and reduce the file using the commands in Data Collection under the
Jobs menu with the respective names. Refer to Edit Instrument File on page 17 and
Reduce Job on page 20 for more information.
and Formats
Download Raw Survey Information from the SMI Data
Collector
To download raw survey information from the SMI data collector in either the SDMS format
or Sokkia SDR2X format, complete the following steps.
1. To download a raw survey file to the computer, select Data Collection ! Jobs !
3. Select either the SMI - SDMS or SMI - SDR2X format from the Format drop list of
supported formats.
! Data Collection supports the downloading and reduction of raw observations by using
either the Lietz2X (Sokkia SDR2X) or the SDMS format.
4. Choose the version of the SMI software on the data collector from the drop list
of SMI versions.
5. Select the appropriate COM port from the Serial Port drop list.
6. Set the baud rate to match the baud rate on the data collector.
7. Select 8, None from the Data Bits drop list.

download.
9. Click on OK.
This displays the Transferring from SMI dialog box and starts the download process.
10. On the SMI data collector, open the job to be transferred and press the [JOB],
{XFER}, and {SEND} buttons successively.
This transfers the selected file to the computer.
You may now edit and reduce the file using the commands in Data Collection under the
Jobs menu with the respective names. Refer to Edit Formatted File on page 19 and
Reduce Job on page 20 for more information.
Upload Coordinate Information to the SMI Data Collector

To upload coordinate information to the SMI data collector, complete the following steps.
1. Select Data Collection ! Jobs ! Upload to Collector.
2. Verify that the Upload Data From Project option is selected.
! You may optionally use the From File setting to upload an existing coordinate file.
3. Type the name of the job to upload to the collector.
% The file name must follow the 8.3 convention and have a CR5 extension.
4. Under Communication Settings, select the SMI - Coordinate format from the
6. Set the baud rate to match the data collector. If you are using an HP48, set the
baud rate to 9600.
7. Set the data bits to 8, None.
The Select Nodes to Upload dialog box displays. You may use any of the standard
methods of selecting Nodes (range, window, description, etc.).
9. Build your selection set of Nodes using the Apply button to select/deselect the
Nodes.
This will display the Transferring to SMI dialog box.
190 Data Collection

11. On the SMI data collector, press the [JOB], {XFER}, and {RECV} buttons
successively.
The selected Nodes begin transferring to the data collector.
Trimble/Tripod Data Systems (TDS)

The TDS data collectors send and receive data in either a coordinate or raw data format.
The coordinate format (.CR5) is typically in a compressed format, and is therefore
unreadable. The coordinate data can be downloaded directly from a TDS data collector,
however. The raw format is not compressed and is readable from any editor. Here is an
example of a raw instrument file:
OC,OP10,N 9983.5450,E 10222.2690,EL101.561,--SPUR SPUR10
BK,OP10,BP2,BS277.58038,BC0.00000
LS,HI1.637,HR1.440
SS,OP10,FP1281,AR173.37330,ZE91.26370,SD21.150,--.EO
SS,OP10,FP1282,AR163.09300,ZE90.35490,SD21.870,--.YY
and Formats
SS,OP10,FP1283,AR140.06100,ZE91.06070,SD8.630,--.YY
SS,OP10,FP1284,AR167.25540,ZE92.32200,SD7.530,--.EO
Transferring Data
Downloading from the TDS HP48GX

1. Select File Transfer from the Main menu.
2. Select either CRD to send a coordinate file, or RAW to send a raw data file.
3. Verify the communication settings:
File Type CRD or RAW
IR/Wire WIRE
Baud Rate 9600
Parity None

Before sending a job file, prepare Data Collection to receive a file. Perform the following
steps on the computer.
1. To download a coordinate file to the computer, select Data Collection ! Jobs !
3. Under Communication Settings, select either TDS - Coordinate or TDS - Raw
format from the drop list of supported formats.
download.
8. Click on OK.
This will display the Transferring from TDS dialog box.
9. Press the Send button and select a job from the list of jobs on the data collector.
This transfers the selected file to the computer.
You may now edit and reduce the file using the commands in Data Collection under
the Jobs menu with the respective names. Refer to Edit Instrument File on page 17
and Reduce Job on page 20 for more information.
Uploading to the TDS HP48GX

To upload information to a TDS data collector, you must first prepare the data collector to
receive a file. Complete the following steps to prepare the data collector.
1. Select File Transfer from the Main menu.
2. Select CRD to receive a coordinate file.
3. Verify the communication settings:
File Type CRD
IR/Wire WIRE
Baud Rate 9600
Parity None
192 Data Collection

To prepare the computer to upload, perform the following steps on the computer.
1. Select Data Collection ! Jobs ! Upload to Collector.
2. Select the Project option to upload data from the current project.
! You may optionally use the From File setting to upload an existing coordinate file.
% The file name must follow the 8.3 convention and have a CR5 extension.
4. Under Communication Settings, select the TDS - Coordinate format from the
The Select Nodes to Upload dialog box displays. You may use any of the standard
methods of selecting Nodes (range, window, description, etc.).
9. Build your selection set of Nodes using the Apply button to select/deselect the
and Formats
Nodes.
This displays the Transferring to TDS dialog box and the selected Nodes begin
transferring to the data collector.
Downloading from the TDS Ranger (SurveyPro v3.x)

Perform the following steps on the Ranger’s touch screen:
1. Ensure that the Ranger is connected to the PC COM port with the transfer cable.
2. Select File from the main left menu on the Ranger screen (or type “1” from the
keypad).

3. Select Transfer from the function right menu on the Ranger screen (or type “F”
from the keypad). SeeFigure D-3 below.
Figure D-3 File – Transfer
4. Verify the communication settings. See Figure D-4 below.

Connecting to: HP48
COM Port (Ranger) COM 1
Baud Rate 38400
! If 38400 does not work, use 9600 as an alternative.
Parity None
Figure D-4 Communication Settings
5. Tap the Send File button.
194 Data Collection

6. Select the type of job from the Type drop list. Choose either Coordinate (*.cr5)
or Raw Files (*.raw). See Figure D-5 below.
Figure D-5 Job Type
7. Select a job from the job list that now displays on the Ranger.
Perform the following steps in Data Collection:
8. Open a project in Eagle Point.
9. Select Products ! Data Collection ! Jobs ! Download from Collector.
and Formats
Figure D-6 Download from Collector Dialog Box
Refer to Figure D-6 above for the following steps.

10. Type a name for Eagle Point to use for the job that is being downloaded.
11. Under Communication Settings, select either the TDS - Coordinate or TDS - Raw
format from the drop list of formats.
13. Set the baud rate to match that of the data collector.
15. Toggle on the Create Legal Backup File checkbox to automatically create a

16. Click on OK.
This displays the Transferring from the TDS dialog box.
Figure D-7 Transferring from the TDS Dialog Box
Perform the final step on the Ranger:

17. Tap the OK button to transfer the job file. See Figure D-5 on page 195.
PROCESSING THE DATA:
18. To process the downloaded job information, select Jobs ! Reduce.
See Figure D-8 below.
Figure D-8 Reduce Job Dialog Box
Uploading to the TDS Ranger (SurveyPro v3.x)

Perform the following steps on the Ranger’s touch screen:
1. Ensure that the Ranger is connected to the PC COM port with the transfer cable.
2. Select File from the main left menu on the Ranger screen (or type “1” from the
keypad).
196 Data Collection

3. Select Transfer from the function right menu on the Ranger screen (or type “F”
from the keypad). See Figure D-9 below.
Figure D-9 File – Transfer
4. Verify the communication settings. See Figure D-10 below.

Connecting to: HP48
COM Port (Ranger) COM 1
Baud Rate 38400
! If 38400 does not work, use 9600 as an alternative.
and Formats
Parity None
Figure D-10 Communication Settings

Perform the following steps in Data Collection:
5. Select Products ! Data Collection ! Jobs ! Upload to Collector.
Figure D-11 Upload to Collector Dialog Box
Refer to Figure D-11 above for the following steps.

6. Select the Project option to upload Nodes from the current project.
% The file name must follow the 8.3 conventions and have a CR5 extension.
8. Under Communication Settings, select the TDS - Coordinate format from the
10. Set the baud rate to match the data collector
198 Data Collection

The Select node(s) to upload dialog box displays.
Figure D-12 Upload to Collector Dialog Box – Select Nodes to Upload
13. You may use any of the standard methods of selecting Nodes (range, Field
Code, etc.). Click on Apply to accept the Nodes.
14. Click on OK.
This displays the Transferring to the TDS dialog box. Your Nodes should begin
and Formats
transferring to the data collector at this time.
Figure D-13 Transferring to the TDS Dialog Box
Perform the final step on the Ranger:

15. Tap the Receive File button. See Figure D-10 on page 197.
The Ranger will now receive the file.
16. The TDS software will now prompt you to save the file either to the name
chosen in Eagle Point, or to a new name.
The upload is now complete.

Troubleshooting
Problem: Not all of the data is downloading.
Solution: If you are downloading and are running the collector without an external power
source, be sure that the battery strength is good. If you are using an HP48 calculator, be
sure that the batteries are changed every one or two months.
Problem: Survey data is coming in rotated 180 degrees.
Solution: Check the Operating Modes under the Setup menu of the data collector and
verify that the Azimuth setting is set to N. Azimuth. Data Collection processes all azimuth
values as being North Azimuth values.
Problem: When uploading to the data collector, you are receiving the message “Point too
small” on the data collector.
Solution: The file that is being uploaded has point numbers that are non-sequential.
Create a file that has point numbers that are sequential, either via Data Transfer or Data
Collection.
Topcon
For information on the Topcon FS-2 data collector, refer to Trimble/Tripod Data Systems
(TDS) on page 191.
! If you are using a total station that is utilizing the Topcon FC-4 data collector, the file format
is supported, but no additional technical information is available at this time.
! If you have a Topcon GTS 200 or 300 series instrument with on-board data collection, you
will need to set the Topcon CRC (Data Communication, Reduction, and Conversion)
program as a custom translator from within Data Collection.
Zeiss
Preparation
For Data Collection to properly process data collected using the Zeiss REC 500 data
collector, the Node ID (point number) and descriptor information needs to be recorded
properly. Field Codes, designators, line information and descriptions may all be entered
using the format displayed in the following example.
200 Data Collection

! Data Collection only supports the coordinate format of Zeiss REC 500. If you use raw
data for checking purposes, you may send both as Data Collection will only process the
coordinate records.
Collecting Data
The format that Data Collection currently supports for the Zeiss REC 500 is based on
setting up the tab stops on the instrument in the Point ID field. Zeiss allows 27 characters
for the point ID, and the tab stops are as follows:
T T T
0123456789012345678901234567
The T represents a tab stop. The first tab stop would represent the location for an alpha
Node ID but is unused by Data Collection at this time. The second tab stop represents
the Node ID. Here you may type a numeric or alphanumeric Node ID to set the point
number for the file. Each sideshot that is recorded from that point will automatically
increment from the entered point number.
The third tab stop represents the location of the point description (PD:), which may include
the Field Code, line designator, line name and descriptor. See Data Collection Concepts,
and Formats
which begins on page 1, and EP SDMS, which begins on page 209.
Here is a sample from a Zeiss REC 500 file:
100 lotcor
101 .ep
102 lotcor
103 88.1 traverse
0123456789012345678901234567
On the first line in the data file, ‘100’ represents the Node ID and ‘lotcor’ represents the
Field Code.
! If the lotcor Field Code does not exist, the default Field Code will be processed with ‘lotcor’
as the description.
The second line represents a shot recorded on an edge of pavement. The Node ID of the
shot is 101. The ‘.’ represents the line designator and the ‘ep’ represents the line name
See Line Work (Recommended for Non-Alphanumeric Instruments) on page 141.
The third line is the same as the first line.
The fourth line represents a combination of a Field Code 88, a line designator, the line
name ‘1’, and a description ‘traverse’ that will be placed instead of the default description
for Field Code 88.

202 Data Collection
TROUBLESHOOTING
In this appendix:
APPENDIX
General Communications Problems . . . . . . . . . . 204
Internal Modem/Digitizer with a Serial Mouse. . . 206
Appendix E: Troubleshooting 203

% Be sure to check Collectors and Formats, which begins on page 129, first for
specific issues related to your data collector.
General Communications Problems

Here are some suggestions that help in case there is a communication problem either
uploading or downloading with a data collector:
! If you are downloading and are using a data collector without an external power source,
be sure that you are using fresh batteries. Weak batteries may not transmit all of the
information and may fail while downloading. If you are using an HP48 calculator, be sure
that the batteries are changed every one or two months.
! Verify that all communication parameters set in Data Collection and on the data collector
match as closely as possible. If you are using a custom translator program, verify the
parameters set in the program match with the collector.
! Most new computers have two 9-pin serial devices on the back of the machine. Most
likely, these will be COM 1 and COM 2. Verify that the user is not trying to plug into one of
the parallel ports. Some older machines used 25-pin serial ports that resembled Parallel/
LPT/Printer ports. Serial ports are 'male' and Parallel ports are 'female'.
! Verify that all communication settings on the collector and Data Collection are set the
same (i.e., baud 9600, data bits 8, no parity, etc.). Check the documentation for special
settings and the latest compatibility list of collectors.
! Verify if you have a Serial or PS/2 mouse. A serial mouse will need a dedicated serial
(COM) port to operate from (i.e., you cannot boot to a mouse/digitizer, and then swap
cables to download to). Windows captures the device on start-up (not hot-swapping).
Keyboard and touch-pad controls should not cause a conflict, but I know of one instance
(Panasonic environmental notebooks) where the laptops have to be reconfigured/disabled
to get the serial port to work. Most new machines have PS/2 mice, so this should not be a
problem if your machine was built after 1997.
! Verify their modem settings. Select Modems from the Control Panels and check the COM/
IRQ settings. COM 3 uses the same interrupt as COM 1 by default. This requires you to
reconfigure the modem to a different IRQ or point it to a different COM setting. (For
example, either IRQ 2 or IRQ 4 is good if you are downloading to COM 1). If you have
many devices, be sure to investigate the settings before making any changes so the
settings can be restored.
204 Data Collection

! Check to see if you have any conflicts with the COM port. Check either Ports (Windows
NT) or System ! Devices (WIN95/98/2000/ME) to see if they have any conflicts with the
Address/ IRQ settings. NT/2000 might display an error '16 bit MS-DOS Subsystem:
The system cannot open COM_ port requested by the application' if there is a
conflict or if the port is not enabled. In most cases, this error can be ignored.
! Use the Kermit program in the /EGPT/Program directory as a check for the port settings.
Run Kermit and type STATUS. If you get a 'Speed Unknown' or 'Port emulated by BIOS 1',
the port may be being used by another device. If you are using Windows 95/98/2000/ME
AND have a plug 'n play BIOS, you may remove the COM port and have Windows reinstall
the device drivers using the default settings. To do this, go into Control Panel ! System
! Device Manager. Select the COM port that you desire to use and click on the 'Remove'
button. Then restart the machine and recheck Kermit for the status. You can detect for
Plug and Play if you toggle the 'View Devices by Connection' and see a 'Plug and Play
BIOS' device in the list. Without Plug and Play, you can still manually remove the device,
re-add the device through Control Panel ! Add New Hardware, and restart. For more
information on how to solve this problem, go to the following address and read the
document entitled “MS-DOS-based programs unable to initialize COM ports on
Computers with ACPI support.” http://support.microsoft.com/support/kb/articles/Q252/1/
84.asp.It is article Q252184 in Microsoft's Knowledge Base.
! Verify the BIOS settings to see if a port is enabled or if there is an IRQ (interrupt request
conflict). You can get into your BIOS by pressing the either the 'F1', 'F2', 'F8', or the
'Delete' key on start up, depending upon what firmware and version your machine has.
Other things that may be applicable:
Troubleshooting
! If the Eagle Point /Program folder is installed on a server or a different machine than the
Appendix E:
one that you are downloading to, right click on the MDATACOL.exe and perform a
Properties. Change the shortcut so that the path to MDATACOL is using drive mappings
and not Universal Naming Convention (UNC).
! If you are downloading TDS or Maptech, you can copy the Kermit program from our ../
Program directory to a different machine and communicate with Kermit. You can
download using Kermit by verifying the communication settings (type STATUS) and then
typing REC to receive the file.
! For Geodimeter data collectors, you will be prompted to select either I for area file or M for
job file. Type either letter and press the Enter key. Type “~” (with quotation marks) to
access the job list in the collector. In the upper right corner of the DOS window is the list of
jobs in the collector. Use the up/down arrows to select the job file and press the Enter key
to select it. Press the Enter key to continue or press the F1 key to terminate the process.

! Low batteries on the collector are a problem if only a portion of the file transfers.
! Swap cables if you have recently replaced this.
! Delete any *.TMP files in the EGPT/Program directory.
! Delete temporary files in TEMP/Eagle Point folder.
! Remove any recently installed devices (i.e., camera, modem, PDA, digitizer, or even
sound/video cards, etc.).
Internal Modem/Digitizer with a Serial Mouse

If you are using the serial port through Windows for a mouse, digitizer, modem or other
external device, or if you are using an internal modem or other device that is assigned to a
COM port, you may experience difficulty when communicating with your data collector. A
common conflict may exist if you are using one serial port for a pointing device, and have
an internal modem. You will need to make sure that the modem and the serial port that is
to be used to communicate with the data collector are not sharing the same interrupt
request setting (IRQ).
A serial port and a COM port are essentially the same. A serial port is considered to be the
physical port on the motherboard or on the back of the machine. A COM port is a virtual
port that may be assigned to an external serial port and other internal devices.
A PC can generally be configured to have up to 4 COM ports, but it can usually share only
up to two IRQ settings among the four ports. Therefore, you cannot run more than two
serial devices at the same time. Specifically, COM1 shares an IRQ setting with COM3,
and COM2 shares an interrupt with COM4. You will need to verify that there are no active
serial devices using the same IRQ setting as the COM port you are using to
COMmunicate with.
If you have an internal modem, many modems are configured to use COM2 on
installation. When Windows detects that a modem has been installed on COM2, it usually
reassigns the external serial port that was previously using COM2 to COM3. This means
that the second serial port is now sharing the same IRQ setting with the serial port on
COM1, thus attempts to use the second external port will fail.
If this is your situation, you need to change the IRQ setting for the second serial port so
that it shares an IRQ with a device that you know will not be in use at the same time.
If you are using an internal modem, determine which COM port and IRQ setting is being
used.
206 Data Collection

QuickSteps
To determine which COM port and IRQ are assigned to an internal mode, proceed
through the following steps:
1. Click on the Modems icon in the Control Panel.
2. Click on Diagnostics.
You will see a listing of all the COM ports known to the system, with the device that is
assigned to that port.
! "No Modem Installed" indicates an unused COM port which can be used for direct
connect. If the modem is installed on COM2, you will need to change the serial port that is
at COM3 to COM4.
QuickSteps
To change the serial port from COM3 to COM4, perform the following steps:
1. Open the System Control Panel, and double click on the Ports (COM & LPT)
section.
2. Select the device you wish to change (e.g. COM3).
3. Click on Properties to show information about that device.
4. Click on the Resources tab.
You will see a checkbox labeled Use automatic settings that is checked.
5. Clear this checkbox to make the necessary changes.
! The drop list labeled Settings based on has four options: Basic configuration 0000 - Basic
Troubleshooting
Appendix E:
configuration 0003. These correspond to COM1 - COM4, i.e. Basic configuration 0000 is
COM1, 0001 is COM2, and so on.
6. To change the serial port using COM3 to use COM4, select Basic configuration
0003.
Notice that the Interrupt Request setting changes to that of the modem, not the other
serial port.
7. Click on OK all the way back to the desktop and reboot.
! If you previously had an internal serial device that caused Windows to reassign your COM
port, simply removing the device will not cause the COM port to return to its original
setting. You must either reassign it manually or remove it using the device manager and
let Windows re-detect the device on the next start-up.

8. Verify that all cable connections are tight and are connected to the correct
ports.
9. Using Data Collection, reattempt communication. If the file terminates abruptly
before it is finished being sent, try lowering the baud rate on the collector and
the computer and resume.
! If you are still having trouble using the serial port, there is a chance that the port is not
even enabled for your computer. You could try a different COM port or enable the port
through the BIOS of the computer.
! If you run out of IRQ settings, you may attempt to assign a different device to another IRQ
setting that would traditionally be used for an LPT device (IRQ 5, 7, 9, etc.), but you will
need to check for conflicts with sound blasters, printers, plotters, and other similar
devices.
208 Data Collection

EP SDMS
In this appendix:
APPENDIX
Beginning of SDMS File . . . . . . . . . . . . . . . . . . . 211
Surveying Activities . . . . . . . . . . . . . . . . . . . . . . . 211
Common Data Tags . . . . . . . . . . . . . . . . . . . . . . 215
Reserved Eagle Point SDMS Data Tags. . . . . . . 233
Minimum Setup Information . . . . . . . . . . . . . . . . 244
Appendix F: EP SDMS 209

EP SDMS stands for the Eagle Point Survey Data Management System. This system of
collecting, recording and processing was adopted from the AASHTO form of labeling and
identifying different activities and organizing the data recorded during a survey.
SDMS is a data structure that is composed of two letter data tags. For example, AC: is an
activity data tag that defines what surveying activity is being recorded. Each data tag that
follows an activity (AC:) data tag is associated with that activity until it is ended or a new
one is started. That is AC:OS will set the surveying activity to be occupied station.
Here is a sample of the beginning of an SDMS file:
PR:Project
TK:COM
AC:PR
DT:10-20-98
RE:B.H.
IT:TC1800
AC:OS
PN:100
IH:1.65
PD:Benchmark #3
YC:10123.311
XC:9342.118
ZC:212.155
AC:BS
SH:1.7
PN:101
PD:Benchmark #17
YC:10172.918
XC:9391.201
ZC:212.265
…
! If you are collecting data using a customizable system and are constructing codes for use
with Eagle Point, create the codes/sequences so that only one activity is being recorded
at a time (OS, BS, etc.).
210 Data Collection

Beginning of SDMS File
Before a file can be processed using Eagle Point, it must contain certain file header
information. Here is a sample of the beginning of an SDMS file:
PR:Project
TK:COM
AC:PR
DT:10-20-98
RE:B.H.
IT:TC1800
…
! Each SDMS formatted file must start with a PR: (Project name) data tag followed by a line
that has a TK:COM (Combined Survey Task).
The main surveying task (TK:) for Eagle Point is the Combined Survey Task (Traverse
and Sideshot). This task allows control traversing, trigonometric leveling and simultaneous
collection of sideshots. All other tasks are actually variations on the combined task (or vice
versa).
Surveying Activities
Activities are the basic building blocks of an EP SDMS surveying task. The data tag, AC:,
is a system data tag that defines the type of shot taken or being recorded. Use this tag to
separate activities. The tag must be entered with the activity, and be the first entry of a
new activity.
All information in the project or file is recognized and processed based on the AC: data
tag. This data tag ensures that each activity is separated from the previous activity.
Use of the AC: data tag signifies that you have completed the previous activity and are
beginning a new activity. Here is a list of activities that are supported by Eagle Point:
Appendix F: EP SDMS
BS=Backsight
CC=Control Check
CK=Check Shot
EC=Elevation Control
FS=Foresight

OS=Occupied Station
PR=Project
SR=Station Resection
SS=Sideshot
TP=Turn Point
The most commonly used activities are described in the following section.
Project (PR) Activity

The project header information is typically contained in the PR (Project) activity. This
activity stores certain descriptive data about the job as well as initializing certain
computational constants.
PR:Project
TK:COM
AC:PR Project Activity
DT:10-20-98
RE:B.H.
IT:TC1800
…
The first data tag after the PR: and the TK: data tags is typically the project activity
(AC:PR). The data tags that follow are associated with various portions of information that
is all part of the PR activity. This information is compiled and processed as soon as a new
activity AC: data tag is read from the file.
Occupied Station (OS) Activity

The Occupied Station activity at the minimum needs to contain the point number (Node
ID). If you are recording data that is only going to be analyzed on a coordinate basis, then
a typical sequence following the AC:OS may be as follows:
…
AC:OS Occupied Station Activity
PN:100
IH:1.65
PD:Benchmark #3
YC:10123.311
212 Data Collection

XC:9342.118
ZC:212.155
…
The instrument height (IH:) and the staff height (SH:) will remain as the values for the
entire file until the values are changed before a subsequent shot.
If the coordinates are unknown and you do not want to use assumed values, you may use
the Station Resection activity (SR) if your data collector supports it, or just omit the
coordinate data tags from the initial occupied station activity. You will be prompted for
coordinate values when the file is processed. If you have your initial control points either in
the CAD graphic or the External Node Database of the project that you are processing the
file, then the coordinate values from the Nodes in the project are automatically used to
process with. See Minimum Setup Information on page 244.
If the ZC: is the only unknown coordinate, enter the XC: and YC:, but omit the ZC: data tag
from the activity (i.e. do not enter ZC:0.000, as this will be used as an actual elevation).
Continue with the project data until a point of known elevation can be determined from the
occupied station. This should be established from a Backsight (BS), Foresight (FS) or
Sideshot (SS). Find the calculated elevation and place it in the initial elevation (ZC:) of the
occupied station.
Backsight (BS) Activity

The Backsight activity is used to establish the back azimuth direction and the
corresponding initial reference angle. If there are multiple references to a backsight within
an activity, then the reference angle may be adjusted slightly as a result; however, the
back azimuth direction will not change.
…
AC:BS Backsight Activity
SH:1.7
PN:101
PD:Benchmark #17
YC:10172.918
XC:9391.201 Appendix F: EP SDMS
ZC:212.265
…
The AZ: data tag may replace the YC: and XC: data tags on a backsight.
! If the AZ: and YC: and XC: coordinates exist for a Backsight Activity, the AZ: will always
take precedent.

If neither an azimuth nor coordinates are entered for the backsight, the SDMS setup
dialog box will display, prompting for the appropriate information needed to complete the
backsight. See Minimum Setup Information on page 244.
Foresight (FS) Activity

The Foresight activity is used to establish the next occupied station and is mainly used
when taking SDMS files into Survey Adjustment for processing. The Foresight activity
may also be used when recording a set of angles between two traverse points.
…
AC:FS Foresight Activity
SH:1.7
PN:192
HZ:272.5162
VT:93.1201
DS:102.312
PD:PK-62
…
Sideshot (SS) Activity

The Sideshot activity is used to record radial topography, features, and for entering
coordinate values of control points.
…
AC:SS Sideshot Activity
PN:1091
YC:11171.1102
XC:8219.2141
ZC:212.21
…
AC:SS Sideshot Activity
SH:1.7
PN:1091
HZ: 171.1102
214 Data Collection

VT:89.2141
DS:22.132
PD:MH #42
…
Elevation Control Check (EC) Activity

The Elevation Control activity is used to record angle and distance measurements to a
point of known elevation. It may be used to verify the elevation of any OS activity. The shot
is most commonly taken from a benchmark that is visible from the current OS. The known
elevations entered from the Elevation Control check activity and the surveyed elevations
will be reported after the file has been processed. No changes are processed in the file.
Other Activities
Other activities, such as Control Check (CC), Station Resection (SR), Check Shot (CK),
and Turn Point (TS) are used primarily for organizing collected information in the formatted
SDMS file. They are not used for computations, but carry the information over so that it
may be checked against the processed information.
Common Data Tags

Some of the most common data tags are described in the following sections. These are
also referred to as Technical Computation Tags and are listed in alphabetical order in this
section.
AZ: Azimuth
The data tag AZ: defines a numeric value representing the north azimuth direction. The
record is measured from an occupied point to the reference point, and is considered to be
measured from true North (where north represents ‘0’) in a clockwise direction. The
reference point may be the initial backsight, a closing foresight, or a sideshot. Appendix F: EP SDMS
The AZ: data tag must be specifically entered and unique to the project or activity.

! If contained within a backsight activity (AC:BS), the AZ: data tag value will take precedent
over entered coordinate data for the backsight location. This is so the horizontal circle
reading is correct for all corresponding records.
Figure F-1 Azimuth Data Tag Diagram
…
AC:BS
PN:Z
PD:SECTION CORNER
HZ:0.0000
VT:92.0258
DS:651.4102
AZ:268.2523 Sets Backsight Azimuth to 268.2523.
.
.
AC:SS
.
DO: Offset Direction

The data tag DO: defines the horizontal or vertical orientation for a PO: (Prism Offset)
within an activity. The value can either be ‘H’ or ‘V’. The primary purpose of the data tag is
for tunneling work where the prism may be offset from the tunnel ring either horizontally or
vertically. See PO: Prism Offset on page 224.
! The data tag DO: must be entered into each activity that it applies to.
…
AC:SS
PN:125
PD:3rd RING
HZ:0.0519
VT:90.2315
216 Data Collection

DS:101.35
DO:H Denotes a horizontal offset.
PO:2.13
.
.
DS: Slope Distance

The data tag DS: defines the slope distance measurement from the occupied station to the
target. The distance data item must be entered into the activity that it applies to and it must
be unique to that activity.
When recording distances, it is common to use the combination of the DS: and VT:
(Vertical angle) data tags. You may also use the HD: (Horizontal distance) and VD:
(Vertical distance) data tags to record the same information.
Figure F-2 Data Tag Diagram
…
AC:CC
PN:15
PD:TBM#35
HZ:33.3148
VT:87.2554
DS:135.972 Slope distance of 135.972
.
. Appendix F: EP SDMS
AC:SS
.

FE: Feature (Field Code)
The data tag FE: defines an alphanumeric description of the recorded feature. This is
associated with the Field Code with the same name in the Nodes (Field Codes) library.
See Nodes (Field Codes) in the Eagle Point Menu manual.
! You may enter line work information if all of the information can fit within the 20 character
limit. See FG: Figure, below, GM: Geometry on page 219 and PD: Point Description on
page 223 for more information.
…
AC:SS
PN:383591
PD:16 OAK
FE:TR The Field Code value is TR.
HZ:39.3050
VT:89.5113
DS:350.002
.
.
AC:SS
.
In this example, the Field Code TR may be associated with a tree symbol, attributes and a
default description of ‘TREE’ in the Node (Field Code) Library.
FG: Figure
The data tag FG: defines the line name of the figure or the functional equivalent. You may
enter a maximum of 10 characters for this data tag.
When the file is processed, all point numbers with the same FG: data tag value will be
processed in the order that they were recorded. Each is connected with the said line
name. See FE: Feature (Field Code), above, GM: Geometry on page 219 and PD: Point
Description on page 223 for more information.
…
AC:SS
PN:31358
PD:PKNAIL
FG:CL Figure (Line Name) = CL.
GM:XSEC
HZ:350.2531
VT:92.3510
DS:639.124
218 Data Collection

.
.
AC:SS
.
GM: Geometry
The data tag GM: establishes how a line is to be placed in the CAD graphic. This may start
the line; stop the line; close the line back to the start; place line as an arc or fitted curve
segment(s); join the last shot recorded to the current line; perform a bearing close; or read
the line as a line pattern name.
You may enter the defined designators listed in the designators dialog box or the defined
values listed below:
Line
Curve
Close
Stop
Join Last
B-Close
X-Section
! If you use GEODAT Labels or Leica Codes, also refer to Collectors and Formats, which
begins on page 129, for additional methods of input.
When the geometry is not specified, or there is no value for the GM: data tag, the activity is
processed as a line segment.
! The GM: data tag may only be used in conjunction with the FG: data tag within an activity.
See FE: Feature (Field Code) on page 218, FG: Figure on page 218, or PD: Point
Description on page 223 for more information.
…
AC:SS
PN:13256
FG:TOPBANK Appendix F: EP SDMS
GM:CURVE This shot is on a curve (POC).
HZ:358.0029
VT:91.3951
DS:481.937
.
.
AC:SS

PN:13257
FG:TOPBANK
GM:- This shot is on a curve using the default designator ‘-’ for a curve
segment.
HZ:12.0143
VT:90.1231
DS:433.127
.
HZ: Horizontal Angle

The data tag HZ: defines the recorded horizontal vernier reading on the instrument. This
value represents a numeric angular value on the horizontal plane.
! A positive horizontal circle value is assumed to be in a clockwise direction (angle right),
whereby a negative circle value is assumed to be in a counterclockwise direction (angle
left).
…
AC:SS
PN:995
PD:MH.EL
HZ:45.0235 Horizontal circle reading of 45°2’35”.
VT:90.0257
DS:79.129
.
.
AC:SS
.
IH: Instrument Height

The data tag IH: defines the height of the instrument at the occupied station. This value
represents the vertical distance from the survey point to the vertical index of the
instrument. When a value is not entered, the default value is zero (0).
The IH: data tag is used as a constant during computations. When the instrument height is
recorded in the file, it is retained to be applied to all subsequent shots until a new
instrument height is entered.
…
AC:OS
PN:1
PD: POB
220 Data Collection

IH:5.520 Instrument Height = 5.520.
SH:5.000
YC:5000.000
XC:5000.000
.
.
AC:BS
PN:1001
.
LO: Length Offset

The data tag LO: defines a numeric value representing the length offset. The offset is
determined from the target to the desired point in front or behind the target location. The
LO: tag only affects the current shot where it is placed.
When the desired point is located between the instrument and the target, enter the
distance as a negative number (LO:-3.4). When the desired point is located beyond the
target location, enter the distance as a positive number (LO:3.4).
! The target must be on the line of sight of the point for the desired point location to be
determined properly.
Appendix F: EP SDMS
Figure F-3 LO: Data Tag Diagram
…
AC:SS
PN:3792
PD:BUILD COR
HZ:72.2131

VT:89.5523
DS:203.678
LO:12.0 The BUILD COR is 12 meters behind the target.
.
.
AC:SS
.
OF: Offset
The data tag OF: defines a numeric value representing a perpendicular offset. The offset
distance is determined from the target to a desired point that is set to the left or right of the
target whereby the target cannot be seen from the instrument on the desired point. This
offset value will only affect the current shot.
When the desired point that is offset appears to the left of the target (from the instrument),
enter the offset as a negative number (OF:-12.4). When the desired point appears to the
right of the target (from the instrument), enter the offset as a positive number (OF: 6.0).
! The offset direction is determined by the line of sight when facing the point from the
instrument.
Figure F-4 OF: Data Tag Diagram
…
AC:SS
PN:1501
PD:ELMH
HZ:13.0125
VT:90.0231
DS:130.351
OF:9.00 Desired point appears 9 meters to the right of the target.
.
222 Data Collection

.
AC:SS
.
PD: Point Description

The data tag PD: provides a short meaningful description of the current shot and does not
effect computations. Use the PD: data tag as an overall or qualifying description of the
point. You may enter up to 125 characters for the description value.
When processing the descriptor field from most data collection formats, the description
may actually contain Field Code, line information, special designators and additional
descriptive information. The default format for this is as follows:
<<FIELD CODE>><<LINE DESIGNATOR>><<LINE NAME>><<SPACE>><<DESCRIPTION>>
This structure actually encompasses the functionality of the FE: (Feature/Field Code), FG:
(Figure/Line Name), GM: (Geometry/Designator), and PD: (Point Description) data tags.
See FE: Feature (Field Code) on page 218, FG: Figure on page 218, or GM: Geometry on
page 219.
This structure is used when processed through Data Collection and only with certain data
collection formats. See Data Collection Concepts, which begins on page 1.
! If you are using the FE:, FG: and GM: data tags within the same activity, the PD: data tag
is used only as a description value.
…
AC:SS
PN:1509
PD:MH.EL.CL_#175 IOWA POWER
YC:500.025
XC:79325.795
ZC:103.25
.
.
AC:SS
.
This example shows a portion of an SDMS file that may be processed through Data Appendix F: EP SDMS
Collection. The description contains a Field Code (MH) with two different lines processed
through it (EL and CL) using the default line designator (.). Additionally, the description for
this shot is #175 IOWA POWER which is separated by the space following the .CL line
name.

PN: Point Number
The data tag PN: defines an alphanumeric value used to identify a Node ID or point
number in the field. The Node ID value is that of the current shot. The data tag must be
entered in the activity it applies to and it must be unique to the activity.
…
AC:OS
PN:22 Numeric Node ID
IH:5.00
SH:5.00
.
.
AC:BS
PN:B1000 Alphanumeric Node ID
.
PO: Prism Offset

The data tag PO: defines a numeric value representing the prism offset. This is
determined to be the distance from the desired point to a prism placed on a different point
whose location can be seen from the instrument. This tag should be used with the Offset
Direction (DO:) data to indicate whether the prism offset is in the horizontal or vertical
direction. See DO: Offset Direction on page 216.
When facing the point (from the instrument) and the prism offset is to the left, enter a
positive value.
PO:20.0
When facing the point (from the instrument) and the prism offset is to the right, enter a
negative value.
PO:-20.0
224 Data Collection

! The offset direction is determined by the line of sight when facing the instrument from the
point, or the opposite of that of the OF: Data Tag. See OF: Offset on page 222.
Figure F-5 PO: Data Tag Diagram
…
AC:SS
PN:35
HZ:180.0032
VT:90.0000
DS:50.0
PO:-20.0 Prism offset of -20.0
DO:H
AC:SS
PN:36
HZ:180.0032
VT:90.0000
DS:50.0
PO:-40.0 Prism offset of -40.0
DO:H
.
PR: Project Name

Appendix F: EP SDMS
The data tag PR: may either be the name of the primary drawing of the project, or the
name of the surveyed job file. This data tag must be the first data tag in the SDMS file, and
there should only be one PR: data tag per file. The length of the name is limited to eight
characters and must meet all limitations for the operating system or data collector (i.e. no
spaces or wild cards).

If you have an SDMS file that was created from another program, it may not have the
required heading on it. Each SDMS file must begin with a PR: data tag followed with a TK:
(Task) data tag. The task is typically COM (Combined Survey). See TK: Task on page 229.
! The PR: data tag is different than the Project activity (PR) which has no limit to the number
of occurrences in the file.
PR:941011A Project Name is 941911A.

TK:COM
AC:PR
IT:T1610
SN:3533A15
NM:SMI48
TE:123
BP:90.012
RE:NEUMANN
DT:NOV-10-98 8:32AM
WE:COLD WINDY
.
.
AC:OS
.
RO: Radial Offset

The data tag RO: defines an angular value representing the radial offset. A radial offset to
the left or right of a point is recorded when the target cannot be placed directly on the
desired point. This offset value will only affect the current shot.
When the desired point that is offset appears to the left of the target (from the instrument),
enter the offset as a negative angular value (OF:-32.2000). When the desired point
appears to the right of the target (from the instrument), enter the offset as a positive
number (OF: 60).
226 Data Collection

! The offset direction is determined by the line of sight when facing the point from the
instrument.
Figure F-6 Radial Offset Example
…
AC:SS
PN:37
HZ:180.0032
VT:90.0000
DS:50.0
RO:30.0 Radial offset of 30°
AC:SS
PN:38
HZ:180.0032
VT:90.0000
DS:50.0
RO:60.0 Radial offset of 60°
.
SH: Staff Height

The data tag SH: defines a numeric value representing the staff height. This is also
considered to be the same as the height of the target, rod or prism for each shot. The SH: Appendix F: EP SDMS
data tag may be initialized anywhere, but is typically set in the occupied station or the
backsight. When a value is not entered, the system uses the default value of zero (0).
The SH: tag is used as a constant during computations. The system uses the value for the
activity and applies it to all subsequent shots until a new staff height is entered.
! The SH: data tag must be entered either to change the staff height value or to reset back
to the original value.

…
AC:OS
PN:2
PD:POB
IH:1.85
SH:1.7 Staff Height set at 5:00
YC:5000
XC:5000
ZC:100
.
.
AC:BS
PN:1
.
SS: Nominal Stationing

The data tag SS: defines a numeric value representing a nominal or computed station
along an alignment. This value is typically a rounded station value, even though it may be
different from the actual station value of the shot. The actual station value of the shot is
recorded by the ST: data tag. See ST: Stationing, below.
! The Data Tag SS: should be used for route or cross-sectional surveys that will be
transferred directly to RoadCalc™. You may place this anywhere within the activity.
! The SS: data tag is different than the activity Sideshot (AC:SS) which may be contained in
the file as much as needed.
…
AC:SS
PN:3931
FE:EOC
FG:EPL
HZ:88.2939
VT:90.0039
DS:107.397
SS:500.00 A fixed normal station = 5+00.00.
.
ST: Stationing
The data tag ST: defines a numeric value representing a station on the alignment. This
may be the distance along an alignment from an arbitrary starting point.
228 Data Collection

You may enter the value using either decimal or by inserting a plus ‘+’ at the proper station
within the station value. For example, 1200.34 and 12 + 00.34 are valid stationing values.
…
AC:SS
ST:2501.13 Actual recorded station value of 2 + 501.13
PN:501
PD:.EPL
OF:-12.01
RR:5.24
.
TK: Task
The data tag TK: defines the type of surveying task that is performed in the file. The only
task that is currently used by Eagle Point is the Combined Survey task (COM) which may
be a combination of traverse and sideshot information. This data tag must be the second
data tag in the SDMS file, and there should only be one TK: data tag per file.
If you have an SDMS file that was created from another program, it may not have the
required heading on it. Each SDMS file must begin with a PR: (Project Name) data tag
followed with a TK: data tag. The project name is typically that of the name of the file from
the data collector.
See PR: Project Name on page 225.
PR:941011A
TK:COM Task is a Combined survey
AC:PR
IT:T1610
SN:3533A15
NM:TDS48
TE:123
BP:90.012
RE:NEUMANN
DT:NOV-10-98 8:32AM
WE:COLD WINDY
.
Appendix F: EP SDMS
.
AC:OS
.

VO: Vertical Offset
The data tag VO: defines a numeric distance representing the temporary adjustment of the
staff. This distance is added to the current value for data tag SH: (Staff Height) only for the
current activity.
See SH: Staff Height on page 227.
Figure F-7 VO: Data Tag Diagram
…
AC:SS
PN:1602
VO:3.00 Added 3.00 only to this activity. Next activity is unaffected.
HZ:176.3941
VT:89.2310
DS:123.219
.
VT: Vertical (Zenith) Angle

The data tag VT: defines the zenith angle measurement from the occupied station to the
target. The angular data item must be entered into the activity that it applies to and it must
be unique to that activity.
When recording distances, it is common to use the combination of the DS: (Slope
Distance) and VT: data tags.
230 Data Collection

You may also use the HD: (Horizontal distance) and VD: (Vertical distance) data tags to
record the same information. See DS: Slope Distance on page 217.
Figure F-8 VT: Data Tag Diagram
…
AC:CC
PN:15
PD:TBM#35
HZ:33.3148
VT:93.2554 Vertical angle of 93.2554
DS:135.972
.
.
AC:SS
.
XC: X Coordinate Value

The data tag XC: defines the value of the X or Easting coordinate. To place a point in the
CAD graphic or the External Node Database, there must either be a calculated X
coordinate value or the file must have enough raw instrument information to place the
point in the correct location.
…
AC:OS
PN:5
PD:IP TM#18 Appendix F: EP SDMS
IH:0.00
SH:0.00
YC:5000.000
XC:5000.000 Easting coordinate = 5000.000.
ZC:1000.000
.
.

AC:BS
PN:4
.
YC: Y Coordinate Value

The data tag YC: defines the value of the Y or Northing coordinate. To place a point in the
CAD graphic or the External Node Database, there must either be a calculated Y
…
AC:OS
PN:5
PD:IP TM#18
IH:0.00
SH:0.00
YC:5000.000 Northing coordinate = 5000.000.
XC:5000.000
ZC:1000.000
.
.
AC:BS
PN:4
.
ZC: Z Coordinate Value/Elevation

The data tag ZC: defines the value of the Z or elevation coordinate. To place a point in the
CAD graphic or the External Node Database, there must either be a calculated Z
! If you do not know the ZC: value for a known point in the file, you may leave a zero value
initially, but will need to calculate the elevation either through your data collector’s station
resection routine, or from the calculated elevation towards the end of your file.
…
AC:OS
PN:5
PD:IP TM#18
IH:0.00
SH:0.00
YC:5000.000
232 Data Collection

XC:5000.000
ZC:1000.000 Elevation coordinate = 1000.000.
.
.
AC:BS
PN:4
.
Reserved Eagle Point SDMS Data Tags

The data tags listed are reserved for the uses described below. Data Collection, COGO,
Data Transfer and Survey Adjustment all use the SDMS structure for processing and/or
storing information in the SDMS format. It is recommended that the data tags outline be
used for the described purpose when importing or downloading any information from other
SDMS - based systems.
Data Tags Outline
Tag Description Possible Values/Examples

AC Activity BS= Backsight
CC= Control Check
CK= Check Shot
EC= Elevation Control
FS= Foresight
OS= Occupied Station
PR= Project
SR= Station Resection
SS= Sideshot
TP= Turn Point
AD Angular Std. Dev. (0.1-120)
AE Adjust Elevations ELEVATIONS= Adjust Elevations
Appendix F: EP SDMS
PROPORTIONAL= Adjust Elevations Proportional
NO= No Elevation Adjustment
AG Adjust Angles CLOSED_TRAVERSE= Adjust Angles w/ Closed Traverse

OPEN_TRAVERSE= Adjust Angles w/ Open Traverse
NO= No Angle Adjustment
AI Alignment ID Numeric Alignment ID

Data Tags Outline
AM Adjustment Method 0= Compass Adjustment

1= Crandall Adjustment
2= Least Squares Adjustment
3= Transit Adjustment
4= No Adjustment
AR Square Area (Any numeric value)
AS Adjust Sideshots (Y/N)? YES= Adjust Sideshots

NO= No Sideshot Adjustment
AT Alignment Type COGO= COGO Alignment

ROADCALC= RoadCalc™ Alignment
WATERSURFACE= Water Surface Profiling Alignment
OTHER
AZ Azimuth 0 - 360° (Any numeric value)
A0 Attribute 0 (Any alphanumeric value)
BC Back Circle 0 - 360° (Any numeric value)
BD Backsight Direction Angle 0 - 360° (Any numeric value)
BP Barometric Pressure (Any numeric value)
BS Backsight Point Number (Any Node ID value)
234 Data Collection

Data Tags Outline
CA Curve Adjustment To Maintain 0= Maintain Arc Length

1= Maintain Degree of Curve
2= Maintain Delta Angle
3= Maintain External Distance
4= Maintain Middle Ordinate
5= Maintain Radius
6= Maintain Tangent
CD Curve Direction Method TANGENT DIRECTION

RADIAL DIRECTION
CHORD DIRECTION
CE Collimation Error (Any numeric value)
CF Combination Factor (Any numeric value)
CI City (Any alphanumeric value)
CL Class F= Feature
G= Ground
CM Comment (Any alphanumeric value)
CN Condition (Any alphanumeric value)
CO County (Any alphanumeric value)
CP Close Project (Any alphanumeric value)
CR Curvature & Refraction Adjust? YES= CR adjustments applied

NO= CR adjustments not applied
CT Closing Angle Type ANG_NONE= No Closing Angle

ANG_RIGHT= Angle Right
ANG_LEFT= Angle Left
CW Clockwise (Angle Direction) CLOCKWISE

COUNTER_CLOCKWISE
Appendix F: EP SDMS
DA Curve Delta Angle 0 - 360° (Any numeric value)
DC Degree of Curvature - Arc 0 - 360° (Any numeric value)

definition
DD Computed Distance (Any numeric value)
DH Degree of Curvature - Chord 0 - 360° (Any numeric value)

definition

Data Tags Outline
DI Diameter (Any numeric value)
DL Delete Shot/Station SH= shot

ST= station
DO Offset Direction H= Horizontal

V= Vertical
DP Depth (Any alphanumeric value)
DS Slope Distance (Any numeric value)
DT Date (Any alphanumeric value)
ED Error Distance (Any numeric value)
EF Error Ellipse Scale Factor (Any integer value)
EI Error Ellipse Confidence Interval STD= Standard Interval

90= 90 Percent
95= 95 Percent
99= 99 Percent
EH Error Horizontal Angle (Any numeric value)
EQ Station Equations (Any alphanumeric value)
ES Ending Station YES= current OS is ending station

NO= current OS is not ending station
ET External Distance (Any numeric value)
EV Error Vertical Angle (Any numeric value)
EX Error in Easting (X) (Any numeric value)
EY Error in Northing (Y) (Any numeric value)
EZ Error in Elevation (Z) (Any numeric value)
FC Face Number 1= direct face

2= reverse face
FD Foresight Direction NE_BEAR= North East Bearing

SE_BEAR= South East Bearing
SW_BEAR= South West Bearing
NW_BEAR= North West Bearing
NORTH_AZ= North Azimuth
SOUTH_AZ= South Azimuth
236 Data Collection

Data Tags Outline
FE Feature/Field Code (Any alphanumeric value)
FG Figure (Any alphanumeric value)
GD Grade (Any numeric value)
GM Geometry (Any alphanumeric value)

BBCLOSE= Bearing-Bearing Close
CLOSE= Close Line
COMBINING= Combining Spiral Point
CURVE= Curve Point
JLAST= Join to last shot
POINT= Point Object
LINE= Point on Line
SPIRAL IN= Transition Spiral in Point
SPIRAL OUT= Transition Spiral Out Point
STOP= Stop Line
XSEC= Point on Cross-Section
GR Group (Any alphanumeric value)
HA Horizontal Align. Control File (Any alphanumeric value)
HD Horizontal Distance (Any numeric value)
HH Computed Horizontal Angle 0 - 360° (Any numeric value)
HT Height (Any alphanumeric value)
HY Highway/Alignment Name (Any alphanumeric value)
HZ Horizontal Angle 0 -360° (Any numeric value), all values are assumed to be
clockwise
H1 Horizontal Angle Face 1 0 - 360° (Any numeric value)
H2 Horizontal Angle Face 2 0 - 360° (Any numeric value)
ID Project ID (Any alphanumeric value)
Appendix F: EP SDMS
IH Instrument Height (Any numeric value)
IN Station Instance Number (Any integer value)
IT Instrument Type (Any alphanumeric value)
I0 Information 0 (Any alphanumeric value)
I2 Information 2 (Any alphnumeric value)

Data Tags Outline
LD Linear Std. Dev. (0.0 - 1.0)
LG Longitude (Any alphanumeric value)
LH Length of Chord (Any alphanumeric value)
LN Length (line, arc or spiral) (Any alphanumeric value)
LO Length Offset (Any numeric value)
LS Length of Spiral (Any numeric value)
LT Latitude (Any alphanumeric value)
L1 Primary Location Control File (Any alphanumeric value)
L2 Secondary Location Control File (Any alphanumeric value)
MH Horizontal Direction Method ABSOLUTE

GEOMETRIC
TO_POINT
TWO_POINTS
BACKSIGHT_ABSOLUTE
BACKSIGHT_GEOMETRIC
BACKSIGHT_TO_POINT
BACKSIGHT_TWO_POINTS
MO Middle Ordinate (Any numeric value)
NI Number of Iterations (1-20)
NM Name (Any alphanumeric value)
NS Number of Shots (Any integer value)
OB Observer (Any alphanumeric value)
OD Origin/Destination (Any Node ID value)
238 Data Collection

Data Tags Outline
OF Offset (Any numeric value)
OO Computed Offset (Any numeric value)
OP Distance Option HORIZONTAL_DISTANCE

DISTANCE_TO_POINT
TWO_POINTS_DISTANCE
SLOPE_DISTANCE
STADIA_DISTANCE
OW Owner (Any alphanumeric value)
PC Prism Correction (Any numeric value)
PD Point Description (Any alphanumeric value)
PH Physical/Block/Cell (Any alphanumeric value)
PI Station at curve PI (Any alphanumeric value)
PM PPM Factor (Any alphanumeric value)
PN Point Number (Any Node ID value)
PO Prism Offset (Any numeric value)

SPIRAL OUT= Transition Spiral Out Point
STOP= Stop Line
XSEC= Point on Cross-Section
PR Project Name (Any alphanumeric value)
PT Station at curve PT (Any alphanumeric value)
RA Radius (Any numeric value)
RD Ring Description (Any alphanumeric value)
RE Recorder (Any alphanumeric value)
RN Ring Number (Any integer value)
RO Radial Offset 0 - 360° (Any numeric value)
RR Rod Reading (Any numeric value) Appendix F: EP SDMS

RS Ring Style (Any alphanumeric value)
RT Rod Type F= foot rod

Y= yard rod
M= Meter rod
R1 Top Wire Rod Reading (Any numeric value)

Data Tags Outline
R2 Middle Wire Rod Reading (Any numeric value)
R3 Bottom Wire Rod Reading (Any numeric value)
S1 Primary Staking Control File (Any alphanumeric value)
S2 Secondary Staking Control File (Any alphanumeric value)
SD Station Direction UP= shots taken up station

DOWN= shots taken down station
SE Set Number (Any integer value)
SF Scale Factor (Any numeric value)
SH Staff Height (Any numeric value)
SI Shot ID BL= begin LOC shots

EL= end LOC shots
RTO= radial topography shot
XSE= cross-section shot
PT= tangent point
PC= point of curve
CS= curve to spiral
SC= spiral to curve
ST= sprial to tangent
TS= tangent to spiral
SL Sea Level Correction (Y/N)? YES= Sea Level Correction Used

NO= Sea Level Correction Not Used
SN Instrument Serial Number (Any alphanumeric value)
SP Suspend Project (Any alphanumeric value)
SR Station Resection Solution NORTH= Point North Selected

EAST= Point East Selected
SOUTH= Point South Selected
WEST= Point West Selected
PICK= Point Graphically Selected
OTHER= Point-Number Selected
SS Computed Stationing (Any alphanumeric value)
ST Stationing (Any alphanumeric value)
SU Subproject Number (Any integer value)
240 Data Collection

Data Tags Outline
TA Tangent Curve (Any numeric value)
TD Tunnel Direction INBOUND/OUTBOUND
TE Temperature (Any numeric value)
TI Tunnel ID (Any alphanumeric value)
TK Task COM= Combined

CON= Control Network
PHO= Photo Control
RTO= Radial Topography
TMO= Terrain Model
TRA= Traverse
XSE= Cross-Section
LEV= Level Run
PRO= Profiling
3WR= Three-Wire Level
TM Time (Any alphanumeric value)
TN Traverse Number (Any integer value)
TO Acceptable Tolerance (0.0 - 1.0)
TS Dat/Time Stamp (Any alphanumeric value)
TY Type/Layer/Level (Any alphanumeric value)
UA Units - Angles D= Decimal Degrees

DMS= Degrees, Minutes, Seconds
G= Grads
M= Mils
R= Radians
UL Units - Lengths F= Feet

M= Metric
UP Units - Pressure Units - Temperature

Appendix F: EP SDMS
V1 Vertical Angle Face 1 0 - 360° (Any numeric value)
V2 Vertical Angle Face 2 0 - 360° (Any numeric value)
VA Vertical Align. Control File (Any alphanumeric value)
VD Vertical Distance (Any numeric value)
VE Vertical Index Error (Any numeric value)

Data Tags Outline
VL Volume (Any numeric value)
VO Vertical Offset (Any numeric value)
VR Version Number (Any alphanumeric value)
VT Vertical (Zenith) Angle 0 - 360° (Any numeric value) assumed to be zenith (90° is
horizontal)
VV Computed Vertical Angle 0 - 360° (Any numeric value) assumed to be zenith (90° is
horizontal)
WC Write Control File (Any alphanumeric value)
WD Width (Any alphanumeric value)
WE Weather (Any alphanumeric value)
WI Witness Description (Any alphanumeric value)
W3 Three-Wire Stadia Constant (Any numeric value)
XC X (Easting) Coordinate (Any numeric value)
XD XY (Horizontal) Datum (Any alphanumeric value)
XX Computed Y Coordinate (Any numeric value)
YC Y (Northing) Coordinate (Any numeric value)
YY Computed Y Coordinate (Any numeric value)
ZC Z Coordinate/Elevation (Any numeric value)
ZD Z (Vertical) Datum (Any alphanumeric value)
ZZ Computed Z Coordinate (Any numeric value)
-- Wild Card (Any alphanumeric value)
// Insert a Sequence (Any alphanumeric value)
$A EDM Type (Any alphanuemric value)
$B EDM Description (Any alphanumeric value)
$C EDM Serial Number (Any alphanumeric value)
$D Greenwich Hour Angle (GH0 & (Any numeric value)

GH24)
$E Mounting Type (Any alphanumeric value)
$F Curvature And Refraction (Y/N)? YES= Atmosphere Correction was Performed

NO= Atmosphere Correction was Not Performed
242 Data Collection

Data Tags Outline
$G EDM Offset (Any alphanumeric value)
$H Reflector Offset (Any numeric value)
$I Prism Constant (Any numeric value)
$K Occupied Station Point Number (Any Node ID value)
$N Left Template (Any alphanumeric value)
$O Right Template (Any alphanumeric value)
$Q Cut Grade (Any numeric value)
$R Fill Grade (Any numeric value)
$S Delta Station (Any numeric value)
$T Delta Offset (Any numeric value)
$U Atmosphere Correction (Y/N)? YES= Atmosphere Correction Was Performed

NO= Atmosphere Correction Was Not Performed
$V Inverted Angle 0 - 360° (Any numeric value)
$W Declination 0 - 360° (Any numeric value)
$X Semi-Diameter of the Sun (Any numeric value)
$Y Backsight Direction 0 - 360° (Any numeric value)
$Z Foresight Direction 0 - 360° (Any numeric value)
&A Vertical Angle Type 1= Zenith

2= Horizontal
RATIO
ZENITH
HORIZONTAL
NADIR
%=% Grade
$1 Foresight Reverse (Any numeric value)
$2 Backsight Reverse (Any numeric value)( Appendix F: EP SDMS

$3 Left Trailing Edge of the Sun 0 - 360° (Any numeric value)
$4 Right Trailing Edge of the Sun 0 - 360° (Any numeric value)
$5 Center Sun Position 0 - 360° (Any numeric value)

Data Tags Outline
$6 Offset Direction 0= Center

1= Right
2= Left
CENTER
LEFT
RIGHT
$7 Azimuth Direction 0= North

1= South
NORTH
SOUTH
$9 Zenith Direction 0 - 360° (Any numeric value)
Minimum Setup Information

General survey practice is assumed to be common knowledge to all users of the
surveying products within Eagle Point; however, there are specific requirements that exist
from a field procedure standpoint to ensure ‘enough’ data is collected in the field. This is
especially true when using a collection system that is customizable, such as Geodimeter
or Leica. See Geodat Labels, which begins on page 117, for GEODAT, Leica Codes,
which begins on page 123, for Leica, and Collectors and Formats, which begins on page
129, for these and other brands of collection systems.
Initial Setup
When collecting information in the field using a data collector, or processing raw
instrument information through Data Collection, there is a minimum amount of
information that is needed to process the raw instrument information correctly.
If the data that you typically work with has coordinate values for every point in the file, then
the raw instrument information (if any exists) is not needed to process the data.
Occupied Station
To process raw instrument observations, the initial setup needs to contain information for
the occupied station and the backsight. The occupied station needs to have coordinate
values, either in the SDMS data file or in the project itself derived from an existing Node.
244 Data Collection

From within the data file, the coordinates may be included in the same activity as the
occupied station (AC:OS), or as a keyed in value which may reside in a sideshot (AC:SS)
located prior to the occupied station in the file.
If you are processing the job file into a project that already has a coordinate for the initial
occupied station, such that there is a Node with the same Node ID either in the External
Node Database (END) or in the CAD graphic, then the coordinate value does not need to
be recorded in the job file. At a minimum, only the Node ID of the occupied station needs
to be in the occupied station activity. This will display the SDMS Set Up Data dialog box
(Figure F-9 on page 246) to verify the coordinate information used from the project.
Backsight
The backsight must also be recorded with coordinate values in the backsight (AC:BS) or
as a keyed in value in a side shot (AC:SS). The backsight may also be entered as an
azimuth value (AZ:) in the backsight activity. See AZ: Azimuth on page 215.
For the initial backsight, the backsight record must occur immediately following the
occupied station to be computed correctly. This may be in the form of a coordinate value
and a horizontal circle reading (HZ:), or just an azimuth value (AZ:). If the azimuth is
recorded, and a circle reading is not recorded, then it was assumed that the gun was
zeroed on the backsight. If a value other than zero was recorded on the backsight circle
reading, then there also needs be a horizontal circle reading (HZ:) recorded to the file.
Just as with the initial occupied station, if there is already coordinate information for the
initial backsight, such that there is a Node with the same Node ID either in the External
Node Database (END) or in the CAD graphic, then the coordinate value does not need to
be entered in the job file. At a minimum, only the Node ID of the backsight needs to be in
the backsight (AC:BS). A circle reading of zero is assumed at this point.
If more information is needed to process the file, or if coordinate values are being read
from the project, then the SDMS Set up Data dialog box, shown in Figure F-9 on page 246
will display.
Appendix F: EP SDMS

You may enter or modify the appropriate information for the occupied station and the
backsight in this dialog box. Click on Apply to confirm the information for data in each
portion in the SDMS Setup Data dialog box (below).
Figure F-9 SDMS Setup Data Dialog Box
SDMS Setup Data Dialog Box Definitions

PIC Click on the PIC icon to graphically select a Node, snap to a point, or pick a
coordinate from the CAD graphic.
Node ID Type the occupied station/backsight Node ID used to record a measurement for
the point number specified at the top of the dialog box. Put a check in the box
next to the value to use it during reduce.
Northing Type the Northing coordinate value for the occupied station/backsight. Put a
Easting Type the Easting coordinate value for the occupied station/backsight. Put a
Elevation Type the elevation value for the occupied station/backsight. Put a check in the
Instrument Type the instrument height for the occupied point. Put a check in the box next to
Height the value to use it during reduce.
Instrument Type the instrument elevation for the occupied station. Put a check in the box
Elevation next to the value to use it during reduce.
! This value is the resultant of the elevation and the instrument height.
Modifying this value will adjust the elevation for the occupied point.
Station Type the station value of the occupied station. Put a check in the box next to the
Description Type the description for the occupied station. Put a check in the box next to the
246 Data Collection

SDMS Setup Data Dialog Box Definitions
Options Select the type of direction to use for entering the backsight. You may select
one of the six supported bearing and azimuth types from the drop list of formats.
Direction Type the direction of the backsight based on the direction type selected (either
Absolute or Geometric).
See Concepts in the COGO manual.
Vertical Angle Type the vertical angle that was recorded from the occupied station to the
backsight. Put a check in the box next to the value to use it during reduce.
Add data to file Turn this toggle on to add the data to the file.
Intermediate Setup
At a minimum, the intermediate setups in the file need to contain information for the
occupied station only. It is assumed that through a normal traverse sequence that the
previously occupied station is the backsight for the intermediate setup.
Intermediate Occupied Station

The occupied station will also have coordinate values calculated from a recorded foresight
or sideshot earlier in the file, as a keyed-in sideshot (AC:SS) coordinate entered at the top
of the file, or from a Node ID that already exists in the project. Therefore, only a Node ID
value number would need to be recorded at a minimum to process the file.
Intermediate Backsight
Unless there is additional information, it is assumed that the instrument vernier is zeroed
on the backsight and the backsight is the previously occupied station. If this not the
situation, then the backsight record must occur immediately following the occupied station
to be computed correctly. This may be in the form of a coordinate value and a horizontal
circle reading (HZ:), or just an azimuth value (AZ:). If the azimuth is recorded, and a circle
reading is not recorded, then it was assumed that the gun was zeroed on the backsight. If
a value other than zero was recorded on the backsight, then there also needs be a
horizontal circle reading recorded as well.
Appendix F: EP SDMS

248 Data Collection
DATA
COLLECTION GLOSSARY
OF
TE R M S
3-D Line Template
You may associate a series of approximated
geometry, or template, with a single shot in the field.
The points and lines for the remainder of the template
are automatically drawn in the CAD graphic based on
the location of the origin shot for each template. This
may be used to automatically generate curb and
gutter sections, sidewalks, ditches or any other
existing feature that only needs to be approximated.
Activity
This is a two character data tag that is associated with
a surveying activity or function. Entered and recorded
information are separated by what activity they are a
part of. For example, information associated with the
occupied station, such as the point number,
instrument height and coordinate values would all be
associated with the Occupied Station (OS:) activity.
Backup File
This file is a duplicate of the original downloaded or
imported instrument file, and may be reverted to in the
event that unwanted changes were made to the
instrument file. It also serves as a legal backup, as the
file is attributed read-only. The downloaded date and
time are stored and displayed in the File Information
dialog box in Data Collection in the event the validity
of the backup file is questioned.
Glossary of Terms 249

Cross-section Pattern
You may record existing cross-sectional data by using a repeating pattern in the field.
The entire pattern may be recorded using the same line name for each shot taken,
then the lines are separated by processing the list of lines based on how they were
recorded (side to side or in a zigzag fashion).
Data Tag
This is a two character label that is used to associate various surveying activities, raw
measurements or information entered in the field. For example, the instrument height
will be associated with the IH: data tag.
Download
This is the process of sending data from a data collector to the Data Collection
product. Data that is downloaded may be post-processed by reducing the job into the
project.
Fitted Alignment
You may record existing alignment data from the field and process it as to approximate
the original tangent-curve geometry. Multiple shots that are recorded along a curved
portion will be approximated to a single curve or arc with tangents on either end.
Formatted File
This file has been formatted into the SDMS format. A formatted file is generated when
a Job is post-processed within Data Collection by previewing or reducing the job.
GEODAT Labels
These labels are associated with data tag values within Data Collection. They may be
used to read data directly a GEODAT data collector or a Geotronics total station into
the SDMS format.
Instrument File
This file is the raw data file in its original condition as it was downloaded or imported
into Data Collection. This file may be edited using any editor of your choice except for
the Field Book editor which can only edit files that are formatted in the SDMS format.
Job
A Job might consist of up to three data files. The instrument file is the original file that
was downloaded or imported into Data Collection. A backup file is a copy of the
instrument file that was made when the Job was downloaded. There is a date stamp
that is matched with the creation of the backup file, and the file is attributed read-only
to prevent editing. The formatted file is a file that has been translated into the Eagle
250 Data Collection

Point SDMS format for processing into the project. This file may then be brought into
Survey Adjustment for processing and generating reports.
Leica Codes
These codes are usable with a Leica or WILD data collector or total station. Each code
is associated with an activity and has one or more data tags used to read the
information presented in the instrument file.
Node
The text and symbol that are placed into the CAD graphic (or external database) that
identify points (Northing, Easting, elevation coordinate triplets) to reference within
various products.
Reduce
This is the process of converting the raw instrument data into coordinates that can be
placed in the project. Nodes are placed, lines are drawn and shot averaging
calculations are all performed in this process.
SDMS Format
This format is based on the AASHTO Survey Data Management System for recording
and processing survey data. The structure is based on two-character labels or data
tags that are assigned to various bits of survey information. The information is then
grouped by what surveying activity was used to record the information.
Shot Averaging
This is a process whereby only the highest priority shot type of a specific point number
is averaged to generate the coordinate of the point. Certain data collectors are flexible
enough to present the recorded data for any given shot several different ways. Data
may be displayed as keyed-in coordinates, raw slope distances and vertical angles,
horizontal and vertical distance observations, azimuth directions, and calculated
coordinates. Data Collection will record and report all instances to a point number, but
only those you specify as the highest priority will be used to actually calculate the
location.
Upload
This is the process of sending coordinate or other data to the data collector. You may
upload information directly from the project CAD graphic, External Node Database or
from an ASCII file.
Glossary of Terms 251

Use Field Code as Line Name
You only need to record the Field Code if there is a line name that is the same as the
Field Code. Each occurrence of the Field Code will be connected as though a line were
processed at the same location.
252 Data Collection

INDEX
Symbols Change of Field Code Example . . . . . . . . . . 164

Change Tag To . . . . . . . . . . . . . . . . . . . . . . . 112
>.....................................3 Changing Field Codes . . . . . . . . . . . . . . . . . . 164
Change of Field Code Example . . . . . . . 164
Numerics Circle Command Alias . . . . . . . . . . . . . . . . . . . 47
3-D Line Templates . . . . . . . . . . . . . . . . . . . . . 76 Clear . . . . . . . . . . . . . . . . . . . . . . 84, 85, 93, 115
3-D Line Templates Dialog Box . . . . . . . . 76 Close Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
New 3-D Line Template . . . . . . . . . . . . . . 77 Close Line Function . . . . . . . . . . . . . . . . . . . . 54
Code . . . . . . . . . . . . . . . . . . . . . . . . . . . 124, 126
A Code 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Code 1 Example . . . . . . . . . . . . . . . . . . 166
About . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Modifications to Code 1 (Azimuth) . . . . . 167
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . 124, 126 Modifications to Code 1 (Typical) . . . . . . 166
Add Column . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Code 1 - Project Setup . . . . . . . . . . . . . . . . . 150
Add data to file . . . . . . . . . . . . . . . . . . . . . 27, 247 Code 1 Example . . . . . . . . . . . . . . . . . . . . . . 166
Add Undefined Lines to Line Library . . . . . . . . 39 Code 100 - Sideshot . . . . . . . . . . . . . . . . . . . 153
All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Code 11 - Control Coordinates . . . . . . . . . . . 150
Alternative Downloading Steps . . . . . . . . . . . 178 Code 13 - New Target Height . . . . . . . . . . . . 151
Options . . . . . . . . . . . . . . . . . . . . . . 178, 179 Code 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Auto Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Modifications to Code 2 . . . . . . . . . . . . . 167
Average Coordinates & Elevations Code 2 - Instrument Setup . . . . . . . . . . . . . . 151
of Selected Nodes . . . . . . . . . . . . . . . . . . 96 Code 3 - Foresight . . . . . . . . . . . . . . . . . . . . 152
AZ: Azimuth . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Code 32 - Radial Sideshot . . . . . . . . . . . . . . 152
Azimuth Data Tag Diagram . . . . . . . . . . 216 Code 52 - Backsight . . . . . . . . . . . . . . . . . . . 151
Azimuth Data Tag Diagram . . . . . . . . . . . . . . 216 Code 99 - Sideshot . . . . . . . . . . . . . . . . . . . . 152
Code Block . . . . . . . . . . . . . . . . . . . . . . . . . . 149
B Code Block Example . . . . . . . . . . . . . . . 149
Backsight . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Code Block Example . . . . . . . . . . . . . . . . . . . 149
Backsight (BS) Activity . . . . . . . . . . . . . . . . . . 213 CODE.HEX . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Backup File . . . . . . . . . . . . . . . . . . . . . . . . 88, 89 Collecting Data . . . . . . . . . . . . . . . 132, 184, 201
Backup File Date . . . . . . . . . . . . . . . . . . . . . . . 86 Entering Field Codes into the Collector . . . 2
Backup File Size . . . . . . . . . . . . . . . . . . . . . . . 87 Line Work (Recommended for
Backup Filename . . . . . . . . . . . . . . . . . . . . . . . 86 Alphanumeric Instruments) . . . . . . . 142
Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . 10, 13 Line Work (Recommended for Non-
Bearing Close . . . . . . . . . . . . . . . . . . . . . . . . . 46 Alphanumeric Instruments) . . . . . . . 141
Beginning of SDMS File . . . . . . . . . . . . . . . . 211 UDS - 10 CROSS-SECTIONS . . . . . . . . 139
Block Example . . . . . . . . . . . . . . . . . . . . . . . . 148 UDS - 11 COMMENT . . . . . . . . . . . . . . . 140
UDS - 12 ACTIVITY LABEL . . . . . . . . . . 140
C UDS - 2 SETUP . . . . . . . . . . . . . . . . . . . 132
UDS - 3 CONTROL CHECK . . . . . . . . . 134
C-100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 UDS - 4 UTILITY WITH LINE WORK . . 134
Change Field Text . . . . . . . . . . . . . . . . . . . . . 112
Index 253
UDS - 5 UTILITY FEATURE . . . . . . . . . 135 Six Sideshots Recorded in a Face 1
UDS - 6 TOPOGRAPHY Position Example . . . . . . . . . . . . . . .157
WITH BREAKLINES . . . . . . . . . . . . 136 Traverse Example . . . . . . . . . . . . . . . . . .156
UDS - 7 TOPOGRAPHY . . . . . . . . . . . . 137 Collecting Data - Using codes based
UDS - 8 CONTROL ENTRY . . . . . . . . . 138 on WILDsoft . . . . . . . . . . . . . . . . . . . . . .150
UDS - 9 TRAVERSE AHEAD . . . . . . . . 138 Code 1 - Project Setup . . . . . . . . . . . . . .150
Collecting Data – Customizing Codes . . . . . 165 Code 100 - Sideshot . . . . . . . . . . . . . . . .153
Code 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Code 11 - Control Coordinates . . . . . . . .150
Code 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Code 13 - New Target Height . . . . . . . . .151
Numeric Activities . . . . . . . . . . . . . . . . . 165 Code 2 - Instrument Setup . . . . . . . . . . .151
Collecting Data – Entering Decimals on the Code 3 - Foresight . . . . . . . . . . . . . . . . .152
Instrument . . . . . . . . . . . . . . . . . . . . . . . 154 Code 32 - Radial Sideshot . . . . . . . . . . .152
Decimal values, example . . . . . . . . . . . . 154 Code 52 - Backsight . . . . . . . . . . . . . . . .151
No decimals method . . . . . . . . . . . . . . . 154 Code 99 - Sideshot . . . . . . . . . . . . . . . . .152
QuickSteps . . . . . . . . . . . . . . . . . . . . . . 154 Collecting Data: Field Codes, Entering . . . . . . .3
Collecting Data - Field Codes . . . . . . . . . . . . 154 Collector Computed Coordinates . . . . . . . . . . .42
Reduction Settings Example . . . . . . . . . 155 Collector Reduced Data . . . . . . . . . . . . . .42, 184
Collecting Data - Leica Instruments . . . . . . . 168 Collector tab . . . . . . . . . . . . . . . . . . . . . . . . . . .35
TPS Series . . . . . . . . . . . . . . . . . . . . . . 168 Collectors and Formats . . . . . . . . . . . . . . . . .129
VIP Series . . . . . . . . . . . . . . . . . . . . . . . 168 GEODAT . . . . . . . . . . . . . . . . . . . . . . . . .130
Collecting Data – Line Work Leica (WILD) . . . . . . . . . . . . . . . . . . . . . .148
(Recommended for Alphanumeric Maptech . . . . . . . . . . . . . . . . . . . . . . . . .174
Instruments) . . . . . . . . . . . . . . . . . . . . . . 161 Nikon . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Changing Field Codes . . . . . . . . . . . . . . 164 Pentax and Corvallis . . . . . . . . . . . . . . . .176
Intermediate Shots . . . . . . . . . . . . . . . . 164 Sokkia (Lietz) . . . . . . . . . . . . . . . . . . . . .182
Line Work Generated Using a Surveyor’s Module (SMI) . . . . . . . . . . . . .188
Cross-section Pattern . . . . . . . . . . . 163 Topcon . . . . . . . . . . . . . . . . . . . . . . . . . .200
Sample File that Contains Trimble/Tripod Data Systems (TDS) . . . .191
Cross-sectional Line Work Using the Zeiss . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
Code Block . . . . . . . . . . . . . . . . . . . 161 Color . . . . . . . . . . . . . . . . . . . . . . . . . . .59, 62, 66
Collecting Data – Line Work Command Indicator . . . . . . . . . . . . . . . . . . . . .47
(Recommended for Non-Alphanumeric Common Data Tags . . . . . . . . . . . . . . . . . . . .215
Instruments) . . . . . . . . . . . . . . . . . . . . . . 158 AZ:Azimuth . . . . . . . . . . . . . . . . . . . . . . .215
Default Implementation for a Code Not DO: Offset Direction . . . . . . . . . . . . . . . .216
Entered in the Current List . . . . . . . 158 DS: Slope Distance . . . . . . . . . . . . . . . . .217
Line Work Generated Using the FE: Feature (Field Code) . . . . . . . . . . . .218
Standard Method . . . . . . . . . . . . . . 161 FG: Figure . . . . . . . . . . . . . . . . . . . . . . . .218
Listing of Geometry Designators . . . . . . 158 GM: Geometry . . . . . . . . . . . . . . . . . . . . .219
Recorded Designator of 18 . . . . . . . . . . 159 HZ: Horizontal Angle . . . . . . . . . . . . . . . .220
Recorded Designator of 3 . . . . . . . . . . . 159 IH: Instrument Height . . . . . . . . . . . . . . .220
Sample File that Includes Line Work LO: Length Offset . . . . . . . . . . . . . . . . . .221
Using Numeric Designators . . . . . . 159 OF: Offset . . . . . . . . . . . . . . . . . . . . . . . .222
Collecting Data - Node ID . . . . . . . . . . . . . . . 153 PD: Point Description . . . . . . . . . . . . . . .223
Node ID Example . . . . . . . . . . . . . . . . . 153 PN: Point Number . . . . . . . . . . . . . . . . . .224
Collecting Data – Temporary Shots . . . . . . . 155 PO: Prism Offset . . . . . . . . . . . . . . . . . . .224
Temporary Shots Example . . . . . . . . . . 155 PR: Project Name . . . . . . . . . . . . . . . . . .225
Collecting Data – Traverse . . . . . . . . . . . . . . 156 RO: Radial Offset . . . . . . . . . . . . . . . . . .226
Face 1/Face 2 Shot Sequence SH: Staff Height . . . . . . . . . . . . . . . . . . .227
on Point 12 Example . . . . . . . . . . . 157 SS: Nominal Stationing . . . . . . . . . . . . . .228
254 Data Collection

ST: Stationing . . . . . . . . . . . . . . . . . . . . . 228 Delete Geodat Label . . . . . . . . . . . . . . . . . . . 119
TK: Task . . . . . . . . . . . . . . . . . . . . . . . . . 229 Delete Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
VO: Vertical Offset . . . . . . . . . . . . . . . . . 230 Delete Leica Codes . . . . . . . . . . . . . . . . . . . . 125
VT: Vertical (Zenith) Angle . . . . . . . . . . . 230 Delete Line . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
XC: X Coordinate Value . . . . . . . . . . . . . 231 Delete Line Library . . . . . . . . . . . . . . . . . . . . . 70
YC: Y Coordinate Value . . . . . . . . . . . . . 232 Delete Linetype Library . . . . . . . . . . . . . . . . . . 71
ZC: Z Coordinate Value/Elevation . . . . . 232 Delete Row . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Common Point Function . . . . . . . . . . . . . . . . . 54 Delete Selected Node(s) . . . . . . . . . . . . . . . . . 96
Communication Parameters Examples . . . . . 185 Description 3, 27, 70, 71, 72, 74, 76, 93, 96, 118,
Communication Settings . . . . . . . . 169, 172, 191 119, 121, 126, 128, 246
Confirm Each Replacement . . . . . . . . . . . . . . 112 Designators . . . . . . . . . . . . . . . . . . . . . . . 44, 142
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Bearing Close Designator . . . . . . . . . . . . 53
Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Circle Designator (Center Point
Copy Cross-Section Pattern . . . . . . . . . . . . . . 73 and Radius) . . . . . . . . . . . . . . . . . . . 56
Create Legal Backup File . . . . . . . . . . . . . 11, 15 Circle Designator (Three Point) . . . . . . . . 57
Created/Edited . . . . . . . . . . . . . . . . . . . . . . . . . 88 Close Line Designator . . . . . . . . . . . . . . . 52
Cross-Section . . . . . . . . . . . . . . . . . . . . . . . . . 46 Cross-Section Designator . . . . . . . . . . . . 53
Cross-Section Patterns . . . . . . . . . . . . . . . . . . 72 Curve Designator . . . . . . . . . . . . . . . . . . . 50
Cross-Section Patterns Dialog Box . . . . . 72 Designators and Associated Defaults . . . 48
New Cross-Section Pattern . . . . . . . . . . . 73 Designators Dialog Box . . . . . . . . . . . . . . 45
Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Examples . . . . . . . . . . . . . . . . . . . . . . . . . 48
Custom Translator . . . . . . . . . . . . . . . . . . . . . . 37 Feature Line (90 Degree Angles) . . . . . . . 57
Customize . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Feature Line (Entered Angles) . . . . . . . . . 58
Cut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Fitted Alignment . . . . . . . . . . . . . . . . . . . . 51
Fitted Alignment Using a Curve
D Designator . . . . . . . . . . . . . . . . . . . . 51
Insert Description Designator . . . . . . . . . . 55
D-50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Join Last Shot Designator . . . . . . . . . . . . 52
Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Line (Draw) Designator . . . . . . . . . . . . . . 49
Data Bits . . . . . . . . . . . . . . . . . . . . . . . . . . 10, 13
More Than One Line Per Shot . . . . . . . . . 50
Data Collection Concepts . . . . . . . . . . . . . . . . . 1
Multiple Shots Along a Curve . . . . . . . . . . 51
Entering Field Codes into the Collector . . . 2
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . 48
Field Entry Examples . . . . . . . . . . . . . . . . . 5
Rectangle Designator . . . . . . . . . . . . . . . 55
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
Shot 3 Has No Line Information . . . . . . . . 52
Node Selection . . . . . . . . . . . . . . . . . . . . . . 6
Stop Line Designator . . . . . . . . . . . . . . . . 54
Data Tag Diagram . . . . . . . . . . . . . . . . . . . . . 217
Use of a Bearing Close Designator . . . . . 53
Data Tags Outline . . . . . . . . . . . . . . . . . . . . . 233
Use of a Close Line Designator . . . . . . . . 52
Data Transfer, terminate . . . . . . . . . . . . . . . . . 11
Use of a Cross-section Designator . . . . . 54
Decimal . . . . . . . . . . . . . . . . . . . . . . . . . 126, 128
Use of a Curve Designator . . . . . . . . . . . . 50
Decimal values, example . . . . . . . . . . . . . . . . 154
Use of a Stop Line Designator . . . . . . . . . 55
Default Designators for Line Work Examples . . 5
Use of Join Last Shot Designator . . . . . . 53
Default Field Code . . . . . . . . . . . . . . . . . . . . . . 38
Use of Line (Draw) Designator . . . . . . . . . 49
Default Format . . . . . . . . . . . . . . . . . . . . . . . . . 36
Designators and Associated Defaults . . . . . . . 48
Default Implementation for a Code Not
Direction . . . . . . . . . . . . . . . . . . . . . . . . . 27, 247
Entered in the Current List . . . . . . . . . . . 158
Display Settings . . . . . . . . . . . . . . . . . . . 24, 116
Delete 3-D Line Template . . . . . . . . . . . . . 76, 78
DO: Offset Direction . . . . . . . . . . . . . . . . . . . 216
Delete Associated Line . . . . . . . . . . . . . . . . . . 75
Example . . . . . . . . . . . . . . . . . . . . . . . . . 216
Delete Cross-Section Pattern . . . . . . . . . . . . . 73
Download Coordinate Information from the
Delete Data Tag . . . . . . . . . . . . . . . . . . 121, 128
SMI Data Collector . . . . . . . . . . . . . . . . . 188
Index 255
Download from an AP700 or 800 Series Beginning of SDMS File . . . . . . . . . . . . .211
Instrument . . . . . . . . . . . . . . . . . . . . . . . 175 Common Data Tags . . . . . . . . . . . . . . . .215
Download from Collector . . . . . . . . . . . . . . . . . 10 Minimum Setup Information . . . . . . . . . .244
Download from Collector Dialog Box . . . . 10 Reserved Eagle Point SDMS Data
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 11 Tags . . . . . . . . . . . . . . . . . . . . . . . . .233
Download Raw Survey Information from the Surveying Activities . . . . . . . . . . . . . . . . .211
SMI Data Collector . . . . . . . . . . . . . . . . 189 Erase on Re-Reduce . . . . . . . . . . . . . . . . . . . .38
Download/New . . . . . . . . . . . . . . . . . . . . . . . . 88 Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Downloading from the Collector . . . . . . 176, 184 Export Nodes . . . . . . . . . . . . . . . . . . . . . . . . . .16
Communication Parameters Examples . 185 Export Nodes Dialog Box . . . . . . . . . . . . .16
Options . . . . . . . . . . . . . . . . . . . . . . . . . 177 QuickSteps . . . . . . . . . . . . . . . . . . . . . . . .17
Downloading from the Collector (GIF10) . . . 169
Communication Settings . . . . . . . . . . . . 169 F
Downloading from the Collector (GRE4) . . . . 172
Face 1/Face 2 Shot Sequence on Point 12
Communication Settings . . . . . . . . . . . . 172
Example . . . . . . . . . . . . . . . . . . . . . . . . .157
Downloading from the TDS HP48GX . . . . . . 191
FE: Feature (Field Code) . . . . . . . . . . . . . . . .218
Communication Settings . . . . . . . . . . . . 191
Example . . . . . . . . . . . . . . . . . . . . . . . . .218
Downloading from the TDS Ranger
Feature Line Command Alias . . . . . . . . . . . . . .47
(SurveyPro v3.x) . . . . . . . . . . . . . . . . . . 193
FG: Figure . . . . . . . . . . . . . . . . . . . . . . . . . . .218
Draw 3-D Lines . . . . . . . . . . . . . . . . . . . . . . . . 40
Example . . . . . . . . . . . . . . . . . . . . . . . . .218
Draw Line Work . . . . . . . . . . . . . . . . . . . . . . . 37
Field Code . . . . . . . . . . . . . . . . . . . . . . .3, 93, 96
DS: Slope Distance . . . . . . . . . . . . . . . . . . . . 217
Field Codes, entering into the collector . . . . . . .2
Data Tag Diagram . . . . . . . . . . . . . . . . . 217
Field Codes, Format . . . . . . . . . . . . . . . . . . . . . .3
Example . . . . . . . . . . . . . . . . . . . . . . . . . 217
Field Coding Format . . . . . . . . . . . . . . . . . . . . . .3
DTM-300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Entry Format for Field Codes . . . . . . . . . . .4
DTM-400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Field Entry Examples . . . . . . . . . . . . . . . . . . . . .5
DTM-700 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Default Designators for Line Work
DTM-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Examples . . . . . . . . . . . . . . . . . . . . . . .5
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
E File Name . . . . . . . . . . . . . . . . . . . .13, 15, 16, 18
Easting . . . . . . . . . . . . . . . . . . . . . . . 27, 95, 246 Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Easting-(X) . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Find Dialog Box . . . . . . . . . . . . . . . . . . . .108
Edit Data Tags . . . . . . . . . . . 119, 120, 125, 128 Find Data Collection Warnings . . . . . . . . . . . .114
Edit Data Tags Dialog Box . . . . . . 120, 128 Find Data Collection Warnings Dialog
Edit Formatted File . . . . . . . . . . . . . . . . . . . . . 19 Box . . . . . . . . . . . . . . . . . . . . . . . . . .115
Edit Formatted File Dialog Box . . . . . . . . 19 Find Next . . . . . . . . . . . . . . . . . . . . . . . .108, 110
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 19 Find Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Edit Instrument File . . . . . . . . . . . . . . . . . . . . . 17 Find text . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Edit Instrument File Dialog Box . . . . . . . . 18 Fitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 18 Foresight (FS) Activity . . . . . . . . . . . . . . . . . .214
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Format . . . . . . . . . .10, 13, 15, 17, 21, 28, 30, 88
Elevation . . . . . . . . . . . . . . . . 27, 60, 81, 96, 246 Formatted File . . . . . . . . . . . . . . . . . . . . . . . . .88
Elevation Control Check (EC) Activity . . . . . . 215 From . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Elevation-(Z) . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Entering Field Codes into a Collector . . . . . . . . 3 G
Entering Field Codes into the Collector . . . . . . 2
General Communications Problems . . . . . . . .204
Field Coding Format . . . . . . . . . . . . . . . . . 3
GEODAT . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
EP SDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Collecting Data . . . . . . . . . . . . . . . . . . . .132
256 Data Collection

Preparation . . . . . . . . . . . . . . . . . . . . . . . 130 Instrument File Size . . . . . . . . . . . . . . . . . . . . 87
Troubleshooting . . . . . . . . . . . . . . . . . . . 143 Instrument Filename . . . . . . . . . . . . . . . . . . . . 87
Geodat Definitions . . . . . . . . . . . . . . . . . . . . . 130 Instrument Height . . . . . . . . . . . . . . . . . . 27, 246
GEODAT Labels . . . . . . . . . . . . . . . . . . . . . . 118 Intermediate Backsight . . . . . . . . . . . . . . . . . 247
Geodat Labels Dialog Box . . . . . . . . . . . 118 Intermediate Occupied Station . . . . . . . . . . . 247
Geodat Labels . . . . . . . . . . . . . . . . . . . . . . . . 117 Intermediate Setup . . . . . . . . . . . . . . . . . . . . 247
Edit Data Tags . . . . . . . . . . . . . . . . . . . . 120 Intermediate Backsight . . . . . . . . . . . . . 247
GEODAT Labels . . . . . . . . . . . . . . . . . . . 118 Intermediate Occupied Station . . . . . . . . 247
New/Modify GEODAT Label . . . . . . . . . . 119 Intermediate Shots . . . . . . . . . . . . . . . . . . . . 164
GIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Sample of a Shot that Does Not Fall
GIF10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 on the Cross-section Pattern . . . . . 164
GIF12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Internal Modem/Digitizer with a Serial
Global Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Global Edit Dialog Box . . . . . . . . . . . . . . 111 QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 207
GM: Geometry . . . . . . . . . . . . . . . . . . . . . . . . 219 interrupt request setting . . . . . . . . . . . . . . . . 206
Example . . . . . . . . . . . . . . . . . . . . . . . . . 219 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2, 100
Goto Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Active Cell with Rectangular Highlight . . 102
Graphics tab . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Data Highlighted in Cell . . . . . . . . . . . . . 102
GRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Focus in Cell with Blinking Cursor . . . . . 102
GSI8+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 SDMS Editor Dialog Box . . . . . . . . . . . . 101
SDMS Editor Toolbar . . . . . . . . . . . . . . . 102
H
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
J
HZ: Horizontal Angle . . . . . . . . . . . . . . . . . . . 220 Job ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Example . . . . . . . . . . . . . . . . . . . . . . . . . 220 Job Name 10, 13, 15, 18, 19, 21, 28, 30, 86, 88, 90
Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
I Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Download from Collector . . . . . . . . . . . . . 10
IH: Instrument Height . . . . . . . . . . . . . . . . . . . 220
Edit Formatted File . . . . . . . . . . . . . . . . . . 19
Example . . . . . . . . . . . . . . . . . . . . . . . . . 220
Edit Instrument File . . . . . . . . . . . . . . . . . 17
Import ASCII File . . . . . . . . . . . . . . . . . . . . . . . 15
Export Nodes . . . . . . . . . . . . . . . . . . . . . . 16
Import ASCII File Dialog Box . . . . . . . . . . 15
Import ASCII File . . . . . . . . . . . . . . . . . . . 15
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . 16
Manage Jobs . . . . . . . . . . . . . . . . . . . . . . 28
Include Data Tag . . . . . . . . . . . . . . . . . . . . . . 108
Reduce Job . . . . . . . . . . . . . . . . . . . . . . . 20
Include Field Text . . . . . . . . . . . . . . . . . . . . . 108
Upload to Collector . . . . . . . . . . . . . . . . . 12
Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Join Last Shot . . . . . . . . . . . . . . . . . . . . . . . . . 46
Information blocks . . . . . . . . . . . . . . . . . . . . . 125
Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Backsight . . . . . . . . . . . . . . . . . . . . . . . . 245
K
Occupied Station . . . . . . . . . . . . . . . . . . 244 Keep Selected Node(s), Delete Remaining
SDMS Setup Data Dialog Box . . . . . . . . 246 Duplicates . . . . . . . . . . . . . . . . . . . . . . . . 96
Input Coordinates . . . . . . . . . . . . . . . . . . . . . . 42 Kermit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Insert Associated Line . . . . . . . . . . . . . . . . . . . 75
Insert Description . . . . . . . . . . . . . . . . . . . . . . . 47 L
Insert Row . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Label . . . . . . . . . . . . . . . . . . . . . . . . . . . 118, 119
Instrument Elevation . . . . . . . . . . . . . . . . 27, 246
Label 66 Default Designators . . . . . . . . . . . . 143
Instrument FIle . . . . . . . . . . . . . . . . . . . . . . . . . 88
Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Instrument File . . . . . . . . . . . . . . . . . . . . . . . . . 88
Layer/ Level . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Instrument FIle Date . . . . . . . . . . . . . . . . . . . . 87
Index 257
Layer/Level . . . . . . . . . . . . . . . . . . . . . . . . 93, 96 Method . . . . . . . . . . . . . . . . . . . . . . . . . .161
Leica (WILD) . . . . . . . . . . . . . . . . . . . . . . . . . 148 Line Work Print Options . . . . . . . . . . . . . . . . . .61
Collecting Data – Customizing Codes . . 165 Line Work tab . . . . . . . . . . . . . . . . . . . . . . . . . .35
Collecting Data – Entering Decimals Linetype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
on the Instrument . . . . . . . . . . . . . . 154 Linetype Libraries . . . . . . . . . . . . . . . . . . . . . . .71
Collecting Data - Field Codes . . . . . . . . 154 Linetype Libraries Dialog Box . . . . . . . . . .71
Collecting Data - Leica Instruments . . . . 168 Linetype Libraries (AutoCAD/BricsCad) . . . . . .61
Collecting Data – Line Work Linetype/Style . . . . . . . . . . . . . . . . . . . . . . . . . .59
(Recommended for Alphanumeric LISCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Instruments) . . . . . . . . . . . . . . . . . . 161 Listing of Geometry Designators . . . . . . . . . .158
Collecting Data – Line Work LO: Data Tag Diagram . . . . . . . . . . . . . . . . . .221
(Recommended for LO: Length Offset . . . . . . . . . . . . . . . . . . . . . .221
Non-Alphanumeric Instruments) . . . 158 Example . . . . . . . . . . . . . . . . . . . . . . . . .221
Collecting Data - Node ID . . . . . . . . . . . 153 LO: Data Tag Diagram . . . . . . . . . . . . . .221
Collecting Data –- Temporary Shots . . . 155 lotcor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Collecting Data – Traverse . . . . . . . . . . 156
Collecting Data - Using codes based M
on WILDsoft . . . . . . . . . . . . . . . . . . 150
Manage Jobs . . . . . . . . . . . . . . . . . . . . . . . . . .28
LISCAD . . . . . . . . . . . . . . . . . . . . . . . . . 148
Manage Jobs Dialog Box . . . . . . . . . . . . .28
Preparation . . . . . . . . . . . . . . . . . . . . . . 148
Modify Job . . . . . . . . . . . . . . . . . . . . . . . . .30
Transferring Data . . . . . . . . . . . . . . . . . . 168
Print Job . . . . . . . . . . . . . . . . . . . . . . . . . .32
WILDsoft . . . . . . . . . . . . . . . . . . . . . . . . 148
Maptech . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Leica Codes . . . . . . . . . . . . . . . . . . . . . 123, 124
Masking . . . . . . . . . . . . . . . . . . . . . . . .60, 63, 67
Edit Data Tags . . . . . . . . . . . . . . . . . . . . 128
Measure Block . . . . . . . . . . . . . . . . . . . . . . . .149
Leica Codes . . . . . . . . . . . . . . . . . . . . . . 124
Measure Block Example . . . . . . . . . . . . .149
Leica Codes Dialog Box . . . . . . . . . . . . 124
Measure Block Example . . . . . . . . . . . . . . . . .149
New Leica Code . . . . . . . . . . . . . . . . . . 126
Method . . . . . . . . . . . . . . . . . . . . . . . . . . . .72, 74
Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Minimum Setup Information . . . . . . . . . . . . . .244
Library Name . . . . . . . . . . . . . . . . . . . . . . 70, 71
Initial Setup . . . . . . . . . . . . . . . . . . . . . . .244
Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Intermediate Setup . . . . . . . . . . . . . . . . .247
Line designator . . . . . . . . . . . . . . . . . . . . . . . . . 3
Modifications to Code 1 (Azimuth) . . . . . . . . .167
Line Libraries . . . . . . . . . . . . . . . . . . . . . . 61, 70
Modifications to Code 1 (Typical) . . . . . . . . . .166
Line Libraries Dialog Box . . . . . . . . . . . . . 70
Modifications to Code 2 . . . . . . . . . . . . . . . . .167
Line Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Modify 3-D Line Template . . . . . . . . . . . . .76, 78
Line name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Modify Associated Line . . . . . . . . . . . . . . . . . .75
Line Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Modify Cross-Section Pattern . . . . . . . . . . . . . .73
Line Libraries . . . . . . . . . . . . . . . . . . . . . . 70
Modify Data Tag . . . . . . . . . . . . . . . . . . .121, 128
Line Work Dialog Box . . . . . . . . . . . . . . . 59
Modify Geodat Label . . . . . . . . . . . . . . . . . . .119
Linetype Libraries . . . . . . . . . . . . . . . . . . 71
Modify Job . . . . . . . . . . . . . . . . . . . . . . . . .29, 30
New Line . . . . . . . . . . . . . . . . . . . . . . . . . 61
Modify Job Dialog Box . . . . . . . . . . . . . . .30
Line Work (Recommended for Alphanumeric
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . .31
Instruments) . . . . . . . . . . . . . . . . . . . . . . 142
Modify Leica Codes . . . . . . . . . . . . . . . . . . . .125
Label 66 Default Designators . . . . . . . . 143
Modify Line . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Line Work (Recommended for
Modify Line Library . . . . . . . . . . . . . . . . . . . . . .70
Non-Alphanumeric Instruments) . . . . . . 141
Modify Linetype Library . . . . . . . . . . . . . . . . . .71
Designators . . . . . . . . . . . . . . . . . . . . . . 142
Move Job Down Arrow . . . . . . . . . . . . . . . . . . .21
Line Work Generated Using a
Move Job Up Arrow . . . . . . . . . . . . . . . . . . . . .21
Cross-section Pattern . . . . . . . . . . . . . . 163
Line Work Generated Using the Standard
258 Data Collection

N O
Name . . . . . . . . . . . . . . . . . . . . . . . 18, 59, 62, 66 Observation Summary . . . . . . . . . . . . . . . . . . 91
New 3-D Line Template . . . . . . . . . . . . . . . 76, 77 Observations . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Example . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Occupied Station . . . . . . . . . . . . . . . . . . . . . . 244
Line Template Diagram . . . . . . . . . . . . . . 79 Occupied Station (OS) Activity . . . . . . . . . . . 212
New 3-D Line Template Breakpoint . . . . . 80 Occupied Station Priority . . . . . . . . . . . . . . . . . 43
New 3-D Line Template Dialog Box . . . . . 77 OF: Data Tag Diagram . . . . . . . . . . . . . . . . . 222
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . 78 OF: Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
New 3-D Line Template Breakpoint . . . . . . . . . 80 Example . . . . . . . . . . . . . . . . . . . . . . . . . 222
New 3-D Line Template Breakpoint OF: Data Tag Diagram . . . . . . . . . . . . . . 222
Dialog Box . . . . . . . . . . . . . . . . . . . . . 80 Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
New Associated Line . . . . . . . . . . . . . . . . . . . . 74 Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63, 67
New Cross-Section Pattern . . . . . . . . . . . . 72, 73 Options 27, 33, 115, 177, 178, 179, 181, 187, 247
New Cross-Section Pattern Dialog Box . . 74 3-D Line Templates . . . . . . . . . . . . . . . . . 76
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . 75 Cross-Section Patterns . . . . . . . . . . . . . . 72
New Data Tag . . . . . . . . . . . . . . . . . . . . 121, 128 Designators . . . . . . . . . . . . . . . . . . . . . . . 44
New Geodat Label . . . . . . . . . . . . . . . . . . . . . 118 Line Work . . . . . . . . . . . . . . . . . . . . . . . . . 58
New Leica Code . . . . . . . . . . . . . . . . . . 125, 126 Reduction Settings . . . . . . . . . . . . . . . . . . 34
New Leica Code Dialog Box . . . . . . . . . . 126 Other Activities . . . . . . . . . . . . . . . . . . . . . . . 215
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 127
New Line . . . . . . . . . . . . . . . . . . . . . . . . . . 60, 61 P
New Line (AutoCAD/BricsCad) . . . . . . . . . 61
Pan Dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . 24
New Line (MicroStation) . . . . . . . . . . . . . . 65
Pan Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
New Line (AutoCAD/BricsCad) . . . . . . . . . . . . 61
Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
New Line Dialog Box . . . . . . . . . . . . . . . . 62
Path Location . . . . . . . . . . . . . . . . . . . . . . . . . 88
QuickSteps (AutoCAD/BricsCad) . . . . . . . 64
Pattern . . . . . . . . . . . . . . . . . . . . . . . . . 59, 62, 66
New Line (MicroStation) . . . . . . . . . . . . . . . . . 65
Pattern Name . . . . . . . . . . . . . . . . . . . . . . 72, 74
New Line Dialog Box . . . . . . . . . . . . . . . . 65
PD: Point Description . . . . . . . . . . . . . . . . . . 223
QuickSteps (MicroStation) . . . . . . . . . . . . 68
Example . . . . . . . . . . . . . . . . . . . . . . . . . 223
New Line Library . . . . . . . . . . . . . . . . . . . . . . . 70
Pentax and Corvallis . . . . . . . . . . . . . . . . . . . 176
New Linetype Library . . . . . . . . . . . . . . . . . . . . 71
New/Download . . . . . . . . . . . . . . . . . . . . . . . . 88
Troubleshooting . . . . . . . . . . . . . . . . . . . 182
New/Modify GEODAT Label . . . . . . . . . . . . . 119
PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . 6, 27, 246
New Geodat Label Dialog Box . . . . . . . . 119
Place Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 38
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . 120
Placement . . . . . . . . . . . . . . . . . . . . . . . . . 64, 68
Nikon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Placement Priority . . . . . . . . . . . . . . . . . . . . . . 42
PN: Point Number . . . . . . . . . . . . . . . . . . . . . 224
No decimals method . . . . . . . . . . . . . . . . . . . 154
Example . . . . . . . . . . . . . . . . . . . . . . . . . 224
Node ID . . . . . . . . . . . . . . . . . 27, 93, 94, 95, 246
PO: Data Tag Diagram . . . . . . . . . . . . . . . . . 225
Node ID Example . . . . . . . . . . . . . . . . . . . . . 153
PO: Prism Offset . . . . . . . . . . . . . . . . . . . . . . 224
Node Selection . . . . . . . . . . . . . . . . . . . . . . . . . 6
Example . . . . . . . . . . . . . . . . . . . . . 225, 227
Northing . . . . . . . . . . . . . . . . . . . . . . . 27, 95, 246
PO: Data Tag Diagram . . . . . . . . . . . . . 225
Northing-(Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
power source . . . . . . . . . . . . . . . . . . . . . . . . . 204
Number of current objects in CAD graphic . . . 88
PR: Project Name . . . . . . . . . . . . . . . . . . . . . 225
Numeric Activities . . . . . . . . . . . . . . . . . . . . . 165
Preparation . . . . . . . . . . . . . . . . . . 130, 148, 200
Numeric Activities Example . . . . . . . . . . 165
Block Example . . . . . . . . . . . . . . . . . . . . 148
Numeric Activities Example . . . . . . . . . . . . . . 165
Code Block . . . . . . . . . . . . . . . . . . . . . . . 149
Numeric Values . . . . . . . . . . . . . . . . . . . . . . . 140
Geodat Definitions . . . . . . . . . . . . . . . . . 130
Index 259
Measure Block . . . . . . . . . . . . . . . . . . . . 149 Query Warnings . . . . . . . . . . . . . . . . . . . . . . . .84
Reordering Definitions . . . . . . . . . . . . . . 131 Query Warnings Dialog Box . . . . . . . . . . .84
Suggested Labels . . . . . . . . . . . . . . . . . 132
Word Example . . . . . . . . . . . . . . . . . . . . 148 R
Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Radial Offset Example . . . . . . . . . . . . . . . . . .227
Preview Objects . . . . . . . . . . . . . . . . . . . . . . . 22
Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Display Settings . . . . . . . . . . . . . . . . . . . . 24
Raw Measured Data . . . . . . . . . . . . . . . . .42, 184
Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Recorded Designator of 18 . . . . . . . . . . . . . .159
Print 3-D Line Template Listing and Data . . . . 77
Recorded Designator of 3 . . . . . . . . . . . . . . .159
Print Backup File . . . . . . . . . . . . . . . . . . . . . . . 32
Rectangle Command Alias . . . . . . . . . . . . . . . .47
Print Data Collection Warnings . . . . . . . . . . . 115
Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Print Data Tag . . . . . . . . . . . . . . . . . . . . 121, 128
Reduce Job . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Print Formatted File . . . . . . . . . . . . . . . . . . . . 32
Preview Objects . . . . . . . . . . . . . . . . . . . .22
Print Geodat Label . . . . . . . . . . . . . . . . . . . . 119
Reduce Job Dialog Box . . . . . . . . . . . . . . .21
Print Instrument File . . . . . . . . . . . . . . . . . . . . 32
SDMS Set-up Data . . . . . . . . . . . . . . . . . .26
Print Job . . . . . . . . . . . . . . . . . . . . . . . . . . 29, 32
SDMS Set-up Data Dialog Box . . . . . . . . .26
Print Job Dialog Box . . . . . . . . . . . . . . . . 32
Reduced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Print Leica Codes . . . . . . . . . . . . . . . . . . . . . 125
Reduction Settings . . . . . . . . . . . . . . . . . . . . . .34
Print List Cross-Section Pattern . . . . . . . . . . . 73
Examples . . . . . . . . . . . . . . . . . . . . . . . . .43
Print Options . . . . . . . . . . . . . . . . . 84, 85, 87, 89
Reduction Settings – Collector Tab . . . . . .36
Print Reduced File . . . . . . . . . . . . . . . . . . . . . 32
Reduction Settings – Graphics Tab . . . . .37
Print Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Reduction Settings – Line Work Tab . . . . .39
Print Unused Nodes . . . . . . . . . . . . . . . . . . . . 94
Reduction Settings – Shot Averaging
Project (PR) Activity . . . . . . . . . . . . . . . . . . . 212
Tab . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Prompt . . . . . . . . . . . . . . . . . . . . . 118, 119, 121
Reduction Settings Dialog Box . . . . . . . . .35
Reduction Settings – Collector Tab . . . . . . . . .36
Q Reduction Settings Dialog Box –
Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 CollectorTab . . . . . . . . . . . . . . . . . . . .36
Query Backup File . . . . . . . . . . . . . . . . . . 86 Reduction Settings – Graphics Tab . . . . . . . . .37
Query File Information . . . . . . . . . . . . . . . 87 Reduction Settings Dialog Box –
Query Nodes . . . . . . . . . . . . . . . . . . . . . . 92 Graphics Tab . . . . . . . . . . . . . . . . . . .37
Query Observations . . . . . . . . . . . . . . . . . 89 Reduction Settings – Line Work Tab . . . . . . . .39
Query Shot Averaging . . . . . . . . . . . . . . . 85 Reduction Settings Dialog Box – Line
Query Unused Nodes . . . . . . . . . . . . . . . 94 Work Tab . . . . . . . . . . . . . . . . . . . . . .39
Query Warnings . . . . . . . . . . . . . . . . . . . . 84 Reduction Settings – Shot Averaging Tab . . . .41
Resolve Duplicate Nodes . . . . . . . . . . . . 95 Reduction Settings Dialog Box – Shot
Query Backup File . . . . . . . . . . . . . . . . . . . . . 86 Averaging Tab . . . . . . . . . . . . . . . . . .41
Query Backup File Dialog Box . . . . . . . . . 86 Reduction Settings Example . . . . . . . . . . . . .155
Query File Information . . . . . . . . . . . . . . . . . . 87 Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Query File Information Dialog Box . . . . . . 88 Renumber Node to Lowest Available . . . . . . . .96
Query Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Renumber Node to Next Available . . . . . . . . . .96
Query Nodes Dialog Box . . . . . . . . . . . . . 93 Renumber Node to Selected Value . . . . . . . . .96
Query Observations . . . . . . . . . . . . . . . . . . . . 89 Reordering Definitions . . . . . . . . . . . . . . . . . .131
Query Observations Dialog Box . . . . . . . 90 Replace . . . . . . . . . . . . . . . . . . . . . . . . .109, 110
Query Shot Averaging . . . . . . . . . . . . . . . . . . 85 Replace Dialog Box . . . . . . . . . . . . . . . . .110
Query Shot Averaging Dialog Box . . . . . . 85 Replace All . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Query Unused Nodes . . . . . . . . . . . . . . . . . . . 94 Replace with . . . . . . . . . . . . . . . . . . . . . . . . . .110
Query Unused Nodes Dialog Box . . . . . . 94 Report Options . . . . . . . . . . . . . . . . . . . . . . . . .93
260 Data Collection

Reserved Eagle Point SDMS Data Tags . . . . 233 Find Next . . . . . . . . . . . . . . . . . . . . . . . . 108
Data Tags Outline . . . . . . . . . . . . . . . . . 233 Global Edit . . . . . . . . . . . . . . . . . . . . . . . 110
Resolve Duplicate Nodes . . . . . . . . . . . . . . . . 95 Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
QuickSteps . . . . . . . . . . . . . . . . . . . . . . . . 96 Redo . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Resolve Duplicate Nodes Dialog Box . . . . 95 Replace . . . . . . . . . . . . . . . . . . . . . . . . . 109
Resolve Duplicate Nodes Print Options . . . . . . 96 Select All . . . . . . . . . . . . . . . . . . . . . . . . 107
Restore Front View . . . . . . . . . . . . . . . . . . . . . 24 Undo . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Restore Iso View . . . . . . . . . . . . . . . . . . . . . . . 24 SDMS Editor – File Menu . . . . . . . . . . . . . . . 103
Restore Top View . . . . . . . . . . . . . . . . . . . . . . 24 Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Revert to Instrument File . . . . . . . . . . . . . . . . . 30 File Menu . . . . . . . . . . . . . . . . . . . . . . . . 103
Revert to Legal Backup . . . . . . . . . . . . . . . . . . 30 Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
RO: Radial Offset . . . . . . . . . . . . . . . . . . . . . 226 Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Radial Offset Example . . . . . . . . . . . . . . 227 Save As . . . . . . . . . . . . . . . . . . . . . . . . . 103
SDMS Editor – Help Menu . . . . . . . . . . . . . . 116
S About . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Contents . . . . . . . . . . . . . . . . . . . . . . . . . 116
Sample File that Contains Cross-sectional
Search For Help On . . . . . . . . . . . . . . . . 116
Line Work Using the Code Block . . . . . . 161
SDMS Editor – Tools Menu . . . . . . . . . . . . . . 113
Sample File that Includes Line Work Using
Add Column . . . . . . . . . . . . . . . . . . . . . . 114
Numeric Designators . . . . . . . . . . . . . . . 159
Delete Row . . . . . . . . . . . . . . . . . . . . . . 113
Sample of a Shot that Does Not Fall on the
Display Settings . . . . . . . . . . . . . . . . . . . 116
Cross-section Pattern . . . . . . . . . . . . . . . 164
Find Data Collection Warnings . . . . . . . 114
Sample of Label 65 (Geometry) . . . . . . . . . . . 137
Insert Row . . . . . . . . . . . . . . . . . . . . . . . 113
Sample of UDS - 10 CROSS-SECTIONS . . . 139
Options . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Sample of UDS - 12 ACTIVITY LABEL . . . . . 140
Tools Menu . . . . . . . . . . . . . . . . . . . . . . 113
Sample of UDS - 2 SETUP . . . . . . . . . . . . . . 133
SDMS Editor Caption Bar . . . . . . . . . . . . . . . 101
Sample of UDS - 3 CONTROL CHECK . . . . . 134
SDMS Set-up Data . . . . . . . . . . . . . . . . . . . . . 26
Sample of UDS - 4 UTILITY WITH LINE
SDMS Setup Data Dialog Box . . . . . . . . . . . 246
WORK . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Search For Help On . . . . . . . . . . . . . . . . . . . 116
Sample of UDS - 5 UTILITY FEATURE . . . . . 135
Select All . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Sample of UDS - 6 TOPOGRAPHY
Select Job(s) . . . . . . . . . . . . . . . . . . . . . . . . . . 21
WITH BREAKLINES . . . . . . . . . . . . . . . . 136
Select Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Sample of UDS - 7 TOPOGRAPHY . . . . . . . 137
Select Objects . . . . . . . . . . . . . . . . . . . . . . . . . 29
Sample of UDS - 8 CONTROL ENTRY . . . . . 138
Selection Method . . . . . . . . . . . . . . . . . 7, 8, 112
Sample of UDS - 9 TRAVERSE AHEAD . . . . 138
Selection Mode . . . . . . . . . . . . . . . . . . . . . . . . . 6
Sample of UDS -11 COMMENT . . . . . . . . . . 140
Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . 10, 13
Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
SH: Staff Height . . . . . . . . . . . . . . . . . . . . . . 227
SDMS Editor . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Example . . . . . . . . . . . . . . . . . . . . . . . . . 228
Introduction . . . . . . . . . . . . . . . . . . . . . . . 100
Shot Averaging . . . . . . . . . . . . . . . . . . . . . . . . 22
SDMS Editor – Edit Menu . . . . . . . . . . . 105
Shot Averaging tab . . . . . . . . . . . . . . . . . . . . . 35
SDMS Editor – File Menu . . . . . . . . . . . . 103
Show Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SDMS Editor – Help Menu . . . . . . . . . . . 116
Sideshot (SS) Activity . . . . . . . . . . . . . . . . . . 214
SDMS Editor – Tools Menu . . . . . . . . . . 113
Six Sideshots Recorded in a Face 1
SDMS Editor – Edit Menu . . . . . . . . . . . . . . . 105
Position Example . . . . . . . . . . . . . . . . . . 157
Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Sokkia (Lietz) . . . . . . . . . . . . . . . . . . . . . . . . 182
Cut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Collecting Data . . . . . . . . . . . . . . . . . . . . 184
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . 105
Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Troubleshooting . . . . . . . . . . . . . . . . . . . 188
Index 261
Special designator(s) . . . . . . . . . . . . . . . . . . . . 3 TPS Series . . . . . . . . . . . . . . . . . . . . . . . . . . .168
SS: Nominal Stationing . . . . . . . . . . . . . . . . . 228 Transferring Data . . . . . .168, 175, 176, 184, 191
Example . . . . . . . . . . . . . . . . . . . . . . . . . 228 Alternative Downloading Steps . . . . . . . .178
ST: Stationing . . . . . . . . . . . . . . . . . . . . . . . . 228 Download from an AP700 or 800 Series
Example . . . . . . . . . . . . . . . . . . . . . . . . . 229 Instrument . . . . . . . . . . . . . . . . . . . .175
Start/Stop Function . . . . . . . . . . . . . . . . . . . . . 54 Downloading from the Collector . . .176, 184
Station . . . . . . . . . . . . . . . . . . . . . . . . . . . 27, 246 Downloading from the Collector
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 GIF10) . . . . . . . . . . . . . . . . . . . . . . .169
Stop Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Downloading from the Collector
Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 (GRE4) . . . . . . . . . . . . . . . . . . . . . . .172
Suggested Labels . . . . . . . . . . . . . . . . . . . . . 132 Downloading from the TDS HP48GX . . .191
Surveying Activities . . . . . . . . . . . . . . . . . . . . 211 Downloading from the TDS Ranger
Backsight (BS) Activity . . . . . . . . . . . . . . 213 (SurveyPro v3.x) . . . . . . . . . . . . . . .193
Elevation Control Check (EC) Activity . . 215 Uploading to the Collector . . . . . . . .180, 186
Foresight (FS) Activity . . . . . . . . . . . . . . 214 Uploading to the Collector (GIF10) . . . . .170
Occupied Station (OS) Activity . . . . . . . 212 Uploading to the TDS HP48GX . . . . . . . .192
Other Activities . . . . . . . . . . . . . . . . . . . 215 Uploading to the TDS Ranger
Project (PR) Activity . . . . . . . . . . . . . . . . 212 (SurveyPro v3.x) . . . . . . . . . . . . . . .196
Sideshot (SS) Activity . . . . . . . . . . . . . . 214 TransIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Surveyor’s Module (SMI) . . . . . . . . . . . . . . . 188 translator program . . . . . . . . . . . . . . . . . . . . .204
Download Coordinate Information Traverse Example . . . . . . . . . . . . . . . . . . . . .156
from the SMI Data Collector . . . . . . 188 Trimble/Tripod Data Systems (TDS) . . . . . . .191
Download Raw Survey Information Transferring Data . . . . . . . . . . . . . . . . . .191
from the SMI Data Collector . . . . . . 189 Troubleshooting . . . . . . . . . . . . . . . . . . .200
Upload Coordinate Information to the Troubleshooting . . . . . . .143, 182, 188, 200, 203
SMI Data Collector . . . . . . . . . . . . . 190 General Communications Problem . . . . .204
Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . 93, 96 Internal Modem/Digitizer with a Serial
Mouse . . . . . . . . . . . . . . . . . . . . . . .206
T Parameters . . . . . . . . . . . . . . . . . . . . . . .147
QuickSteps . . . . . . . . . . . . . . .144, 145, 146
Tag . . . . . . . . . . . . . . . . 118, 119, 121, 126, 128
Type . . . . . . . . . . . . . . . . . . . . . . . . . . .60, 63, 67
Technical Computation Tags . . . . . . . . . . . . 215
AZ: Azimuth . . . . . . . . . . . . . . . . . . . . . . 215
DO: Offset Direction . . . . . . . . . . . . . . . 216
U
DS: Slope Distance . . . . . . . . . . . . . . . . 217 UDS - 10 CROSS-SECTIONS . . . . . . . . . . . .139
FE: Feature (Field Code) . . . . . . . . . . . . 218 Sample of UDS - 10
GM: Geometry . . . . . . . . . . . . . . . . . . . . 219 CROSS-SECTIONS . . . . . . . . . . . . .139
OF: Offset . . . . . . . . . . . . . . . . . . . . . . . 222 UDS - 11 COMMENT . . . . . . . . . . . . . . . . . . .140
ST: Stationing . . . . . . . . . . . . . . . . . . . . 228 Sample of UDS -11 COMMENT . . . . . . .140
Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 UDS - 12 ACTIVITY LABEL . . . . . . . . . . . . . .140
Template Name . . . . . . . . . . . . . . . . . . . . . . . 77 Numeric Values . . . . . . . . . . . . . . . . . . . .140
Temporary Shots Example . . . . . . . . . . . . . . 155 Sample of UDS - 12 ACTIVITY LABEL . .140
TK: Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 UDS - 2 SETUP . . . . . . . . . . . . . . . . . . . . . . .132
To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Sample of UDS - 2 SETUP . . . . . . . . . . .133
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 102 UDS - 3 CONTROL CHECK . . . . . . . . . . . . .134
Topcon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Sample of UDS - 3 CONTROL CHECK .134
Topcon CRC . . . . . . . . . . . . . . . . . . . . . . . . . 200 UDS - 4 UTILITY WITH LINE WORK . . . . . . .134
Topcon FC-4 . . . . . . . . . . . . . . . . . . . . . . . . . 200 Sample of UDS - 4 UTILITY WITH LINE
Topcon GTS 200 or 300 . . . . . . . . . . . . . . . . 200 WORK . . . . . . . . . . . . . . . . . . . . . . .134
262 Data Collection

UDS - 5 UTILITY FEATURE . . . . . . . . . . . . . 135 W
Sample of UDS - 5 UTILITY FEATURE . 135
UDS - 6 TOPOGRAPHY WITH BREAKLINES 136 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . 22, 92
Sample of Label 65 (Geometry) . . . . . . . 137 Warnings list . . . . . . . . . . . . . . . . . . . . . . . . . 115
Sample of UDS - 6 TOPOGRAPHY Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
WITH BREAKLINES . . . . . . . . . . . . 136 Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
UDS - 7 TOPOGRAPHY . . . . . . . . . . . . . . . . 137 Width/ Weight . . . . . . . . . . . . . . . . . . . . . . . . . 59
Sample of UDS - 7 TOPOGRAPHY . . . . 137 WILDsoft . . . . . . . . 148, 150, 156, 158, 165, 166
UDS - 8 CONTROL ENTRY . . . . . . . . . . . . . 138 Word Example . . . . . . . . . . . . . . . . . . . . . . . . 148
Sample of UDS - 8 CONTROL ENTRY . 138
UDS - 9 TRAVERSE AHEAD . . . . . . . . . . . . 138 X
Sample of UDS - 9 TRAVERSE AHEAD 138 X Trans program . . . . . . . . . . . . . . . . . . . . . . 168
Undo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 X-Axis Angle . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Upload Coordinate Information to the SMI XC: X Coordinate Value . . . . . . . . . . . . . . . . 231
Data Collector . . . . . . . . . . . . . . . . . . . . . 190 Example . . . . . . . . . . . . . . . . . . . . . . . . . 231
Upload Data From File . . . . . . . . . . . . . . . . . . . 12 XY Plane Angle . . . . . . . . . . . . . . . . . . . . . . . . 24
Upload Data From Project . . . . . . . . . . . . . . . . 13
Upload to Collector . . . . . . . . . . . . . . . . . . . . . 12 Y
QuickSteps for Uploading ASCII File . . . . 13
QuickSteps for Uploading from Project . . 14 YC: Y Coordinate Value . . . . . . . . . . . . . . . . 232
Upload to Collector Dialog Box . . . . . . . . . 12 Example . . . . . . . . . . . . . . . . . . . . . . . . . 232
Uploading to the Collector . . . . . . . . . . . 180, 186
Options . . . . . . . . . . . . . . . . . . . . . . 181, 187 Z
Uploading to the Collector (GIF10) . . . . . . . . 170 ZC: Z Coordinate Value/Elevation . . . . . . . . . 232
Uploading to the TDS HP48GX . . . . . . . . . . . 192 Example . . . . . . . . . . . . . . . . . . . . . . . . . 232
Uploading to the TDS Ranger Zeiss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
(SurveyPro v3.x) . . . . . . . . . . . . . . . . . . . 196 Collecting Data . . . . . . . . . . . . . . . . . . . . 201
Use 3-D Line Template . . . . . . . . . . . . . . . . . . 40 Preparation . . . . . . . . . . . . . . . . . . . . . . 200
Use Cross-Section Patterning . . . . . . . . . . . . . 40 Zeiss REC 500 . . . . . . . . . . . . . . . . . . . . . . . 200
Use Field Code as Line Name . . . . . . . . . . . . . 40 Zoom Dynamic . . . . . . . . . . . . . . . . . . . . . . . . 23
Use Line Library . . . . . . . . . . . . . . . . . . . . . . . 39 Zoom Extents . . . . . . . . . . . . . . . . . . . . . . . . . 23
Use Line Name as Counter . . . . . . . . . . . . . . . 40 Zoom Previous . . . . . . . . . . . . . . . . . . . . . . . . 23
Use Pattern Lines . . . . . . . . . . . . . . . . . . . . . . 41 Zoom Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Use Shot Averaging . . . . . . . . . . . . . . . . . . . . . 42 Zoom Window . . . . . . . . . . . . . . . . . . . . . . . . . 23
V
Version . . . . . . . . . . . . . . . . . . . . . . . . . . . 10, 13
Vertical Angle . . . . . . . . . . . . . . . . . . . . . 27, 247
View Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
VIP Series . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
VO: Data Tag Diagram . . . . . . . . . . . . . . . . . 230
VO: Vertical Offset . . . . . . . . . . . . . . . . . . . . . 230
Example . . . . . . . . . . . . . . . . . . . . . . . . . 230
VO: Data Tag Diagram . . . . . . . . . . . . . . 230
VT: Data Tag Diagram . . . . . . . . . . . . . . . . . . 231
VT: Vertical (Zenith) Angle . . . . . . . . . . . . . . . 230
Example . . . . . . . . . . . . . . . . . . . . . . . . . 231
VT: Data Tag Diagram . . . . . . . . . . . . . . 231
Index 263
264 Data Collection

Data Collection by Eagle Point

Uploaded by

Copyright:

Available Formats

Data Collection by Eagle Point

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Collection by Eagle Point

Uploaded by

Copyright:

Available Formats

Data Collection by Eagle Point

A SDMS Editor . . . . . . . . . . . . . . . . . . . . . .99

Table of Contents iii

C Leica Codes . . . . . . . . . . . . . . . . . . . . . 123

D Collectors and Formats . . . . . . . . . . . 129

Data Collection Glossary . . . . . . . . . . .249

Table of Contents vii

Chapter 1: Data Collection Concepts 1

Entering Field Codes into the Collector

Field Coding Format

Definitions for Entering Field Codes into a Collector

Chapter 1: Data Collection Concepts 3

Designators System Defaults

Close line + (plus)

Join last shot * (asterisk)

Bearing close # (pound sign)

Cross-section = (equal sign)

Stop line ! (exclamation point)

Insert description * (asterisk)

Command indicator / (forward slash)

Default Designators for Line Work Examples

Chapter 1: Data Collection Concepts 5

Figure 1-2 Query Nodes Dialog Box

Query Nodes Dialog Box Definitions

Chapter 1: Data Collection Concepts 7

KEY-IN COMMAND: download

Figure 2-1 Download from Collector Dialog Box

Download from Collector Dialog Box Definitions

KEY-IN COMMAND: upload

Figure 2-2 Upload to Collector Dialog Box

Upload to Collector Dialog Box Definitions

QuickSteps for Uploading ASCII File

QuickSteps for Uploading from Project

KEY-IN COMMAND: dcimp

Figure 2-3 Import ASCII File Dialog Box

Import ASCII File Dialog Box Definitions

KEY-IN COMMAND: dcexp

Figure 2-4 Export Nodes Dialog Box

Export Nodes Dialog Box Definitions

Edit Instrument File

KEY-IN COMMAND: editinst

Figure 2-5 Edit Instrument File Dialog Box

Edit Instrument File Dialog Box Definitions

KEY-IN COMMAND: editformat

Figure 2-6 Edit Formatted File Dialog Box

Edit Formatted File Dialog Box Definition

KEY-IN COMMAND: reduce

Reduce Job Dialog Box Definitions

Preview Objects Dialog Box Definitions

Display Settings Dialog Box Definitions

SDMS Set-up Data

Figure 2-10 SDMS Set-up Data Dialog Box

KEY-IN COMMAND: dcman

Figure 2-11 Manage Jobs Dialog Box

Manage Jobs Dialog Box Definitions

Figure 2-12 Modify Job Dialog Box

Modify Job Dialog Box Definitions

Figure 2-13 Print Job Dialog Box

Print Job Dialog Box Definitions