Working With Feature Definitions
Working With Feature Definitions
www.trimble.com
© 2021, Trimble Inc. All rights reserved. Trimble and the Globe & Triangle logo are trademarks of Trimble Inc. registered in the United States and in other
countries. All other trademarks are the property of their respective owners.
About this tutorial
Note: If you need additional help at any time you are using the software, press F1 to
display the online help.
Note: The downloaded WorkingwithFeatureDefinitions folder contains this PDF file, the
Working with Feature Definitions.vce project file, and the TutorialGlobalFeatures.fxl file,
which you will import into the project.
The project file is read-only. You can perform the tutorial steps without saving the
project file. However, if you are interrupted while performing the tutorial, you can save
it with a new name by selecting File > Save Project As. Then, you can re-open the
project to continue the tutorial at a later time.
Note: As an alternative to importing a Feature Definition (.fxl) file into your project to
populate the project's Feature Library for feature code processing, you can use the New
Feature Library command to create a new Feature Library "from scratch." See the TBC
Help for instructions.
To view or edit a control code or feature definition, you can double-click its node or
right-click it and select Properties. Following is a description of each of the object
types that make up the library
Line Control Codes - Surveyors can assign line control codes to points during
field data collection to specify properties for an associated line feature. For
example, they can assign a line control code to a point to specify where a
feature line starts or ends. When the feature codes are processed, line control
codes modify line objects according to the actions (instructions) associated with
the code.
Block Control Codes - Surveyors can assign block control codes to points during
field data collection to specify properties for an associated block feature. For
example, they can assign a block control code to a point to specify to scale the
feature block on the X, Y, or Z axis. Or, they can assign block control codes to
one to three points (depending on the block definition) that are used as
insertion points for the block.
When the feature codes are processed, block control codes modify block objects
according to the actions (instructions) associated with the code.
Line feature definitions - A line feature is made up of two or more points that
define a line, such as a fence or path. A line feature may also include line control
codes that are used to further define linear features (for example, add lines,
curves, and arcs between points) and one or more feature attributes.
Related line feature definitions are typically grouped in the same category (for
example, all road-related line feature definitions might be grouped together in a
Roads category). You can edit the definition's properties (including how the line
displays in graphic views) and supported attributes as necessary.
Groups - Some field devices enable you to group a set of feature definition
codes and control codes so that they correspond with a single button/action on
the device. Multiple groups can be created from which field crews can select the
one they need for the particular job.
If you had imported point feature data into the project, other source options
would be available.
b. Uncheck the Close command after processing check box located near the
bottom of the pane.
You will use this command to reprocess feature codes later as you create and
edit definitions.
c. Click the Process Source(s) button.
When processing is complete, several new processed city park features display in
the Plan View:
Points 2 through 5 have been feature coded to produce a curved line
representing the edge of some landscaping. Later, you will modify the
associated feature definition to change the look of the line.
Note that no feature has been assigned to point 1, which indicates the location of an
outdoor drinking fountain. This is because there was not a drinking fountain feature
definition contained in the imported Feature Library (.fxl) file. So, you will create
one directly in your project's Feature Library.
Verify Drinking Fountain is selected in the Layer drop-down list in the Properties
pane.
Next, you will create a label to display with the feature. The label will include
the point name and a list of any attributes assigned to the feature. (You will
assign attribute types to the feature definition later in this procedure.)
d. In the Label style drop-down list, select <New Label Style>.
In the Label Style Manager dialog, ensure that the Point Styles tab is selected.
e. Click the New button and enter the Style name Drinking Fountain.
f. In the Label Properties > Label type drop-down list, select Name and click the
Add button.
g. In the Label Properties > Label type drop-down list, select Feature Code
Attributes and click the Add button.
h. Check the Display attributes vertically check box and click the Down arrow
located beneath the Preview frame to move the label beneath the Name label
as shown here.
You are now ready to assign three attributes to the new feature definition:
Vendor name (required)
Condition (required)
Height (optional)
3. To assign a Vendor attribute to the new Drinking Fountain feature:
a. In the Project Explorer, right-click Drinking Fountain and select New Attribute >
List.
b. In the List Attribute Definition Properties pane, enter Vendor for the Name.
f. Click OK.
Do not select a Default item; the user will have to make a choice when they
assign the feature code.
Next, you will create an attribute for the Condition of the fountain.
4. Use the same procedure to add a second list attribute definition named Condition
with three option items: Good, Repair, and Replace.
As with the Vendor attribute, this attribute is required and there is no default; the
user must make a selection.
Note that the attributes are sorted in alphabetical order in the Project Explorer.
They will display in the same order in the Feature Code Editor (which you will use
later in this procedure) and in the field software.
The next thing you need to do for the new Drinking Fountain feature definition is
assign a symbol to display in graphic views.
6. To assign a display symbol to the Drinking Fountain feature definition:
a. In the Project Explorer, right-click Drinking Fountain and select New Symbol.
7. In the Project Explorer,right-click Drinking Fountain and select Add to Group >
Water Utilities.
A new DF feature code node displays nested beneath the Groups > Water Utilities
node.
You are now ready to assign the new DF feature definition code to point 1 to verify that
the definition is working correctly.
2. Click the Browse button located to the right of the Feature code field and do the
following:
a. Select the new DF code in the list and click the Add Code button.
Note that the Condition and Vendor attributes are flagged as "required".
b. In the Condition drop-down list, select Good.
c. In the Height field, enter 1.5.
d. In the Vendor drop-down list, select Elkay.
e. Click OK.
You are now ready to re-process the feature codes in your project.
3. In the Process Feature Codes pane, ensure Keyed in Block is still selected and click
Process Sources.
4. In the Plan View, zoom in on point 1 to view the Drinking Fountain feature.
The label looks fine, but the symbol is too small. So you will make it bigger.
5. Display the Properties pane for the new Drinking Fountain symbol, change the scale
to 30, and press the Tab key.
The symbol size changes immediately, without the need to reprocess feature codes.
Note that the symbol is purple, which is the color assigned to the Drinking Fountain
layer on which the Drinking Fountain feature definition is displayed. To change the
color, you could simply select a color in the Color drop-down list.
Your new feature definition now seems to be working correctly. Next, you will edit some
existing definitions.
Change 1:
As mentioned earlier, points 2 through 5 have been feature coded to produce a curved
line representing the edge of some landscaping. You are going to modify the associated
feature definition to change the displayed line from solid to dashed.
1. In the Plan View or Project Explorer, select point 2.
In the Properties pane, note that LSE SSC is displayed in the Feature code field.
2. Click the More button located to the right of the Feature code field to display the
Feature Code Editor dialog.
Use the list on the right to find out that LSE is the line feature code for the
LandscapeEdge feature definition and SSC is the line control code for
StartSmoothCurve. (You will modify the feature definition only, not the control
code.) Note that the LandscapeEdge feature definition is contained in the
Landscape category.
If you were to view the properties for points 3 thorough 5, you would see that they
also have been assigned the LSE feature code. So they will be affected by any
changes you make in the Feature Library.
3. In the the Feature Code Editor dialog, click Cancel.
4. In the Project Explorer, select the LandscapeEdge line feature definition (nested
beneath the Landscape category node).
5. In the Properties pane, change Line style to Dashed 1-1 and click off the control.
Unlike the symbol change you made earlier, a change to the feature definition itself
will require that you re-process the feature codes.
6. In the Process Feature Codes command pane, click Process Sources.
Before change:
After change:
Change 2:
Points 6 though 9 have been feature coded to produce a rectangle representing a
building. You will modify the associated feature definition to add a label to the feature
that specifies what the feature is and its area and perimeter.
1. Select point 6 to view its feature code in the Polygon Feature Definition Properties
pane.
The feature code BLDG has been assigned to this point (and to points 7 through 9
as well).
2. Click the More button located to the right of the Feature code field to display the
Feature Code Editor dialog.
You can see that this feature code is for the Building polygon feature definition,
which is contained in the Structures category.
3. In the the Feature Code Editor dialog, click Cancel.
4. In the Project Explorer, select the Building polygon feature definition (nested
beneath the Structures category node).
5. In the Properties pane, select <New Label Style> in the Label style drop-down list
(located in the Style group).
The Label Style Manager dialog displays.
6. In the Label Style Manager, do the following:
a. Ensure that the Polygon Styles tab is selected.
b. Click the New button and name the new style Park Building.
c. In the Label type drop-down list, ensure Name is selected.
d. In the Prefix field, enter Park followed by a space. Then, click the Add button
e. In the Label type drop-down list, select Perimeter. Then, in the Offset drop-
down list, select 1 Below and click the Add button.
f. In the Label type drop-down list, select Area. Then, in the Offset drop-down list,
select 2 Below and click the Add button.
g. Click OK.
7. In the Polygon Feature Definition Properties pane for the Building feature
definition, select the new Park Building style in the Label style drop-down list.
8. In the Process Feature Codes command pane, click Process Sources.
Change 3:
Each of the points 10 through 14 has been feature coded to produce two symbols
combined to represent a tree. In this step, you will replace these two symbols with a
single symbol that is more visible.
1. In the Plan View or Project Explorer, select point 10.
In the Properties pane, note that BT is displayed in the Feature code field. Also note
that BroadleadTree is displayed in the Feature field, since this is a point feature.
2. Click the More button located to the right of the Feature code field to display the
Feature Code Editor dialog.
You can see that the BroadleadTree point feature definition is contained in the
Earth category.
3. In the the Feature Code Editor dialog, click Cancel.
4. In the Project Explorer, expand the BroadleadTree feature definition node (nested
beneath the Earth category node), and select Symbols.
Note that two symbols have been assigned to the BroadleadTree feature definition.
You will delete both of them.
5. Right-click the dtree symbol node and select Delete.
6. Right-click the trunk symbol node and select Delete.
7. Right-click the BroadleafTree node and select New Symbol.
8. In the Symbol Definition Properties pane, do the following:
a. Enter Broadleaf Tree in the Name field.
b. In the Symbol drop-down list, select Tree 1.
You can see in the Plan View that the symbol is too small. So you will make it
bigger.
c. In the Scale field, enter 20 and click off the field.
Before change:
After change: