TopoDOT FeatureCodeExport Workflow
TopoDOT FeatureCodeExport Workflow
DEPARTMENT OF
TRANSPORTATION
Overview:
This document describes the process for configuring options and using the Feature Code Export
TopoDOT tool. This tool is used to export a .csv file of your mapped features for importing into an ORD
Survey Field Book.
Required:
The latest approved ICARe version of TopoDOT
Extracted features (points and lines are both supported) on the “field code” levels. Points can
have descriptions and attribute pairs assigned using the ODOT_FieldCodes.cel cell library and
the Asset Identification TopoDOT tools.
SeedTopoDOT.dgn and Seed3D.dgn seed files
Table of Contents
A. Configure Options (Settings) for Feature Code Export Tool ..................................................................... 1
B. Using the Feature Code Export Tool ......................................................................................................... 5
C. Importing the .CSV Into an ORD Survey Fieldbook ................................................................................... 9
NOTE: The following steps should only need to be completed prior to the initial use of the tool.
1. Internal ODOT users will have the configuration files installed automatically.
a. Skip to step 3 to confirm the settings of the Feature Code Export tool.
2. External users can copy the ODOT_TopoDOT_Configuration.zip folder from this ODOT FTP location
(open FTP using Windows File Explorer) - ftp://ftp.odot.state.or.us/isb/appeng/CONNECT/Survey/
NOTE: The.ini files configure various tool settings. If you do not want to overwrite your existing .ini files
you should make a backup copy and rename them.
b. Start TopoDOT
i. In the TopoDOT workflow, TopoDOT tab, <D> on TopoDOT Start icon
d. <D> on the Manual tab in the Feature Code Export tool dialog box to ensure it is active
i. Verify the Feature Code List dropdown in the Feature Code Export tool dialog contains the
“field codes” list as shown in the image below.
iii.If your settings do not match, verify that you have properly copied/pasted the
FeatureCodeExport.ini file in Step 2.a. above. <D> on Cancel when done.
f. <D> on the Auto tab in the Feature Code Export tool dialog to make it active
i. Verify that the Levels and Feature Code columns match the following image.
NOTE: To use the Feature Code Export tool most efficiently with the settings above, the mapped
features should be on the “Field Code” levels. If the ODOT Survey Ribbon was used to extract features,
the features will be on the Existing (E_...) levels and the Auto tab workflow (Step 3 below) will not work
correctly. The features can be changed to the field code levels using either the Change Attributes tool or
the Properties dialog. If you choose not to use the field code levels, you must use the manual tab as
described in Step 2 below.
1. Setting up Point Numbers (Index) and Stringing ID’s (Feature Code Index)
i. In either the Manual or Auto tab and before any features are added to the Output Preview
box, <D> on Clear
ii. A dialog box will appear and ask for the Current Index? (Point Number). Enter an
appropriate value and <D> on OK
iii. A second dialog box will appear for the Current Feature Code Index? (Stringing ID). Enter an
appropriate value and <D> on OK
iv. When the features are extracted the assigned values will be placed on each point.
2. Using the Manual tab (this tab should be used sparingly as the Auto tab is more efficient)
i. Extract Level – extracts all features on the chosen level and assigns the defined code (field
code) in the Feature Code List dropdown. Note that ODOT has only one level for striping,
but many different striping types, so this button cannot be used to extract features that
don’t have unique levels such as striping or barrier.
A. In the Level Extraction dropdown, select the level for the features that you want to
extract
B. In the Feature Code list dropdown, select the code (field code) that you want to
assign to the extracted level
C. <D> on Extract Level and the features on the chosen level will be displayed in the
preview box with the assigned field code
D. Steps A-C will be repeated for each level that you want to extract.
ii. Extract Selected Elements – extracts all features that are selected using the Microstation
Element Selection tool and assigns the defined code (field code) in the Feature Code List
dropdown. If the striping features are not on the field code levels, this method can be used
to extract the different striping types to their respective field codes; however, the Auto tab
with the features on the Field Code levels is the preferred and easiest method.
A. In your Microstation view, select the features that you want to extract to a specific
field code using the Element Selector.
B. In the Feature Code list dropdown, select the feature code (field code) that you
want to assign to the selected elements
C. <D> on Extract Selected Elements to add the selected elements to the preview box
with the assigned field code
iv. When you have finished extracting your mapped features, <D> on Save (lower left of dialog
box) to create a .csv file of your extracted features.
A. In the Save As dialog, navigate to the location to save your file
B. Enter an appropriate File Name
C. <D> on Save
NOTE: To use the Auto tab, the mapped features must be on the field code levels. It is recommended to
use the field code levels due to its efficiency and lower chance for missing features that you manually
select using the Manual tab.
i. In the Microstation model, verify that all of the mapped features are assigned the correct
Field Code levels
ii. <D> on the Auto tab
iii. <D> on Clear to setup the starting point number (Index) and feature stringing ID (Feature
Code Index)
A. Enter point number (index), <D> on OK
B. Enter stringing ID (feature code index), <D> on OK
iv. <D> on Process to populate the preview box with the features in your model that are
assigned Field Code levels. All linear and point features on the field code levels within the
model will be imported.
NOTE: To use the standard “TIW Oregon DOT CSV file (*.csv)” import process (also used with importing
field data from Leica Infinity), a header will need to be added to the .csv file prior to importing into the
Survey Field Book. If you do not have the header, ORD will not read the lines with the descriptions and
attribute pairs farther down the list in your .csv file.
1. With Excel or Notepad++ open the .csv file you exported from the Feature Code Export tool
2. Insert the following header into row 1 to define the columns:
6. The features will import into the field book as dynamic link features. If you had descriptions and
attribute pairs, they should also be added to the point/line data in the field book (see image below).