Processing Feature Codes
Processing Feature Codes
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 Feature Definition Manager, which can be launched directly from TBC,
enables you to create or edit a Feature Definition (.fxl) file. This application is not
covered in this tutorial.
After feature codes have been processed, the software can display symbols and line
work that represent the real world objects. Features can then be exported to other
systems (for example, CAD or GIS) as necessary.
There are four basic types of features:
Point feature - A point feature is used to identify a single feature, such as tree or
utility pole. Each point feature is assigned to a point, which specifies its location.
After a point feature code is processed in TBC, the resulting feature is typically
represented by a specific symbol displayed on top of the point in the various graphic
views. You can view and edit attribute values assigned to a point feature by opening
the Properties pane for the point to which it is assigned.
Line feature - A line feature is used to identify a line, such as a fence or curb. When
points with line feature codes are processed in TBC, a linestring with feature data is
created. The feature linestring can be easily edited using the Edit Linestring
command. If offset lines are specified for the line feature, additional linestrings are
created. The line style used for the linestring is determined by the feature definition
used to define the line feature. You can view and edit attribute values assigned to a
linestring feature by opening the Properties pane for the linestring.
Note: The downloaded ProcessingFeatureCodes folder contains this PDF file, a Data
folder, a Processing Feature Codes project folder, and the Processing Feature
Codes.vce project file. You will import data from the Data folder later in this tutorial.
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.
2. In the navigation (left) pane in the Project Settings dialog, select Feature Code
Processing.
3. Click the Browse button located to the right of the Feature definition file field.
4. In the Open dialog, browse to
..\ProcessingFeatureCodes\Data\GlobalFeaturesTutorial.fxl and click Open.
Be sure to import the GlobalFeaturesTutorial.fxl file, which is part of your
downloaded tutorial package, not the default GlobalFeatures.fxl (installed with TBC)
that first displays when you click the Browse button
5. In the Project Settings dialog, click OK to close the Project Settings dialog.
The feature definitions contained in GlobalFeaturesTutorial.fxl are imported into
your project's Feature Library to be used for feature processing.
6. In the Project Explorer, click to expand the Feature Libraries > Global Features
Tutorial node.
You could, if necessary, make changes or additions to the project's Feature Library
using the Properties pane. See the TBC Help for instructions. For this tutorial, you
will not make any changes.
Before processing, you will take a look at the unprocessed feature codes in your project.
2. In the Project Explorer pane, expand the Points node. Then double-click point 700.
The Properties pane displays showing properties for point 700. The feature code
assigned to the point displays in the Point Information section.
3. Click the Browse button in the Feature code field to view more information
about the feature code in the Feature Code Editor dialog.
This dialog allows you to remove a feature code, select a different feature code, add
a feature code, and/or change attribute values. Note that the feature codes are
defined in the GlobalFeaturesTutorial.fxl file.
4. To view the photo assigned to point 700, select the photo attribute row and click
the View File icon located near the top of the dialog.
The photo displays in your default photo viewing software.
5. When you are done viewing the Feature Code Editor, click Cancel to close the
dialog.
You are now ready to process the feature codes in your project.
After processing is complete, the Feature Codes Processing dialog displays asking if
you want to view the Feature Code Processing Report.
3. In the Feature Codes Processing dialog, click Yes.
The Feature Code Processing Report displays on a new tab in the TBC window.
4. Scroll to the "Unknown Feature Codes" section.
Note that there are four points whose feature codes are unknown. This means that
there is no corresponding feature code contained in the project's Feature Definition
Library to process the codes. In this case, the codes were incorrectly entered in the
field.
Do not close the report. You will continue to use it in the next step.
Next, you will fix the unknown feature codes before reprocessing.
The yellow icon located at the right in the Feature code field indicates the point
has an unknown feature code. You can enter a new code directly in the field if you
know it and you do not need to specify any attributes. Otherwise, you can click the
button to open the Feature Code Editor dialog to make the changes. For this
tutorial, you will use both methods.
3. Click the Browse button in the Feature code field.
The Feature Code Editor dialog displays.
6. Click OK.
The newly assigned code displays in the Feature code field in the Properties pane
for point 727. The yellow icon no longer displays with the feature code.
7. Change codes for the other points displayed in the "Unknown Feature Codes"
section of the Feature Code Processing Report. Just click each point in the report to
display its properties in the Properties pane.
a. For point 728, change rd end to RB END.
For this change, click the button to open the Feature Code Editor dialog.
Delete rd end from the Feature code field. Then select RB (RoadBarrier) in the
GlobalFeaturesTutorial.fxl list and click the Add Code button. The code RB
represents a line feature and should include the END (EndLine) line control
code. Click the Category filter icon and select Line Control Code to display
only line control codes in the list.
Select END in the list, and click the Add Code button.
Then click OK to see the change in the Properties pane for point 728.
You are now ready to reprocess the feature codes with the changes you made.
4. In the Process Feature Codes pane, select the checkbox for rtd topo.jxl and click the
Process Source(s) button.
After processing is complete, the Feature Codes Processing dialog displays asking if
you want to view the Feature Code Processing Report.
5. In the Feature Codes Processing dialog, click Yes.
A new Feature Code Processing Report displays on a new tab in the TBC window.
Note that there are no longer any unknown feature codes listed in the report.
You can now view the processed features.
To better view the features, you can choose to hide unnecessary data in the Plan
View.
2. In the TBC ribbon, select Home > View > View Filter Manager.
The View Filter Manager pane displays.
To view information about a feature, including any attribute values, you can select
the point or linestring to which the feature is assigned.
4. In the Plan View, click the red symbol on point 700 and select Point: 700 in the
context menu.
If necessary, right-click anywhere on the Plan View and select Properties in the
context menu to display the Properties pane.
The Properties pane for point 700 displays. In the lower portion of the pane, the
Feature section displays the processed feature name and attribute values assigned
to the point feature.
You can select a different feature or change any attribute values using these fields. If
you select a different feature for the point and then reprocess the feature codes in
your project, the new feature you assigned to the point is kept with the point, while
the original feature code is used to create a "secondary" feature for the point, which
you can select in the Plan View.
In addition, because the Allow editing of processed feature codes check box is
checked (by default) in Project Settings > Feature Code Processing, you can edit the
point's feature code directly in the Feature code field. However, for your change to
take effect, you must re-process the feature codes in the project.
Note: When you type into an empty Feature code field, the auto-fill feature
automatically displays the "next" suggested character based on the feature codes
imported from the Feature Definition (.fxl) file.
Note: A Media Folder is attached to any point or line to which a media file is
assigned, whether it was assigned to the point as a feature attribute or assigned
some other way. If a media file (for example, a photo) is assigned to a point as a
feature attribute and additional media files are assigned to the point as well, you
can select to use one of the other media files as the feature attribute by selecting it
in the media (for example, Photo) drop-down list in the Feature section of the
Properties pane.
5. In the Plan View, click the Media Folder icon for point 700 and, if necessary, select
Media Folder: 700 in the context menu.
The Properties pane for the Media Folder is displayed showing the media file
assigned to the point and information associated with it. You can click the View
button located to the right of the media file path to view the image in your
default photo viewing software.
6. In the Plan View, click the line running through point 700 and, if necessary, select
Linestring: GutterLeft in the context menu.
This is a linestring created from line feature codes during processing. The Properties
pane for the linestring displays showing the feature name and any feature
attributes.
On closer examination of the Plan View, you can see what appears to be an error in
coding for point 747.
If you view the Properties pane for point 747, you can see that it is feature coded
gutl for gutter left. However, if you view the Properties pane for the line feature
points that precede and follow it (746 and 752), you can see that their codes include
the numeric instance identifier 1 following the gutl code: gutl1.
If you view the Properties pane for points 1051 and 1061 (upper close-up), you can
see that they both are coded gutl, just like point 747. (Point 1061 also includes a
non-processed description string.) Because 747, 1051, and 1061 share the same gutl
feature code, the resulting line connects them; when, in fact 747 should be
connected to 746 and 752.
7. To fix this problem, use the Properties pane to change the feature code for point
747 from gutl to gutl1. Then re-process the feature codes.
You can also view the features in your project in 3D. But before you do, you will
apply additional filters to your view to make the features easier to see.
8. In the View Filter Manager pane:
In the Raw Data list, uncheck Media Folder.
In the Layers list, uncheck Points.
On the Point tab, uncheck Show point IDs.
On the Point tab, check Show feature symbol only.
9. In the TBC ribbon, select Home > View > 3D View. Then use your mouse wheel to
zoom in as shown here.
10. In the TBC ribbon, select Home > Views > 3D View > 3D View Settings.
The 3D View Settings pane displays. You can use the controls in this pane to change
the 3D view of the features.
a. In the Vertical angle field, enter 54°00'00".
b. In the Azimuth field, enter 25°00'00".
You can also click any of the Preset Views buttons in the 3D View Settings
command pane or on the ribbon.
11. To view the feature data in Google Earth Pro, do the following:
Note: It is recommended that you use the Google Earth Pro desktop application to
view data from TBC due to its extensive feature set when compared to the browser-
based Google Earth application.
a. In the TBC ribbon, select Home > View > Google Earth.
b. In the Google Earth pane, click the Options button and select Select All.
Note that the features extend across a roadway that did not exist when the
survey was performed. Using Google Earth Pro's Historical Imagery view option,
change the date to 3/2008 to see the parking lot that was originally surveyed.
Next, you will export the processed feature data as a CAD drawing file.
2. On the CAD tab, select DWG exporter in the list at the top of the tab.
3. In the Data section, click the Options button and select Select All.
4. Click the Export button to create the CAD drawing (.dwg) file and save it to your
project folder.