ITD CADD Standards Manual 2011
ITD CADD Standards Manual 2011
Search
CADD Standards
Manual
July 2011
Edition Changes
January 2011
Section 100 wording was changed to from “MicroStation XM” to “MicroStation”.
Sections 565 and 575 were edited to clarify the use of upper case text.
Appendix B was updated to reflect new Construction folders.
Appendix D S-1-E-2_TRAFFIC_Util_ENV_Etc was updated with new Environmental symbology.
July 2010
Appendix B was updated to include addition of directories for Plan Reviews.
Appendix D, and F were updated to add levels and symbology to Alignments, Design, Survey and
Topography.
Created Appendix G, Survey Features, Codes and Styles.
Section 675 was edited to include reference to Appendix G.
Section 710 was edited to include plan sheet scales for Traffic Drawings.
Cadd Standards Table of Contents
Manual
APPENDIX
3/8/2010
SECTION 100 - INTRODUCTION
The ITD Computer Aided Drafting and Design Standards and Procedures Manual (CADD
Standards Manual) is intended to outline the use of Idaho Transportation Department‘s (ITD)
corporate workspace and Bentley System’s MicroStation and InRoads software, as well as other
tools and procedures developed internally.
Following these standards will help to unify the appearance of drawings included in plan sets and
facilitate the exchange of information between ITD districts and sections as well as consultants
working on ITD projects. The ITD CADD Standards Manual will address issues such as
software, standards, tools, and procedures which will aid in the efficient, consistent production of
ITD plan sets. This manual and the electronic resource files contained in the ITD workspace are
intended to be used by both ITD internal design sections and the consulting firms doing business
with ITD.
Phase I of the CADD Standards project began in 2005 with the development of electronic
resource and configuration files and the creation of an ITD Corporate Workspace. The project
was implemented in March of 2007, coinciding with the release of Bentley’s V8 XM Edition of
software. User training was provided and existing projects were updated at that time.
In the initial phase of this project the Project Development disciplines were emphasized. The
goal over time is to continue the standards project by addressing each of the specialty groups
within ITD as well as providing continued enhancement of the current configuration by
continually updating software and adding to ITD’s Workspace configuration, workflows, and
training programs.
Ultimately, the CADD Standards project will create a complete electronic project delivery and
archival system beginning with Planning and continuing through Construction and Maintenance.
The combination of software, workspace, and workflows will allow all users to work together in
the most efficient and productive environment possible.
Updating of the manual is intended to be a continuous process and revisions will be issued
regularly in conjunction with the release of the ITD Design Manual updates. The current
workspace version can be obtained by going to the “About_ ITD_Workspace” folder in the
Corporate Workspace and accessing the “Readme_WhatsNew” file.
SECTION 200 - ITD Corporate Workspace
205 - Installation
225 - ITD_Standard.xin
1
SECTION 200 - ITD Corporate Workspace
The ITD configuration files define locations where MicroStation and InRoads will find ITD
specific resources. They also enable or disable specific MicroStation and InRoads tools allowing
for a streamlined and standard environment within ITD. Along with the configuration files,
custom tools, tasks and utilities needed to perform design and drafting functions have also been
created and made available to the user within the workspace. These tools have been included to
save the users time and enable them to be consistent between projects.
205 Installation
For ITD users, the installation of the Workspace will be performed and maintained by the HQ
CADD Support Team and the District IS or CADD Coordinator or Primary User. This includes
the CADD software upgrades and the maintenance and backup of ITD workspace files. This will
ensure that all ITD CADD workstations have the latest Workspace files available and that they
are updated through automated routines.
Custom configuration files have been created that will set the correct MicroStation resource files
and other standard files located on the user's computer. Along with these configuration files,
personal DGNLIB files have also been included in the workspace allowing users to customize
their workstations without impacting other users.
For the Consultant process to install the ITD Workspace and Configuration Files see the
instructions in Appendix A.
An ITD Corporate folder structure has been developed to store all project related data from
planning through maintenance. This manual is concerned only with folders under the CADD
directory and to the resource files and information related to the ITD Workspace. The CADD
folder structure is integrated with the MicroStation configuration files so that the user will not
2
have to navigate to find files. MicroStation and InRoads will find the necessary files to ensure
the ITD configuration runs correctly.
A custom utility named ITD Project Creation Utility has been developed to create the ITD
project folder structure on the Projects server and populate those folders with the proper files
including cell libraries, font libraries, seed files, InRoads preferences and template files, sheet
borders and all other resources.
The ITD workspace contains a personal DGNLIB file called “My Interface” under ITD Tools
dropdown on the main menu bar that allows users to make changes to the configuration
without affecting other users.
The customized ITD Task Navigation sidebar menu provides access to tools and tasks
intended to provide the user a simple, efficient method to apply ITD’s CADD standards to
every project. These tools and tasks direct MicroStation to place elements on discipline-
defined levels using ByLevel symbology for drawing consistency.
MicroStation levels can be filtered to make specific levels more readily available during the
design session. Standard filters have been created in the ITD workspace to allow the user to
quickly and efficiently select the proper level. These filters, the levels and By-Level symbology
assigned to each are shown as separate tabs in the spreadsheet in Appendix D.
225 ITD_Standard.xin
ITD has developed an “ITD_Standard.xin” file to provide a means by which to apply ITD
standards to InRoads and Survey generated data and graphics. This preference file stores the
preferences available for use in each dialog box. Style settings and Named Symbology settings
apply ITD’s standard ByLevel symbology when data is displayed. The .xin file is placed in the
project folder structure by the Project Creation Utility when the utility is run and is used by
surveyors and designers through out the life of the project.
3
SECTION 300 - Project Directory Structure and Project Creation Utility
310 - Security
Page 1 of 2
SECTION 300 - Project Directory Structure and Project Creation Utility
ITD has adopted a standard Project Directory Structure for all project related data. This directory
structure, along with a standard CADD file naming convention, has been created to enable
efficient management of all files within an ITD project. This will aid in the exchange of data
between ITD sections and ensure consistent, reliable data retrieval by all members of a project
team. This document will only address that portion of the file structure that pertains to the
CADD design process.
The ITD “Projects” Directory has been designed so that the top level directory for each project is
designated by the 5 digit project Key Number prefaced by the letters “prj”. Under this directory
the user will find sub-directories where all project information will be created and stored using
ITD’s standard file naming convention. Below the project directory you will find subdirectories
for each of ITD’s specialty sections. Under each specialty section directory is a sub-directory
structure unique to that section.
This directory structure is the foundation of a project lifecycle that includes electronic plan
review, bidding, inspection, machine control and maintenance. Following this standard directory
structure without revision will ensure the accurate sharing of information between sections
within the department as well as with consultants and contractors
ITD has developed a Project Creation Utility that automates the creation of ITD’s standard
project directory structure on the file server. At the beginning of each project, the CADD
Coordinator or Primary User will run the Project Creation Utility to create the directories in the
Projects folder. These directories will be the permanent location for all information pertaining to
a given project. The utility will create the project directory folders and sub-folders as well as
populating certain folders with project related resources and appropriate security
310 Security
Security and access permissions are controlled by active directory groups and assigned to each
folder by the Project Creation Utility. The ITD active directory groups are shown on the file
structure in Appendix B. Each district is required to determine the level of security needed by
members of their design teams and to arrange for them to be included in the appropriate active
directory groups.
The ITD active directory groups are removed from the Consultant version of the Project Creation
Utility. Security on project folders should be assigned by consultants to meets the needs of their
organizations.
Page 2 of 2
SECTION 400 - CADD File Naming Convention
The ITD design process requires that CADD drawings be created in multiple design files
depending on their discipline. Over the life of an design project, many of the specialty sections
will create CADD data in design files that need to be referenced together to produce a final plan
set. These design files need standard, unique, names that allow the CADD user to easily identify
the specialty section responsible for the file and the type of design data the file contains.
When used consistently, ITD’s CADD File Naming Convention will allow for easy, dependable,
archiving and retrieval of data for the complete lifecycle of a project. All ITD CADD drawings
should follow this standardized naming convention so that project data can easily be identified
and accessed by all sections.
Page 1 of 1
SECTION 500 - Drafting Standards and Resource Files
565 - Annotation
Page 1 of 5
SECTION 500 - Drafting Standards and Resource Files
ITD standard resource files consist of cell libraries, seed files, level libraries, text and linestyle
design libraries, and other CADD information necessary to create project plan sets that conform
to ITD standards. Adherence to these standards ensures consistent plan set appearance and
accuracy.
Seed files are the basis for all ITD MicroStation Design files. Seed files are templates in which
parameters have been set for the ITD standards. The seed files define the working units, global
origin of the coordinate system, resolution, and whether the file is a 2D or 3D file. Seed files for
both 2D and 3D are available in the workspace and should always be used when creating a new
design file. All ITD design disciplines use the ITD “Standard” seed files with the exception of
the Bridge Section. ITD’s Bridge Section has its own “Bridge” 2D and 3D files.
Working units settings are used to control units of measurement for design files. ITD
requires that all design projects be completed in imperial or “English” units; therefore, ITD
seed files have been developed for imperial units only. ITD working units are based on the
U.S. Survey Foot for master units and inches for the sub unit.
The resolution for all ITD seed files, including Bridge seed files, has been set to 12000 units
per Survey Foot and this resolution setting should not be changed. This setting affects the
size of the elements within a MicroStation file and if changed will incorrectly scale all
existing elements within the file.
The coordinate system determines the accuracy and format of the design file. ITD uses the
Idaho State Plane Coordinate System on all roadway design projects and the standard seed
files will accommodate this coordinate system.
The Coordinates set the format and accuracy of the design file based on the working units.
The degree of accuracy is based on the number of decimal places or, for Bridge, the fraction
selected. ITD Standard seed files are set to a coordinate readout of Master Units with an
accuracy of three decimal places. The Bridge seed files are set to a coordinate readout of
Master Units and accuracy of 1/32.
The Angle settings control the format, mode, or accuracy of the design file angular readout.
ITD Standard 2D and 3D seed files are set with the angular format of
Degrees/Minutes/Seconds and the mode set to “Bearing” with an accuracy of 0. The Bridge
seed files set the angular format to Degrees/Minutes/Seconds and the mode to
“Conventional” with an accuracy of 0.
Page 2 of 5
525 Global Origin
The file global origin is a point within the design plane used as a base point for the placement
of graphics elements. ITD’s 2D and 3D files use the default MicroStation global origin
which is located in the center of the design plane.
The ITD Standards contains both 2D and 3D seed files and both are available for use when
creating a new design file. Both files have the same settings applied to them with the
addition of the Z value in the 3D file. All design model files should be created using the 3D
seed file. The XM version of MicroStation allows 3D model files to be referenced to 2D
sheet files and the ITD border or *.bdr files have been developed in 2D and are to be
referenced to a 3D sheet file.
The ITD Workspace contains many cell libraries, each of which is made up of discipline specific
data, and is intended to be accessed and used by designers of all sections. All cell libraries are
assigned to the seed files and most cell libraries have a corresponding Cell Selector feature with
an icon on the ITD Task Navigation menu to sort the cells into discipline specific groups for ease
of use.
Design File Level Libraries (DGNLIB) and corresponding specialty section filters have been
developed to allow users to seamlessly work across disciplines and level duplication has been
avoided wherever possible. The DGNLIB files are assigned to the seed files and available when
a new file is created. The creation of new levels and changes to the existing levels has been
locked within the ITD Workspace in order to maintain the “ByLevel” symbology that allows
data to inherit attributes for color, linestyle and weight from the level it is placed on. This
ByLevel Symbology also allows for the data’s use by other applications such as InRoads and
Quantity Manager. ByLevel symbology is the default for all level libraries and is the required
ITD standard.
Filters have been created for each of the ITD discipline specific level libraries to allow users
to quickly and efficiently place elements on the appropriate levels and to turn levels on or
off.
For a complete list of ITD’s MicroStation Levels and their Named Symbology see Appendix
D.
The standard color table file, ITD.tbl, is attached by default to all ITD seed files. The colors
within the table correspond to the By Level color symbology specified in the level libraries.
Specific colors are assigned to ensure consistency and to enable users to easily identify data.
Page 3 of 5
Colors are defined by a number and MicroStation reads this color table to determine the correct
color to display.
Line weights in MicroStation are defined by designating the thickness of the line used when
plotting an element. ITD uses line weights 0-4 on plan sets. These weights correspond to the
ByLevel weight assignments within the level libraries and are shown in Appendix F.
A custom line styles library has been developed for use within ITD. The line styles are contained
within the workspace in a MicroStation resource file called Line_Style.DGNLIB. These lines
styles correspond to ByLevel line style assignments within the level libraries and are shown in
Appendix F.
565 Annotation
ITD has developed several font resources available in the ITD workspace and they are attached
to the design file by configuration variables. The standard Font for plan sheet text is “130 ITD
Gen Eng” and is loaded as the default font in the text editor.
ITD standard annotation text styles and dimension styles are contained in DGNLIB files. These
libraries contain predefined text and dimension settings for several different sizes of text. These
standard text styles have been defined to ensure consistent legibility on all plan sheets. When a
user selects a text style, the height, width, line spacing and justification is set automatically so no
adjustments are needed. The desired style must be picked from the drop down menu before
placing text as the default style attached to all ITD Seed files is “No Style”. If Italics or
Underline is desired, it can be selected through the MicroStation Text Editor.
ITD text style names include whether it is a “Standard” or “Bridge” style and the text size
(08”). The default justification is at the left bottom and other justifications, such as CB for
Center Bottom, are included in the text style name. Standard text sizes refer to the size of the
text when plotted, not the text size in the MicroStation file. The text size in the MicroStation
file is dependent upon the intended plot scale and the annotation scale. There is also a style
for masked text which blocks out other graphics around the text being placed.
Maintaining the minimum letter height and letter stroke width is very important so that
information does not disappear or become illegible when plan sheets are photocopied or reduced.
The standard text style to be used for general purpose annotation is “Standard 08”. There are
several larger size text styles available, however, these sizes are normally only used as titles or
on presentations or exhibits.
The Dim_Styles.DGNLIB file contains standard dimension styles for Bridge, Traffic and Design
drawings.
Page 4 of 5
570 Annotation Scale
The annotation scale is used for defining the scale of the cells, text, custom line styles, and
dimensioning in both sheet files and model files. Only custom linestyles are affected by this
scale factor, native MicroStation line codes are not. By default the annotation scale lock is
turned on. The default drawing scale setting is 1:40. If a different scaled drawing is desired, the
user must edit the drawing scale in the model properties or under the “Settings” option on the
main menu bar. Annotation that has been placed by InRoads is not affected by the model
drawing scale. InRoads text size is controlled by the global scale factor in InRoads. If InRoads
text is not displayed the right size or if a different scale is required, the annotation should be
redisplayed with InRoads using the correct global scale factor.
Capsules designate the pay item callouts. (Numbers to reflect bid items
and/or special provision items. Use the pay item number.)
Triangles designate revisions to the plans. (Start with number 1 and increase
by increments of 1. To be used only during Contract Advertising submittal by
Roadway Design.)
Page 5 of 5
SECTION 600 - InRoads Standards
610 - Preferences
615 - Styles
Page 1 of 5
SECTION 600 - InRoads Standards
This chapter covers directory locations, descriptions, and naming conventions for the data
files used or created by the InRoads design software. These binary files contain all
engineering design data created during a project and the instructions on how that data is
output, whether to a MicroStation graphic format or to a text report format.
InRoads requires multiple file types to perform the various functions required for the
creation of a roadway model. These files can be generally segregated into two
categories.
The first group, or preference files, controls the graphic display, text reporting, and
precision of data.
The second group, InRoads Data files, contains the data files created during the process
of designing a roadway project.
610 Preferences
615 Styles
InRoads Styles control symbology for the display of horizontal and vertical geometry
in the MicroStation Model file. Points, Lines, Arcs, and Spirals from the InRoads
alignment files are displayed according to ITD by-level symbology.
Page 2 of 5
620 Drafting Notes
This file contains InRoads intelligent drafting notes that access engineering data from
the geometry file and digital terrain model files. The drafting notes file sets the
graphic parameters for displaying notes that contain data such as station, offset, or
elevation from the data files.
InRoads data files contain all pertinent engineering-generated data assembled during the
project. These files are user-created during the evolution of a project and are saved in the
project folder. See Appendix C_ITD Naming Convention for naming and location of
InRoads data files.
Digital Terrain Models are mathematical representations of the surface of the earth.
InRoads uses DTM data to produce contours, display the existing and proposed
groundlines in profile and cross section grids and in the calculation of cut and fill
quantities. DTMs are created with a combination of surface points identified as spot
points, breaklines, contour lines or other point types used to define the surface.
ITD Geometry Project files contain horizontal alignment, vertical alignment, and
superelevation information. The Existing Geometry Project contains the centerline of
survey as acquired by the Survey department. Proposed Geometry files contain
geometry relating to proposed horizontal and vertical data. The proposed geometry
file will contain all alignments for the roadway design including ramps, detours, cross
streets and the associated vertical profiles.
Important note: There are a number of settings in the alignment file that must be
evaluated by the design engineer. Many of the settings have been addressed in
the ITD configuration; however care must be taken to assign proper values for the
Page 3 of 5
modeling of the design surface as required by the project. One example of these
settings is the Rounding Linear Transitions variable for superelevation which is
on by default in the ITD configuration. With the setting to on, superelevation
transitions will be rounded to the nearest 30 feet. With the setting off, InRoads
will calculate the transitions exactly.
The Template Library contains templates, template components and end conditions,
transition control names, and other data used to model the proposed roadway surface.
The standard ITD Template Library file contains standard templates and tables that
can be copied and modified for each specific project requirement and is placed in the
Project Development\Civil folder when the Project Creation Utility is run. The
naming convention for Template Library consists of the project key number with the
.itl file extension.
The Project File contains the directory location of all the InRoads data files used for a
particular project and is used to load all necessary files for an InRoads session. This
file is an ASCII file that can be edited using Notepad. The naming convention for the
Project File consists of the project key number with the .rwk file extension and is
stored in the Project Development\Civil_Data folder.
This file contains the geometry project cogo points and surface data that is used to
create XML reports. When the xml file is generated by the InRoads XML Report
tool, the file is placed in a temporary directory. If the xml file is to be saved for later
formatting, the file should be placed in the Project_Development\Civil_Data folder in
the project directory.
InRoads reports are the result of xml data formatted by an .xsl or Style Sheet file.
These files specify what information is used from the XML Data files that are output
by InRoads and how the information will be formatted and displayed to create an
Inroads report. Several ITD standard style sheets have been defined and are stored in
the Corporate Workspace\InRoads\Style Sheets directory.
Page 4 of 5
675 Survey Files
InRoads Survey requires similar files to InRoads and uses the ITD_Standard.xin file for
the control and display of survey data. The ITD_Standard.xin file specifies survey field
coding, survey control codes, and code properties for planimetrics, DTMs, and geometry
symbology. See Appendix G for Survey Features, Codes, and Styles.
Page 5 of 5
SECTION 700 - Project Plan Sets
715.01 - Revisions
715.04 - Date
Page 1 of 7
SECTION 700 - Project Plan Sets
This chapter is concerned with the CADD standards aspects of preparing an ITD plan set. For
help with the required design elements of the plans see Section 800 – Plans in the Design
Manual.
All plan sheets should be developed using ITD's CADD Standards and the ITD Corporate
Workspace. All plan sets will have English units throughout and shall be in a format compatible
with the ITD CADD system.
Historical or archived data that was produced before the system was available and those plan
sheets that cannot be produced using the ITD CADD system may be scanned and stored on the
CADD system.
Final plan sheets submitted for advertisement shall be properly endorsed by the engineer. They
shall be on a durable medium such as Mylar to preserve the drawings for archival purposes.
Some necessary details for preparing project plan sheets may not be covered in these procedures.
If questions arise on the amount of detail or appropriate format, other similar project plans
should be reviewed for example or the Roadway Design section should be contacted. Variations
to these instructions require approval from Roadway Design.
Appendix E contains specific plans, drawings, examples, etc., that can be followed when
preparing project plans.
The following information explains typical plan preparations and organization for preparing
project plan sheets for the Idaho Transportation Department.
The following plan sheet scales shall be used on all drawings for the Idaho Transportation
Department:
Roadway drawings
1”=10’
1”=20’
1”=40’
1”=100’
1”=200’
1”=400’
Full Size 1=1
Page 2 of 7
Traffic drawings
1” = 100’ ----- Minimum scale for pavement markings plan sheets without transitions or special
details.
1” = 40’ ------ Preferred scale for pavement markings plan sheets with transitions or special
details.
Bridge drawings
1”=1’
1”=5’
1”=10’
1”=20’
1”=30’
1”=40’
1”=50’
1”=60’
1”=100’
3/32”=1’
1/8”=1’
3/16”=1’
1/4”=1’
3/8”=1’
1/2”=1’
3/4”=1’
1 1/2”=1’
All plan sheets shall use the ITD title block designed for that specific sheet. The title block shall
have all the necessary information shown in its appropriate place. Changes to the title block may
be made with the approval of the Roadway Design section. The following describes the basic
information in a standard title block.
715.01 Revisions
The revisions section is only for changes to the plan sheets after they have been stamped and
endorsed by the engineer. Each change should be marked with a triangle and numbered
successively. In the revisions box the triangle shape should be marked with the corresponding
number of the plan sheet change and a date, the initials of the person making the revisions, and a
description of the revision entered in the appropriate place. Each different change should be
Page 3 of 7
entered on a new line. Entries in this box should primarily be made by the Roadway Design
section.
Enter the names of the designer, the person who checks the design, the detailer, and the person
who checks the drawing, whenever appropriate.
File Name: A standard electronic file naming convention is used by ITD for the naming of plan
sheets to be retained and archived.
See Appendix C for complete details of the file naming convention.
715.04 Date
Enter the date the drawing is completed, which is usually when the last corrections are made for
Final Design or Contract Advertising submittal.
The section name box is directly below the ITD name and seal and is for the area section name,
or the consultant may place their business name within this box. Appropriate names would
include the district and section, such as “District 6 Design” or “Headquarters Traffic Section.”
On the title sheet only, for federal-aid projects it may be necessary to show two or more project
numbers when right of way and construction are handled under separate project numbers. Show
the construction project number only on all other sheets.
If it is a state project, show the project number in this box.
A sheet title consisting of the type of sheet it is should be shown for each sheet. The names
should generally coincide with those shown in the index.
The large box below should generally have the project name, but may include additional
information such as sheet station limits, structure numbers, intersection names, and other brief
identifying descriptions.
The top box is generally open but may contain the catalog number or the ITD sheet number for a
particular sheet. The second box should show the county or counties in which the project is
located. The third box should show the project key number. The bottom box is for sheet
numbering.
Page 4 of 7
715.09 Engineer's Endorsement Space
The endorsement by the engineer must be on a standard size plan sheet. Full size electronic
representations of the engineer's stamp shall be used on standard size plan sheets.
Roadway Group
Title Sheet
Standard Drawing Index
Vicinity Sketch
Total Ownership Map
Plan sheet index showing the area covered by each plan sheet on the Total Ownership
Special Maps
Project Clearance Summary
Typical Sections
Summaries
Roadway
Bridge
Pipe Culvert
Pipe Siphon
Irrigation Pipe
Sewer Pipe
Pipe Under drain
Plan and Profile Sheets
Special Drawing Group
Sediment and Erosion Control
Minor Structures Drawings
Drainage Plans
Paving, Concrete Joint, Approach Slab Details
Roadside Development and Landscaping Plans
Bike Lanes and Pedestrian Path Plans
Source Plat and Reclamation Plans
Traffic Group
Illumination Materials List
Illumination Plans
Traffic Signalization Materials List
Traffic Signal Plans
Railroad Signal and Crossings
Signing Erection Specifications
Signing Plans
Pavement Marking
Delineation and Raised Channelization
Traffic Control Plans
Page 5 of 7
Utility Group
Optional separate numbering
Bridge Drawings
Optional separate numbering
Standard Drawings
Detail sheets shall be located directly after the plan sheets to which they are related.
Projects plan sets consist of both planimetric sheets, which contain plan and/or profile views of a
design model and informational sheets that contain text-only information.
Project plan sheet files should be made up of design model files drawn in real world coordinates
and attached to the sheet files as reference files. Informational sheets need not contain design
graphics, but may only contain text such as general notes, or other instructions or details. It is
recommended that text-only information be placed within the sheet file. If the text is in a table
format the text and linework should be placed on their appropriate levels. In the case of a typical
section or detail drawing it is suggested that the linework be drawn in a model file on the
appropriate drafting levels and the text and dimensioning be placed in the sheet file.
Some types of graphic information that does not reside in real world coordinates such as a scaled
detail of an irrigation structure, could be placed in either a model file or a sheet file.
Right of way or Utility plans are put together in the same manner as Roadway plan sheets,
according to the guidelines in the ROW or Utility section of the ITD CD-ROM Publications, by
referencing a combination of existing design and plan sheet files to specific Right-of-Way or
Utility files to show the necessary topo, survey and roadway details required to make up a
detailed set of plans for the use of the Right of Way and Utility sections in their work.
ROW plans should be plotted using the “Halfsize ROW.pen” design script which plots
everything on levels ROW_Parcel, ROW_Easement-Hatch, and ROW_Total-Ownership-
Boundary in color with a transparency of 80% and everything else black.
Utility plans should be plotted using the “Halfsize Utility.pen” design script which plots
everything on levels beginning with UTIL_ in color with a transparency of 80% and everything
else black.
ITD has adopted the use of the InRoads Plan and Profile Generator tool for the creation of plan
sheet files and can be used to create plan only, profile only, or plan and profile sheets. The Plan
Page 6 of 7
and Profile Generator automates the attachment of reference files and rotates and clips the files
to align with the profile and sheet border. Sheet files must be created by the Plan and Profile
Generator before the InRoads Quantity Tools can gather pay item quantities from the design
files.
The Plan and profile generator tool uses the designated InRoads horizontal alignment to
determine the center of the plan view window. The clipping boundaries and match line locations
are defined by the user. This tool has the ability to automatically shift the displayed elevation
range to insure that the vertical alignment and surface graphics fit inside the profile window.
Plan and Profile Generator also fills in certain fields in the title block, automatically rotates and
places the north arrow cell, and creates and annotates match lines based on user defined station
limits.
Plan sheets for projects that do not contain InRoads alignments will need to be set up by
individually attaching, rotating and clipping the required reference files to the sheet file.
Standard linestyles, cells, symbols, and levels used on project plans are shown in the Standard
Drawing “S” series in Appendix F. The “S” series drawings show the symbol size and BY-
Level symbology (line style, line weight and color) for each symbol or linestyle and the named
level assignment for each. These standard symbols and linestyles are stored in the CADD
system for internal reference and use and are available on the ITD web site for use outside of the
Department.
Page 7 of 7
SECTION 800 - ProjectWise Plot Organizer
Page 1 of 2
SECTION 800 - ProjectWise Plot Organizer
ITD has selected ProjectWise Plot Organizer as its standard plotting software. ITD
standard settings files and design scripts have been developed to create uniform plot
sets that can be quickly re-plotted with updated data when needed. Project Wise plots
can also be published as PDF files for sharing with other programs or archiving of
project data.
Settings files provide a way of defining standard plotting parameters such as plotter,
design script, scale, and rotation for plots each time the plotting dialog box is opened.
ITD settings files have been developed to create plots on plotters in each district and are
imbedded in the district specific plotter queue loaded to the workstation through the
“Printers and Faxes” section of the Control Panel.
ITD design scripts are applied during plotting to control pen widths, colors, and specially
colored plots such as right-of-way plan sheets. These design scripts recognize ITD’s
named levels and elements placed on incorrect levels may not plot as desired. Standard
design scripts have been created for black and white plotting, full color plotting, and for
black and white plotting with colored right-of-way or utility details in each acceptable
sheet size.
The standard ITD plot size is 11" x 17" which is the default setting. Other plot size
settings are available, such as 8 ½”x11” for “Maintenance” type jobs or 22”x34” for
Bridge drawings and “Roll” for larger size exhibits or presentations.
Page 2 of 2
APPENDIX A
ITD WORKSPACE INSTALLATION
The ITD Workspace resides on the District file server DXitfs01 in the DX\CADD directory and
must be mapped as the drive letter “S”. No other installation is necessary. The CADD directory
also contains documentation files and other supporting data. For ITD sections, the workspace
itself resides in a folder named “Corporate_Workspace.” Project files reside on the server in the
“Projects” directory and must be mapped to the drive letter P. All users working in the
workspace must have appropriate read/write permissions on those drives.
For Consultant installation, the ITD Workspace resides on the file server in the
“ITD_Workspace” directory and must be mapped to the drive letter S. Project files reside in the
“Projects” directory and must be mapped to the drive letter P. For example: S:\ITD_Workspace,
and P:\ Projects. These drive letters are hard coded in the workspace and some software
functions can not find a URL address. All users working in the workspace must have
appropriate read/write permissions on those drives.
Unzip the file ITD_Workspace.zip to the S: drive. This file will create the folder named
ITD_Workspace that contains all the files and resources necessary for the workspace. Create a
folder named “Projects” on the P: drive.
Software
The ITD workspace is compatible only with Bentley Systems Inc.’s MicroStation and InRoads
software and they must be installed on the user’s computer.
Custom configuration files have been created that will set up the correct MicroStation resource
files and other standard files on the user's computer. Copy the configuration file,
ITD_Standards_Local.cfg from S:\Software\Local_CFG_File to C:\Program
Files\Bentley\MicroStation\config\appl.
Installing the ITD workspace does not over ride the standard MicroStation environment. Users
can choose to enter the standard MicroStation workspace or the ITD Workspace by selecting the
appropriate shortcut icon on the desktop. The “ITD MicroStation” shortcut icon resides in the
Cadd\Software\Software Icons” folder and can be copied to the users desktop. The target for this
shortcut may need to be edited as the path to the MicroStation installation may vary from version
to version.
Create Users
Each user working in the ITD Workspace must have a folder for his personal resource files such
as a personal DGNLIB file, user preference file, function key menus, etc. This folder is created
in the workspace under the User_Workspace folder by running the Create User.bat file located in
Page 1 of 2
that folder. Enter the user’s server login at the prompt and run the .bat file for each person that
will be working in the ITD Workspace.
The ITD workspace contains a Project Creation Utility that automates the creation of ITD’s
standard project directory structure. At the beginning of each project, the project manager will
run the Project Creation Utility to create the directories in the “Projects” folder on the P drive.
These directories will be the permanent location for all information pertaining to a given project.
The utility will create the project directory folders and sub-folders as well as populating certain
folders with project related resources.
This directory structure is the foundation of a project lifecycle that includes electronic plan
review, bidding, inspection, machine control and maintenance. Following this standard directory
structure without revision will ensure the accurate sharing of information between ITD and
consultants and contractors.
Quantity Manager
ITD uses InRoads’ Quantity Manager to compute and harvest quantities from InRoads features
and tagged MicroStation elements. Quantity Manager uses that data to create a report that is used
to populate the fields in the project Roadway Summary sheet. This summary sheet is an Excel
spreadsheet and contains all instructions and macros required to produce the Roadway Summary
Sheet. Quantity Manager also creates a .pdf file containing pay item information for the sidebar
summary and a .csv file to import the pay item information into Estimator and TrnsPort. The
Quantity Manager Configuration file, qm.cfg, must be copied from the
ITD_Workspace\CFG_Files folder to the C:\Program Files\Bentley\InRoads Group
v8.9\QM\classes folder on each user’s workstation.
Page 2 of 2
ITD Project Directory Structure (Expanded) (4_2011)
Documentation (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Exhibits Information such as photos and data for public exhibits
Photographs Digital photos, prints and videos
GIS (Dx GIS) All files and documentation related to GIS
Maintenance (Dx Maint Prj)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Photographs Digital photos, prints and videos
Plan Review (Domain Users)
Final All files needed for Final Plan Reviews (PDF, Design Files & Documents)
Intermediate All files needed for Intermediate Plan Reviews (PDF, Design Files & Documents)
Preliminary All files needed for Preliminary Plan Reviews (PDF, Design Files & Documents)
PS&E All files needed for PS&E Plan Reviews (PDF, Design Files & Documents)
Plan Submittal (Domain Users) All files needed for Plan Submittals (PDF, Design Files & Documents)
PlotTemp (Domain Users) IPARM files and metafiles from Iplot
Project_Development
Civil_Data (Dx Civil) (Dx Design) (Dx Loc) Civil data files (InRoads System Files)
Quantities Quantity Manager Quantities
District_Bridge_Data (Dx Design) District Bridge model files (Design Files)
Correspondence (Dx RW Prj) (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Photographs Digital photos, prints and videos
Erosion and Sediment Control (Dx Design) Erosion and Sediment Control Plans
Existing (Dx Design) (Dx Loc) All existing data including data collected from field surveys, aerial or satellite surveys, scanned-in drawings,
existing utilities, existing right of way information, existing signaling information, etc.
Hydraulics (Dx Hydro) (Dx Design) Hydraulic model files (Design Files)
Hydraulic_Studies Signed ITD-210 Reports and all Hydraulic Reports
Correspondence (Dx Admin Prj) Any letters, e-mails and memorandums concerning Hydraulic issues
Documentation (Dx RW Prj) Hydrographic and hydraulics calculations,computer runs,charts, graphs,permits,maps and etc.
Photographs Digital photos, prints and videos at hydraulic sites
Intelligent_Transportation_Systems (HQ Traffic Prj)
Closed_Circuit_Television
Communication
Dynamic_Message_Signs
Highway_Advisory_Radio
Misc_ITS_Data
Landscape (Dx Landscape) (Dx Design) Landscape model files (Design Files)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx RW Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Photographs Digital photos, prints and videos
Location (Dx Loc) Location section model files (Design Files)
Civil_Data Civil data files ie InRoads system files and GPS files
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx RW Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Photographs Digital photos, prints and videos
Materials (Dx Mtls Prj) Materials source plats (Design Files)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Phase_Reports Materials Phase Report files and documentation
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
District_Review District adds comments prior to HQ review
Final Final copy of each phase report with draft watermark removed
HQ_ Review (ITD\Mtls Phase Reports Change) HQ Materials can add comments; copy of HQ Mtls' review memo
Joint_Comments Copy with Dist & HQ comments; District reconciles & sends to consultant
Under_Revision ITD developed projects or Consultant's original submittals
Minor_Structures (Dx Str) (Dx Design) Minor structure model files (Design Files)
Analysis All calculations,computer runs,charts, graphs,permits,maps and etc.
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Photographs Digital photos, prints and videos
Quantities Minor structures quantity calculations and documentation
Specifications Minor structure related special provisions
Plan_Sheets (Dx Design) Project construction design drawings (Design Files)
Project_Resources (Dx Resource) (Dx Design) (Dx Loc) MicroStation support files that are specific to the project
InRoads
MicroStation
Miscellaneous
Right_of_Way (Dx RW) Right-of-way model files (Design Files)
Correspondence (Dx RW Prj) (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx RW Prj) (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Exhibits (Dx RW Prj) Information such as photos and data for court exhibits
Parcels (Dx RW Prj) Add subdirectories as needed for parcels
Parcel_1–name All files and documents related to Parcel No. 1
Parcel_2–name All files and documents related to Parcel No. 2
Negotiations All Owner contact and negotiations done by Right of Way (Right of Way only)
Photographs (Dx RW Prj) Digital photos, prints and videos
Quantities (Dx RW Prj) Right-of-way quantity calculations, including documentation for Payments in Lieu of Construction
Roadway (Dx Design) Main design model, typical sections, profiles, cross section and contour files (Design Files)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Photographs Digital photos, prints and videos
Traffic (Dx Traffic Prj) Traffic related model files (Design Files)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
HQ_Review (HQ Traffic Prj)
Signal_Cabinets (HQ Traffic Prj)
Photographs Digital photos, prints and videos
Utilities (Dx Utility) (Dx Design) Utility model files (Design Files)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Photographs Digital photos, prints and videos
Project_Management (Dx Proj Mgmt) (Dx Design)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Estimating_Data All calculations,computer runs and data used to create the estimate
Professional_Agreement Consultant Agreement documents
Proposals Working and final design proposals
Scope Project description and scope
Scheduling Project and construction schedule
Public_Involvement (Dx Public Involve) (Dx Design)
Correspondence (Dx Admin Prj) Any letters, e-mails (in RTF format) and memorandums
Documentation (Dx Admin Prj) All calculations,computer runs,charts, graphs,permits,maps and etc.
Exhibits Information such as photos and data for public exhibits
Public_Comments Informal and formal public comments
Visualization (Dx Visual) (Dx Design) All files and supporting resources for visualization projects
APPENDIX C
Design File Types and Standard Naming Convention
Four primary design file types have been adopted with the new CADD standard naming
convention.
1. Border Files
Border files are MicroStation design files that contain a border template and annotation
that is common to all pages within the plan set. This border file is referenced to the sheet
files. Border files are stored with a .BDR file extension and are copied into the project
“prj#####\Project_Development\Project_Resources” directory when the Project Creation
Utility is run.
2. Sheet Files
Sheet files are MicroStation design files that contain annotation and graphics that are
specific to one page in a plan set. Model files and border files are referenced to the sheet
file to create a plan set drawing ready for plotting. Sheet files are created by the designer
or by the InRoads “Plan and Profile Generator” and are stored in the project
“prj#####\Project_Development\Plan_Sheets” directory with a .SHT file extension.
Sheet files will be named using a project key number prefix, four-letter sheet designator
code, a three-digit sheet number and an alpha character used only if the sheet is being
inserted into an existing plan set. The three primary components will be separated by
underscores in the file name, as shown below:
12345_desn_001a.sht
Alpha Character for Inserted Drawings
Sheet Number
Sheet Designator
Key Number
There will be slight differences in the naming convention for Bridge files.
12345_brvi_001a.dgn
* The spaces in the naming convention for the Bridge sheets indicate where a two-
character code will be inserted to denote the location of the bridge in the roadway project.
3. Model Files
Model files are MicroStation design files that contain design graphics representing
existing or proposed features and conditions of the project. These files are referenced to
the sheet files. Models could be referenced to a single sheet file multiple times, or may be
referenced to multiple sheet files. Model files are created by the designer and stored in
the appropriate section or discipline’s directory in the “prj#####”\Project_Development
directory with the standard MicroStation .DGN file extension.
Page 2 of 8
The naming conventions that are presented below are intended for model design files.
Names will include a project key number prefix, a file type designator code, three-digit
sequence number, and alpha character used only for design files that are inserted into the
sheet sequence at a later time. The three primary components of the name will be
separated by underscores when the design file is created, as shown in the example below:
12345_desn_001a.dgn
Alpha Character for Inserted Drawings
Sequence Number
File Type Designator
Key Number
For Bridge model design files, the “br” drawing type designation will be used to
indicate that the file contains bridge structure information, followed by a name code for
the street, river, or other feature for which the bridge is being generated, as illustrated in
the example below:
12345_brvi_001a.dgn
* The spaces in the naming convention for the Bridge sheets indicate where a two-
character code will be inserted to denote the location of the bridge in the roadway project.
Five primary InRoads file types have been adopted with the new CADD standard naming
convention.
Page 4 of 8
This working file may contain many horizontal alignments and working variations of the
project geometry. The alignment description should include the date, the route number
and a brief explanation of the purpose. For example:
Horizontal alignments are generally used to represent geometry of the centerline of both
existing and proposed routes. Horizontal alignment will be named using the route
number or name. For example:
US-20
Route Number
When alternate horizontal geometry alignments become necessary during the course of a
roadway project, their names will consist of the name of the route, an underscore
character, the letters “alt” to designate that the file contains alternate geometry and a
sequencing number:
US-20_alt1
Sequence Number
Alternate
Route Number
For final horizontal alignments simply add the word “final” to the name to indicate that
the horizontal alignment represents the final vertical geometry as shown below:
US-20_final
Final Horizontal Alignment
Vertical alignments are children of the horizontal alignment. Each parent alignment may
have several “children” and their names only need to designate the difference between
versions or revisions. Vertical alignments will be named “alt” with a sequencing number
to designate different alternates as shown below:
alt1
Vertical Alignment with Sequencing Number
For final vertical alignments simply use the word “final” in the name to indicate that the
vertical alignment represents the final vertical geometry as shown below:
final
Final Vertical Alignment
Alignments for streets or cross streets will include the street name. Alternate alignments
for streets will include the “_alt” designation and final alignments for streets will include
“_final” in their names as shown below:
Page 5 of 8
broadway.alg
Street Name
broadway_alt1.alg
Sequence Number
Alternate
Key Number
broadway_final.alg
Final Alignment Designator
Street Name
Alignments for ramps will include the name of the street to which the ramp will connect,
an underscore, and a two-letter code representing the terminal points of the ramp.
Alternate alignments for ramps will include a “ _alt” designation and final alignments for
streets will include “_final” in their names as shown below:
broadway_ab.alg
Ramp Code
Street Name
broadway_ab_alt1.alg
Alternate
Ramp Code
Street Name
broadway_ab_final.alg
Final Alignment Designator
Ramp Code
Street Name
3. Surface files
Original ground surface names will include the project key number, the descriptive name
“orig” to indicate that the surface represents original ground and a 3 digit number to
indicate the surface sequence. Original ground surface files will be stored in the
prj12345\Project_Development\Location directory.
12345_orig_001.dtm
Sequence Number
Original Ground Designator
Key Number
The description will include the date, the route number and a brief description of the
surface, as shown below:
Page 6 of 8
The surface files that are created during the design process will also use this convention
with a descriptive name indicating the design layer the surface represents and a 3 digit
number to indicate the surface sequence. These files will be stored in the
prj12345\Project_Development\Civil_Data directory.
12345_subgrade_001.dtm
Sequence Number
Surface Layer Descriptive Name
Key Number
The surface description will include the date, the route number and a brief explanation of
the surface, as shown in the example below.
4. Template Libraries
Template library names will use the project key number and will be stored in the
prj12345\Project_Development\Civil_Data directory. If alternate template libraries are
created, the names will consist of the project key number, an underscore character, the
letters “alt” to designate that the file contains alternate templates and a sequencing
number. The final template libraries will include “_final” in their names as shown below:
12345.tml
Key Number
12345_alt1.tml
Sequence Number
Alternate
Key Number
12345_final.tml
Final Template Library Designator
Key Number
The template library description will include the date, the route number and a brief
explanation of the purpose of the template library. For example:
Template names will include descriptive information, such as the route number, the
number of lanes that the template will model and a sequencing number to differentiate
between multiple templates. For example, a two-lane template for a section of highway
on Idaho State Highway 21 could be named as follows:
SH-21_2ln_001
Sequence Number
Two-Lane
Route Number
Page 7 of 8
The template description will include the date, route number, short indication of the
template’s purpose and the station range in which the template will be used, as shown in
the example below:
5. Corridor Definitions
Corridors Libraries will be named using the route number, as shown below, and stored in
the prj12345\Project_Development\Civil_Data directory. If alternate Corridor Libraries
are created, the names will consist of the letters “alt”, to designate that the file contains
alternate corridors, and a sequencing number. The final corridor definition will include
“_final” in their names as shown below:
SH-24_001.ird
Sequencing Number
Route Number
SH-24_alt1.ird
Sequence Number
Alternate
Route Number
SH-24_final.ird
Final Corridor Designator
Route Number
The corridor library description will include the date, the route number and a brief
explanation of the corridor. For example:
Corridor names for the roadway project will include the route number, an underscore
character and a sequencing number. For example, a roadway definition for a section of
highway on State Highway 24 will be named as follows:
SH-24_01
Sequencing Number
Route Number
The Corridor description will include the date, route, street or location and station range
of the corridor being modeled. For example:
Page 8 of 8
APPENDIX D - LEVEL ASSIGNMENTS
ALIGNMENT
BRIDGE
CONSTRUCTION
DESIGN
ENVIRONMENTAL
GENERAL
BORDER
GIS
HYDROLOGY
LANDSCAPE
MATERIALS
RIGHT OF WAY
STANDARD DRAWING
MINOR STRUCTURES
SURVEY
TOPOGRAPHY
TRAFFIC
UTILITIES
VISUALIZATION
APPENDIX E
PLANS EXAMPLES
The Example ITD plans are in the process of being updated to the new CADD Standards
and Symbology and will be available with a future release of this manual.
APPENDIX F - LINESTYLES, CELLS, NAMED LEVELS AND BY-LEVEL
SYMBOLOGY
S–1–A-1_ TOPO_SURVEY
S–1–A-2_ TOPO_SURVEY
S–1–A-3_ TOPO_SURVEY
S–1–A-4_ TOPO_SURVEY
S–1–A-5_ TOPO_SURVEY
S–1–B-1_ ALG_BORDER_GEN
S–1–B-2_ ALG_BORDER_GEN
S–1–B-3_ ALG_BORDER_GEN
S–1–B-4_ ALG_BORDER_GEN
S–1–B-5_ ALG_BORDER_GEN
S–1–C-1_ BRDG_HYDR_STRUC
S–1–C-2_ BRDG_HYDR_STRUC
S–1–D-1_ DESIGN_ROW
S–1–D-2_ DESIGN_ROW
S–1–E-1_ TRAFFIC_UTIL_ENV_Etc
S–1–E-2_ TRAFFIC_UTIL_ENV_Etc
Feature Table Report
Alpha
Feature Description Code Point Type Style
SURV_MON_Rebar-Six-Found BARC Random - Do Not Triangulate SURV_MON_Rebar-Six-Found
SURV_MON_Spike-Set RRSPIKE Random - Do Not Triangulate SURV_MON_Spike-Set
SPKS
Survey Monument Bench Mark BM Random - Do Not Triangulate SURV_MON_Bench-Mark
BMRK
Survey Monument Cap Alloy Found ALCAP Random - Do Not Triangulate SURV_MON_Cap-Alloy-Found
ALCAPF
Survey Monument Cap Alloy Set ALCAPS Random - Do Not Triangulate SURV_MON_Cap-Alloy-Set
Survey Monument Cap Brass Found BCF Random - Do Not Triangulate SURV_MON_Cap-Brass-Found
BRCAP
BRCAPF
Survey Monument Cap Brass Set BCS Random - Do Not Triangulate SURV_MON_Cap-Brass-Set
BRCAPS
Survey Monument Cap Plastic Found PLCAP Random - Do Not Triangulate SURV_MON_Cap-Plastic-Found
Survey Monument Concrete Found CMONF Random - Do Not Triangulate SURV_MON_Concrete-Found
Survey Monument Control Traverse TRAV Random - Do Not Triangulate SURV_MON_Control-Traverse
TRV
Survey Monument GPS Control Point Found GPS Random - Do Not Triangulate SURV_MON_GPS-Con-Pt-Found
GPSF
GPSX
Survey Monument GPS Control Point Set GPSP Random - Do Not Triangulate SURV_MON_GPS-Con-Pt-Set
GPSS
Survey Monument Iron Pipe Found IRPIPEF Random - Do Not Triangulate SURV_MON_Pipe-Iron-Found
Survey Monument Iron Pipe Set IRPIPES Random - Do Not Triangulate SURV_MON_Pipe-Iron-Set
Survey Monument Miscellaneous CHK Random - Do Not Triangulate SURV_MON_Misc
CKPNT
HBTK
IP
IRPIN
MISCPNT
MSCMT
Survey Monument PK Found PK Random - Do Not Triangulate SURV_MON_PK-Found
PKF
Survey Monument PK Set PKS Random - Do Not Triangulate SURV_MON_PK-Set
Survey Monument Point of Curvature PCPNT Random - Do Not Triangulate SURV_MON_PC
Survey Monument Point of Intersection PI Random - Do Not Triangulate SURV_MON_PI
PIPNT
Survey Monument Point of Tangency PTPNT Random - Do Not Triangulate SURV_MON_PT
Survey Monument Property Line Existing LINEPL Breakline - Do Not Triangulate SURV_MON_Property-Line-Ex
LINESPL
Survey Monument Railroad Right-of-Way Line Existing RRRW Breakline - Do Not Triangulate SURV_MON_RR-ROW-Line-Ex
Survey Monument Rebar Number Five Found BARB Random - Do Not Triangulate SURV_MON_Rebar-Five-Found
BARBF
BARFFV
Survey Monument Rebar Number Five Set BARSFV Random - Do Not Triangulate SURV_MON_Rebar-Five-Set
Survey Monument Rebar Number Four Found BARA Random - Do Not Triangulate SURV_MON_Rebar-Four-Found
BARAF
BARFHF
Survey Monument Rebar Number Four Set BARSHF Random - Do Not Triangulate SURV_MON_Rebar-Four-Set
Survey Monument Right-of-Way Line Existing RW Breakline - Do Not Triangulate SURV_MON_ROW-Line-Ex
Survey Monument Right-of-Way Line Existing with RWF Breakline - Do Not Triangulate SURV_MON_ROW-Line-Ex-With-Fnc
Fence
Survey Monument Right-of-Way Marker Found RWM Random - Do Not Triangulate SURV_MON_ROW-Found
Survey Monument Section Corner SCRN Random - Do Not Triangulate SURV_MON_Section-Corner
Survey Monument Section Line SECLINE Breakline - Do Not Triangulate SURV_MON_Section-Line
Survey Monument Section Quarter Corner SCRNQ Random - Do Not Triangulate SURV_MON_Section-Qtr-Corner
Survey Monument Section Quarter Line QTRLINE Breakline - Do Not Triangulate SURV_MON_Section-Qtr-Line
Survey Monument Section Sixteenth Corner SCRNSIX Random - Do Not Triangulate SURV_MON_Section-Six-Corner
Survey Monument Section Sixteenth Line LINESIX Breakline - Do Not Triangulate SURV_MON_Section-Six-Line
Survey Monument Spike Found SPIKE Random - Do Not Triangulate SURV_MON_Spike-Found
SPKF
Survey Monument Stone Found STONE Random - Do Not Triangulate SURV_MON_Stone-Found
STONEF
Survey Monument Survey Line Township Range TRLINE Breakline - Do Not Triangulate SURV_MON_Survey-Line-Twnshp-Rng
Survey Monument Survey Marker Miscellaneous MARKER Random - Do Not Triangulate SURV_MON_Survey-Marker-Misc
FENCHN
Topo Fence Combination Wire CMBOFEN Random TOPO_FENCE_Combination-Wire
Topo Fence Corner FCOR Random TOPO_FENCE_Corner
Topo Fence Electric ELECFEN Random TOPO_FENCE_Electric
FENE
Topo Fence Gate FGATE Random TOPO_FENCE_Gate
GATE
GT
Topo Fence Line FEN Breakline TOPO_FENCE_Line
FLINE
Topo Fence Other FENCE Random TOPO_FENCE_Other
FENM
FNC
Topo Fence Silt SILTFEN Breakline TOPO_FENCE_Silt
Topo Fence Snow FNSNOW Random TOPO_FENCE_Snow
SNFNC
SNOWFEN
Topo Fence Wood FENW Random TOPO_FENCE_Wood
WOODFEN
Topo Gas Air Vent GVENT Random - Do Not Triangulate TOPO_GAS_Air-Vent
Topo Gas Line GLINE Breakline - Do Not Triangulate TOPO_GAS_Line
Topo Gas Line High Pressure GLINEHP Breakline - Do Not Triangulate TOPO_GAS_Line-High-Pressure
Topo Gas Line Marker GMARK Random TOPO_GAS_Line-Marker
Topo Gas Meter GMTR Random - Do Not Triangulate TOPO_GAS_Meter
Topo Gas Miscellaneous GMISC Random TOPO_GAS_Misc
Topo Gas Propane Tank GPROTK Breakline - Do Not Triangulate TOPO_GAS_Propane-Tank
GPRPANE
PTANK
Topo Gas Riser GRSR Random - Do Not Triangulate TOPO_GAS_Riser
Topo Gas Valve GVLV Random - Do Not Triangulate TOPO_GAS_Valve
Topo Geology Test Hole BH Random - Do Not Triangulate TOPO_GEOLOGY_Test-Hole
DH
TH
TSTHL
Topo Guardrail Cable GRCABLE Random TOPO_GRDRAIL_Cable
Topo Guardrail Concrete CRAIL Random TOPO_GRDRAIL_Concrete
GRAILC
Topo Guardrail End Anchor GRANCH Random TOPO_GRDRAIL_End-Anchor`
Topo Guardrail Metal GRAILM Random TOPO_GRDRAIL_Metal
GRAILW
GRDRL
MRAIL
WBEAM
Topo Guardrail Post GRPOST Random TOPO_GRDRAIL_Guard-Post
Topo Landscape Bush BUSH Random TOPO_LNDSCP_Bush
Topo Landscape Bush Boundary BRSHL Random TOPO_LNDSCP_Bush-Boundary
BUSHB
Topo Landscape Coniferous Tree CTREE Random - Do Not Triangulate TOPO_LNDSCP_Coniferous-Tree
TREEC
Topo Landscape Cultivation Boundary AGR Breakline TOPO_LNDSCP_Cultiv-Boundary
CULTB
FIELD
LAWN
LNDSCP
Topo Landscape Deciduous Tree DTREE Random - Do Not Triangulate TOPO_LNDSCP_Deciduous-Tree
TREED
Topo Landscape Embankment Protector EMBNK Random TOPO_LNDSCP_Embank-Protector
Topo Landscape Miscellaneous LNDSCPMS Random TOPO_LNDSCP_Misc
C
Topo Landscape Stump STUMP Random - Do Not Triangulate TOPO_LNDSCP_Stump
Topo Landscape Tree TREE Random - Do Not Triangulate TOPO_LNDSCP_Tree
Topo Landscape Tree Boundary TREEB Random TOPO_LNDSCP_Tree-Boundary
Topo Lighting Luminaire Pole LMNR Random - Do Not Triangulate TOPO_LIGHTING_Luminaire-Pole
LPOLE
Topo Lighting Other LIGHTNG Random - Do Not Triangulate TOPO_LIGHTING_Light-Other
Topo Miscellaneous Above Grou;nd Fuel Tank FTANKAG Breakline - Do Not Triangulate TOPO_MISC_Above-Grnd-Fuel-Tank
Topo Miscellaneous Bollard BOLLARD Random TOPO_MISC_Bollard
Topo Miscellaneous Feature Line ML Random TOPO_MISC_Feature-Line
Topo Miscellaneous Flag Pole FLAG Random - Do Not Triangulate TOPO_MISC_Flag-Pole
Topo Miscellaneous flat Asphalt PADA Breakline TOPO_MISC_Flat-Asphalt
Topo Miscellaneous Flat Concrete CON Breakline TOPO_MISC_Flat-Concrete
PADC
Topo Miscellaneous Gas Pump FUELP Breakline TOPO_MISC_Gas-Pump
GASPMP
GPMP
Topo Miscellaneous Item MISC Random - Do Not Triangulate TOPO_MISC_Item
Topo Miscellaneous Mailbox MBOX Random TOPO_MISC_Mailbox
Topo Miscellaneous Manhole Type Unknown MHMISC Random - Do Not Triangulate TOPO_MISC_Manhole-Type-Unknown
Topo Miscellaneous Underground Fuel Tank FTANK Random - Do Not Triangulate TOPO_MISC_Underground-Fuel-Tank
FTANKUG
TANK
Topo Oil Line OLINE Breakline - Do Not Triangulate TOPO_OIL_Line
Topo Oil Line Marker OMARK Random TOPO_OIL_Line-Marker
Topo Oil Meter OMTR Random - Do Not Triangulate TOPO_OIL_Meter
Topo Oil Miscellaneous OMISC Random - Do Not Triangulate TOPO_OIL_Misc
Topo Oil Riser ORSR Random - Do Not Triangulate TOPO_OIL_Riser
Topo Oil Valve OVLV Random - Do Not Triangulate TOPO_OIL_Valve
Topo Railroad Bridge RRBRDG Breakline TOPO_RROAD_Bridge
Topo Railroad Protective Device RRDEV Random - Do Not Triangulate TOPO_RROAD_Protective-Device
Topo Railroad Signal RRLIT Random - Do Not Triangulate TOPO_RROAD_Signal
RRSINGL
Topo Railroad Signal Cabinet RRCAB Breakline - Do Not Triangulate TOPO_RROAD_Signal-Cabinet
SRCAB
Topo Railroad Switch RRSW Random - Do Not Triangulate TOPO_RROAD_Switch
Topo Railroad Top of Rail RR Breakline - Do Not Triangulate TOPO_RROAD_Top-of-Rail
RRA
RRB
TOPRAIL
Topo Railroad Track Centerline RRCL Breakline TOPO_RROAD_Centerline-Track
Topo Roadway Approach Paved Rural APPR Breakline TOPO_RDWY_Approach-Paved-Rural
APPRPR
Topo Roadway Approach Unpaved Rural APPRU Breakline TOPO_RDWY_Approach-Unpvd-Rural
BRDGRL
Topo Structure Bridge Timber Rail BRDGRAILT Breakline - Do Not Triangulate TOPO_STRUCT_Bridge-Rail-Timber