CADD Engineering Standards - Ohio Department of Transportation

Ohio Department of Transportation 

CADD Engineering Standards 

1/18/2013

This page intentionally left blank.

Table of Contents 

January 18, 2013 

100 GENERAL .............................................................................................................................................. 1 

101 Introduction (Draft) ................................................................................................................. 1 

102 Distribution .............................................................................................................................. 1 

103 Revisions and Updates .......................................................................................................... 2 

104 Trademarks (Draft) .................................................................................................................. 2 

200 CADD STANDARDS ............................................................................................................................. 3 

201 Installation and Configuration ............................................................................................... 3 

201.1 General ..................................................................................................................... 3 

201.2 Installation ................................................................................................................. 3 

201.3 CADD Standards Directory ....................................................................................... 3 

201.4 Configuration Variables and Files ............................................................................. 4 

202 Level Assignments ................................................................................................................. 5 

202.1 General ..................................................................................................................... 5 

202.2 Level Naming Convention ......................................................................................... 6 

202.3 ByLevel Considerations ............................................................................................ 7 

202.4 Filters ........................................................................................................................ 8 

202.5 Priority and Transparency ....................................................................................... 11 

203 Colors ..................................................................................................................................... 18 

203.1 General ................................................................................................................... 18 

204 Line Styles ............................................................................................................................. 18 

204.1 General ................................................................................................................... 18 

204.2 Types of Line Styles ................................................................................................ 19 

204.3 Line Style Scales .................................................................................................... 20 

204.4 Plotting .................................................................................................................... 29 

205 Line Weights .......................................................................................................................... 30 

205.1 General ................................................................................................................... 30 

205.2 Plotting .................................................................................................................... 30 

206 Cell Libraries ......................................................................................................................... 30 

206.1 General ................................................................................................................... 30 

206.2 Cell Types ............................................................................................................... 30 

206.3 Cell Libraries ........................................................................................................... 31 

206.4 Cell Placement ........................................................................................................ 31 

207 Fonts ...................................................................................................................................... 42 

207.1 General ................................................................................................................... 42 

207.2 Text Size ................................................................................................................. 43 

207.3 Text Line Spacing ................................................................................................... 43 

207.4 Text Styles .............................................................................................................. 44 

207.5 Dimension Styles .................................................................................................... 47 

208 Seed Files .............................................................................................................................. 49 

208.1 General ................................................................................................................... 49 

208.2 Models ..................................................................................................................... 49 

ODOT CADD Engineering Standards i


209 GEOPAK Design and Computation Manager Database .................................................... 50 

209.1 General ................................................................................................................... 50 

210 GEOPAK Survey Manager Database................................................................................... 50 

210.1 General ................................................................................................................... 50 

210.2 Survey Field Codes ................................................................................................. 50 

210.3 Survey Manager Database ..................................................................................... 50 

211 Working Units ........................................................................................................................ 51 

211.1 General ................................................................................................................... 51 

212 Global Origin ......................................................................................................................... 51 

212.1 General ................................................................................................................... 51 

213 Custom Applications ............................................................................................................ 52 

213.1 General ................................................................................................................... 52 

214 GEOPAK Criteria Files .......................................................................................................... 53 

214.1 General ................................................................................................................... 53 

214.2 Cross Section Criteria Files .................................................................................... 53 

214.3 3 PC Criteria Files ................................................................................................... 54 

214.4 Cross Section Input Files ........................................................................................ 54 

300 FILE MANAGEMENT .......................................................................................................................... 55 

301 General ................................................................................................................................... 55 

301.1 General ................................................................................................................... 55 

302 Project Directory Structure .................................................................................................. 55 

302.1 Standard Directory Structure .................................................................................. 55 

303 References ............................................................................................................................. 63 

303.1 General ................................................................................................................... 63 

303.2 Models ..................................................................................................................... 63 

303.2.1 Types of Models ...................................................................................... 65 

303.2.2 Model Names .......................................................................................... 66 

303.2.3 Model Properties ..................................................................................... 67 

303.2.4 Referencing Models ................................................................................ 69 

303.3 Basemap Design Files ............................................................................................ 69 

303.4 Sheet Design Files .................................................................................................. 70 

304 File Naming Conventions ..................................................................................................... 72 

304.1 General ................................................................................................................... 72 

304.2 File Extensions ........................................................................................................ 72 

304.3 File Name Format ................................................................................................... 73 

304.4 Supplemental Description Guidelines ..................................................................... 74 

304.5 Assigning Supplemental Descriptions .................................................................... 75 

304.6 Viewing Supplemental Descriptions ....................................................................... 76 

305 GEOPAK Digital Terrain Models .......................................................................................... 82 

305.1 General ................................................................................................................... 82 

306 GEOPAK Coordinate Geometry Databases ....................................................................... 82 

306.1 General ................................................................................................................... 82 

306.2 GEOPAK COGO Element Names .......................................................................... 83 

ii ODOT CADD Engineering Standards


307 GEOPAK Project Manager ................................................................................................... 86 

307.1 General ................................................................................................................... 86 

307.2 Setting up a Project for GEOPAK Road ................................................................. 86 

307.3 Setting up a Project for GEOPAK Survey ............................................................... 88 

400 PLOTTING ........................................................................................................................................... 89 

401 General ................................................................................................................................... 89 

401.1 General ................................................................................................................... 89 

401.2 Plotting .................................................................................................................... 90 

401.2.1 Priority ..................................................................................................... 90 

401.2.2 Transparency .......................................................................................... 90 

401.2.3 Shading ................................................................................................... 91 

401.2.4 Masking ................................................................................................... 91 

401.2.5 Issues with Pen Tables encountered with V8i plotting: .......................... 91 

500 ELECTRONIC SUBMISSIONS ........................................................................................................... 92 

501 Information Exchange and Electronic Submissions ......................................................... 92 

501.1 General ................................................................................................................... 92 

502 File Format ............................................................................................................................. 92 

502.1 General ................................................................................................................... 92 

502.2 Saved View ............................................................................................................. 93 

503 Project Index File .................................................................................................................. 94 

503.1 General ................................................................................................................... 94 

504 CADD File Requirements for Design and Construction .................................................... 95 

504.1 General ................................................................................................................... 95 

504.2 Horizontal Alignment ASCII Reports ....................................................................... 95 

504.3 Vertical Alignment ASCII Reports ........................................................................... 99 

504.4 LandXML Reports for Horizontal and Vertical Alignments ................................... 101 

504.5 LandXML Reports for Triangle Models ................................................................. 103 

504.6 Monumentation Reports ........................................................................................ 104 

504.7 Cross Section Staking Reports ............................................................................. 107 

504.8 Submission of Electronic Files to Central Office ................................................... 110 

APPENDIX A – CADD Information Table ……………………………………..………………………….1-108 

APPENDIX B – Fonts ……………………………………………………………………….…………….....1-2 

APPENDIX C – Line Styles ………..…………………………………………………….………………….1-9 

APPENDIX C – Cells ………………..…………………………………………………….………………….1-180 

APPENDIX D – Cell Origins …………………………………………………………………………………1-36 

APPENDIX E – Electronic Submission Checklist ………………………………….……………………1-2 

APPENDIX F – Level Scale Factors ………………………………….………………………………..…..1 

ODOT CADD Engineering Standards iii


This page intentionally left blank. 

iv ODOT CADD Engineering Standards

100 GENERAL 

101 Introduction 


Computer-Aided Drafting and Design (CADD) is the preferred method of preparing plans for the Ohio 

Department of Transportation (ODOT). The requirements presented in this manual ensure that CADD 

files can be used by the entire project team (surveyors, planners, environmentalists, designers, reviewers, 

contractors, etc.) throughout all phases of project development. 

ODOT has adopted MicroStation and GEOPAK as its standard drafting and design software packages, 

respectively. The standards referenced in this manual have been developed and tested using the 

software versions listed on the following Web page: 

http://www.dot.state.oh.us/Divisions/Engineering/CADDMapping/CADD/Pages/Support.aspx 

Note: All references to V8i are for the V8i SELECTseries 2 version of MicroStation and GEOPAK. 

ODOT will accept electronic and printed deliverables generated from Autodesk tools. 

ODOT will provide no support, standards, documentation, or guidance of any kind with respect to design 

and delivery using Autodesk tools. All CADD related documentation, training, supporting files, and 

customization provided by ODOT shall be MicroStation/GEOPAK based only. 

The design software to be used on a project shall be mutually agreed upon by the district and consultant, 

and shall be explicitly stated in the project’s scope. Once the decision has been made to use either 

MicroStation/GEOPAK or Autodesk, there shall be no deviation from the agreed upon design package, 

and the same one shall be used until the project’s completion. 

ODOT will continue to operate internally using MicroStation and GEOPAK only. 

The final deliverables of an Autodesk designed project in printed or electronic format shall mimic that of a 

project designed and delivered using MicroStation/GEOPAK. The electronic deliverables for projects 

designed using Autodesk tools shall be delivered in the native Autodesk format, and not converted to 

MicroStation/GEOPAK format. 

This manual supersedes all CADD standards previously published in the Bridge Design Manual, the 

Right-of-Way Manual, and the Location and Design Manual, Volume 3. 

This manual is not a textbook and does not exempt the professional from performing responsible 

engineering and/or surveying. It is intended to provide uniform procedures and standards for 

organizations that perform CADD related services for ODOT. The professional shall have final 

responsibility for the accuracy of all input and output of computer-based applications. 

102 Distribution 

This manual, in its entirety, may be freely copied and distributed for the purpose of providing a consistent 

guide to the CADD requirements of the Ohio Department of Transportation. The manual, Standard 

CADD files and other support files can be downloaded from the ODOT CADD Standards website at the 

following address: 

http://www.dot.state.oh.us/Divisions/Engineering/CADDMapping/CADD/Pages/CADDManual.aspx 

ODOT CADD Engineering Standards 1


For ODOT CADD Users, MicroStation and GEOPAK V8i standard CADD files are located on each District 

and Central Office CADD Server under the ODOTstd\V8istd directory. 

103 Revisions and Updates 

The Office of CADD and Mapping Services, CADD Section, with input from ODOT’s District Offices and 

the consultant and construction community, will develop, and maintain procedures and standards for the 

Department’s CADD related activities. CADD Manual holders are encouraged to submit comments and 

suggestions for improvements to the manual or ODOT’s CADD Standards. Any errors found should be 

brought to the attention of the ODOT Office of CADD and Mapping Services via the following website: 

http://www.dot.state.oh.us/Divisions/Engineering/CADDMapping/CADD/Pages/suggestions.aspx 

The Ohio Department of Transportation strives to stay current with state of the art trends in the market. 

However, impacts on project delivery schedules and the resources necessary to provide future support 

for new features must be considered prior to any change. 

Updating this manual is intended to be a continuous process and revisions will be issued periodically per 

the release dates stated on the Design Reference Resource Center (DRRC) web page at the following 

address: 

http://www.dot.state.oh.us/drrc/Pages/default.aspx 

The DRRC web page also provides the option to subscribe to an email list for notification of updates to 

ODOT’s Standard CADD Files. Once you have subscribed to the ODOT CADD Standards mailing list, it 

is your responsibility to notify ODOT of a change of email address by unsubscribing your old email 

address and re-subscribing using your new email address. See the DRRC web page for instructions on 

subscribing and unsubscribing. 

Revisions to the manual are noted in red text. 

104 Trademarks 

MicroStation is a registered trademark of Bentley Systems, Incorporated. GEOPAK is a registered 

trademark of GEOPAK Corporation, now a wholly owned subsidiary of Bentley Systems, Incorporated. © 

2012 Bentley Systems, Incorporated. 

Autodesk is a registered trademark of Autodesk, Incorporated. 

Other trade names, computer protocols, and file formats mentioned in this manual are the trademarks of 

their respective owners. In no event will the appearance of any graphic, description of any graphic, 

picture, screen display, or any other method of conveying meaning be considered to impair the rights of 

the respective owners. 

2 ODOT CADD Engineering Standards

200 CADD STANDARDS 

201 Installation and Configuration 

201.1 General 


This section outlines the setup for a typical installation of MicroStation V8i at ODOT. The configuration 

files discussed in this section are available from the ODOT CADD Standards website. 

201.2 Installation 

For a typical installation of MicroStation V8i SELECTseries 2 at ODOT see the document 

ODOT_Config.pdf. This document outlines the setup for a typical installation of MicroStation V8i 

SELECTseries 2. 

The ODOT_Config.pdf file is located in the ODOT\V8istd\config\doc directory or the file can be 

downloaded from the ODOT CADD Standards website. 

Note: The department has recently migrated to a Windows 7, 64-bit Operating System environment. 

The directory paths for Windows XP and Windows 7 are different. The paths for both Operating 

Systems are contained in the ODOT_Config.pdf. In the future only the Windows 7 directories may be 

provided. 

201.3 CADD Standards Directory 

The configuration and associated files for MicroStation and GEOPAK that are used for plan development 

at ODOT are typically stored in a directory tree with the root of the tree named “ODOTstd”. This directory 

structure is set to i:\ODOTstd for a typical ODOT installation, where “i” is a network drive mapped to the 

primary CADD file server. 

Configuration files and the associated CADD standards for specific versions of MicroStation are stored in 

separate folders beneath the ODOTstd folder as shown below: 

• Projects 

The Projects directory contains the various project configuration files (.pcf) which are read from 

this directory. 

• V7std 

The V7std directory contains all the CADD Standards for MicroStation and GEOPAK v7. 

• V8istd 

The V8istd directory contains all the CADD Standards for MicroStation and GEOPAK V8i. 



201.4 Configuration Variables and Files 

ODOT uses four (4) environment variables, ODOTSTD, V8iSTD, HOMEV8i, and V8iGSTD, to locate files 

necessary for the operation of MicroStation V8i in a typical ODOT setup. 

1. The ODOTSTD variable is used to define the location of the root ODOT CADD standards folder. 

This variable is assigned a value in V8iODOTstandards.cfg. 

2. The V8iSTD variable is used to define the location of the MicroStation V8i CADD standards. This 

variable is assigned a value in V8iODOTstandards.cfg. 

3. The HOMEV8i variable is defined in the V8iODOTstandards.cfg file to specify the location of the 

MicroStation User Configuration Files (UCF) and User Preference Files (UPF). The HOMEV8i 

variable is defined as a Windows System Environment Variable and set to w:\V8iUser\ for a 

typical ODOT setup, where w:\ is connected to a share on a file server. 

4. The V8iGSTD variable is used to define the location of site specific settings. The primary use of 

this variable is to identify the location of Bentley InterPlot (IPLOT) settings files. For a typical 

ODOT setup, this variable is defined in ODOTV8i.ucf file as follows: V8iGSTD: i:\V8igstd. 

The following ODOT standard configuration files for MicroStation V8i are typically used for plan 

development. A brief description of each file is included below. 

V8iODOTstandards.cfg 

This CFG file is used to set the location of the Project Configuration Files (PCF), User 

Configuration Files (UCF), and User Preference Files (UPF). See the document 

ODOT_Config.pdf for the file location. 

dfltuser.cfg 

This file tells MicroStation what UCF file to use on initial startup. 

ODOTV8i.pcf 

This PCF file is the Project Configuration File used to set the configuration variables for ODOT’s 

MicroStation V8i CADD standards stored in the ODOTstd\Projects folder. 

ODOTV8i.ucf 

This UCF file is the seed User Configuration File for MicroStation V8i. This file is used to define 

any user specific configuration variables for MicroStation V8i. This file should be copied to the 

location defined by the Variable HOMEV8i. 

ODOTV8iSeed.upf 

This UPF file is the default seed User Preference File that contains the settings defined in the 

MicroStation Preferences dialog. 

For further details on the setup and use of these configuration files, see MicroStation Configuration Files 

download page on the ODOT CADD Standards website. 


Alternate Configuration Files 

There are alternate configuration files available to ODOT users as described below: 


• ODOTV7.ucf & ODOTV7.pcf 

These configuration files are used to open design files in MicroStation/J (v7) format. This 

configuration is intended to be used for viewing, plotting, and making minor edits to old design 

files in v7 format. Access to GEOPAK has been disabled in this configuration. 

• ODOTV8_JUL07.ucf & ODOTV8_JUL07.pcf 

These configuration files are used when viewing or editing MicroStation V8 design files developed 

using the Bridge custom line styles with the ODOT CADD Standards that were in place on or 

before July 20, 2007. 

In order to use one of the alternate ODOT configurations, the .ucf file must be copied to the directory 

specified by the variable HOMEV8i. 

202 Level Assignments 

202.1 General 

To maintain uniformity among different drawing files, it is essential that an organized leveling system be 

used. MicroStation permits data to be organized in any fashion on an unlimited number of drawing levels. 

ODOT has developed a standard set of levels to be used with all design files submitted to or exchanged 

with the Department. 

ODOT’s standard levels are defined in a MicroStation DGN Library, ODOT_Levels.dgnlib, which can be 

obtained from the ODOT CADD Standards website. The DGN library is attached by use of the 

MicroStation configuration variable MS_DGNLIBLIST. 

Users shall not create their own levels for use in any design files submitted or exchanged with ODOT. 

See the CADD Information Table, Appendix A, for a complete list of the ODOT levels. 



202.2 Level Naming Convention 

ODOT level names use the following naming convention: 

Classification_Disposition_Logical Name 

The Classification consists of two (2) uppercase characters used to group the levels into categories. 

The Classification names are listed in the table below: 

Classification Description 

AP Airports 

BD Buildings 

BR Bridge 

CM Corridor Modeler 

DR Drainage 

DT Digital Terrain Models 

DV Divisions 

EV Environmental 

GE Geometry 

GK GEOPAK 

GM Geomedia (County Maps) 

GT Geotechnical 

HY Hydraulics 

LT Lighting 

MT Maintenance of Traffic 

PF Profiles 

PM Pavement Marking 

PV Pavement 

RC Recreational 

RD Roadway 

RS Raster Files 

RW Right-of-Way 

SC Scratch 

SG Signals 

SH Sheets 

SN Signs 

ST Standard Construction Drawings & Plan Insert Sheets 

SV Survey 

TR Truck Turning Paths 

TX Text 

UT Utilities 

VG Vegetation 

XS Cross Sections 

The Disposition is used to identify the level for placement of either X (existing) or P (proposed) 

information. 

The Logical Name is used as a description of the element contents. Where appropriate, common 

industry abbreviations are used. 

All ODOT levels names use alphanumeric characters only. No spaces or special characters are used 

other than the underscore “_” character. 


202.3 ByLevel Considerations 


In general, to facilitate use of MicroStation’s ByLevel attributes, the ODOT levels have been established 

such that each curvilinear feature will have its own level. In order to keep the overall number of levels 

manageable, there are cases where similar features will be placed on the same level making it impossible 

to use ByLevel attributes for those features. Some exceptions are noted below: 

• Standard ODOT cells are placed on the level in which they were created. Each cell is not placed 

on its own level, rather, like cells are grouped on one level. For example, existing electric utility 

cells are all placed on the level UT_X_Electric_Cells. 

• Storm Sewer Lines – Each proposed storm sewer line 12” and above will be placed using the 

custom line style stormline, which shall be scaled, based on the pipe size. All proposed storm 

sewer lines will be placed on the level DR_P_Storm_Sewer. 

• Culvert Lines – Each proposed culvert line will be placed using a custom line style based on the 

culvert size. All proposed culvert lines will be placed on the level DR_P_Culvert. 

• Maintenance of Traffic Drums – Multiple line styles have been created to represent various typical 

drum spacing’s. These lines are placed on level MT_P_Drums. 

• Centerline Pavement Marking – Multiple line styles and colors are available representing various 

centerline pavement markings. These lines are placed on level PM_P_CL (proposed) or 

PM_X_CL (existing). 

As a general rule, curvilinear design file elements should be placed using ByLevel attributes except in the 

cases noted in the CADD Information Table Appendix A. 



202.4 Filters 

ODOT’s level library, ODOT_Levels.dgnlib, has been configured with a set of default level filters that can 

be used to control the display of levels based on their attributes. Users may add new filters as deemed 

necessary to facilitate project development. Users shall not edit or delete the default filters. 

The filters included in ODOT_Levels.dgnlib are listed in the table below: 

Filter Value Result 

Aerial Mapping 

Spatial Features 

Topo Features 

Airport AP* 

Bridge BR* 

BD_X_Building|"BR_X_SV_Abut"|"BR_X_S 

V_Deck_Top"|DR_X_Culvert|DR_X_Headw 

all|DT_X_Break_Line|DT_X_TIN_Hull|DT_X 

_Void|HY_X_Water_Edge|HY_X_Wetland_ 

Area|PV_X_Bikeway|PV_X_Curb|PV_X_Dri 

veway|PV_X_EOP|PV_X_Field_Drive|"PV_ 

X_Shoulder"|PV_X_Walk|RD_X_Concrete_ 

Barrier|RD_X_Fence|RD_X_Gate|RD_X_G 

R_Lt|RD_X_GR_Rt|RD_X_Misc_Items|RD_ 

X_Noise_Wall|RD_X_RR_2|RD_X_Wall|VG 

_X_Tree_line_Lt|VG_X_Tree_Line_Rt 

BD_X_Building|DT_X_Break_Line|DT_X_TI 

N_Hull|DT_X_Void|HY_X_Water_Edge|PV_ 

X_Curb|PV_X_Driveway|PV_X_EOP|PV_X 

_Shoulder|RD_X_RR_2 

BR_X_SV_Abut|BR_X_SV_Deck_Top|DR_ 

X_Culvert|DR_X_Headwall|HY_X_Wetland 

_Area|PV_X_Bikeway|PV_X_Field_Drive|P 

V_X_Walk|RD_X_Concrete_Barrier|RD_X_ 

Fence|RD_X_Gate|RD_X_GR_Lt|RD_X_G 

R_Rt|RD_X_Misc_Items|RD_X_Noise_Wall 

|RD_X_Wall|VG_X_Tree_Line_Lt|VG_X_Tr 

ee_Line_Rt 

Bridge Beam Beam – SV|BR_*_Gen_Text 

Bridge Bearing Brg - SV|BR_*_Gen_Text 

Bridge Details 

Det – [Beam|Brg|Dia|Rail| 

Prestress|Slab] |BR_*_Gen_Text 

Bridge Diaphragm Dia - SV|BR_*_Gen_Text 

Bridge Drainage Drain|BR_*_Gen_Text 

Displays all levels that are used by Aerial 

digital mapping. 

Displays levels containing the Spatial 

features used by Aerial digital mapping. 

Displays levels containing the Topo 

Features used by Aerial digital mapping. 

Displays levels starting with the characters 

“AP”. 


“BR”. 

Displays bridge levels containing “Beam” 

except for levels containing “SV” and 

contains the levels for the Bridge Generic 

Text. 

Displays bridge levels containing “Brg” 



Text. 

Displays bridge levels containing “Det” 

except for levels containing “Beam”, “Brg”, 

“Dia”, “Rail”, “Prestress” or “Slab” and 


Text. 

Displays bridge levels containing “Dia” 



Text. 

Displays bridge levels containing “Drain” 

and contains the levels for the Bridge 

Generic Text. 


Bridge General Gen - SV 

Bridge Prestress Prestress|BR_*_Gen_Text 

Bridge Railing Rail - SV|BR_*_Gen_Text 

Bridge Slab 

Bridge 

Sub_Deep_Foundatio 

n 

Slab - [Gen|SV]| 

BR_*_Gen_Text 

Deep - SV|BR_*_Gen_Text 

Bridge Sub_Footing Foot - SV|BR_*_Gen_Text 

Bridge Substructure 

Sub - [Foot|Deep|SV]| 

BR_*_Gen_Text 


Displays bridge levels containing “Gen” 

except for levels containing “SV”. 

Displays bridge levels containing 

“Prestress” and contains the levels for the 

Bridge Generic Text. 

Displays bridge levels containing “Rail” 



Text. 

Displays bridge levels containing “Slab” 

except for levels containing “Gen” or “SV” 

and contains the levels for the Bridge 

Generic Text. 

Displays bridge levels containing “Deep” 

except for levels containing “SV” 

Displays bridge levels containing “Foot” 



ODOT CADD Engineering Standards 9 

Text. 

Displays bridge levels containing “Sub” 

except for levels containing “Foot” or “Deep” 

or “SV” and contains the levels for the 

Bridge Generic Text. 

Bridge Survey _X_SV Displays bridge levels containing “_X_SV”. 

Buildings BD* 


“BD”. 

Corridor Modeler CM* 


“CM”. 

Cross Sections XS* 


“XS”. 

Divisions DV* 


“DV”. 

Drainage DR* 


“DR”. 

DTM DT* 


“DT”. 

Environmental EV* 


“EV”. 

Existing Levels _X_|GT_Historic 

Displays all existing levels containing “X” 

and “GT_Historic”. 

Geometry GE* 


“GE”. 

GEOPAK GK* 


“GK”. 

Geotechnical GT* 


“GT”. 

Hydraulics HY* 


“HY”. 

Lighting LT* 


“LT”. 

MOT MT* 


“MT”. 

Pavement PV* 


“RV”. 

Pavement Marking PM* 


“PM”.


Profile PF* 


“PF”. 

Proposed Levels _P_|GT_Instrumented|GT_Project 

Displays all proposed levels containing “P”, 

“GT_Instrumented” and “GT_Project”. 

Raster RS* 


“RS”. 

Recreational RC* 


“RC”. 

Right-of-Way RW* 


“RW”. 

Roadway RD* 


“RD”. 

Scratch SC* 


“SC”. 

Sheets SH* 


“SH”. 

Signals SG* 


“SG”. 

Signing SN* 


“SN”. 

Std_Constr_Plan_Ins 

ert_Shts 

ST* 


“ST”. 

Survey SV* 


“SV”. 

Text (Generic) TX*|*Text 


“TX” and the levels containing “Text”. 

Truck Paths TR* 


“TR”. 

Used * Displays levels that are currently in use. 

Utilities UT* 


“UT”. 

Vegetation VG* 


“VG”. 


202.5 Priority and Transparency 


The levels defined in the MicroStation DGN Library, ODOT_Levels.dgnlib, utilize the Element Priority 

and Transparency features. The Priority and some Transparency settings have been incorporated in 

ODOT CADD Standards to facilitate the on-screen viewing of the plan features. See the CADD 

Information Table Appendix A, for a complete list of Priority and Transparency values. 

Priority 

• Priority 

Elements, levels, and references can be assigned a Priority value. Elements with a higher priority 

will display on top of elements with a lower value. 

• Transparency 

Dialog boxes, as well as elements, levels, and references can be set with a transparency value. 

Transparent elements allow you to see other graphic elements that are “underneath” a 

transparent element. 

Display priority is a technique for specifying the relative front-to-back order in which 2D elements appear 

in a 2D model (only) when they are displayed in a view. Display priority is only useful or necessary for 2D 

models, since all elements in 3D models have their own explicit 3D coordinate space. In 3D models, 

elements closer to the eye are always drawn in front of elements further from the eye so display priority is 

not necessary. 

The elements with the highest priority values are displayed in front, while the elements with the lowest 

priority values are displayed in the back. Values for Element and Level priority may range from -500 to 

500. 

By default, MicroStation displays the elements on your screen in the order in which they were drawn. If 

you're using reference files, the active file will display first followed by the reference files in the order of 

attachment. And finally, if you're using raster reference files, the order is: the raster images first, then the 

active file elements, followed by the vector reference files. 

Note: Levels for Raster Reference files have been created. The Raster Reference files have 

been assigned a low priority value so they will always be displayed behind any existing and 

proposed features and references. 



Display priority is not supported in editions prior to MicroStation XM. Files created using display priority 

will appear “unsorted” when displayed in previous editions of MicroStation V8, or when saved to DGN V7. 

In 2D models, you can assign display priority values to references, levels, and to individual elements. 

The hierarchy for display priority is reference: level: element. That is: 

• All elements in a reference with a higher reference display priority will appear in front of all 

elements from references with a lower value. 

• Within a single model, or from references with the same reference display priority, elements on 

levels with higher level display priority will appear in front of those with a lower value. 

• Where elements have the same reference and level display priority, the element display priority 

determines those that will appear in front of others. 

• Where two elements have the same reference, level, and element display priorities, the one that 

appears later in the display order (that is, file position and update sequence) appears on top. 

Levels are the main priority differentiator on top of which the individual elements of a particular level can 

be tweaked relative to each other. Priority values have been assigned for each level in the ODOT level 

library as shown below. 

• Levels for Existing plan features have been assigned a priority value of -100. 

• Levels for Proposed plan features have been assigned a priority value of 100. 

• Levels for Existing and Proposed Text have been assigned a priority value of 500. 

• The level SH_Major_Grid_Line has been assigned a priority value of -480. 

• The level SH_Minor_Grid_Line has been assigned a priority value of -490. 

• Levels used for GEOPAK specific features have been assigned various priority values to facilitate 

better on-screen viewing of the graphics. 

• Levels configured for Raster Reference files have been assigned a priority value of -500. 

With these priority assignments, proposed plan view features will always display on top of existing plan 

view features regardless of the order in which the elements are drawn. 



You do not need to assign a priority value to the elements as they are placed in the design file. The 

elements will be displayed according to the priority value that is assigned to the level. 

Note: The Active Element Priority value is not a ByLevel setting. When the Active Level is 

changed on the Attributes tool bar, the value of the Active Element Priority is not set to match 

the value assigned to the level. 

In the case where two elements are placed on different levels that have the same priority setting, the last 

element drawn is displayed on top. This can be changed by assigning a priority value to the element. 

Priority values can be assigned when the element is initially placed, or assigned later with the Change 

Element Attributes tool. 

The priority value assigned to an element is not an “override” of the level setting. The priority value 

assigned to an individual element is “relative” to the level setting. Behind the scenes, MicroStation uses 

an equation (See BE Communites for further details) to determine the “final” priority value of the element. 

However, most users will be content to know that modifying the priority assigned to an individual element 

up or down by increments of one (1) will allow them to modify the display priority as needed. 

It should be noted that the priority value of an element that is reported in the Element Info dialog is the 

actual value assigned to the element, not the calculated value. 

The priority of an element can be modified using the Change Element Attributes tool. 



Priority can also be assigned to Reference files. By default, where a reference is attached it is assigned a 

value of 0 as shown below. 

Values for priority assigned to a reference file can range from -5 to 5. 

The hierarchy for display priority is reference: level: element. Therefore, when an element is drawn over 

referenced graphics, the reference file will take priority over elements placed in the master design file on 

a level that has the same priority value. 

All of the graphics representing existing features, which are in a reference file, are displayed on top of the 

shape drawn on the existing building level as shown below. 


Transparency 


Transparency can be set for elements, levels, and references. Transparency may vary from 0% to 100%. 

A value of 0 indicates no transparency at all, while a value of 100% indicates almost complete 

transparency. 

Transparency can be assigned to elements when they are placed by selecting a value from the Attributes 

tool bar. 

Note: The Active Element Transparency value is not a ByLevel setting. When the Active Level 

is changed on the Attributes tool bar, the value of the Active Element Transparency is not set to 

match the value assigned to the level. 



The Change Element Attributes dialog can be used to set the Transparency values for previously 

placed elements. 

Just like Priority, when new elements are drawn they take on the Transparency value assigned to the 

level. Setting the Active Element Transparency in the Attributes tool box is not an “override”. Behind the 

scenes, MicroStation uses an equation (See BE Communites for further details) to determine the “final” 

transparency value of the element. 



The Transparency value reported in the Element Information dialog box represents the value assigned to 

the element and not the “final” transparency value as calculated by MicroStation. 

Note: When opening an existing MicroStation V8 design file in XM or V8i, the priority and 

transparency values will not be in effect unless an “Update Levels from Library” command is 

issued. 



203 Colors 

203.1 General 

Standard colors are specified to ensure consistency and to enable users to easily identify plan elements 

in shared files. 

Each element in a MicroStation design file is assigned a color number. MicroStation reads a color table 

to determine the correct color to display for the specified number. Standard color numbers for plan 

graphics are specified in the CADD Information Table, Appendix A. 

The ODOT standard color table, ODOT_color.ctb, can be obtained from the ODOT CADD Standards 

website. The MicroStation configuration variable MS_DEFCTBL is used to specify the ODOT color table. 

The color values may vary or appear different on screen due to the graphics cards, monitors display 

capability, etc. 

204 Line Styles 

204.1 General 

Line styles are used to differentiate curvilinear elements in the design file and on the plotted sheet. There 

are eight default line styles available in MicroStation using the values zero (0) through seven (7). 

Additionally, ODOT has developed a set of Custom Line Styles to be used for drawing various plan view 

graphic items requiring custom symbology. Custom Line Styles are created as Cosmetic or Physical line 

types. For detailed information see Section 204.2 Types of Line Styles. 

The ODOT standard line style resource file, ODOT_Linestyles.rsc, can be obtained from the ODOT 

CADD Standards website. The MicroStation configuration variable MS_SYMBRSC is used to specify the 

custom line style resource file. 

Users shall not create their own custom line styles for use on ODOT plan sheets. 

Standard line codes and custom line styles for plan graphics are specified in the CADD Information Table, 

Appendix A and displayed in Appendix D. 


204.2 Types of Line Styles 

ODOT CADD Standards contain two (2) types of custom line style definitions: 


1. “Cosmetic” line styles 

Cosmetic line styles are used to represent the location of an item, but not the actual size or 

spacing of the item. A fence line, shown below, is an example of a cosmetic custom line style. 

• The location of the symbols along the custom line style does not represent the actual 

location of fence posts, and are intended only to designate the line as a fence line. 

• Cosmetic line styles are typically placed in the design file at a scale of one (1) and then 

displayed using the Global Line Style Scale or Annotation Scale factors in the design file at 

a scale corresponding to the intended plotting scale of the final plans. 

2. “Physical” line styles 

Physical line styles are used to represent the location of an item, and the linear spacing of the 

components of the item. A pavement marking lane line, shown below, which consists of 

alternating 10’ dashes and 30’ gaps, is an example of a physical custom line style. 

• Physical line styles are always placed in the design file at a scale of 1, regardless of the 

plotting scale. 

• Physical line styles are designated as such that the Global Line Style Scale and Annotation 

Scale factors when applied are ignored. 

Cosmetic and Physical line styles for plan graphics are specified in the CADD Information Table, 

Appendix A and displayed in Appendix D. 



204.3 Line Style Scales 

During the development of a set of plans, it is common to reference the same basemap design file into 

different detail sheet files that may be plotted at different scales. The location and dimensions of all plan 

view basemap design file information shall be drawn in the default “Design” model using real world 

dimensions at a 1:1 scale. Custom Line Styles are to be placed in the basemap at a scale of one (1) so 

the Model Properties “Line Style Scale” feature can be used. 

The Model Properties Line Style Scale feature can be used to control the display size of line styles in 

the active design file, and in any Reference attachments. This will allow the designer to control the 

display size of the line styles for any intended plotting scale. 

All custom Line Styles should be placed at a scale of one (1) and then scaled using the Model 

Properties Line Style Scale feature. 



The following details the recommendations for Scaling Custom Line Styles when drafting and designing 

ODOT plans using the features available in MicroStation V8i. The final decision regarding plan drafting 

and design is at the discretion of the designer. 

Recommendations for Scaling Custom Line Styles on ODOT plans: 

When attaching the basemaps as References into the “Sheet” model, set the Model Properties Line Style 

Scale for the appropriate sheet scale. Changing the Model Properties Line Style Scale value will cause 

the display of the line styles to change according to the value selected. This will affect line styles drawn 

in the active file, as well as referenced graphics, depending on the settings when the references were 

attached. 

Basemap: 

Manual Placement (Existing and Proposed): 

Place all Line Styles in the basemap design file at a scale of one (1.0). 



When working in the basemap, use the following steps to set the Line Style Scale: 

In the Model Properties dialog box, set the Line Style Scale using one of the following two (2) 

methods: 

1. From the Line Style Scale drop-down menu, select Annotation Scale to set the line style 

scale factor to match the Model Annotation Scale. 

Note: This is the recommended procedure for all Roadway Design files. 

2. From the Line Style Scale drop-down menu, select Global Line Style Scale to set the line 

style scale factor to a value different than the Model Annotation Scale. 


GEOPAK Placement (Existing and Proposed): 


The GEOPAK Design and Computation Manager dialog box can be used to place line styles in the 

basemap using the default Design mode. 

The Design mode is used to plot COGO elements into MicroStation, with the desired symbology, by 

use of the Draw Plan and Profile dialog box. It can also be used to set drafting standards used in 

conjunction with MicroStation’s element placement commands, with the Place Influence option 

toggled on, as shown below: 

When using the Design mode the following procedure is used to place Line Styles in the basemap: 

Before you begin placing MicroStation elements in Design Mode, it is good practice to check the 

Design Settings to ensure that the Custom Line Style Creation’s Scale Factor value is set 

properly. 

From the Design and Computation Manager dialog 

box, select Settings > Design to access the Design 

Settings dialog box shown at right. 



The following options related to Line Style placement are available from or when using the Design 

Settings dialog box: 

Custom Line Style Creation 

The default custom line style Scale Factor to be 

used when drawing MicroStation elements is 

specified here. For ODOT plans, this value should 

be set to one (1.0) as shown right, to allow the Model 

Annotation Scale to control the custom line style 

scale. 

The Annotation Scale is set as follows for Custom Line Styles: 

• Select the Models dialog box. 

• From the Models dialog box, select Edit Model Properties to access the Model 

Properties dialog box as shown below. 

• From the Line Style Scale drop-down menu, set the Line Style Scale as desired. 

In the example shown right, the 

Annotation Scale is set to a value 

of Engr 1:20. The Line Style 

Scale value is set to match the 

Annotation Scale. 


Survey Processing (Existing Basemap): 


The GEOPAK Project Preferences dialog box is used to control how the line styles in the basemap will 

be drawn. To use the Model Properties “Line Style Scale” feature, the field data must be visualized at 

a scale of one (1.0) as shown below: 

The Plot Scale feature is used to control the size of the custom line styles used in the mapping of the 

survey data. The base scale is defined for each feature code in the SMD file. The Plot Scale should 

normally be set to a value of one (1.0) for all ODOT projects. 

Note: For more detailed information on processing the survey data into MicroStation see the 

ODOT GEOPAK V8i Survey Training Guide and the ODOT GEOPAK V8i Road 1 Training Guide. 



Sheet Files: 

In the “Sheet” model, set the Model Properties Line Style Scale for the appropriate sheet scale. 

In the Model Properties dialog box, set the Line Style Scale using one of the following two (2) 

methods: 

1. From the Line Style Scale drop-down menu, select Annotation Scale to set the line style 

scale factor of the lines styles to match the Model Annotation Scale. 

Note: This is the recommended procedure for all Roadway Design files. 

2. From the Line Style Scale drop-down menu, select Global Line Style Scale to set the line 

style scale factor to a value different than the Model Annotation Scale. 



When attaching References in the “Sheet” model, set the Global LineStyle Scale to Master in the 

Reference Attachment Settings dialog box. This will allow the master file to control the scaling of line 

styles in the active file and all reference attachments. 



Important Notes when Referencing: 

• Be aware that if the Line Styles were placed in the basemap using a Scale factor other 

than a Scale of 1. The referenced line styles are scaled by the Model Properties Line 

Style Scale set in the new design file and will appear out of scale. 

• If the survey data was mapped (visualized) in the basemap for a specific scale, such as 

20, set the option “Global Line Style Scale” to Reference in the Reference 

Attachment Settings dialog box to match the Annotation Scale value set in the original 

reference file. 

• If the Model Annotation Scale is already set in the design file and the Model Annotation 

Scale is set in the Reference at 1:1, the Detail Scale in the Reference Attachment 

Settings dialog box displays the Model Annotation Scale and the Scale (Master:Ref) 

displays a 1:1 scale like shown below: 

• Be aware if the Model Annotation Scale is already set in the design file and the Model 

Annotation Scale is set in the Reference other than 1:1, the Detail Scale in the 

Reference Attachment Settings dialog box displays the Reference’s Model Annotation 

Scale and the Scale (Master:Ref) is then calculated from the referenced model's 

annotation scale and the active model's annotation scale. 

For example if the Reference file has a Model Annotation Scale set at 1:20 and the 

design file has a Model Annotation Scale set at 1:50 the Detail Scale displays the 

Reference’s Model Annotation Scale (1:20) and the Scale (Master:Ref) is calculated 

2.5:1 as shown below: 

To avoid the Reference from scaling in the design file like shown in the example 

above make sure the Scale (Master:Ref) is set to 1:1. If the Scale (Master:Ref) is not 

set at 1:1 you will need to change it. Once you have set the Scale to 1:1 the Detail 

Scale will then read the design file’s Model Annotation Scale that was set like shown 

below: 


Bridge Design Files: 


Multiple custom line styles for centerlines have been designated for specific plotting scales (10 scale, 20 

scale, 50 scale, etc). Separate levels have been established for the representation of these centerlines. 

These line styles and levels are specified in the CADD Information Table, Appendix A. 

Several line styles have been developed specifically for use on Bridge plans that are not always placed at 

a specific scale relative to the plotting scale. See Appendix F for suggested Scale factors. The line 

styles listed in the table below shall be scaled as necessary to produce a legible detail. These line styles 

are assigned to the appropriate level by use of ByLevel attributes. 

204.4 Plotting 

Line Style Name Description 

brcllong Centerline Long 

brclshort Centerline Short 

brconstjoint Construction Joint 

brexisting Existing Objects 

brhiddenex Hidden Line Existing 

brhiddenpr Hidden Line Proposed 

brphasepr Phase Construction Line 

brbarex Existing Reinforcement Bars 

brbarpr Proposed Reinforcement Bars 

The dash and gap lengths of the MicroStation default line codes 0-7 are defined by the plotting software. 

See Section 400 for the ODOT plotting values for line codes 0-7. 



205 Line Weights 

205.1 General 

Line weights are used to differentiate graphical elements in the design file and on the plotted sheet. Line 

Weight width ranges from weight 0 (narrowest) to weight 31 (widest) and designate the thickness of the 

line used to draw or plot a graphic element. 

Standard line weights for plan graphics are specified in the CADD Information Table, Appendix A. 


See Section 400 Plotting for information on line weight plotting thickness values. 

206 Cell Libraries 

206.1 General 

A cell is a complex element composed of a group of primary elements or other complex elements. Cells 

are stored in a cell library. For plan consistency, it is advantageous to create cells for items that will be 

repeatedly placed in a design file. Several ODOT standard cell libraries are available as detailed in 

Section 206.3 Cell Libraries. 

206.2 Cell Types 

Most of the cells created in ODOT’s cell libraries have been created as graphic cells. The symbology 

(color, line style, line weight, and level) of a graphic cell is determined when it is created. When graphic 

cells are placed, they are level-independent, i.e., they do not rotate with the view and they keep the 

settings that were active when they were created. A few cells have been created as point cells where 

appropriate. A point cell takes on the active symbology set in the file at the time it is placed and are view 

independent, i.e., they rotate with the view. 

Several “Pattern and Terminator Type" symbols that were created as graphic type cells in the following 

cell libraries are now taking advantage of a new feature in MicroStation when placing them in the design 

file: 

ODOT_Geotech.cel 

ODOT_Geotech_1996.cel 

ODOT_Symbols.cel 

Graphic Cells can be produced on the “Default” Level using specific symbology, such as, color, line style, 

and line weight. A benefit to graphic cells being created on the “Default” level is the new symbols act 

similar to point cells when placed in the design file they inherit the Active Level, but not the symbology 

(color, line style, line weight). It is important to note, that the graphic cell does not inherit the Active 

Symbology (i.e. color, weight, line style) like a “Point Cell”, unless the graphic cell was drawn on the 

“Default” level with the attributes set to “ByLevel”. 


206.3 Cell Libraries 


The following Cell Libraries are available to facilitate the drawing of commonly used symbols and sheet 

borders as described below: 

Cell Library Description 

ODOT_Bridge.cel Commonly used cells for Bridge plans. 

ODOT_Drainage.cel Cells for standard drainage structures. 

ODOT_Geotech.cel Cells used for Geotechnical Information. 

ODOT_Geotech_1996.cel Cells used for the Specifications for Subsurface Investigation. 

ODOT_RW.cel Commonly used cells for Right-of-Way plans. 

ODOT_Sheets.cel Cells for standard plan sheet borders. 

ODOT_Symbols.cel Cells representing standard plan symbols. 

A set of cell libraries has been developed to include standard signs from the Office of Roadway 

Engineering, Sign Designs and Markings Manual. These sign cells are easily placed using a custom 

application, ODOT_Signs.mvba. A complete list of the sign cell libraries and instructions for running the 

signs application can be found on the ODOT CADD Standards website. 

The Cell libraries can be accessed from the ODOT CADD Standards website via the MicroStation 

Downloads web page. 

206.4 Cell Placement 

The ODOT cell libraries have been updated to utilize the new enhancement for Annotation Cells. Every 

cell can be placed as an Annotation Cell when the new feature “Can be placed as an annotation cell” is 

toggled on in the Model Properties dialog box. 



When you change the active model's Annotation Scale value, annotation cells in the model are 

automatically scaled by the new value. 

Annotation Scale - sets the scale for Text, Dimensions and Cells in the model. You can select from the 

list of common scales used for ODOT plan sheets. When placing Text, Dimensions or Cells, the 

Annotation Lock must be on to ensure that the text, dimensions and cells are placed at the defined scale. 


ODOT CADD Standards contain two (2) types of cell definitions: 


1. “Cosmetic” cells 

Cosmetic cells are used to represent the location of an object and are intended only to designate 

the location not the actual size or dimensions of the object. A Mail Box, shown below, is an 

example of a cosmetic cell. 

• Cosmetic cells are typically placed in the design file at a scale of one (1) and then displayed 

using the Annotation Scale factors in the design file at a scale corresponding to the intended 

plotting scale of the final plans. 

• The ability to place Cosmetic cells using the Annotation Scale Lock has been enabled in 

the cell definition by toggling on the Can be placed as annotation cell option. 

2. “Physical” cells 

Physical cells are used to represent the actual size or dimensions of an object. A Catch Basin, 

shown below, is an example of a physical cell. 

• Physical cells are always placed in the design file at a scale of 1, regardless of the plotting 

scale and are designated as such that the Annotation Scale factors when applied are 

ignored. 

• The ability to place Physical cells using the Annotation Scale Lock has been disabled in the 

cell definition. 

The Place Active Cell tool is used to place annotation cells. The 

tool's settings window has an Annotation Scale Lock icon similar 

to the one for the Place Text tool and dimensioning tools. When 

you set the Active Cell to a cell that can be placed as an 

annotation cell, the Annotation Scale icon should be enabled as 

shown right. 

The icon's tool tip tells you the active model's annotation scale 

factor and the off/on state of the Annotation Scale Lock. If this 

lock is on, the model's Annotation Scale factor will be applied to 

the cell you are placing. To turn on the Annotation Scale Lock, 

click the icon. 

Note: If the Annotation Scale lock is off when placing cells 

in the design file the Annotation Scale feature is ignored. 

Cosmetic and Physical cells for plan graphics are specified in the CADD Information Table, Appendix A 

and displayed in Appendix C along with the Cell Origins. 



Recommendations for Scaling Cells on ODOT plans: 

Basemap design files are used to draw existing and proposed plan view information for the entire length 

of the project for both Roadway and Bridge projects. All basemap information shall be drawn in the 

default Design model. The location and dimensions of all plan view basemap design file information shall 

be drawn using real world dimensions at a 1:1 scale. Cells are to be placed in the basemap at a scale of 

one (1), with the Place Active Cell’s Annotation Scale Lock toggled on so the Model Properties 

Annotation Scale feature can be used. 

When attaching the basemaps as References to the “Sheet” model, set the Model Properties 

Annotation Scale for the appropriate sheet scale. Changing the Model Properties Annotation Scale 

value will cause the display of the Cells to change according to the value selected. This will affect cells, 

text and dimensions drawn in the active file, as well as referenced graphics depending on the settings 

when the references were attached. 

All cells should be placed at a scale of one (1) with the Place Active Cell’s Annotation Scale Lock 

toggled on and then scaled using the Model Properties Annotation Scale as shown below. 



The following procedures listed are based on the expanded features available in MicroStation. The final 

decision regarding plan drafting and design is at the discretion of the designer. 

Basemap: 

Manual Placement (Existing and Proposed): 

Place all Cells in the basemap design file at a Scale of one (1.0) with the Place Active Cell 

Annotation Scale Lock toggled on. 

When working in the basemap, use the following procedure to set the Annotation Scale: 

In the Model Properties dialog box, set the Annotation Scale to the appropriate Engineering 

Scale desired. 



GEOPAK Placement (Existing and Proposed): 

The GEOPAK Design and Computation Manager dialog box can be used to place cells in the 

basemap using the default Design mode. 

The Design mode is used to plot COGO elements into MicroStation with the desired symbology by 

use of the Draw Plan and Profile dialog box. It can also be used to set drafting standards to be used 

in conjunction with MicroStation’s element placement commands, with the Place Influence option 

toggled on as shown below. 

When using the Design mode, the following procedure should be used to place Cells in the base 

map: 

Before you begin placing MicroStation elements in 

Design Mode, it is good practice to check the Design 

Settings to ensure that the Cell Creation’s Plot Scale 

value is set properly. 

From the Design and Computation Manager dialog 

box, select Settings > Design to access the Design 

Settings dialog box shown at right. 



The following options related to Cell placement are available from or when using the Design Settings 

dialog box: 

Cell Creation 

The default Plot Scale factor for placing cells is specified here. For ODOT plans, this value should 

be set to one (1.0) to allow the Model Annotation Scale to control the cell scale. 

Influence Graphic Cell Level Symbology 

When active, the Influence Graphic Cell Symbology uses the symbology within the Design and 

Computation Manager, ignoring the element symbology used when the cell was created. This option 

should always be toggled off for ODOT plans. 



The Annotation Scale is set as follows for Cells: 

• Select the Models dialog box. 

• From the Models dialog box, select Edit Model Properties to access the Model 

Properties dialog box as shown below. 

• Set the Annotation Scale as 

desired. 

In the example shown at right, the Annotation 

Scale is set to a value of Engr 1:20, with the 

Line Style Scale value set to match the 

Annotation Scale. 

Notes: 

• The method described above is a change in procedure from previous MicroStation 

releases. 

• The ODOT Design & Computation Manager Database for GEOPAK V8i has been 

specifically modified to accommodate placing cells using the Model Annotation Scale. 

Previous versions of ODOT.ddb will not allow the cells to be scaled using the Annotation 

Scale. 


Survey Processing (Existing Basemap): 


The GEOPAK Project Preferences dialog box is used to control how the Cells in the basemap will 

be drawn. To use the Model Properties “Annotation Scale” feature, the Cells must be visualized at 

a scale of one (1.0) as shown below: 

The Plot Scale item is used to control the size of the Cells, and Text used in the mapping of the 

survey data. The base scale is defined for each feature code in the SMD file. The Plot Scale should 

normally be set to a value of one 1.0 for all ODOT projects. 

Text and cells placed by GEOPAK Survey are not automatically scaled until the annotation scale is 

manually applied to the survey mapping. 

To apply the model annotation scale to the Cells and Text, type the command Annotationscale Add 

into the Key-in window inside MicroStation as shown below: 

This command will apply the annotation scale to all the cells and text in the model. The cells and text 

will now take on the active model annotation scale value. 

After the annotation scale has been applied to the cells and text in the file by use of the 

Annotationscale Add command, you do not need to run the key-in command again for the cells and 

text to honor changes to the model annotation scale. 



Sheet Files: 

Important Survey Processing Notes: 

• If additional survey data is mapped to the same design file, it will be necessary to run the 

key-in Annotationscale Add command again in order for the new data to honor the 

current annotation scale value. 

• The display of the text, cell, and line styles can be controlled uniquely for reference 

attachments. For example, the Survey Basemap file can be set with the model 

annotation scale value necessary for the Surveyor. Designers may reference the file and 

set the model annotation scale for a different value as needed for the plans without 

altering the survey basemap. 

• The Annotationscale Add command will optionally work with a MicroStation selection set. 

If no elements are selected when the command is processed, all cells and text in the 

active model will be processed. 

• Care must be taken to ensure that elements other than the survey information are not 

selected when the Annotationscale Add command is applied. For example, the text for 

centerline stationing and curve data that is placed by the GEOPAK Design and 

Computation Manager is placed for a specific plotting scale (this procedure will not 

change). If you apply the Annotationscale Add command to these elements, they will 

appear out of scale when the command is applied since they were not originally placed at 

a scale of one (1). 

In the “Sheet” model, set the Model Properties Annotation Scale for the appropriate sheet scale. 



Changing the Annotation Scale value will cause the display of the Text, Cells and Dimensions to change 

according to the value selected. This will affect elements drawn in the active file, as well as Referenced 

graphics, depending on the settings when the references were attached. 

Important Notes when Referencing: 

• Be aware that if the Cells were placed in the basemap using a Scale factor other than a 

Scale of 1, with the Cell Annotation Scale Lock on, the referenced cells will be scaled by 

the Model Annotation Scale set in the new dgn file and will appear out of scale. 

• If the Model Annotation Scale is already set in the design file and the Model Annotation 

Scale is set in the Reference at 1:1, the Detail Scale in the Reference Attachment 

Settings dialog box displays the Model Annotation Scale and the Scale (Master:Ref) 

displays a 1:1 scale like shown below: 

• Be aware if the Model Annotation Scale is already set in the design file and the Model 

Annotation Scale is set in the Reference other than 1:1, the Detail Scale in the 

Reference Attachment Settings dialog box displays the Reference’s Model Annotation 

Scale and the Scale (Master:Ref) is then calculated from the referenced model's 

annotation scale and the active model's annotation scale. 

For example if the Reference file has a Model Annotation Scale set at 1:20 and the 

design file has a Model Annotation Scale set at 1:50 the Detail Scale displays the 

Reference’s Model Annotation Scale (1:20) and the Scale (Master:Ref) is calculated 

2.5:1 as shown below: 

To avoid the Reference from scaling in the design file like shown in the example 

above make sure the Scale (Master:Ref) is set to 1:1. If the Scale (Master:Ref) is not 

set at 1:1 you will need to change it. Once you have set the Scale to 1:1 the Detail 

Scale will then read the design file’s Model Annotation Scale that was set like shown 

below: 



207 Fonts 

207.1 General 

ODOT has defined several standard fonts for use on all plans. It is important to use these fonts so that 

the final plotted version matches the electronic version of the file. Only the fonts provided by ODOT (30, 

31, 57, and 70) are acceptable for use on ODOT plans. True Type fonts shall not be used on ODOT 

Construction plans. 

The ODOT standard font resource file, ODOT_Fonts.rsc, can be obtained from the ODOT CADD 

Standards website. The MicroStation configuration variable MS_FONTPATH is used to specify the font 

library. 

The following fonts are available in the ODOT standard font resource file, ODOT_Fonts.rsc: 

Font 30 - Straight, proportional characters with uppercase, lowercase, and fractions. This font is 

for general plan use and has the modified keystrokes set. 

Font 31 - Slanted, proportional characters with uppercase, lowercase, and fractions. This font is 

for general plan use and has the modified keystrokes set. 

Font 57 – Straight, proportional characters with the Greek alphabet in upper and lowercase. 

Font 70 - Block filled. This font is used on plan sheets when a bold title is necessary. 

Modified keystrokes are used to generate certain symbols and special characters for Font 30 and Font 31 

as shown in Appendix B. Font 57 and Font 70 are also shown for reference. 

All text placed on Bridge sheets, excluding text contained in standard border cells, shall use Font 31. 

All text placed on Geotechnical Exploration sheets, excluding text contained in standard border cells, 

shall use Font 30 or Font 31. For purposes of this manual, the term “Geotechnical Exploration sheets” 

shall apply to all sheets generated per the Specifications for Subsurface Investigations (SSI) or the 

Specifications for Geotechnical Explorations (SGE). 


207.2 Text Size 


Standard text sizes have been defined to ensure uniform legibility of all plan sheets. Standard text size 

refers to the size of the text on the finished plot, not the text size in the design file. The correct design file 

text size is dependent upon the intended plot scale. ODOT standard text sizes for the finished plot scale 

are shown in the following table: 

Text Type Plotted Text Size 

Normal 0.14” 

Subtitle 0.17” 

Title 0.20” 

Main Title 0.25” 

To calculate text size used in a MicroStation design file for various scaled plan sheets use this method: 

(Text Size) x (Plotting Scale) = Design File Text Size 

Example: 0.14 inch x 20 feet/inch = 2.8 feet 

Text sizes smaller than the Normal text size are not acceptable. 

For all Roadway plan sheets and Geotechnical Exploration sheets, the preferred method to set the text 

size is by use of the Model Annotation Scale parameter. See section 207.4 Text Styles for more 

information. 

Text placed in the sheet model for bridge detail sheets should normally be placed at a scale of 1. For 

more information on the use of design models and sheet models, see section 303 References. 

207.3 Text Line Spacing 

In general, Text Line Spacing should be one-half (0.50”) the text height. The spacing between lines on 

summary, sub-summary, general note sheets and charts is generally equal to the minimum text size. 

Note: If needed it is permissible to use Text Line Spacing equal to the minimum text size. 

Text Line Spacing distances is now relative to the Text Height. In the previous versions of MicroStation 

these distances were an absolute value in master units. If the text height changed dramatically, the 

spacing could become inappropriate. Now, if the text height changes the spacing adjusts relative to the 

change in the text height. The Text Line Spacing is now a factor of the Text Height. 

For example with the scale factor set at 0.50” (one-half) the Line Spacing for ODOT’s Text Styles would 

be as follows: 

Normal Text Size 0.14” x Line Spacing 0.50” = a Line Spacing of 0.07” 

Sub-Title Text Size 0.17” x Line Spacing 0.50” = a Line Spacing of 0.085” 

Title Text Size 0.20” x Line Spacing 0.50” = a Line Spacing of 0.10” 

Main Title Text Size 0.25” x Line Spacing 0.50” = a Line Spacing of 0.125” 



207.4 Text Styles 

A MicroStation Text Style is a saved set of text parameters such as font type, text width, text height, color, 

etc. Text styles enable you to place text in a consistent and automated manner. ODOT’s standard text 

styles are defined in a MicroStation DGN Library, ODOT_Styles.dgnlib, which can be obtained from the 

ODOT CADD Standards website. This file is attached for use by the MicroStation configuration variable 

MS_DGNLIB. 

The following Text Styles have been configured for use on ODOT plans: 

Style Name *Text Size *Line Spacing Font 

Font 70-Main Title 0.25 0.50 70 

Font 70-Title 0.20 0.50 70 

Font 70-Sub Title 0.17 0.50 70 

Masked Slanted-Normal LS=0.50 0.14 0.50 31 

Masked Straight-Normal LS=0.50 0.14 0.50 30 

Slanted-Normal FX Spacing 0.14 0.50 31 

Slanted-Normal LS=0.50 0.14 0.50 31 



Slanted-Sub Title 0.17 0.50 31 

Slanted-Title 0.20 0.50 31 

Straight-Normal FX Spacing 0.14 0.50 30 

Straight-Normal LS=0.50 0.14 0.50 30 



Straight-Sub Title 0.17 0.50 30 

Straight-Title 0.20 0.50 30 

*Text size and Line Spacing units are “inches”. 

All text placed on Bridge sheets, excluding text contained in standard border cells, shall use the “Slanted” 

text styles. 

The active text style can be selected in MicroStation prior to 

placing text. Select the Place Text command to access the 

following dialog box shown at right. 



Selecting a Text Style will set the text size appropriate for a 1:1 plot. To place text for other plotting 

scales, users can automatically set the text size by setting the MicroStation Model Annotation Scale 

before placing the text. From the MicroStation pull-down menu, select File > Models or select the 

Models icon on the Primary Tools box, then select Edit Model Properties from the Models dialog box to 

access the dialog shown below. 

The list of available annotation scales is defined in the ODOT Standard file ODOT_scales.def which can 

be obtained from the ODOT CADD Standards Website. The MicroStation configuration variable 

MS_CUSTOMSCALEDEF is used to assign the scale definition file. 



The following annotation scales have been defined in ODOT_scales.def: 

Engineering Scales 

Architectural Scales 

Name Scale Name Scale 

Engr 1:1 1:1 Arch 12"=1'-0" 1:12 

Engr 1:2 2:1 Arch 6"=1'-0" 1:6 

Engr 1:3 3:1 Arch 3"=1'-0" 1:3 

Engr 1:4 4:1 Arch 1 1/2"=1'-0" 2:3 

Engr 1:5 5:1 Arch 1"=1'-0" 1:1 

Engr 1:6 6:1 Arch 3/4"=1'-0" 4:3 

Engr 1:8 8:1 Arch 1/2"=1'-0" 2:1 

Engr 1:10 10:1 Arch 3/8"=1'-0" 8:3 

Engr 1:20 20:1 Arch 1/4"=1'-0" 4:1 

Engr 1:25 25:1 Arch 3/16"=1'-0 16:3 

Engr 1:30 30:1 Arch 1/8"=1'-0" 8:1 

Engr 1:40 40:1 Arch 1/16"=1'-0" 16:1 

Engr 1:50 50:1 Arch 1/32"=1'-0" 32:1 

Engr 1:100 100:1 

Engr 1:200 200:1 

Engr 1:250 250:1 

Engr 1:400 400:1 

Engr 1:500 500:1 

Engr 1:1000 1000:1 

Engr 1:2000 2000:1 

Engr 1:5000 5000:1 

Engr 1:10,000 10,000:1 

Engr 1:25,000 25,000:1 

Engr 1:50,000 50,000:1 

Engr 1:100,000 100,000:1 

Engr 1:250,000 250,000:1 

Architectural scales are used for annotating bridge details when the text is placed in the design model 

instead of the sheet model. 

Engineering scales should be used for all Roadway sheets including the Bridge Site Plan sheet and 

Geotechnical Exploration sheets. 

See the Location and Design Manual, Volume 3 – Roadway Design, the Bridge Design Manual, and the 

Specifications for Geotechnical Explorations (SGE) for recommended sheet scales. 



In order to apply the annotation scale to a Text Style, you must toggle on the Annotation Scale Lock in 

the Place Text dialog box before placing the text. Select the Place Text command to access the dialog 

box shown below. 

In the example above, the ODOT, standard text style Slanted-Normal LS=0.50 has been selected with 

the Model annotation scale set to Engr 1:20. The text size and line spacing will be set as follows: 

Text Size: 0.14 inch x 20 feet/inch = 2.8 feet 

Line Spacing: 0.50 inch x 2.8 feet = 1.4 feet 

(Line Spacing is set to half the Text size) 

Text Styles do not set the Level or Weight for the text placement. The text will be placed on the active 

level with the active weight. All text placed using Text Styles established for Title and Sub-Title text 

should be placed at a weight of 2. 

207.5 Dimension Styles 

Similar to Text Styles, a MicroStation Dimension Style is a saved set of dimensioning parameters. ODOT 

has configured a set of dimension styles to be used on ODOT plans. These styles are defined in the 

ODOT Standard DGN Library, ODOT_Styles.dgnlib, which can be obtained from the ODOT CADD 

Standards website. This file is attached or used by the MicroStation configuration variable MS_DGNLIB. 



The following dimension styles have been defined in ODOT_Styles.dgnlib: 

Dimension Style Font *Text Size Description 

Dec-0, Slanted 31 0.14 Decimal Feet, No decimal places 

Dec-0, Straight 30 0.14 Decimal Feet, No decimal places 

Dec-1, Slanted 31 0.14 Decimal Feet, 1 decimal place 

Dec-1, Straight 30 0.14 Decimal Feet, 1 decimal place 

Dec-2, Slanted 31 0.14 Decimal Feet, 2 decimal places 

Dec-2, Straight 30 0.14 Decimal Feet, 2 decimal places 

Dec-Multiline, Slanted 31 0.14 Decimal Feet, 0.01 accuracy 

Dec-Multiline, Straight 30 0.14 Decimal Feet, 0.01 accuracy 

Fract-Multiline, Slanted 31 0.14 Fractions, 1/16” accuracy 

Fract, Slanted 31 0.14 Fractions, 1/16” accuracy 

Masked Fract, Slanted 31 0.14 Fractions, 1/16” accuracy 

Masked Fract-Multiline, Slanted 31 0.14 Fractions, 1/16” accuracy 

*Text size units are “inches”. 

Line Terminators shall be a filled arrow created with a width to height ratio of 2.5:1. The terminator width 

shall equal the text height. 

Leader Lines may be broken when crossing dimension lines. In order to keep broken lines to a minimum, 

it is recommended that the user relocate the dimension callout or reposition the dimension. Leader lines 

and terminators shall be a weight of zero (0) and shall be placed on the same level as required for text 

notes and callouts. 

Similar to Text Styles, the text size for Dimension Styles can be set by use of the Model Annotation Scale 

parameter. See section 207.4 Text Styles for more information. 

The Multiline dimension styles have been configured to place dimension text above and below the 

dimension line as shown at left in the example below. These Dimension styles have been provided to 

allow the user to edit the dimension text to contain a label as part of the dimension element. This is 

advantageous in the case where the dimension is moved or modified since the text is part of the 

dimension and not a separate text string that must be moved manually. The MicroStation Edit Text 

command is used to edit the dimension text. An example of the edited text is shown at right below. 

Bridge plans shall use the “Fract, Slanted”, “Fract-Multiline, Slanted” or “Masked Fract, Slanted”, 

“Masked Fract-Multiline, Slanted” dimension styles. All Bridge dimensions shall be placed associated. 

Dimensions shall not have their status dropped. 


208 Seed Files 

208.1 General 


MicroStation uses a “seed file” to create all design files. A seed file is a template in which standard 

parameters are set. Seed files do not typically contain elements, but like other design files they do 

contain settings like working units and view configurations. Using a standard, customized seed file helps 

maintain uniformity and keeps the user from having to adjust design file settings each time a file is 

created. 

The following two-dimensional (2D) and three dimensional (3D) seed files are available on the ODOT 

CADD Standards website: 

Dimension Seed File Name 

2D ODOTSeed2d.dgn 

3D ODOTSeed3d.dgn 

The MicroStation configuration variable MS_DESIGNSEED is used to define the default seed file. 

208.2 Models 

ODOT’s seed files each contain two models as listed in the table below. 

Model Name Type 

Design Design Model 

Sheet Sheet Model 

For more information on the use of models, see section 303 References. 



209 GEOPAK Design and Computation Manager Database 

209.1 General 

The primary purpose of the GEOPAK Design and Computation Manager (D&C Manager) is to assist the 

user with the placement of MicroStation elements according to a set of predefined CADD standards. 

ODOT provides a standard D&C Manger database, ODOT.ddb that has been configured according to the 

CADD standards outlined in this manual. The ODOT.ddb can be obtained from the ODOT CADD 

Standards website. 

The D&C Manager can be used to facilitate the placement of curvilinear features or point features 

represented by cells according to ODOT standards. For more information on the use of the GEOPAK 

Design and Computation Manager, see the ODOT GEOPAK Road 1 Training Guide on the ODOT 

CADD Standards website. 

Users are not permitted to edit the ODOT.ddb. 

210 GEOPAK Survey Manager Database 

210.1 General 

The GEOPAK Survey Manager Database is primarily used to assist the user with mapping field survey 

codes to the appropriate MicroStation symbology according to a predefined set of CADD Standards and 

Survey field codes. 

210.2 Survey Field Codes 

ODOT has developed a set of standardized field codes for all survey data submitted to the Department. 

The list of standard field codes for ODOT projects can be obtained from the ODOT CADD Standards 

website. 

Users are not permitted to use other field codes to supplement the ODOT code list for any project related 

survey data submitted to or exchanged with ODOT. 

210.3 Survey Manager Database 

ODOT has developed a standard Survey Manager Database, ODOT.smd, for use with GEOPAK Survey 

Software to map the field codes contained within a set of survey data to the appropriate symbology in a 

MicroStation design file according to the CADD Standards set forth within this manual. The ODOT.smd 

can be obtained from the ODOT CADD Standards website. 

Users are not permitted to edit ODOT.smd. 


211 Working Units 

211.1 General 


MicroStation lets you draw in "real world" units; feet, inches, meters, etc. These real world units are 

called working units. Working units are expressed as Master Units (the largest units in common use in a 

design file, such as feet) and fractional Sub Units (such as inches). 

The default definition for a foot in MicroStation is the International Foot. The U.S. Survey Foot definition 

can be defined by use of a unit definition file. ODOT has developed a standard unit definition file, 

ODOT_Units.def, to define the U.S. Survey Foot as the standard Master Unit. This file can be obtained 

from the ODOT CADD Standards website. The active unit definition file is specified by the configuration 

variable MS_CUSTOMUNITDEF. 

MicroStation design files used in plan preparation shall use the following standard working units as 

defined in the ODOT seed files and in ODOT_Units.def: 

Unit Names Label 

Master Unit: Survey Feet ‘ 

Sub Unit: Inches “ 

The ODOT seed files have been defined with a standard resolution setting of 12000 per Survey Foot. 

This setting shall not be changed by the user. 

ODOT’s seed files are set up with the standard working units described above. Deviation from these 

working units is not permitted. 

212 Global Origin 

212.1 General 

Elements in the design file are drawn by placing data points. Each data point placed in the design plane 

has associated X (easting), Y (northing) and Z (elevation, 3D files only) positions or coordinates. The 

design plane is simply a Cartesian coordinate system upon which your design model lies. 

In the ODOT Seed files, the point called the Global Origin is set to the design plane's exact center 

(178,956.9707, 178,956.9707) and assigned the coordinates 0,0 (2D files) and 0,0,0 (3D files). 

The Global Origin is defined in ODOT’s Seed Files and should never be changed for ODOT projects. 



213 Custom Applications 

213.1 General 

ODOT has written several programs to assist the user with specific CADD related functions. Each 

application can be accessed from the main menu bar under the ODOT pull-down menu as shown below. 

The ODOT pull-down menu has been configured to group the applications logically. 

A detailed list of applications including documentation is available on the ODOT CADD Standards website 

for download. 

ODOT’s pull-down menu for applications is defined in a MicroStation DGN Library, ODOT_Menu.dgnlib, 

which can be obtained from the ODOT CADD Standards website. The DGN library is attached by use of 

the MicroStation configuration variable MS_DGNLIBLIST. 


214 GEOPAK Criteria Files 

214.1 General 


Criteria files are ASCII text files written in the GEOPAK Criteria language. Criteria files are primarily used 

to draw proposed cross section graphics in a MicroStation design file. 

Three Port Criteria (3PC) commands can be used to extend the processing capabilities of GEOPAK 

Criteria to draw MicroStation elements in a plan or profile design files in addition to the cross section 

design file. For ODOT purposes, criteria files that are processed from the GEOPAK Design and 

Computation Manager to draw plan or profile information are referred to as “3PC files”. Criteria files that 

are processed from cross section mode are referred to as “criteria files” even though the cross section 

criteria file may contain 3PC commands to draw elements in the Plan or Profile design files. 

214.2 Cross Section Criteria Files 

ODOT has developed a set of criteria files to assist the user with the drawing and detailing of the 

proposed cross sections. These criteria files are available on the ODOT CADD Standards website. 

The ODOT cross sections criteria files have been developed according to the standards defined in the 

Location and Design Manual, Volume 1 – Roadway Design. These criteria files are provided as a 

convenience to the user and are not intended to draw all aspects of every cross section correctly. The 

designer must take care to review the results and make any modifications necessary to the cross section 

graphics to ensure compliance with ODOT design standards. 

Cross Section Criteria files shall have an .x file extension. 

Users are permitted to copy and modify the criteria files as necessary to achieve the desired results. 

Modified criteria files should be renamed to avoid confusion with the ODOT standard criteria files. All new 

or modified criteria files shall be submitted to ODOT with the completed project data. 

As a standard practice, users should copy all cross section criteria files used on the project to the 

project’s \geopak\criteria sub-directory. See Section 302 Project Directory Structure for information on 

project directories. 



214.3 3 PC Criteria Files 

ODOT has developed various 3PC applications, which are used in conjunction with the GEOPAK Design 

and Computation Manager. These applications can be obtained from the ODOT CADD Standards 

website. 

Three Port Criteria files run from the GEOPAK Design and Computation Manager shall have a .3pc file 

extension. 

The configuration variable GPK_DC_3PCDIR is used to specify the directory location containing the 3PC 

applications. 

Users are permitted to copy and modify the 3PC criteria files as necessary to achieve the desired results. 

Modified 3PC criteria files should be renamed to avoid confusion with the ODOT standard criteria files. 

All new or modified criteria files shall be submitted to ODOT with the completed project data. 

As a standard practice, users should store new or modified 3PC criteria files in the project’s 

\geopak\criteria\3pc sub-directory. See Section 302 Project Directory Structure for information on project 

directories. 

214.4 Cross Section Input Files 

Cross sections can be processed in GEOPAK through a dialog box interface by use of the GEOPAK 

Project Manager, or by an ASCII input file. 

All cross section input files used on the project shall be submitted to ODOT. Input files shall be stored in 

the project’s \geopak\input sub-directory. 

Cross Section input files shall use relative paths where applicable. 


300 FILE MANAGEMENT 

301 General 

301.1 General 


File management refers to how documents are organized and stored. Its primary purpose is to provide a 

safe repository for information and to minimize the possibility of that information being lost. 

302 Project Directory Structure 

302.1 Standard Directory Structure 

A standard project directory structure should consist of a main directory on the server named “projects”. 

Under the projects directory a sub-directory will be created with the three (3)-letter character of the 

County (County codes are defined in the Location and Design Manual, Volume 3, Section 1302.2.2.1). 

Under the County sub-directory, another sub-directory will be created using the five (5) digit ODOT 

Project Identification Number (PID) and will contain all project related information. 

Two directory structure options are provided to contain project related information: 

• Minor project directory structure, shown in Figure 302-1, lists the required discipline directories 

under the project directory name (PID number). This directory structure is intended for use on 

Minor Projects as defined by the Project Development Process manual. 

• Major project directory structure will be used on larger projects involving multiple design teams. 

On larger projects, it is sometimes desirable to use an expanded directory structure to split the 

Roadway design information into separate discipline specific sub-directories. This project 

directory structure, shown in Figure 302-2, is provided for these types of projects. This directory 

structure will allow each design team to set file permissions to restrict access to their data as 

needed. This directory structure is intended for use on Major Projects as defined by the Project 

Development Process manual. 



Data from each discipline shall be maintained as individual sub-directories under the project directory. 

The discipline sub-directories will be defined for the division of work by ownership, not necessarily the 

type of work. As files are developed by the various disciplines, those files should generally be placed into 

the project sub-directories corresponding to the creator of the work. Roadway design would typically 

place their files under the roadway sub-directory, Surveyors under the survey sub-directory, and so forth. 

If a discipline requires information from another discipline or shares files with multiple disciplines, the 

needed files should be referenced from the original directory and not copied (see section 303 

References). Disciplines may overlap work with some components of a design. 

For example, if a roadway designer develops the drainage sheets, the files produced would, by the above 

convention, go in the roadway sub-directory, rather than the drainage sub-directory, as the “roadway” 

designer is the owner of the work. However, if so desired, the files could be put in the drainage subdirectory 

by use of the Major project directory structure option. In making the determination of which 

discipline’s sub-directory the file should be placed in, the designer must use common sense. 

In some cases, it will be advantageous to create non-standard directories for additional separation of 

work. This is common when multiple parties work on a single discipline design and the data must be 

managed and merged. These additional directories can be created under the discipline specific 

subdirectories to accommodate such circumstances. Do not create subdirectories at the same level as 

the standard discipline subdirectories. 

The following Table is provided to assist designers in managing Survey Basemap information within the 

Project Directory for all Projects. 

All Projects: 

File Type (Per Fig. 304 -1) Directory 

Existing Ground Survey – BE Per Figure 302-1; Projects (Survey Sub Directory) 

Alphanumeric characters and underscores “_” are the only characters to be used in directory names. 

ODOT provides a custom program, ODOT_Directory.exe that can be used to create the project 

directories. This program is available on the ODOT CADD Standards Website. 



Figure 302-1 

Minor Project Directory Structure 

Notes: 

projects Active projects folder. 

aaa 

Three character County as defined by the Location 

and Design manual, Volume 3, Section 1302.2.2.1. 

12345 Five-digit PID number. 

admin 

aerial 

geopak 

geotechnical 

roadway 

row 

standards 

structures 

survey 

Parent folder for project administration. 

See Figure 302-3 for sub-directories. 

Parent folder for aerial information. 


Parent folder for all GEOPAK specific files. 


Parent folder for geotechnical information. 


Parent folder for roadway design. 


Parent folder for right-of-way design. 


ODOT standards using during project development. 

This directory is used for project archiving and digital 

submissions only. See Figure 302-11 for subdirectories. 

Parent folder for bridge and wall design. 


Parent folder for survey information. 




Figure 302-2 

Major Project Directory Structure 

Notes: 

projects Active projects folder. 

aaa 

Three character County as defined by the Location 

and Design manual, Volume 3, Section 1302.2.2.1. 

12345 Five-digit PID number. 

admin 

aerial 

asbuilt 

drainage 

geopak 

geotechnical 

landscape 

lighting 

mot 

roadway 

row 

signals 

standards 

structures 

survey 

traffic 

utilities 

Parent folder for project administration. 


Parent folder for aerial mapping files. 

See figure 302-4 for sub-directories. 

Parent folder for as-built plans. 

See figure 302-5 for sub-directories. 

Parent folder for drainage design. 


Parent folder for all GEOPAK specific files. 


Parent folder for geotechnical information. 


Parent folder for landscape design. 


Parent folder for lighting design. 


Parent folder for maintenance of traffic design. 


Parent folder for roadway design. 


Parent folder for right-of-way design. 


Parent folder for signal design. 


ODOT standards using during project development. 

This directory is used for project archiving and digital 

submissions only. 


Parent folder for bridge and wall design. 


Parent folder for survey information. 


Parent folder for traffic control. 


Parent folder for utility information. 




Figure 302-3 

Project Administration Sub-Directories 

Notes: 

contracts Contract documents 

docs Documents, letters, memos, etc… 

email Email correspondence. 

estimate Project Estimate 

forms Forms 

images Scanned images. 

mdb Access databases 

modifications Modifications 

photos Digital photos. 

publicinfo Public information 

reports Reports 

reviews Review submission TIF images 

final RW Final RW TIF files 

final tracings Final tracing TIF files 

prelim eng Preliminary engineering TIF files 

prelim RW Preliminary RW TIF files 

RW tracings RW tracing TIF files 

stage 1 Stage 1 TIF files 



schedules Project schedules. 

spreadsheets Spreadsheets. 

Figure 302-4 

Aerial Sub-Directories 

Notes: 

basemaps Aerial mapping basemap design files. 

Figure 302-5 

As Built Plans Sub-Directories 

Notes: 

images Scanned drawings. 



Figure 302-6 

Discipline Specific Sub-Directories 

Notes: 

discipline 

Where discipline = the following sub-directories: 

drainage, geotechnical, landscape, lighting, mot, 

roadway, signals, traffic, utilities. 

basemaps Basemap design files for the discipline. 


engapps Data files for related engineering applications. 



sheets Plan sheet MicroStation design files for the discipline. 


Figure 302-7 

GEOPAK Sub-Directories 

Notes: The GEOPAK Project Manager creates additional subdirectories 

as required by the software. 

geopak GEOPAK related files including the .gpk and .prj files 

criteria Custom criteria files used for the project. 

3pc Customized three port criteria files used for the project. 

input COGO input files. 

output COGO output files. 

Figure 302-8 

Right-of-Way Sub-Directories 

Notes: 

basemaps Right-of-Way basemap design files. 



legal Legal descriptions for all property takes. 

closures Survey closures for all the property takes. 


sheets Plan sheet MicroStation design files. 




Figure 302-9 

Structures Sub-Directories 

Notes: 

AAA000_1111S 

Parent folder for bridge data, where: 

AAA = 3 character county code 

000 = 3 digit Route number 

1111 = 4 digit SLM of the structure without the 

decimal point. 

S = 1 digit code (For twin structures: L for Left, R 

for Right. C for collector/distributor roads or twin 

structures combined in the same directory, P for 

Ramps.) 

wall_111 

Parent folder for wall data, where: 

111 = 3 alphanumeric character wall number 

basemaps All bridge related basemap design files. 


Data files for bridge design applications. Users 

engapps 

may elect to replace the engapps directory with 

separate directories for each bridge design 

software package. 



sheets All bridge related plan sheet design files. 




Figure 302-10 

Survey Sub-Directories 

Notes: 

basemaps Basemap design files. 


GPS GPS data 



rawdata 

Raw survey data. Multiple directories may be used for 

multiple datasets. 

sheets Plan sheet MicroStation design files. 


Figure 

Standards Sub-Directories 

302-11 

Notes: This sub-directory is used for project archiving and electronic 

submission only. During project development, ODOT users should 

always reference all CADD Standards from the main CADD Standards 

directory. 

cell Cell Libraries 

config Configuration files 

ctb Color Tables 

dgnlib DGN Libraries 

macros MicroStation Basic Macros 

mdlapps MDL Applications 

office Standard template for the project index file 

plotdrv Plot drivers 

seed Seed files 

symb Symbology .rsc files 

tables Pen tables 

vba Visual Basic Applications 


303 References 

303.1 General 


References are used to display the contents of one or more MicroStation design files within the active 

design file. 

The most common use of references is to display Basemap design file information (See Section 303.3 

Basemap Design Files) in a Sheet design file (See Section 303.4 Sheet Design Files) to generate the 

various plan sheets used by a typical ODOT roadway project. 

References are also used to display the contents of one basemap design file in another basemap design 

file to facilitate the design process (i.e. display the existing survey data in the proposed right-of-way 

basemap). 

303.2 Models 

A Model is a 2 or 3 dimensional drawing area that is stored in a design file. A single design file can 

contain multiple models, which means you can have multiple, independent, drawing areas in a single 

design file. Each model has its own set of view parameters, working units, reference attachments, etc.; 

however all models within the same design file share the same Color Table and Background Colors. 

Users can only edit one model at a time in a design file. 

To manage the model’s properties in a DGN file open the Models dialog box. This dialog box contains 

tools that not only allows the user to edit the model’s properties but also allows the user to create, copy, 

import, delete and open specific models in the DGN file. 

The Models dialog box can be accessed several ways: 

Key in: model manager 

Or 

Select File > Models from the Main Menu bar. 

Or 

Select the Models icon in the Primary Tools box. 



The Models dialog box contains the following various tools that allow the user to work with models: 

• Models in Active Design File – if you click the down arrow and select one of two modes: 

o Active File Mode – shows the current source of the models in the master file. 

o Link Set Mode – shows the models in Project Explorer, allowing you to select an 

active file or folder from the active project in Project Explorer. 

• Create a new Model - allows the user to create a new model inside the dgn file. This user can 

also select the type and dimensionality they wish to create. See Section 303.2.2 Model Names. 

• Copy a Model - allows the user to copy an existing model in the open dgn file. 

• Edit Model Properties - allows the user to Edit Model Properties of a selected model, like the 

name, description, Annotation scale and Line Style Scale. 

• Delete Model(s) - allows the user to delete a selected model. 

• Import Models - allows the user to import a selected model through a different design file. 

• Sheet Boundary - allows the user to define the size of a sheet layout. This is for Sheet Models 

only. ODOT does not use this function. ODOT places all sheets as cells from the standard sheet 

cell library, ODOT_Sheets.cel. 

• List Filter - if on displays a filter row in the list box that lets you define a filter for any of the list 

columns. 

• List Box – contains columns that can be added or hidden to the list box in the Models dialog box 

to make it easy to identify models designated as cells and annotation cells and to determine the 

cell types of such models. The Cell Type and Is Annotation Cell columns are not displayed by 

default. To enable their display, Right-Click on the list heading row and turn on Cell Type and Is 

Annotation Cell from the pop-up columns menu. 

Double-clicking a Model within the dialog box makes the model active. Alternatively, you can use the 

View Groups window to rapidly switch between models visited in the current design session as shown 

below. 


303.2.1 Types of Models 


MicroStation has different types of models available in MicroStation. The model types are Design, 

Drawing and Sheet. The Design and Sheet models are used by ODOT for creating all new models. 

The other model types are Design From Seed, Drawing From Seed, and Sheet From Seed use a model’s 

attributes from a chosen seed file to create a model and are typically not used by ODOT for creating new 

models 

• Design – type model is used for creating design geometry that can be either 2D or 3D. All 

basemap information shall be drawn in the default design model. See Section 303.3 Basemap 

Design Files for more detailed information. 

• Drawing – type model serves as a Drawing Area for centralizing annotations that need to be 

shared across multiple sheets. A drawing model is always a 2D model. ODOT does not use the 

Drawing model at this time. 

• Sheet – type model is used to assemble the plan sheets that are used for plotting a set of plans 

that can be either 2D or 3D. Sheet border cells and annotations are placed in the Sheet model. 

See Section 303.4 Sheet Design Files for more detailed information. 



303.2.2 Model Names 

When creating a new design file using ODOT’s seed files, ODOTSeed2d.dgn or ODOTSeed3d.dgn, a 

Design and Sheet model is already created for you as follows: 

ODOT has a recommended standard for naming models when developing a set of plans. ODOT 

Applications utilize the Model name “Sheet” except for cross sections. The GEOPAK Cross Section 

attachment options do not provide the capability to generate each cross section sheet in a separate 

design file, see the ODOT GEOPAK V8i Road 2, Chapter 10, Training Guide for details. The model 

name “*Sheet*” as provided by ODOT’s seed files is utilized by ODOT’s plotting software. 

Therefore, it is strongly recommended not to change the model names in the design files since the 

programs and or software are dependent on the model names. Any name changes to the models could 

prevent the application(s) from working properly. 

For detailed information on how models are set up for Plan and Profile sheets and Cross Section Sheets 

see the ODOT GEOPAK V8i Road 1 and 2 Training Guides. 


303.2.3 Model Properties 


You can select or edit Properties of a model in the open design file. The model properties are different 

depending on what type of model is selected, Design, or Sheet as shown below. 

“Design” Model Properties 

• Type - sets the model's type (Design or Sheet) and dimensionality (2D or 3D). 

• Name – is a text field to enter a name for the model. See section 303.2.2 Model Names. 

• Description – is a text field to enter a description of the model. 

• Ref Logical - sets the Reference Logical name for the model. The logical name identifies the 

model when it is attached to another model as a reference. 

• Annotation Scale - sets the scale for text, dimensions and cells in the model. You can 

select from the list of common scales used for ODOT plan sheets. When placing text, 

dimensions and cells the Annotation Lock in the tool settings window must be on to ensure that 

they are placed at the defined scale. The list of common scales is located from the 

ODOT_Scales.def file located in the i:/ODOTstd/V8istd/data directory. 

• Line Style Scale - Lets you set the scale for custom line styles. 

“Sheet” Model Properties 

• Update Fields Automatically - If set on, fields are automatically updated when a file is opened. 



Cell Properties: 

2D or 3D Models can be placed in a design file as a cell. Therefore, any cell library (*cel) can be 

opened in MicroStation as if it were a DGN file. 

• Can be placed as a cell – if toggled on, it is possible to place the model as a cell. 

• Cell Type - sets the cell type (Graphic or Point). This option menu is enabled only if “Can be 

placed as a cell” is toggled on. 

• Can be placed as an annotation cell – if toggled on, it is possible to place the model as an 

annotation cell. When placed as an annotation cell, the current annotation scale is applied to 

the cell. 

Sheet Properties: 

• Sheet Name – Lets you assign a name to the sheet model. 

• Sheet Number – Lets you assign a sheet number to sheet models. This makes it easy to 

control the order of sheet models for presentation, printing, cataloging in a project, or 

generating PDFs. 

• Display Sheet Boundary – If toggled on, a sheet element will display in the new sheet 

model. This is not used since the sheet border cells are placed from the cell library, 

ODOT_Sheets.cel, in the Sheet model. 

• Border Attachment - When you associate a border attachment to a sheet model, any 

changes to the annotation scale for the sheet, automatically are propagated to the border 

attachment. 

o Size - sets the sheet size. 

o Origin - sets the origin of the sheet. 

o Rotation - sets the rotation angle of the sheet, measured in degrees counterclockwise 

from the x-axis (horizontal). 

• Create a View Group – if toggled on, a View Group is created with the model. This is a property 

in the Create Model dialog box when Create a new model is selected in the Models dialog box. 

If you define at least one view group for each model in a DGN file, you can use the View Groups 

window to switch between models. 

• OK - accepts the changes and closes the dialog box. 

• Cancel - Closes the dialog box without making any changes. 


303.2.4 Referencing Models 


When selecting a reference to attach, users must select the appropriate model, Design or Sheet, in a 

design file. A Design or Sheet model can be attached as a reference to the currently active model in the 

open design file or in other design files. See Section 303.3 Basemap Design Files and Section 303.4 

Sheet Design Files. 

303.3 Basemap Design Files 

Basemap design files are used to draw existing and proposed plan view information for the entire length 

of the project for both Roadway and Bridge projects. All basemap information shall be drawn in the 

default Design model. The location and dimensions of all plan view basemap design file information shall 

be drawn using real world dimensions at a 1:1 scale. 

For Roadway projects, the three most common Basemap design files are as follows:: 

• One containing the existing information (typically from ground survey or Aerial mapping). 

• A second containing the proposed roadway information. 

• A third containing the proposed Right-of-Way information. Existing Right-of-Way information may 

be in the same file with the proposed Right-of-Way information, or in the same file with the 

existing ground survey. 

Plan view information may be separated into multiple discipline-specific basemap design files as listed 

below: 

Allowable Plan View Basemap Files 

Aerial mapping 

Bridge 

Drainage 

Environmental 

Existing Ground Survey 

Geotechnical 

Landscaping 

Lighting 

Maintenance of Traffic 

Proposed Roadway 

Right-of-Way 

Signals 

Traffic Control 

Utilities 

Walls 



If a bridge basemap is used, a separate basemap design file is required for each bridge on the project. 

A basemap is also used for profiles and cross section graphics. Unlike plan view basemap files, profile 

and cross section basemap design files shall contain both the existing and proposed information in one 

file. 

The profile basemap may be used to plot all the profiles for the entire project in one file. It is not 

necessary to create separate profile basemaps for each alignment in the project. Profiles should always 

be plotted in their own design file and never combined with any other basemap. After generating the 

profile basemap, do not delete the profile cell. The profile cell is placed on the level “GK_Cells” as 

defined by the Configuration Variable GPK_LEVEL_PROFILE_CELL and can be toggled on or off using 

Level Manager, if required. If the configuration variable is not defined, the profile cell is placed on the 

level “Default”. 

A separate cross section basemap should be used for each alignment in the project. Cross sections for 

multiple alignments should never be plotted in the same cross section basemap. Cross sections should 

always be plotted in their own design file and never combined with any other basemap. After generating 

the cross sections, do not delete the cross section cells. Cross section cells are placed on the “GK_Cells” 

level as defined by the Configuration Variable GPK_LEVEL_XS_CELL and can be toggled on or off using 

Level Manager, if required. If the configuration variable is not defined, cross section cells are placed on 

the level Default. 

All basemap design files shall be stored in the appropriate discipline specific basemaps sub-directory and 

shall not be copied into another sub-directory for editing or referencing. 

See Section 302.1 Standard Directory Structure, for guidance on maintaining Survey Basemaps for 

Roadway and Bridge Projects. 

Standard design file names for Basemaps are detailed in Section 304.3 File Name Format. 

303.4 Sheet Design Files 

Sheet design files are used to assemble the plan sheets that are used for plotting a set of plans. The 

Sheet design files are assembled by referencing Design models from the necessary basemap design files 

to the sheet model of the sheet file. Sheet border cells and annotation are typically placed in the sheet 

model. 

For Roadway projects including the Bridge site plan and Geotechnical Exploration sheets when attaching 

basemap Design models to the Sheet models the user shall not scale, move, or rotate the basemap 

reference attachment. Basemap Design models shall be attached using the MicroStation Coincident- 

World setting. If a rotated plot view is required, the user shall rotate the sheet design file view for proper 

plot orientation. The sheet border cells shall be placed in the rotated view. All reference file clipping shall 

be done in the rotated view. 

For Bridge sheets, a single design file may include both existing and proposed plan view information. 

When developing Bridge profiles (including profiles for culverts greater than 10 feet in diameter or span), 

place the profile in a design model. Reference the profile from the Design model into the Sheet model 

(Site Plan or Culvert Detail sheet). All profile labeling shall be completed in the Sheet model. 



Final plan sheets shall be in the Sheet Model. No items other than what is shown on the final plotted 

sheet are allowed to be shown in the Sheet Model. Any detail shown in the final plotted sheet shall be 

represented at a 1:1 scale in either the Design model or Sheet model of the corresponding file. 

The purpose of having the existing details drafted or referenced at a 1:1 scale is to facilitate the electronic 

transmission of design data (via email or equivalent) without providing the entire project directory. If 

necessary, the designer can merge the referenced details within the design file. 

Each plan sheet shall be contained within the Sheet Model. Therefore, each plan sheet will be separated 

into individual design files when submitted to the Department. 

When sheet design files are submitted to the Department, no other graphics are permitted in the Sheet 

model other than the graphics representing the final plotted sheet. All extra graphics used to generate 

the sheet, or old versions of the sheet, should be deleted or moved to a design model. No extra 

reference attachments that are not a part of the final sheet are permitted to be attached to the sheet 

model. 

In order to ensure that reference file attachments are maintained when moving project files from the 

original project directory to another location, such as a CD for submission or to an archive directory, 

references shall be attached using relative paths. The user shall not use MicroStation or GEOPAK 

options to “Save Full Path” for reference attachments. 

All completed sheet design files submitted to or exchanged with ODOT shall use references where 

applicable. It is not recommended that users copy referenced graphics into the sheet files for the 

completed sheet design files submitted to ODOT. 



304 File Naming Conventions 

304.1 General 

The efficient sharing and transfer of information from consultants/contractors to ODOT and vice versa 

relies on the use of a systematic file naming convention. This section outlines a consistent, 

comprehensive file naming convention for graphic and associated files used in the CADD environment, 

which shall be used for all projects. 

With such large quantities of data being created, it is essential that operators create their new files with 

names that signify the content of each. Therefore, each sheet of the plan shall be contained in its own 

separate design file. 

Standard naming conventions shall be used for all design files, standard input files and GEOPAK criteria 

files. Document all file names, both standard and project specific, in the Project Index file (See Section 

503 Project Index File). In the event a particular file type for the project is not addressed by this manual, 

use the file naming convention as a template for selecting an appropriate name or contact the Office of 

CADD and Mapping Services, CADD Section for assistance. 

In order to avoid conflicting attachments of reference files, there shall be no duplicate file names within 

the project directory structure or copies of the same file within the project directory. It is not permissible to 

copy the same basemap design files into multiple discipline specific sub-directories. 

304.2 File Extensions 

Standard file name extensions for information submitted to or exchanged with ODOT shall be as follows: 

File Type Extension 

MicroStation design files .dgn 

MicroStation cell libraries .cel 

MicroStation/GEOPAK Resource file .rsc 

GEOPAK Criteria files .x 

GEOPAK Cross Section Input files .inp 

GEOPAK GPK Files .gpk 

GEOPAK Triangle Models .tin 

Postscript Sheet Image Files .ps 

Adobe Acrobat Files .pdf 

Microsoft Word Documents .doc or .docx 

Microsoft Excel Spreadsheets .xls or .xlsx 

Microsoft Project files .mpp 

XML files .xml 

For file types not listed above, the default file extension defined by the software shall be used. 


304.3 File Name Format 


ODOT has defined the following naming convention to be used on all design files submitted to, or 

exchanged with the Department. 

It is not permissible to use special characters (i.e. @, #, -, >, +, %, etc.) in file names. 

Standard Plan Insert sheets shall retain the name designated by the issuing office. 

Standard Design File Naming Format 

nnnnnaa###.dgn 

nnnnn = Five (5) digit PID Number 

aa = Two (2) letter code identifying the plan sheet type 

### 

(see Figure 304-1 File Name Type Codes) 

= Three (3) digit number identifying the number of drawings of 

the same type. The three digit number is required even if 

there is only one drawing of a particular type in the plan set. 

Examples: 

12345BE001.dgn 

12345GP005.dgn 

Bridge Design File Naming Format 

rrr_nnnnsaa###.dgn 

rrr = Three (3) digit route number 

nnnn = Four (4) digit SLM of the structure without the decimal point. 

s = One (1) digit code (For twin structures: L for Left, R for Right. C for 

collector/distributor roads or twin structures combined in the same 

directory, P for Ramps.) 

aa = Two (2) digit Bridge plan sheet type 

### 





Examples: 

071_0546LPI002.dgn 

071_0546RSP001.dgn 

Wall Design File Naming Format 

nnnnn_yyyaa###.dgn 

nnnnn = Five (5) digit PID Number 

yyy = Three (3) digit wall number (three digits required and 

maximum). 

aa = Two (2) digit wall plan sheet type 

### 





Examples: 

12345_001WP005.dgn 

12345_001WS001.dgn 



304.4 Supplemental Description Guidelines 

ODOT allows users to provide supplemental description information by use of MicroStation’s File 

Properties. The intent of the supplemental description is to provide additional descriptive information to 

aid the designer in identifying a particular file. 

The following properties are available in a MicroStation Design File: Title, Subject, Client, Keywords, and 

Comments. 

For ODOT projects, the following properties shall be used for design files submitted to or exchanged with 

the Department: 

Title 

The Title property can be used to specify the file type description. If used, the description shall 

correspond to the file descriptions for each file type shown in Figure 304-1 File Name Type 

Codes, prefixed with the Discipline name (see the examples on the following page). 

Comments 

The Comments property can be used to provide additional descriptive information to aid the 

designer in identifying a particular file. Comments are user definable with the following 

guidelines: 

For Roadway design files the comment should start with the route name/number, where 

applicable, using the route name as follows: 

IR### Interstate route with three digit number, e.g. IR071 for Interstate route 71. 

US### United State route with three digit number, e.g. US033 for US route 33. 

SR### State route with three digit number, e.g. SR315 for State route 315. 

CR### County Road with three digit number, e.g. CR056 for County road 56. 

RAMP### 

Ramp with up to three character name/number, e.g. RAMP2S for ramp 2- 

S. 

Road name, e.g. Paris for Paris road. Note, directions (N, S, E, W) can be 

ROADNAME used on projects where plans exist for two different directions of the same 

roadway, e.g. Paris N for Paris road north. 

Following the route name/number, the Comment property can contain additional information to 

help identify the specific sheet of the plan. 

For Bridge design files, a brief description of the plan sheet contents should be included. 


Supplemental Description Examples: 

File Name Title Property Comments 

12345GP001.dgn Roadway Plan & Profile or Plan IR071 Sta 50+00 to 60+00 

12345MH002.dgn MOT Phase Details TR123 Phase 2 

12345BP005.dgn Basemap Proposed Roadway SR185 

070_1234LBS003.dgn Basemap Bridge Alternate C 

070_1234LSD001.dgn Superstructure Details Framing Plan 

070_1234LSD002.dgn Superstructure Details Camber/Deflection 

Supplemental descriptions are optional and may be used at the designer’s discretion. 

304.5 Assigning Supplemental Descriptions 

Supplemental descriptions can be assigned in one of two ways: 


1. Assigning properties in MicroStation. Select File > Properties to access the Properties dialog 

shown below. Select the Summary tab to assign the Title and Comments properties. 

2. ODOT provides a Visual Basic application, ODOT_Files.mvba, to create files using the ODOT 

file naming conventions detailed in this manual. The program will automatically assign the Title 

property. A key-in field is provided to enter the comments for each file created by the program. 

See the ODOT CADD Standards website for more information. 



304.6 Viewing Supplemental Descriptions 

Supplemental description information assigned to the file properties can be viewed in Windows Explorer, 

and in MicroStation file open dialog boxes. 

To view the information in Windows Explorer on Windows 7 systems take the following steps: 

1. From the View pull-down menu, select Details 

2. Right-click on the column header to access the pop-up menu shown below. Toggle on the Title 

and Comments options in the pop-up menu or if they are not available select More and toggle on 

the options in the Choose Details dialog box shown below. 

3. The columns can be arranged in the desired order by dragging the column headers. 



4. To save these changes, from the Windows Explorer pull-down menu select Tools > Folder 

Options… to open the Folder Options dialog shown below. From the View tab, select Apply to 

Folders. 

If the title and comments fields are not displaying in the MicroStation File Open dialog box, take the 

following steps: 

1. Open a MicroStation design file. 

2. From the MicroStation pull-down menus, select Workspace > Preferences to access the 

Preferences dialog. 

3. From the Preferences dialog, select the Look and Feel category. Toggle on the Use Windows 

File Open Dialogs option. 

4. Close MicroStation. 

5. From the MicroStation Manager dialog, change the View Menu option to Details as shown on the 

following page. 



Notes: 

• The Title and Comments columns are not displayed by default. To display the columns, right 

click on the column headings and toggle the options for Title and Comments on. 

• You can set Windows to always display the Title and Comments columns by taking the following 

steps in Windows Explorer: 

From the Windows Explorer pull-down menu select Tools > Folder Options… to open the Folder 

Options dialog. From the View tab, select Apply to Folders. 


Figure 304-1 File Name Type Codes 

BASEMAP DESIGN FILES 

Aerial Mapping - BA 

Bridge - BS 

Combined Aerial and Ground - BC 

Drainage - BD 

Environmental - BV 

Existing Ground Survey - BE 

Geotechnical - BI 

Landscaping - BL 

Lighting - BH 

Maintenance of Traffic - BM 

Profiles - BF 

Proposed Roadway - BP 

Right of Way - BR 

Signals - BG 

Traffic Control - BT 

Utilities - BU 

Walls - BW 

GEOPAK RELATED BASEMAP FILES 

GEOPAK Components in single file 

(Clipping Borders, Pattern Lines, - KA 

Superelevation Shapes) 

Clipping Borders - KC 

Digital Terrain Model Features - KD 

GEOPAK Bridge - KB 

GEOPAK Site Elements - KI 

Profile Motif File - KF 

Pattern Lines - KL 

Plan Motif File - KP 

Superelevation Shapes - KS 

GEOPAK Cross Section Cells (Channel) - XA 

GEOPAK Cross Section Cells (MOT) - XT 

GEOPAK 

(Roadway) 

Cross Section Cells 

- XC 


BRIDGE SHEETS 

Site Plan - SP 

General Plan - GP 

General Notes - GN 

Estimated Quantities - EQ 

Staged Construction Details - PC 

Removal - RE 

Foundation Plan - FP 

Rear Abutment - AR 

Forward Abutment - AF 

Piers - PI 

Superstructure Details - SD 

Transverse Section - TS 

Deck Plan - DP 

Railing - RA 

Bearing - BR 

Expansion Device Details - EX 

Miscellaneous Details - MD 

Reinforcing Steel List - RL 

Sheeting - SH 

DRAINAGE SHEETS 

Drainage Schematic / Site Plan - DB 

Project Site Plan / Erosion Control / 

- DE 

Storm Water Pollution Prevention Plan 

Notes - DN 

Sub-Summary - DS 

Plan & Profile or Plan - DP 

Profile - DF 

Quantity Table - DQ 

Culvert Details - DC 

Details - DD 

Miscellaneous - DM 

Channel Section Sheets - XD 



LIGHTING SHEETS 

Schematic - LB 

Notes - LN 

General Summary - LG 

Sub-Summary - LS 

Plan - LP 

Quantity Table - LQ 

Circuit Diagrams - LC 

Elevation Views - LE 

Details - LD 

Miscellaneous - LM 

LANDSCAPING SHEETS 

Schematic - PB 

Notes - PN 

Sub-Summary - PS 

Plan - PP 

Details - PD 

Miscellaneous - PM 

MAINTENANCE OF TRAFFIC SHEETS 

Schematic - MB 

Notes - MN 

Detour Plan - MD 

Sub-Summary - MS 

Typical Sections - MY 

Miscellaneous - MM 

Phase Details - MH 

Phase Plan & Profile or Plan - MP 

Profile - MF 

Quantity Table - MQ 

MOT Cross Section Sheets - XM 

RIGHT-OF-WAY SHEETS 

Legend - RL 

Centerline Survey Plat - RC 

Property Map - RM 

Summary of Additional R/W - RS 

R/W Detail - RD 

R/W Topo - RT 

R/W Boundary - RB 

Railroad Plat - RR 

ROADWAY SHEETS 

Title Sheet - GT 

Schematic Plan - GB 

Typical Sections - GY 

General Notes - GN 

General Summary - GG 

Maintenance Data - GJ 

Sub-Summary - GS 

Calculations / Computations - GC 

Plan & Profile or Plan - GP 

Profile - GF 

Quantity Table - GQ 

Superelevation Table - GE 

Pavement Details - GA 

Intersection / Interchange Details - GI 

Guardrail / Barrier Details - GR 

Drive Details - GD 

Miscellaneous - GM 

Fencing Plan - GX 

Layout Plan - XL 

Grading Plan - XG 

Cross Section Sheets - XS 


SIGNAL SHEETS 

Notes - CN 

General Summary - CG 

Sub-Summary - CS 

Plan - CP 

Quantity Table - CQ 

Details - CD 

Miscellaneous - CM 

GEOTECHNICAL EXPLORATION SHEETS 

Boring Logs (8.5x11) - IL 

SOIL PROFILE SHEETS 

Cover - IC 

Lab Data - ID 

Plan & Profile or Plan - IP 

Profile - IF 

Cross Sections - IX 

STRUCTURE 

SHEETS 

FOUNDATION EXPLORATION 

Cover - ZC 

Plan & Profile or Plan - ZP 

Profile - ZF 

Boring Logs - ZL 

Lab Data - ZD 

GEOHAZARD EXPLORATION SHEETS 

Cover - YC 

Plan & Profile or Plan - YP 

Profile - YF 

Cross Sections - YX 

Boring Logs - YL 

Lab Data - YD 

TRAFFIC CONTROL SHEETS 

(Pavement Marking and Signing) 

Schematic - TB 

General Notes - TN 

General Summary - TG 

Sub-Summary - TS 

Calculations / Computations - TC 

Plan - TP 


Quantity Table - TQ 

Elevation Views - TE 

Details - TD 

Miscellaneous - TM 

UTILITY SHEETS (Water, Sanitary, etc) 

Schematic - UB 

Notes - UN 

General Summary - UG 

Sub-Summary - US 

Calculation / Computations - UC 

Plan & Profile or Plan - UP 

Profile - UF 

Quantity Table - UQ 

Elevation Views - UE 

Details - UD 

Miscellaneous - UM 

WALL SHEETS 

Schematic - WB 

Calculation / Computations - WC 

Details - WD 

Elevation - WE 

Estimated Quantities - WQ 

Foundation - WT 

Plan & Profile or Plan - WP 

Profile - WF 

Miscellaneous - WM 

Notes - WN 

Sheeting - WH 

Typical Section - WY 

Sub-Summary - WS 

Steel List - WL 

Cross Section Sheets - WX 



305 GEOPAK Digital Terrain Models 

305.1 General 

The naming of GEOPAK Digital Terrain Models (DTM) is defined as shown in the table below: 

Digital Terrain Models (DTM) - .tin 

Aerial Mapping Existing - nnnnnXAE## 

Bridge Deck/Surface Existing - nnnnnXBR## 

Bridge Deck/Surface 

- 

Proposed 

nnnnnPBR## 

Combined Aerial and Ground - nnnnnXCB## 

Survey Existing 

Ground Survey Existing - nnnnnXGR## 

Proposed - nnnnnP## 

where: 

nnnnn = 5 digit PID number 

## = 2 digit number 01, 02, 03, . . . 

306 GEOPAK Coordinate Geometry Databases 

306.1 General 

When coordinate geometry calculations are processed in GEOPAK, the resulting geometric elements are 

stored in a separate binary file. This Coordinate Geometry (COGO) database is then used by other 

GEOPAK processes for a variety of tasks. 

Each project, regardless of its size, shall have one COGO database (.gpk file) containing all project data 

processed through GEOPAK Survey or GEOPAK COGO commands. For projects involving multiple 

locations or multiple design alternatives, it is permissible to use separate GPK files for each location or 

alternative. 

The naming of the GEOPAK Coordinate Geometry Database files submitted to ODOT shall be as follows: 

GPK Files - .gpk 

GEOPAK Coordinate Geometry 

- 

Database 

Job###.gpk 

where: 

job = GEOPAK Naming Convention 

### = 3 digit route number or first three 

characters of street name 


306.2 GEOPAK COGO Element Names 


To facilitate the efficient sharing and transfer of COGO information between consultants, ODOT, and 

contractors, the GEOPAK COGO Element Names detailed below have been established. 

COGO Points 

Bridge aBR## 

Centerline Station or Station Equation aCS## 

Construction Limits aCN## 

Curve PC aPC## 

Curve PT aPT## 

Design aDN## 

Drainage aDR## 

GPS GP## 

Miscellaneous / Junk aJK## 

Monument MN## 

Property PP## 

Right of Way Existing RE## 

Right of Way Proposed aRP## 

Roadway Point of Intersection (PI) aPI## 

Survey SV## 

Utility Location UT## 

where: 

a = Alternate A, B, C, . . . (if applicable) 

## = Two or more digit number 01, 42, 541, 2235, etc. 

Notes: GEOPAK supports alphanumeric point numbers 

to a maximum of nine characters. Alphanumeric 

point numbers must have an alpha prefix and a 

numeric suffix. For example, 123abc is not 

acceptable, while abc123 is supported. The 

number portion must be greater than zero, i.e., 

abc0 or abc000 are not acceptable. Also, do not 

use special characters, such as %,*,


COGO Roadway / Misc. Elements 

Chains / Profiles 

Cable Line CABt###o 

Construction Limit CON###o 

Construction Limit Alternates a##CON##o 

Culvert CULt### 

Ditch DITt###o 

Driveway DRtssssso 

Electric Line ELEt###o 

Gas Line GASt###o 

Right of Way RWrddd##o 

River / Stream RIVt### 

Sanitary SANt###o 

Storm Sewer STMt###o 

Telecommunication TELt###o 

Water Line WATt###o 

where: 

a = Alternate A, B, C, . . . 

t = Type, X (Existing) or P (Proposed) 

o = Side, if applicable, L (Left) or R (Right) 

sssss = Station or Drive Name 

10+23.45 would be 01023 

100+25.67 would be 10026 

## = 2 digit number maximum 01, 02, . . . 

### = 3 digit number maximum 01, 100, etc. 

r = Route Type 

C = County Road 

I = Interstate Route 

R = Ramp 

S = State Route 

T = Township Road 

U = U.S. Route 

ddd = 3 digit route number 020, 270, 142, etc. 

Notes: $ If the route type is unknown or the road is a 

local street, the rddd code should be 

replaced with the first four characters of the 

street name. 

$ If a profile is needed for the above 

elements, name the profile the same as the 

corresponding chain including the chain’s 

number. 

COGO Spirals and Curve Elements 

Alternates Curve a##trddd%% 

Alternates Spiral a##trddd%%l 

Curve trddd%%pi+ 

Spiral trddd%%pi+l 

where: 

a = Alternate A, B, C, . . . 

t = Type, X (Existing) or P (Proposed) 

l = Location, if applicable, A (Ahead) or B 

(Back) 

pi+ = 2-3 digit PI number 01, 100, etc. if known 

= 2-3 digit number in order of creation 

## = 2 digit number maximum 01, 02, . . . 




R = Ramp 





%% = 1-2 digit Ramp number A, 2S, 3A, etc. 

Notes: If the route type is unknown or the road is a 



street name. 


COGO Right of Way Elements 

Chains RWrddd### 

Curves RWC### 

where: 

### = 3 digit number maximum 01, 100, etc. 








Notes: If the route type is unknown or the road is a 



street name. 


COGO Right of Way Parcels 

Parent Tract ## 

Types of Title 

where: 

##_ppppnz 

## = 2 or more digit number 01, 02, 03, . . . 

Note: The number for the Types of Title shall 

match the number of the Parent Tract. 

pppp = 1 to 4 character parcel identification code as 

shown below. 

Fee Simple Title (store a Taking in 

GEOPAK) 

Acquired Fee Simple Excess Land EL 

Excess Land Sold or Swapped ES 

Fee Simple Excess Land E 

Fee Simple Uneconomic Remnant ER 

Limitation of Access WL 

Reservation of Access WD 

Easements (store as Easement in GEOPAK) 

Aerial A 

Channel CH 

Flowage FL 

Limited Access LA 

Railroad or Public Utility U 

Scenic Easement SC 

Standard Highway SH 

Sewer SW 

Slope SL 

Temporary Easement T 

Agreements 

GEOPAK) 

(store as Easement in 

Work WA 

Others (store as Occupied in GEOPAK) 

Present Road Occupied (PRO) PRO 

PRO Inside PROI 

PRO Total PROT 

n = When the parent tract has multiple Types of 

Title of the same type, a 1 digit number is 

used to identify each Type of Title. 

z = Additional Modifiers: 

In the name of another State 

agency, LPA, etc. 

V 

Special Reservation R 

Examples: 

03 (parent tract) 

03_LA (easement for parent tract 03) 

03_WD1 (taking for parent tract 03) 

03_PRO (occupied area for parent tract 03) 



307 GEOPAK Project Manager 

307.1 General 

The GEOPAK Project Manager is used to facilitate the organization of GEOPAK related data during 

project development. The GEOPAK Project Manager file has a .prj file extension. For ODOT projects, 

use of the Project Manager with GEOPAK Road is optional, but is recommended with GEOPAK Survey. 

The GEOPAK Road and GEOPAK Survey software applications both make use of the .prj file. For ODOT 

projects, it is recommended that you do not use the same .prj file for both the GEOPAK Road and 

GEOPAK survey software applications. 

For GEOPAK Road users, the GEOPAK Project Manager files (.prj) should be stored in the \geopak subdirectory. 

GEOPAK will create additional files and sub-directories in the \geopak sub-directory as 

required by the software. The .prj file shall be named as follows for use with GEOPAK Road: 

nnnnn_Design.prj 

where nnnnn = Five digit PID Number 

For GEOPAK Survey users, the GEOPAK Project Manager file (.prj) should be stored in the \survey 

subdirectory. GEOPAK Survey will create additional files and subdirectories as required by the software. 

The .prj file shall be named as follows for use with GEOPAK Survey: 

nnnnn_Survey.prj 

where nnnnn = Five digit PID Number 

307.2 Setting up a Project for GEOPAK Road 

When creating a new project for GEOPAK Road, use the following guidelines to supplement the project 

information. 

Items under the Create New Project dialog. 


(1) Project Name: For this example, this field would be nnnnn_Design. 


(2) Working Directory: Used to specify the default directory that GEOPAK will use to open and save 

files. For this example this field would be set to \project\FRA\12345\geopak\ 

(3) Job Number: This is used to identify the Coordinate Geometry (COGO) Database (gpk) for the 

project. 

Use the three digit number for the mainline route number. For example, State Route 4 the Job 

Number would be 004, Township Road 50 would be 050, etc. 

In cases where there is not an established route number, the first three characters of the road 

name should be used. 

(4) The Project Description field shall contain the following information. 

County-Route-Section: FRA-070-0.00 

PID Number: 12345 

State Job Number: 555555* 

Project Manager: Ms. Jane Doe 

Project Designer: Mr. John Dow 

Project Description: The scope of work for project 12345 goes here. Include 

as much detail as necessary to define the work done for 

the project. 

* If the State Job Number (SJN) is not assigned at the time of creation, leave the area blank where the 

number is required. Update this field when SJN number is assigned. 

In the middle of the Create New Project dialog, select the Preferences button to access the GEOPAK 

User Preferences dialog. The values shown below are the recommended settings for an English unit 

project. 



307.3 Setting up a Project for GEOPAK Survey 

Before you create a new Survey project, you must first set the default Survey Preferences using the 

Default Preferences dialog. The values assigned for the Default Preferences are used when the Survey 

project is created. 

Items under the Default Preferences dialog related to creating the .prj file for use with GEOPAK Survey: 

1) Name: This field is used as the name for the .prj file. For this example, the name would be 

nnnnn_Survey, where nnnnn = the PID number for the project. 

2) Directory: This field is used to define the directory where the .prj file is created. The directory 

would be set to the \survey folder for the project. 

3) Job Directory: This field is used to define the directory where the .gpk file for the project will be 

stored. The .gpk file shall be shared between the GEOPAK Road users and the GEOPAK 

Survey users. The Job Directory should be set to the \geopak folder for the project. 

4) Global Working Directory: This field is used to define the folder used as the parent folder for all 

other GEOPAK Survey software functions. The Global Working Directory should be set to the 

\survey folder for the project. 


400 PLOTTING 

401 General 

401.1 General 


ODOT uses pen tables that are applied to the graphical elements when the design file is plotted. This 

can be thought of as a type of filter. The pen tables translate various elements in the design file to the 

final output version that can be used to map MicroStation line weights to specific pen sizes or 

thicknesses. An example would be mapping all WT=0 lines to 0.006-inch and WT=1 to a 0.014-inch line 

thickness to differentiate the design file elements’ weights on the plotted sheet. Line thickness should be 

plotted as shown in the table below: 

Element Weight Thickness (approximate inches) 

WT= 0 0.006” 

WT=1 0.014” 

WT=2 0.026” 

WT=3 0.036” 

WT=4 0.046” 

WT=5 0.056” 

WT=6 0.066” 

WT=7 0.076” 

WT=8 0.086” 

WT=9 0.096” 

WT>=10 0.106” 

Due to the variation in plotting accuracy of various printers, the thickness’ shown in the table above can 

be modified as deemed necessary to achieve the desired results. 

All elements should be plotted black, except for the major and minor grid lines on cross-section or profile 

sheets. The major and minor grid lines on the cross-section and profile sheets should be prioritized so 

that the details will be plotted on top of the grids. Cross section and profile grids should be plotted as 

shown in the Location and Design Manual, Volume 3, Figure 1202-1. 

Standard MicroStation pen tables and IPLOT design scripts are available on ODOT’s Pen Tables web 

page. The files available for download include user documentation defining the pen table functions. The 

Pen tables and Design Scripts were created to match ODOT’s current plotting standards. 




IPLOT Design Scripts and MicroStation pen tables and Printer Driver Configuration files for use with 

MicroStation V8i and are located in the following directories for ODOT users: 

• ODOTstd\V8istd\iplot\ - IPLOT 

• ODOTstd\V8istd\pltcfg\ - MicroStation 

The following plotting files for IPLOT and MicroStation are: 

• Half.pen - for 8-1/2”x11” or 11”x17” Prints - IPLOT 

• Halfc.pen - for 8-1/2”x11” or 11”x17” Color Prints - IPLOT 

• Full.pen - for 22”X34” Prints - IPLOT 

• Fullc.pen - for 22”X34” Color Prints – IPLOT 

• ODOTV8i_Full.pltcfg – for 22”x34” Prints – MicroStation 

• ODOTV8i_Half.pltcfg – 11”x17” Prints - MicroStation 

• ODOTV8i_Pen.tbl - for 22”X34” & 11”x17” Prints - MicroStation 

401.2.1 Priority 

The plotting files no longer contain any priority settings. Plotting priorities are determined by the 

MicroStation level and the assigned element priority values in the ODOT_Levels.dgnlib. 

401.2.2 Transparency 

The use of Transparency for plotting is currently under development and will be implemented at a future 

date. 


401.2.3 Shading 

The following are options to shade elements in a plan sheet: 

• Shading Filled Shapes – is an option to highlight specific areas on the plan sheet. 


Shading levels were created to fill shapes with varying shades of Gray. The half.pen, full.pen and 

ODOTV8i_Pen.tbl plot and fill shapes based on the following shading levels: 

SC_Shading1 – uses Color = 41 



• Shading Reference(s) – is a method to fade the entire Reference into the background. 

To gray shade a reference, the Logical Name must begin with gray, for example gray1, gray2, 

etc. Color 39 (RGB Value = 128, 128, 128) is used to gray shade references. When plotting a 

reference using a logical name beginning with gray, the half.pen, full.pen and ODOTV8i_Pen.tbl 

will gray shade the entire reference. 

401.2.4 Masking 

Masking is an option to hide specific areas on a plan sheet. No elements will show underneath. 

The Masking level plots all elements or filled shapes as White to mask any elements underneath. The 

half.pen, full.pen and ODOTV8i_Pen.tbl plot and fill shapes are based on the following masking level: 

SH_Masking – uses Color = 255 (Background Color) 

Note: To create a border around the shape change the color and place the shape using the Fill 

Type set to Outlined. 

401.2.5 Issues with Pen Tables encountered with V8i plotting: 

• When plotting a title sheet with a corporation boundary in the title map using V8i, the corporation 

boundary area would plot solid black. This area is now a Type 2 Grouped Hole in MicroStation 

V8i, where previously it was a Type 2 Unnamed Cell in MicroStation V8 2004 Edition. The 

previous V8 pen tables would not process a Grouped Hole element in V8i. Therefore, the pen 

tables were modified to accommodate this change and plot the title maps correctly. 

• A TR has been filed with Bentley Plotting Support regarding this issue. Future ODOT CADD 

Updates will include revisions to the pen tables pending Bentley’s fix for the Type 2 Grouped 

Hole. 



500 ELECTRONIC SUBMISSIONS 

501 Information Exchange and Electronic Submissions 

501.1 General 

All CADD data submitted or exchanged with ODOT shall conform to the requirements of this manual. 

Organizations exchanging CADD data with ODOT are responsible for ensuring they are using the current 

version of these requirements and all ODOT MicroStation/GEOPAK files. 

502 File Format 

502.1 General 

All CADD information to be submitted or exchanged with the Department shall be developed per the 

current MicroStation and GEOPAK version listed on the CADD Engineering Standards Web page, unless 

otherwise specified in the Scope of Services. This requirement ensures that ODOT receives a product 

that is immediately usable on ODOT’s CADD system. 

The content of all final submission MicroStation design files delivered to the Department shall match the 

content of the printed Mylar sheets and/or Tiff Images. Editing the Mylar’s and/or Tiff Images without 

updating the CADD files shall not be permitted. 

All projects are required to submit the following files regardless of the PDP (Old or New) the project is 

scoped to follow: 

• Existing Plans (Roadway and Bridge) 

• Designer Office Calculations (such as Pavement, Earthwork, and Structure Quantities) 

If the scope of services requires supplemental engineering data files (ie. Hec-Ras, etc.), the Department 

requires that all supplemental engineering data files be delivered in the native format of the system used 

to produce it. Reference the respective Technical Manual (i.e. Bridge Design Manual, etc.) for software 

requirements. 

Any questions regarding items not included in this manual, or interpretations of this manual should be 

addressed to the CADD Section in the Central Office, Office of CADD and Mapping Services. 

Consultants, contractors, and suppliers should direct questions regarding interpretations of this manual to 

the CADD Section through the ODOT Project Manager/ Job Manager/ Consultant Manager, as 

applicable. 


502.2 Saved View 


Whenever files are submitted or exchanged with the Department, the MicroStation command Saved View 

shall be initiated to capture all reference file and level settings in place at the time of final plotting. Saving 

a view allows you to quickly recall a view with specific attributes. 

From the MicroStation Utilities menu, select Saved Views to access the dialog shown below. 

• Select the Create Saved View command, 

• Select the Method: From View or From 2- 

Points, 

• Name: the view Final Print, 

• Select the Source View by placing a Data point in 

the view window. 



503 Project Index File 

503.1 General 

Whenever files are submitted or exchanged with the Department, a Project Index file in Microsoft Excel 

format shall be provided containing design file and coordinate geometry information as shown in Figure 

503-1 and Figure 503-2. The Project Index file is also required for internal projects when the project is 

archived. 

ODOT provides a custom program, ODOT_ProjectIndex.mvba that can be used to create the Project 

Index File. This program, including documentation, is available on the ODOT CADD Standards Website. 

The program automatically establishes hyperlinks to facilitate opening design files by selecting the file 

name within the Project Index File. The Hyperlink Base directory may also be updated to specify the 

location where the project is located. See the program documentation for information regarding updates 

to the Hyperlink base directory. 

The program is based on the ODOT standard file structure and file naming convention listed in this 

manual. Any modifications to the file structure or file names will render the program nonfunctional. 

Plan sheet descriptions should include station ranges where appropriate. 

The Project Index file shall be stored in the \admin\spreadsheets directory using the following naming 

convention: 

nnnnnIndex.xls 

nnnnn = Five digit PID Number 

Figure 503-1 


Figure 503-2 

504 CADD File Requirements for Design and Construction 

504.1 General 


Section 1503 of The Location and Design Manual, Volume Three – Highway Plans details the file types 

required for CADD and electronic files submitted to the Department for Minimal, Minor, and Major projects 

as defined by the Old Project Development Process (PDP) Manual and Paths 2, 3, 4, and 5 for the New 

PDP. When electronic files are required, the files shall conform to the requirements detailed throughout 

this manual with the additional requirements specified in this section. 

504.2 Horizontal Alignment ASCII Reports 

When horizontal alignment reports in ASCII text format are required, the following information shall be 

included in the ASCII reports: 

• A listing of all COGO elements contained in the chain. 

• Northing and Easting coordinates, and stations for all horizontal key points (PI, PC, PT, SC, CS, 

CC, etc.) 

• Bearings and distances between all key points. 

• Curve and Spiral data containing the information defined in the Location and Design Manual, 

Volume 3 - Highway Plans, Figures 1303-1 and 1303-2. 

• Station Equation values and coordinates. 

• All stations, distances, and coordinates shall be shown to three decimal places. 

• All bearings shall be shown to one tenth of one second. 



The horizontal alignment reports shall be stored in the \geopak\output directory using the following file 

naming convention: 

nnnnn_Chain_Name.txt 


Name = The GEOPAK COGO Chain name 

Example: 12345_Chain_CLPS185.txt 

Each horizontal alignment report shall be stored as a separate ASCII text file. 

The GEOPAK COGO command Describe Chain can be used to generate the ASCII report files 

containing the required information for each chain. From the GEOPAK Coordinate Geometry dialog, 

select Element > Chain > Utility to access the dialog shown below. Select the desired alignment, and 

then select the Describe command to generate the alignment description. 

The results of the Describe Alignment command can be saved in an ASCII text file by selecting View > 

Command Output > Save Content As… as shown below. 



A sample ASCII report file as generated by the GEOPAK Describe Chain command is shown below. 


Spiral PS18512B Type 1 Spiral Element 

Angle 6° 27' 00.0" (LT) P 2.016 BK S 1° 03' 01.0" W 

LS 215.000 K 107.455 AH S 5° 23' 59.0" E 

R 954.930 LT 143.429 Defl 2° 08' 59.2" 

YS 8.060 ST 71.753 Deg 6° 00' 00.0" 

XS 214.728 LC 214.879 

Spiral Coordinates 

*------------------* 

Point North East Station 

----- ------------------- ------------------- ------------------- 

TS 721,044.089 1,360,571.641 60+28.872 

PI 720,900.685 1,360,569.012 61+72.300 

SC 720,829.250 1,360,575.764 62+43.872 

CC 720,919.112 1,361,526.456 

Circular Section 

Curve Data 

*----------* 

Curve PS18512 

P.I. Station 67+07.858 N 720,367.323 E 1,360,619.427 

Delta = 51° 49' 44.0" (LT) 

Degree = 6° 00' 00.0" 

Tangent = 463.986 

Length = 863.815 

Radius = 954.930 

External = 106.755 

Long Chord = 834.663 

Mid. Ord. = 96.020 

P.C. Station 62+43.872 N 720,829.250 E 1,360,575.764 

P.T. Station 71+07.687 N 720,116.172 E 1,361,009.564 

C.C. N 720,919.112 E 1,361,526.456 

Back = S 5° 23' 59.0" E 

Ahead = S 57° 13' 43.0" E 

Chord Bear = S 31° 18' 51.0" E 

Spiral Ahead 

Spiral PS18512A Type 2 Spiral Element 

Angle 6° 27' 00.0" (LT) P 2.016 BK S 57° 13' 43.0" E 

LS 215.000 K 107.455 AH S 63° 40' 43.0" E 

R 954.930 LT 143.429 Defl 2° 08' 59.2" 

YS 8.060 ST 71.753 Deg 6° 00' 00.0" 

XS 214.728 LC 214.879 

Spiral Coordinates 

*------------------* 

Point North East Station 

----- ------------------- ------------------- ------------------- 

CS 720,116.172 1,361,009.564 71+07.687 

PI 720,077.333 1,361,069.896 71+79.440 

ST 720,013.736 1,361,198.455 73+22.687 

CC 720,919.112 1,361,526.456 

------------------------------------------------------------------------------ 

Ending SCS PS18512 description 

End Region 1 

Equation: Sta 73+22.687 (BK) = Sta 74+15.378 (AH) ---------------- 

Begin Region 2 

Point CS01 N 720,013.736 E 1,361,198.455 Sta 74+15.378 

Course from CS01 to PI13 S 63° 40' 43.0" E Dist 595.782 

Point PI13 N 719,749.563 E 1,361,732.466 Sta 80+11.160 

=============================================================================== 

Ending chain CLPS185 description 


504.3 Vertical Alignment ASCII Reports 


When vertical alignment reports in ASCII text format are required, the following information shall be 


• Station and elevation for all vertical alignment key-points (VPI, VPC, VPT, etc.) 

• Entrance and exit grades for vertical curves. 

• Vertical curve length. 

• K-Value for each vertical curve. 

• Stopping sight distance for crest vertical curves. 

• Station equations. 

• All stations, distances, grades, and elevations shall be shown to three decimal places. 

The vertical alignment reports shall be stored in the \geopak\output directory using the following file 


nnnnn_Profile_Name.txt 


Name = The GEOPAK COGO Chain name 

Example: 12345_Profile_PS185P.txt 

Each vertical alignment report shall be stored as a separate ASCII text file. 

The GEOPAK Print Profile command can be used to generate an ASCII report containing the required 

information. From the GEOPAK Coordinate Geometry dialog, select Element > Profile > Utility to access 

the dialog shown below, select the desired profile, and then select Print. 



To save the ASCII report, select View > Command Output > Save Content As… as shown below. 

A sample ASCII report file as generated by the GEOPAK Print Profile command is shown on the 

following page. 



Each horizontal alignment shall be stored in a separate LandXML report file. GEOPAK does not provide 

the capability to export profiles independently from the chains, therefore the LandXML report for a given 

horizontal alignment shall also contain the associated vertical alignment as shown in the following 

example. 

To generate a LandXML 1.2 report using GEOPAK, select File > Export LandXML 1.2 Geometry from 

the GEOPAK Coordinate Geometry dialog as show below. 

Use the PID number for the Project Name. The Description is optional. Select the desired Chain and 

Profile to export as shown in the example below. 

It is not permissible to export all Chains and Profiles in a single LandXML report file. 


504.5 LandXML Reports for Triangle Models 


When LandXML reports are required for existing and/or proposed triangle model, the reports shall be 

stored in the \geopak\output directory using the following file naming convention: 

nnnnn_TIN_Name.xml 


Name = The TIN model name 

Example: 12345_TIN_12345EXGR.xml 

Each triangle model shall be stored in a separate LandXML report file. 

To generate a LandXML 1.2 triangle model report using GEOPAK, select the LandXML Export icon as 

show below. 

Select the TIN File to export. 

Use the PID Number for the Project Name. 

The Description is optional. 

It is not permissible to append multiple triangle models to the same xml output file. 



504.6 Monumentation Reports 

When monumentation reports in comma separated value ASCII text format are required, the following 

information shall be included in the ASCII reports: 

• COGO Point Number, Feature Code, Northing, Easting, Elevation, Chain Name (used for the 

station and offset reference), Station, and Offset. 

• The values for the Northing, Easting, Elevation, Station, and Offset shall be reported to three 

decimal places. 

Monumentation reports shall be stored in the \geopak\output directory using the following file naming 

convention: 

nnnnn_Monuments_ChainName.csv 


ChainName = The name of the COGO chain used to generate the station and offset 

values for the monument report. 

Example: 12345_Monuments_CLPS185.csv 

Monuments for each centerline chain shall be stored in a separate ASCII file. 

The following ODOT standard field codes are used to denote various types of monuments: 

Field Code Description 

Field Code Description 

AXLE Axle Found IPINS Iron Pin Set 

BM Benchmark Found IPIPE Iron Pipe Found 

CMON Concrete Monument Found IPIPES Iron Pipe Set 

CMONS Concrete Monument Set MAG Mag Nail Found 

CNPT Miscellaneous Control Point MAGS Mag Nail Set 

CSF Corner Stone Found MONBOX Monument Box Found 

CUT Cross Cut Found MONBOXS Monument Box Set 

CUTS Cross Cut Set MSPK Mine Spike Found 

DRILLH Drill Hole Set MSPKS Mine Spike Set 

DRILLS Drill Hole Set PK PK Nail Found 

GOVCON Government Control Point Found PKS PK Nail Set 

GOVCONS Government Control Point Set RSPK Railroad Spike Found 

HUB Tacked Hub Found RSPKS Railroad Spike Set 

HUBSET Tacked Hub Set SCOR Section Corner 

IPIN Iron Pin Found TBAR T-Bar Found 

A custom visual basic application, available from the ODOT website, has been developed by ODOT to 

generate the monument report. 

This application must be run from within MicroStation with GEOPAK active and the GEOPAK Working 

Directory set to specify the location of the .gpk file. Key-in the following command to run the application: 

vba load ODOT_Monument_Report.mvba;vba run ODOTMonuments 


The dialog shown below will appear. 

The ODOT Monument Report has the following options: 


Job number 

Select the Job Number for the GEOPAK COGO Database that contains the monument 

points. 

Chain 

Select the GEOPAK COGO Chain that will be used to generate the Station and Offset 

references contained in the completed monument report. 

Begin Station/End Station 

With the station range option toggled off, all monument points found in the selected Job 

Number will be included in the monument report. If a given monument point falls outside 

the limits of the selected Chain, the report will show values of “NA” for the Chain, Station, 

and Offset. 

With the station range option toggled on, only monument points that are found within the 

specified station limits will be included in the report file. 



Left Offset/Right Offset 

The Left/Right Offset values are only available if the station range option is toggled on. 

With the Left/Right Offset values toggled on, only monument points that fall within the 

specified station limits and the offset limits will be included in the monument report. 

With the Left/Right Offset values toggled off, all monument points within the specified 

station limits will be included in the monument report regardless of how far they are offset 

from the selected Chain. 

Monument Features Found in GPK 

Only the monument types found in the currently selected Job Number are available for 

export to the report file. Toggle on/off the monument types that you wish to export to the 

report file. 

Report File Name 

Key-in the full path and the name for the report file to be generated. The Select button 

may also be used to select the path and key in the name for the report file to be 

generated. 

Generate Report 

Select this button to initiate report generation. The report is an ASCII text file in csv 

(comma separated values) format. A sample report, opened with Microsoft Excel, is 

shown below. The first line of the report file designates the content of each column in the 

report file. 


504.7 Cross Section Staking Reports 


When cross section staking reports in ASCII text format are required, the following information shall be 


• Station, Northing, Easting, Elevation, and Offset for each vertex of the proposed finished 

grade from the left edge to the right edge of each cross section along the surface of the 

pavement. 

• All values shall be reported to three decimal places. 

Cross section staking reports shall be stored in the \geopak\output directory using the following file 


nnnnn_XS_ChainName.txt 


ChainName = The name of the COGO chain used to extract the cross sections. 

Example: 12345_XS_CLPS185.txt 

Cross section reports for each centerline chain shall be stored in a separate ASCII file. 

The GEOPAK Cross Section Multi-Line report can be used to generate the required information. Take the 

following steps to generate the report. 

Select Cross Section Reports as shown below. 



The XS Reports dialog shown below is opened. 

Select Multi-Line to access the Multi-Line Report dialog shown below. 



Select the symbology box to the right of the XS Elements label to identify the cross section elements that 

make up the proposed finished grade. 

If ODOT criteria files are used to generate the proposed cross section graphics, the following levels 

should be selected within the Candidate Elements dialog: 

XS_P_Ditch_Bottom 

XS_P_Finished_Grade 

XS_P_Finished_Grade_Seeded 

XS_P_Pavt_Surface 

XS_P_Shoulder_Surface 

Note: Additional levels may need to be selected depending on how the cross sections graphics were 

drawn. Use the Match button on the Candidate Elements dialog to select the desired cross section 

elements. 

Set the Output Format to X,Y,ELEV,OFFSET. 

Check on the 5-Point option. 

Key-in the name of the ASCII File for the cross section report. 

Select the Add icon to the right of the Multi-Line Report dialog to add the report to the list. The report will 

show up in the list box in the center of the dialog as shown in the example on the previous page. 



Select the Apply button to generate the report. An example of the output for one cross section station is 

shown below. 

Station X Y Z Offset 

1360970.473 720238.200 970.520 -75.863 

70+00.000 R 1 1360964.235 720230.561 967.232 -66.000 

1360963.602 720229.786 967.232 -65.000 

1360962.970 720229.012 967.232 -64.000 

1360959.175 720224.364 968.732 -58.000 

1360953.483 720217.393 969.452 -49.000 

1360952.850 720216.618 969.532 -48.000 

1360950.320 720213.520 969.864 -44.000 

1360942.731 720204.225 970.860 -32.000 

1360935.141 720194.930 971.856 -20.000 

1360933.560 720192.993 972.064 -17.500 

1360928.816 720187.184 971.986 -10.000 

1360928.184 720186.410 971.906 -9.000 

1360922.543 720179.501 969.676 -0.081 

1360920.013 720176.403 969.676 3.919 

1360916.799 720172.467 970.946 9.000 

1360916.167 720171.692 971.026 10.000 

1360909.842 720163.947 971.856 20.000 

1360902.253 720154.651 972.852 32.000 

1360894.663 720145.356 973.848 44.000 

1360893.398 720143.807 974.014 46.000 

1360892.133 720142.258 973.994 48.000 

1360891.501 720141.484 973.914 49.000 

1360885.808 720134.512 973.194 58.000 

1360862.284 720105.702 960.795 95.194 

1360860.387 720103.378 959.795 98.194 

1360859.754 720102.604 959.795 99.194 

1360859.122 720101.829 959.795 100.194 

1360857.906 720100.340 960.757 102.117 

504.8 Submission of Electronic Files to Central Office 

Section 1503 of The Location and Design Manual, Volume Three – Highway Plans details the plan 

documents required for electronic submission, which will be made available to contractors during ODOT’s 

construction contract bidding process. The District shall review the electronic documents submitted to the 

Department to ensure the required CADD and ASCII files are provided. It is the District’s responsibility to 

submit these files to Central Office as per Section 1503.4 of The Location and Design Manual, Volume 

Three – Highway Plans, and as detailed below. 

The District shall consolidate the electronic files to be provided to bidders into a .zip file to be submitted to 

the Office of Contracts. The .zip file shall conform to the following file naming convention: 

nnnnn.zip 


Example: 12345.zip 



The Office of Contracts will post the electronic files on the ODOT website for contractor access during the 

bidding process. The District is responsible for uploading the .zip file to the “Reference Only” folder on 

the following Central Office server: 

\\CTRFS100\D##$ 

The District can map a network drive to the Central Office Server using the following codes: 

D1 = \\CTRFS100\D01$ D7 = \\CTRFS100\D07$ CO = \\CTRFS100\CEN$ 

D2 = \\CTRFS100\D02$ D8 = \\CTRFS100\D08$ 





A separate folder is set up for each District and Central Office. Each folder is set up with write 

permissions for the corresponding District or Central Office with the exception of the TEMP folder, which 

has been set up with write access for everyone. 

Note: The electronic files submitted to the District from an external consultant may include additional files 

that should not be provided to bidders via the Office of Contracts. The District shall ensure that the .zip 

file provided to the Office of Contracts contains only the required documents as specified in section 1503 

of The Location and Design Manual, Volume Three – Highway Plans. A checklist of required files is 

provided in Appendix E. 

Care must be taken to ensure that the Save full path info option is toggled on when adding files to the 

.zip file as shown in the example below. This will ensure that all design file reference attachments are 

maintained when the files are unzipped by the recipients. 


Appendix A – CADD Information Table Revised January 20, 2012 

By Level Attributes 

AP_X_Lights 

Level Name Description 

Color 

Style 

AP – AIRPORT - EXISTING: 

Airport Marker Lights 3 0 0 0 -100 

CELLS PLACED ON LEVEL AP_X_Lights: 

Weight 

Transparency 

Priority 

Cell Name Cell Library Name 

Airport Marker Light - - - 0 -100 AIRLIGHT ODOT_Symbols.cel C 

AP_X_Markings Airport Pavement Markings 0 0 0 0 -100 

AP_X_Misc 

Airport Miscellaneous Features 0 0 0 0 -100 

CELLS PLACED ON LEVEL AP_X_Misc: 

Airport Windsock - - - 0 -100 WINDSOCK ODOT_Symbols.cel C 

AP_X_Runway Airport Runway or Taxiway 16 5 0 0 -100 

AP_X_Text Airport Text 0 0 0 0 500 

BD – BUILDINGS - EXISTING: 

BD_X_Building Any type of Building 13 0 0 0 -100 

BD_X_Canopy Any type of Canopy/Awning 4 2 0 0 -100 

BD_X_Porch_or_Deck Porch or Deck 0 0 0 0 -100 

BD_X_Text Building Text 0 0 0 0 500 

BD – BUILDINGS - PROPOSED: 

BD_P_Building Any type of Building 7 0 1 0 100 

BD_P_Text Building Text 0 0 1 0 500 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

NOTE: * Indicates Not By Level Page 1 of 108




Color 

Style 

BR – BRIDGE - EXISTING: 

Weight 

Transparency 

Priority 


BR_X_Beam_Centerline Beam Centerline 5 bcenterline 0 0 -100 C 

BR_X_Beam_Const_Joint Beam Construction Joint 5 bconstruction 0 0 -100 C 

BR_X_Beam_Hidden Beam Hidden Line 5 bexisting 0 0 -100 C 

BR_X_Beam_Object Beam Object Line 5 bexisting 1 0 -100 C 

BR_X_Beam_Reinforcing Beam Reinforcing (rebar, pre-stress) 5 brebarex 0 0 -100 C 

BR_X_Beam_Stl_Det 

Beam Steel Details 

(Shear studs, Connections, etc.) 

5 bexisting 0 0 -100 C 

BR_X_Beam_Stl_Det_Hidden Beam Steel Details Hidden 5 bexisting 0 0 -100 C 

BR_X_Beam_Text Beam Text and Dimensions 0 0 1 0 500 

BR_X_Brg_Centerline Bearing Centerline 5 bcenterline 0 0 -100 C 

BR_X_Brg_Const_Joint Bearing Construction Joint 5 bconstruction 0 0 -100 C 

BR_X_Brg_Pad_Hidden Bearing Pad Hidden 5 bexisting 0 0 -100 C 

BR_X_Brg_Pad_Object Bearing Pad Object 5 bexisting 1 0 -100 C 

BR_X_Brg_Stl_Det 

Bearing Steel Details 

(load plate, post, etc.) 


BR_X_Brg_Stl_Det_Hidden Bearing Steel Details Hidden 5 bexisting 0 0 -100 C 

BR_X_Brg_Text Bearing Text and Dimensions 0 0 1 0 500 

BR_X_Det_Centerline 

BR_X_Det_Const_Joint 

BR_X_Det_Hidden 

BR_X_Det_Object 

BR_X_Det_Text 

Centerline Details not covered by 

the other Bridge Levels 

Construction Joint Details not covered 

by the other Bridge Levels 

Hidden Details not covered by the other 

Bridge Levels 

Object Details not covered by the other 

Bridge Levels 

Text Details not covered by the other Bridge 

Levels 

5 bcenterline 0 0 -100 C 

5 bconstruction 0 0 -100 C 



0 0 1 0 500 

BR_X_Dia_Centerline Diaphragm Centerline 5 bcenterline 0 0 -100 C 

BR_X_Dia_Const_Joint Diaphragm Construction Joint 5 bconstruction 0 0 -100 C 

BR_X_Dia_Hidden Diaphragm Hidden Line 5 bexisting 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

BR – BRIDGE – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


BR_X_Dia_Object Diaphragm Object Line 5 bexisting 1 0 -100 C 

BR_X_Dia_Reinforcing Diaphragm Reinforcing 5 brebarex 0 0 -100 C 

BR_X_Dia_Stl_Det 

Diaphragm Steel Details\ 

(Connections, plates, etc.) 


BR_X_Dia_Stl_Det_Hidden Diaphragm Steel Details Hidden 5 bexisting 0 0 -100 C 

BR_X_Dia_Text Diaphragm Text and Dimensions 0 0 1 0 500 

BR_X_Drain_Centerline Bridge Drainage Centerline 5 bcenterline 0 0 -100 C 

BR_X_Drain_Hidden Bridge Drainage Hidden 5 bexisting 0 0 -100 C 

BR_X_Drain_Object Bridge Drainage Object 5 bexisting 0 0 -100 C 

BR_X_Drain_Text Bridge Drainage Text 0 0 1 0 500 

BR_X_Gen_Approach_Slab General Bridge Approach Slab 5 bexisting 1 0 -100 C 

BR_X_Gen_Approach_Slab_Hidden General Bridge Approach Slab-Hidden 5 bexisting 0 0 -100 C 

BR_X_Gen_Ground_Slope General Bridge Ground Slope 5 bexisting 0 0 -100 C 

BR_X_Gen_Hatch 

General Bridge Hatching 

(Architectural patterns, etc.) 


BR_X_Gen_Joint_Filler General Bridge Joint Filler (PEJF, etc.) 5 bexisting 0 0 -100 C 

BR_X_Gen_NonPerf_Pipe General Bridge NonPerforated Pipe 5 bexisting 0 0 -100 C 

BR_X_Gen_Perforated_Pipe General Bridge Perforated Pipe 5 bexisting 0 0 -100 C 

BR_X_Gen_Porous_Backfill General Bridge Porous Backfill 5 bexisting 0 0 -100 C 

BR_X_Gen_Sheet_Piling General Bridge Sheet Piling 5 bexisting 0 0 -100 C 

BR_X_Gen_Slope_Protection General Bridge Slope Protection 5 bexisting 1 0 -100 C 

BR_X_Gen_Text General Bridge Text and Dimensions 0 0 1 0 500 

BR_X_Gen_Utilities 

General Bridge Utilities 

(Utilities on the Bridge) 


BR_X_Gen_Utilities_Hidden General Bridge Utilities Hidden 5 bexisting 0 0 -100 C 

BR_X_Gen_Water_Elevation General Bridge Water Elevation 5 bexisting 0 0 -100 C 

BR_X_Gen_Waterproofing 

General Bridge Waterproofing 

(Neoprene sheeting, sealing, etc.) 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





BR_X_Prestress_Centerline 

BR_X_Prestress_Det 

BR_X_Prestress_Det_Hidden 

BR_X_Prestress_Hidden 

BR_X_Prestress_Object 

BR_X_Prestress_Text 

Pre-Stressing Centerline Details for either 

Pre-Tensioning or Post Tensioning 

Pre-Stressing Details for either 


Pre-Stressing Hidden Details for either 




Pre-Stressing Object Details for either 


Pre-Stressing Text Details for either 


Color 

Style 


Weight 

Transparency 

Priority 


5 bcenterline 0 0 -100 C 

5 0 0 0 -100 




0 0 1 0 500 

BR_X_Rail_Centerline Rail Centerline 5 bcenterline 0 0 -100 C 

BR_X_Rail_Const_Joint Rail Construction Joint 5 bconstruction 0 0 -100 C 

BR_X_Rail_Hidden Rail Hidden Line 5 bexisting 0 0 -100 C 

BR_X_Rail_Object Rail Object Line 5 bexisting 1 0 -100 C 

BR_X_Rail_Reinforcing Rail Reinforcing 5 brebarex 0 0 -100 C 

BR_X_Rail_Stl_Det Rail Steel Details (connections, etc.) 5 bexisting 0 0 -100 C 

BR_X_Rail_Stl_Det_Hidden Rail Steel Details Hidden 5 bexisting 0 0 -100 C 

BR_X_Rail_Text Rail Text and Dimensions 0 0 1 0 500 

BR_X_Slab_Centerline Slab Centerline 5 bcenterline 0 0 -100 C 

BR_X_Slab_Const_Joint Slab Construction Joint 5 bconstruction 0 0 -100 C 

BR_X_Slab_Hidden Slab Hidden Line 5 bexisting 0 0 -100 C 

BR_X_Slab_Object Slab Object Line 5 bexisting 1 0 -100 C 

BR_X_Slab_Reinforcing Slab Reinforcing (rebar, pre-stress) 5 brebarex 0 0 -100 C 

BR_X_Slab_Stl_Det Slab Steel Details (anchor plates, etc.) 5 bexisting 0 0 -100 C 

BR_X_Slab_Stl_Det_Hidden Slab Steel Details Hidden 5 bexisting 0 0 -100 C 

BR_X_Slab_Text Slab Text and Dimensions 0 0 1 0 500 

BR_X_Sub_Backwall Substructure Backwall 5 bexisting 1 0 -100 C 

BR_X_Sub_Centerline Substructure Centerline 5 bcenterline 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 


Weight 

Transparency 

Priority 


BR_X_Sub_Const_Joint Substructure Construction Joint 5 bconstruction 0 0 -100 C 

BR_X_Sub_Deep_Centerline Substructure Deep Foundation Centerline 5 bcenterline 0 0 -100 C 

BR_X_Sub_Deep_Const_Joint 

BR_X_Sub_Deep_Hidden 

BR_X_Sub_Deep_Object 

Substructure Deep Foundation Construction 

Joint 

Substructure Deep Foundation Hidden 

(H-Piles, Drilled Shaft, etc.) 

Substructure Deep Foundation Object 

(H-Piles, Drilled Shaft, etc.) 

5 bconstruction 0 0 -100 C 



BR_X_Sub_Deep_Reinforcing Substructure Deep Foundation Reinforcing 5 brebarex 0 0 -100 C 

BR_X_Sub_Deep_Text 

Substructure Deep Foundation Text and 

Dimensions 

0 0 1 0 500 

BR_X_Sub_Foot_Centerline Substructure Footing Centerline 5 bcenterline 0 0 -100 C 

BR_X_Sub_Foot_Const_Joint Substructure Footing Construction Joint 5 bconstruction 0 0 -100 C 

BR_X_Sub_Foot_Hidden 

BR_X_Sub_Foot_Object 

Substructure Footing Hidden 

(Spreadfooting, Pile cap, etc) 

Substructure Footing Object (Spreadfooting, 

Pile cap, etc) 



BR_X_Sub_Foot_Reinforcing Substructure Footing Reinforcing 5 brebarex 0 0 -100 C 

BR_X_Sub_Foot_Text Substructure Footing Text and Dimensions 0 0 1 0 500 

BR_X_Sub_Hidden 

BR_X_Sub_Object 

Substructure Hidden 

(Abutment, Pier, retaining wall) 

Substructure Object 

(Abutment, Pier, retaining wall) 



BR_X_Sub_Reinforcing Substructure Reinforcing 5 brebarex 0 0 -100 C 

BR_X_Sub_Text Substructure Text and Dimensions 0 0 1 0 500 

BR_X_SV_Abut 

Bridge Abutment Face and Wingwall 

(as Surveyed or Aerial Mapping) 

8 3 0 0 -100 

BR_X_SV_Abut_Text Bridge Abutment Face and Wingwall Text 0 0 0 0 500 

BR_X_SV_Beam_Seat 

BR_X_SV_Bottom_of_Beam 

Beam Seat Elevation 


Bottom of Beam 


8 0 0 0 -100 

8 3 0 0 -100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 


BR_X_SV_Bottom_of_Beam_Text Bottom of Beam Text 0 0 0 0 500 

BR_X_SV_Deck_Floor 

Bottom of Bridge Deck 


8 3 0 0 -100 

BR_X_SV_Deck_Floor_Text Bottom of Bridge Deck Text 0 0 0 0 500 

BR_X_SV_Deck_Top 

Top of Bridge Deck 


8 3 0 0 -100 

BR_X_SV_Deck_Top_Text Top of Bridge Deck Text 0 0 0 0 500 

BR_X_SV_Pier 

BR_X_SV_Pier_Cap_Bottom 

Perimeter of Pier 


Pier Cap Bottom 


8 3 0 0 -100 

8 3 0 0 -100 

BR_X_SV_Pier_Cap_Bottom_Text Pier Cap Bottom Text 0 0 0 0 500 

BR_X_SV_Pier_Cap_Top 

Pier Cap Top 


8 3 0 0 -100 

BR_X_SV_Pier_Cap_Top_Text Pier Cap Top Text 0 0 0 0 500 

BR_X_SV_Pier_Text Perimeter of Pier Text 0 0 0 0 500 

BR_X_SV_Rail 

Top of Bridge Rail 


8 3 0 0 -100 

BR_X_SV_Rail_Text Top of Bridge Rail Text 0 0 0 0 500 

Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

BR – BRIDGE - PROPOSED: 

Weight 

Transparency 

Priority 


BR_P_Beam_Centerline Beam Centerline 4 bcenterline 0 0 100 C 

BR_P_Beam_Const_Joint Beam Construction Joint 1 bconstruction 1 0 100 C 

BR_P_Beam_Hidden Beam Hidden Line 0 bhiddenpr 1 0 100 C 

BR_P_Beam_Object Beam Object Line 0 0 2 0 100 

BR_P_Beam_Reinforcing Beam Reinforcing (rebar, pre-stress) 6 brebarpr 1 0 100 C 

BR_P_Beam_Stl_Det 

Beam Steel Details 

(Shear studs, connections, etc.) 

3 0 1 0 100 

BR_P_Beam_Stl_Det_Hidden Beam Steel Details Hidden 3 bhiddenpr 0 0 100 C 

BR_P_Beam_Text Beam Text and Dimensions 0 0 1 0 500 

BR_P_Brg_Centerline Bearing Centerline 4 bcenterline 0 0 100 C 

BR_P_Brg_Const_Joint Bearing Construction Joint 1 bconstruction 1 0 100 C 

BR_P_Brg_Pad_Hidden Bearing Pad Hidden 7 bhiddenpr 1 0 100 C 

BR_P_Brg_Pad_Object Bearing Pad Object 7 0 2 0 100 

BR_P_Brg_Stl_Det 

Bearing Steel Details 

(Load plate, post, etc.) 

3 0 1 0 100 

BR_P_Brg_Stl_Det_Hidden Bearing Steel Details Hidden 3 bhiddenpr 0 0 100 C 

BR_P_Brg_Text Bearing Text and Dimensions 0 0 1 0 500 

BR_P_Det_Centerline 

BR_P_Det_Const_Joint 

BR_P_Det_Hidden 

BR_P_Det_Object 

BR_P_Det_Text 

Centerline Details not covered by the 

other Bridge Levels 

Construction Joint Details not covered by 

the other Bridge Levels 

Hidden Details not covered by the other 

Bridge Levels 

Object Details not covered by the other 

Bridge Levels 

Text Details not covered by the other Bridge 

Levels 

4 bcenterline 1 0 100 C 

1 bconstruction 1 0 100 C 

2 bhiddenpr 1 0 100 C 

2 0 2 0 100 

0 0 1 0 500 

BR_P_Dia_Centerline Diaphragm Centerline 4 bcenterline 0 0 100 C 

BR_P_Dia_Const_Joint Diaphragm Construction Joint 1 bconstruction 1 0 100 C 

BR_P_Dia_Hidden Diaphragm Hidden Line 4 bhiddenpr 1 0 100 C 

BR_P_Dia_Object Diaphragm Object Line 4 0 2 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

BR – BRIDGE – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 


BR_P_Dia_Reinforcing Diaphragm Reinforcing 6 brebarpr 1 0 100 C 

BR_P_Dia_Stl_Det 

Diaphragm Steel Details 

(Connections, plates, etc.) 

3 0 1 0 100 

BR_P_Dia_Stl_Det_Hidden Diaphragm Steel Details Hidden 3 bhiddenpr 0 0 100 C 

BR_P_Dia_Text Diaphragm Text and Dimensions 0 0 1 0 500 

BR_P_Drain_Centerline Bridge Drainage Centerline 4 bcenterline 1 0 100 C 

BR_P_Drain_Hidden Bridge Drainage Hidden 7 bhiddenpr 1 0 100 C 

BR_P_Drain_Object Bridge Drainage Object 7 0 2 0 100 

BR_P_Drain_Text Bridge Drainage Text 0 0 1 0 500 

BR_P_Gen_Approach_Slab General Bridge Approach Slab 6 0 2 0 100 

BR_P_Gen_Approach_Slab_Hidden General Bridge Approach Slab-Hidden 6 bhiddenpr 1 0 100 C 

BR_P_Gen_Centerline Centerline of Lane, CL Roadway in elevations 0 bcenterline 1 0 100 C 

BR_P_Gen_CL_Chord Centerline Chord 3 0 1 0 100 

BR_P_Gen_Ground_Slope General Bridge Ground Slope 40 0 1 0 100 

BR_P_Gen_Hatch 

General Bridge Hatching 

(Architectural patterns, etc.) 

42 0 0 0 100 

BR_P_Gen_Joint_Filler General Bridge Joint Filler (PEJF, etc.) 4 0 0 0 100 

BR_P_Gen_NonPerf_Pipe General Bridge NonPerforated Pipe 4 0 0 0 100 

BR_P_Gen_Perforated_Pipe General Bridge Perforated Pipe 7 0 0 0 100 

BR_P_Gen_Phase_Construction Phase Construction Line 6 bconstruction 1 0 100 C 

BR_P_Gen_Porous_Backfill General Bridge Porous Backfill 2 0 0 0 100 

BR_P_Gen_Profile_Grade Profile Grade 7 bcenterline 1 0 100 C 

BR_P_Gen_Sheet_Piling General Bridge Sheet Piling 6 0 0 0 100 

BR_P_Gen_Slope_Protection General Bridge Slope Protection 40 0 2 0 100 

BR_P_Gen_Text 

General Bridge Text and Dimensions 0 0 1 0 500 

CELLS PLACED ON LEVEL BR_P_Gen_Text: 

Battered Pile Equation - - - 0 500 BAT_PILE_EQUATION ODOT_Bridge.cel C 

Arrowhead Filled - - - 0 500 BTERMF ODOT_Bridge.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





BR_P_Gen_Text (cont’d) 

CELLS PLACED ON LEVEL BR_P_Gen_Text (cont’d): 

Symbol - CrossBuck, 

(Circle with X inside) 

Color 

Style 


Weight 

Transparency 

Priority 


- - - 0 500 CROSSB ODOT_Bridge.cel C 

High Water Mark - - - 0 500 HWM ODOT_Bridge.cel C 

Minimum Vertical Clearance Locator - - - 0 500 MINVER ODOT_Bridge.cel C 

Symbol - Plus, (Circle with Plus inside) - - - 0 500 PLUS ODOT_Bridge.cel C 

Rebar Shape 1 - - - 0 500 REBAR01 ODOT_Bridge.cel P 






















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





BR_P_Gen_Text (cont’d) 

BR_P_Gen_Utilities 

CELLS PLACED ON LEVEL BR_P_Gen_Text (cont’d): 

Color 

Style 


Weight 

Transparency 

Priority 












Removal Indicator, (Square Box 

Cross-hatched to Show Removal) 

- - - 0 500 REMOVE ODOT_Bridge.cel C 

Section Cut Call Out - - - 0 500 SCUT ODOT_Bridge.cel C 

Circle with Sheet Number and 

Total Sheet Numbers 

- - - 0 500 SHEETCIR ODOT_Bridge.cel C 

Sheet Reference Box - - - 0 500 SHEETREF ODOT_Bridge.cel C 

Symbol - Square - - - 0 500 SQUARE ODOT_Bridge.cel C 

Symbol - Star - - - 0 500 STAR ODOT_Bridge.cel C 

Symbol - Star , (Circle with Star inside) - - - 0 500 STARWC ODOT_Bridge.cel C 

Section Title - - - 0 500 STITLE ODOT_Bridge.cel C 

Symbol - Triangle - - - 0 500 TRIANGLE ODOT_Bridge.cel C 

Symbol - Triangle, 

(Triangle with Circle inside) 

General Bridge Utilities 

(Utilities on the Bridge) 

- - - 0 500 TRIANGLEWC ODOT_Bridge.cel C 

12 0 1 0 100 

BR_P_Gen_Utilities_Hidden General Bridge Utilities Hidden 8 bhiddenpr 1 0 100 C 

BR_P_Gen_Water_Elevation General Bridge Water Elevation 10 0 1 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





BR_P_Gen_Waterproofing 

BR_P_Prestress_Centerline 

BR_P_Prestress_Det 

BR_P_Prestress_Det_Hidden 

BR_P_Prestress_Hidden 

BR_P_Prestress_Object 

BR_P_Prestress_Text 

General Bridge Waterproofing 

(Neoprene sheeting, sealing, etc.) 

Pre-Stressing Centerline Details for either 


Pre-Stressing Details for either 






Pre-Stressing Object Details for either 


Pre-Stressing Text Details for either 


Color 

Style 


4 0 1 0 100 

Weight 

Transparency 

Priority 


4 bcenterline 1 0 100 C 

3 0 1 0 100 



2 0 2 0 100 

0 0 1 0 500 

BR_P_Rail_Centerline Rail Centerline 4 bcenterline 0 0 100 C 

BR_P_Rail_Const_Joint Rail Construction Joint 1 bconstruction 1 0 100 C 

BR_P_Rail_Hidden Rail Hidden Line 8 bhiddenpr 1 0 100 C 

BR_P_Rail_Object Rail Object Line (Railing, Sidewalk) 8 0 2 0 100 

BR_P_Rail_Reinforcing Rail Reinforcing 6 brebarpr 1 0 100 C 

BR_P_Rail_Stl_Det Rail Steel Details (connections, etc.) 3 0 1 0 100 

BR_P_Rail_Stl_Det_Hidden Rail Steel Details Hidden 3 bhiddenpr 0 0 100 C 

BR_P_Rail_Text Rail Text and Dimensions 0 0 1 0 500 

BR_P_Slab_Centerline Slab Centerline 4 bcenterline 0 0 100 C 

BR_P_Slab_Const_Joint Slab Construction Joint 1 bconstruction 1 0 100 C 

BR_P_Slab_Hidden Slab Hidden Line 2 bhiddenpr 1 0 100 C 

BR_P_Slab_Object Slab Object Line 2 0 2 0 100 

BR_P_Slab_Reinforcing Slab Reinforcing (rebar, pre-stress) 6 brebarpr 1 0 100 C 

BR_P_Slab_Stl_Det Slab Steel Details (anchor plates, etc.) 3 0 1 0 100 

BR_P_Slab_Stl_Det_Hidden Slab Steel Details Hidden 3 bhiddenpr 0 0 100 C 

BR_P_Slab_Text Slab Text and Dimensions 0 0 1 0 500 

BR_P_Sub_Backwall Substructure Backwall 24 0 2 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 


Weight 

Transparency 

Priority 


BR_P_Sub_Centerline Substructure Centerline 4 bcenterline 0 0 100 C 

BR_P_Sub_Const_Joint Substructure Construction Joint 1 bconstruction 1 0 100 C 

BR_P_Sub_Deep_Centerline Substructure Deep Foundation Centerline 4 bcenterline 0 0 100 C 

BR_P_Sub_Deep_Const_Joint 

BR_P_Sub_Deep_Hidden 

BR_P_Sub_Deep_Object 

Substructure Deep Foundation Construction 

Joint 

Substructure Deep Foundation Hidden 

(H-Piles, Drilled Shafts, etc.) 

CELLS PLACED ON LEVEL BR_P_Sub_Deep_Hidden: 

1 bconstruction 1 0 100 C 


12 inch Dia. Pile Battered - - - 0 100 PILE12B ODOT_Bridge.cel P 

12 inch Dia. Pile Not Battered - - - 0 100 PILE12NB ODOT_Bridge.cel P 





Substructure Deep Foundation Object 

(H-Piles, Drilled Shafts, etc.) 

7 0 2 0 100 

BR_P_Sub_Deep_Reinforcing Substructure Deep Foundation Reinforcing 6 brebarpr 1 0 100 C 

BR_P_Sub_Deep_Text 

Substructure Deep Foundation Text and 

Dimensions 

0 0 1 0 500 

BR_P_Sub_Foot_Centerline Substructure Footing Centerline 4 bcenterline 0 0 100 C 

BR_P_Sub_Foot_Const_Joint Substructure Footing Construction Joint 1 bconstruction 1 0 100 C 

BR_P_Sub_Foot_Hidden 

BR_P_Sub_Foot_Object 

Substructure Footing Hidden 

(Spreadfooting, Pile cap, etc) 

Substructure Footing Object (Spreadfooting, 

Pile cap, etc) 


0 0 2 0 100 

BR_P_Sub_Foot_Reinforcing Substructure Footing Reinforcing 6 brebarpr 1 0 100 C 

BR_P_Sub_Foot_Text Substructure Footing Text and Dimensions 0 0 1 0 500 

BR_P_Sub_Hidden 

BR_P_Sub_Object 

Substructure Hidden 

(Abutment, Pier, Retaining wall) 

Substructure Object 

(Abutment, Pier, Retaining wall) 


3 0 2 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 


Weight 

Transparency 

Priority 


BR_P_Sub_Reinforcing Substructure Reinforcing 6 brebarpr 1 0 100 C 

BR_P_Sub_Text Substructure Text and Dimensions 0 0 1 0 500 

CM – CORRIDOR MODELER - EXISTING: 

CM_X_Curb Curb 44 0 0 0 0 

CM_X_Curb_Barrier Barrier Curb 44 0 0 0 0 

CM_X_Curb_Gutter Curb and Gutter 44 0 0 0 0 

CM_X_Feature_Liines Point Control Lines 0 0 0 0 0 

CM_X_Pavt_Asphalt Pavement, Asphalt 0 0 0 0 0 

CM_X_Pavt_Concrete Pavement, Concrete 36 0 0 0 0 

CM_X_Sidewalk Sidewalk 44 0 0 0 0 

CM_X_Wall Wall 44 0 0 0 0 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

CM – CORRIDOR MODELER - PROPOSED: 

CM_P_Barrier Barrier 44 0 1 0 0 

CM_P_Bikeway Bikeway 40 0 1 0 0 

CM_P_Curb Curb 44 0 1 0 0 

CM_P_Curb_Barrier Curb Barrier 44 0 1 0 0 

CM_P_Curb_Gutter Curb and Gutter 44 0 1 0 0 

CM_P_Ditch_Bottom Ditch Bottom 171 0 2 0 0 

CM_P_Feature_Lines Point Control Lines 0 0 0 0 0 

CM_P_Finished_Grade Finished Grade 2 0 2 0 0 

CM_P_Finished_Grade_Seeded Finished Grade Seeded 2 0 2 0 0 

CM_P_Pavt_Base1 Pavement Base Course 1 3 0 1 0 0 



CM_P_Pavt_Intermediate1 Pavement Intermediate Course 1 1 0 1 0 0 

CM_P_Pavt_Intermediate2 Pavement Intermediate Course 2 1 0 1 0 0 

CM_P_Pavt_Leveling Pavement Leveling Course 5 0 1 0 0 

CM_P_Pavt_Overlay Pavement Overlay 43 0 1 0 0 

CM_P_Pavt_Planing Pavement Planing 6 0 1 0 0 

CM_P_Pavt_Surface Pavement Surface Course 41 0 1 0 0 

CM_P_Shoulder_Base1 Shoulder Base Course 1 3 0 1 0 0 



CM_P_Shoulder_Intermediate1 Shoulder Intermediate Course 1 1 0 1 0 0 

CM_P_Shoulder_Intermediate2 Shoulder Intermediate Course 2 1 0 1 0 0 

CM_P_Shoulder_Surface Shoulder Surface Course 43 0 1 0 0 

CM_P_Sidewalk Sidewalk 44 0 1 0 0 

CM_P_Subgrade Subgrade 7 0 2 0 0 

CM_P_Wall Wall 44 0 1 0 0 

Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




DR_X_Cells 


Color 

Style 

DR – DRAINAGE - EXISTING: 

Drainage Symbols 17 2 0 0 -100 

CELLS PLACED ON LEVEL DR_X_Cells: 

Weight 

Transparency 

Priority 


Catch Basin No. 2-2A - - - 0 -100 CB22A-X ODOT_Drainage.cel P 

Catch Basin No. 2-2B - - - 0 -100 CB22B-X ODOT_Drainage.cel P 

Catch Basin No. 2-3 - - - 0 -100 CB23-X ODOT_Drainage.cel P 




Catch Basin No. 3 - - - 0 -100 CB3-X ODOT_Drainage.cel P 

Catch Basin No. 3A - - - 0 -100 CB3A-X ODOT_Drainage.cel P 


Catch Basin No. 4A for 42" Pipe - - - 0 -100 CB4A-42-X ODOT_Drainage.cel P 






Catch Basin No. 4A for Pipe < 42" - - - 0 -100 CB4A-X ODOT_Drainage.cel P 










C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




DR_X_Cells (cont’d) 


CELLS PLACED ON LEVEL DR_X_Cells (cont’d): 

Color 

Style 

DR – DRAINAGE – EXISTING (cont’d): 

Weight 

Transparency 

Priority 











Generic Round Catch Basin - - - 0 -100 CBRND-X ODOT_Drainage.cel P 

Tile Clean Out - - - 0 -100 COUT-X ODOT_Drainage.cel C 

DM-1.1, Precast Reinforced Concrete 

Outlet 

- - - 0 -100 DM11-X ODOT_Drainage.cel P 

Storm Sewer Dry Well - - - 0 -100 DRYW-X ODOT_Drainage.cel P 

Floor Drain - - - 0 -100 FDRN-X ODOT_Drainage.cel P 

Generic Rectangular Catch Basin - - - 0 -100 GCB-X ODOT_Drainage.cel P 

Jersey Barrier, Inlet Type D - - - 0 -100 I-D-JS-X ODOT_Drainage.cel P 

Single Slope Barrier, Inlet Type D - - - 0 -100 I-D-SS-X ODOT_Drainage.cel P 

Median Inlet No. 2, 10' - - - 0 -100 I210-X ODOT_Drainage.cel P 








Pavement Inlet No. 2A, 06' - - - 0 -100 I2A6-X ODOT_Drainage.cel P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 









Jersey Barrier, Median Inlets 

3A and 3A50 


3B and 3B50 


3C and 3C50 


3D and 3D50 

Single Slope Barrier, Median Inlet 

915-2 Types A, A1, B and B1 

Single Slope Barrier, Median Inlet 

915 Types A, A1, B and B1 

Single Slope Barrier, 

Median Inlet 915 Type C 

Single Slope Barrier, 

Median Inlet 915 Type C1 

- - - 0 -100 I3A-JS-X ODOT_Drainage.cel P 

- - - 0 -100 I3B-JS-X ODOT_Drainage.cel P 

- - - 0 -100 I3C-JS-X ODOT_Drainage.cel P 

- - - 0 -100 I3D-JS-X ODOT_Drainage.cel P 

- - - 0 -100 I915-2-X ODOT_Drainage.cel P 

- - - 0 -100 I915-X ODOT_Drainage.cel P 

- - - 0 -100 I915C-X ODOT_Drainage.cel P 

- - - 0 -100 I915C1-X ODOT_Drainage.cel P 

Inspection Well - - - 0 -100 IW-X ODOT_Drainage.cel P 

Storm Manhole No. 1 - - - 0 -100 MH1D-X ODOT_Drainage.cel P 

Storm Manhole No. 3, 048" Diameter - - - 0 -100 MH3-48D-X ODOT_Drainage.cel P 





C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 
















Generic Outlet - - - 0 -100 Outlet-X ODOT_Drainage.cel P 

Side Ditch Inlet - - - 0 -100 SDI1-X ODOT_Drainage.cel P 

Sewer Pump Station - - - 0 -100 SPMP-X ODOT_Drainage.cel P 

DR_X_Culvert Drainage Culvert 7 1 0 0 -100 

DR_X_Ditch Ditch Line 11 stream 0 0 -100 C 

DR_X_Drainage_Area Drainage Area Outline 23 0 1 0 -100 

DR_X_Drive_Pipe Drive Pipe 17 5 0 0 -100 

DR_X_Elev_Flow Flow elevation from Survey 17 0 0 0 -100 

DR_X_Elev_Inlet Inlet elevation from Survey 17 0 0 0 -100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





DR_X_Erosion_Control 

Erosion Control Outline for RipRap, Rock 

Channel Protection and Jute Matting 

Color 

Style 


0 1 0 0 -100 

AREA PATTERNING CELLS TO BE PLACED ON LEVEL DR_X_Erosion_Control: 

Jute Matting 

(use Cross-Hatch Pattern tool) 

Rock Channel Protection 

(Pattern Cell) 

- - - 0 -100 

Weight 

Transparency 

Priority 


- - - 0 -100 RCP ODOT-Symbols.cel C 

Rip Rap (Pattern Cell) - - - 0 -100 RIPRAP ODOT-Symbols.cel C 

DR_X_Flood_Boundary Flood Boundary 170 5 1 0 -100 

DR_X_Floodway Floodway 167 7 0 0 -100 

DR_X_Flow_Arrow 

DR_X_Headwall 

Drainage Flow Arrow Symbols 17 0 0 0 -100 

CELLS PLACED ON LEVEL DR_X_Flow_Arrow: 

Drainage Flow Arrow - - - 0 -100 DFL-X ODOT_Drainage.cel C 

Drainage Headwall Symbols 10 1 0 0 -100 

CELLS PLACED ON LEVEL DR_X_Headwall: 

Head Wall No. 1 for 15" RCP - - - 0 -100 HW1-15-X ODOT_Drainage.cel P 






Head Wall No. 1.1, 15° for 42" Pipe - - - 0 -100 HW1.1-15-42-X ODOT_Drainage.cel P 








C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





DR_X_Headwall (cont’d) 

CELLS PLACED ON LEVEL DR_X_Headwall (cont’d): 

Color 

Style 


Weight 

Transparency 

Priority 






Head Wall No. 1.1 for 42" Pipe - - - 0 -100 HW1.1-42-X ODOT_Drainage.cel P 












Head Wall No. 2.1 for 012" CMP - - - 0 -100 HW2.1-12-X ODOT_Drainage.cel P 










C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 




























C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 












Head Wall No. 2.1 for Pipe Arch 

17"x13" with 2-2/3"x1/2" Corrugations 










40"x31" with 3"x1" Corrugations 









- - - 0 -100 HW2.1PA-17x13-X ODOT_Drainage.cel P 










C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 









Head Wall No. 2.1 for Pipe Arc 
































Color 

Style 


Weight 

Transparency 

Priority 



















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 


Head Wall No. 2.2 for 102" RCP - - - 0 -100 HW2.2-102-X ODOT_Drainage.cel P 

Head Wall No. 2.2 for Elliptical 

106"x68" RCP 

- - - 0 -100 HW2.2-106x68-X ODOT_Drainage.cel P 






23"x14" RCP 






30"x19" RCP 




34"x22" RCP 




38"x24" RCP 




42"x27" RCP 


45"x29" RCP 





49"x32" RCP 


53"x34" RCP 




C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 




60"x38" RCP 




68"x43" RCP 




76"x48" RCP 




83"x53" RCP 





91"x58" RCP 




98"x63" RCP 


Head Wall No. 2.2 for 108" Concrete - - - 0 -100 HW2.2-108-X ODOT_Drainage.cel P 


113"x72" RCP 





121"x77" RCP 



Head Wall No. 2.2 for 128"x82" RCP - - - 0 -100 HW2.2-128x82-X ODOT_Drainage.cel P 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 








136"x87" RCP 


143"x92" RCP 

Color 

Style 


Weight 

Transparency 

Priority 






151"x97" RCP 


166"x106" RCP 


180"x116" RCP 

DR_X_Paved_Gutter Paved Gutter 11 2 0 0 -100 

DR_X_Storm_Sewer 

Storm Sewer Line 17 5 0 0 -100 

Storm Sewer Line 17 * stormlineex 0 0 -100 

DR_X_Text Drainage Text 0 0 0 0 500 




DR_X_Trench_Drain Trench Drain 5 trenchex 0 0 -100 P 

DR_X_Underdrain Underdrain 1 underdrainex 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

DR – DRAINAGE - PROPOSED: 

DR_P_Asphalt_Batch_Plant Asphalt Batch Plant 17 0 2 0 100 

DR_P_Cells 

Drainage Symbols 17 0 0 0 100 

CELLS PLACED ON LEVEL DR_P_Cells: 

Weight 

Transparency 

Priority 


Catch Basin No. 2-2A, Adjusted - - - 0 100 CB22A-A ODOT_Drainage.cel P 

Catch Basin No. 2-2A - - - 0 100 CB22A-P ODOT_Drainage.cel P 

Catch Basin No. 2-2B, Adjusted - - - 0 100 CB22B-A ODOT_Drainage.cel P 

Catch Basin No. 2-2B - - - 0 100 CB22B-P ODOT_Drainage.cel P 

Catch Basin No. 2-3, Adjusted - - - 0 100 CB23-A ODOT_Drainage.cel P 

Catch Basin No. 2-3 - - - 0 100 CB23-P ODOT_Drainage.cel P 







Catch Basin No. 3, Adjusted - - - 0 100 CB3-A ODOT_Drainage.cel P 

Catch Basin No. 3 - - - 0 100 CB3-P ODOT_Drainage.cel P 

Catch Basin No. 3A, Adjusted - - - 0 100 CB3A-A ODOT_Drainage.cel P 

Catch Basin No. 3A - - - 0 100 CB3A-P ODOT_Drainage.cel P 



Catch Basin No. 4A for 42" Pipe, Adjusted - - - 0 100 CB4A-42-A ODOT_Drainage.cel P 

Catch Basin No. 4A for 42" Pipe - - - 0 100 CB4A-42-P ODOT_Drainage.cel P 





C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




DR_P_Cells (cont’d) 


CELLS PLACED ON LEVEL DR_P_Cells (cont’d): 

Color 

Style 

DR – DRAINAGE – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 








Catch Basin No. 4A for Pipe < 42", Adjusted - - - 0 100 CB4A-A ODOT_Drainage.cel P 

Catch Basin No. 4A for Pipe < 42" - - - 0 100 CB4A-P ODOT_Drainage.cel P 



















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 




















Precast Reinforced Concrete Outlet - - - 0 100 DM11-P ODOT_Drainage.cel P 

Floor Drain - - - 0 100 FDRN-P ODOT_Drainage.cel P 

Median Inlet No. 2, 06' - - - 0 100 I26-P ODOT_Drainage.cel P 






C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 




Pavement Inlet No. 2A, 06' - - - 0 100 I2A6-P ODOT_Drainage.cel P 








Inlet No. 3 for Single Slope Barrier, 

Type A 


Type A1 


Type B 


Type B1 


Type C 


Type C1 


Type D 


Type A 


Type A1 


Type B 


Type B1 

- - - 0 100 I3A-SS-P ODOT_Drainage.cel P 

- - - 0 100 I3A1-SS-P ODOT_Drainage.cel P 

- - - 0 100 I3B-SS-P ODOT_Drainage.cel P 

- - - 0 100 I3B1-SS-P ODOT_Drainage.cel P 

- - - 0 100 I3C-SS-P ODOT_Drainage.cel P 

- - - 0 100 I3C1-SS-P ODOT_Drainage.cel P 

- - - 0 100 I3D-SS-P ODOT_Drainage.cel P 

- - - 0 100 I4A-SS-P ODOT_Drainage.cel P 

- - - 0 100 I4A1-SS-P ODOT_Drainage.cel P 

- - - 0 100 I4B-SS-P ODOT_Drainage.cel P 

- - - 0 100 I4B1-SS-P ODOT_Drainage.cel P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 


Inspection Well, Adjusted - - - 0 100 IW-A ODOT_Drainage.cel P 

Inspection Well - - - 0 100 IW-P ODOT_Drainage.cel P 

Storm Manhole No. 1, Adjusted - - - 0 100 MH1D-A ODOT_Drainage.cel P 

Storm Manhole No. 1 - - - 0 100 MH1D-P ODOT_Drainage.cel P 

Storm Manhole No. 2 for Pipe < 21" 

depth 12'-25', Adjusted 


depth 12'-25' 


depth 25'-40' , Adjusted 


depth 25'-40' 




depth 40'-55' 

Storm Manhole No. 2 for 21" Pipe 



depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 12'-25' 

- - - 0 100 MH2-18D-12'-25'-A ODOT_Drainage.cel P 

- - - 0 100 MH2-18D-12'-25'-P ODOT_Drainage.cel P 













C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 










depth 25'-40' 




depth 40'-55' 




depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 12'-25' 




depth 25'-40' 




depth 40'-55' 



Color 

Style 


Weight 

Transparency 

Priority 



















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 








depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 12'-25' 




depth 25'-40' 




depth 40'-55' 

Color 

Style 


Weight 

Transparency 

Priority 



















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 










depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 12'-25' 




depth 25'-40' 



Color 

Style 


Weight 

Transparency 

Priority 













- - - 0 100 MH2-54D-40’-55'-P ODOT_Drainage.cel P 






C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 








depth 40'-55' 




depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 12'-25' 




depth 25'-40' 




depth 40'-55' 




depth 25'-40' 




depth 40'-55' 

Color 

Style 


Weight 

Transparency 

Priority 



















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 










depth 25'-40' 




depth 40'-55' 




depth 25'-40' 




depth 40'-55' 




depth 25'-40' 




depth 40'-55' 




depth 25'-40' 




depth 40'-55' 



Color 

Style 


Weight 

Transparency 

Priority 



















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 








depth 25'-40' 




depth 40'-55' 




depth 25'-40' 




depth 40'-55' 




depth 25'-40' 




depth 40'-55' 

Storm Manhole No. 3, 048" Diameter, 

Adjusted 

Color 

Style 


Weight 

Transparency 

Priority 













- - - 0 100 MH3-48D-A ODOT_Drainage.cel P 

Storm Manhole No. 3, 048" Diameter - - - 0 100 MH3-48D-P ODOT_Drainage.cel P 


Adjusted 




Adjusted 




Adjusted 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 




Adjusted 




Adjusted 




Adjusted 




Adjusted 




Adjusted 




Adjusted 




Adjusted 




Adjusted 




Adjusted 




Adjusted 



C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 








Adjusted 

Color 

Style 


Weight 

Transparency 

Priority 





Adjusted 




Adjusted 




Adjusted 




Adjusted 



Storm Manhole No. 5 for Pipe < 33", 

Adjusted 


Storm Manhole No. 5 for Pipe < 33" - - - 0 100 MH5-30D-P ODOT_Drainage.cel P 

Storm Manhole No. 5 for 33" to 42" Pipe, 

Adjusted 


Storm Manhole No. 5 for 33" to 42" Pipe - - - 0 100 MH5-42D-P ODOT_Drainage.cel P 

Storm Manhole No. 5 for 48" Pipe, Adjusted - - - 0 100 MH5-48D-A ODOT_Drainage.cel P 

Storm Manhole No. 5 for 48" Pipe - - - 0 100 MH5-48D-P ODOT_Drainage.cel P 








C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





DR_P_Culvert 



Color 

Style 


Weight 

Transparency 

Priority 











Storm Manhole No. 5 for 102" Pipe, 

Adjusted 




Adjusted 




Adjusted 




Adjusted 



Generic Outlet - - - 0 100 Outlet-P ODOT_Drainage.cel P 

Side Ditch Inlet - - - 0 100 SDI1-P ODOT_Drainage.cel P 

Culvert 7 0 1 0 100 

4' Culvert 7 * culvert04 1 0 100 P 




C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





DR_P_Culvert (cont’d) 

Color 

Style 


Weight 

Transparency 

Priority 










DR_P_Dike Dike 17 0 1 0 100 

DR_P_Ditch Ditch Line 11 stream 1 0 100 C 

DR_P_Drainage_Area Drainage Area Outline 12 0 5 0 100 

DR_P_Drive_Pipe Drive Pipe 17 0 1 0 100 

DR_P_Erosion_Control 

Erosion Control Outline for RipRap, Rock 

Channel Protection and Jute Matting 

0 0 1 0 100 

AREA PATTERNING CELLS TO BE PLACED ON LEVEL DR_P_Erosion_Control: 

Jute Matting 

(use the Cross-Hatch Pattern tool) 

- - - 0 100 

Rock Channel Protection (Pattern Cell) - - - 0 100 RCP ODOT-Symbols.cel C 

Rip Rap (Pattern Cell) - - - 0 100 RIPRAP ODOT-Symbols.cel C 

DR_P_Filter_Fabric_Fence Filter Fabric Fence 17 fenceex 0 0 100 C 

DR_P_Flood_Boundary Flood Boundary 171 6 1 0 100 

DR_P_Floodway Floodway 169 0 2 0 100 

DR_P_Flow_Arrow 

Drainage Flow Arrow Symbols 17 0 1 0 100 

CELLS PLACED ON LEVEL DR_P_Flow_Arrow: 

Drainage Flow Arrow - - - 0 100 DFL-P ODOT_Drainage.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




DR_P_Headwall 


Color 

Style 


Drainage Headwall Symbols 10 0 1 0 100 

CELLS PLACED ON LEVEL DR_P_Headwall: 

Weight 

Transparency 

Priority 


Head Wall No. 1.1, 15° for 42" Pipe - - - 0 100 HW1.1-15-42-P ODOT_Drainage.cel P 












Head Wall No. 1.1 for 42" Pipe - - - 0 100 HW1.1-42-P ODOT_Drainage.cel P 












Head Wall No. 2.1 for 012" CMP - - - 0 100 HW2.1-12-P ODOT_Drainage.cel P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





DR_P_Headwall (cont’d) 

CELLS PLACED ON LEVEL DR_P_Headwall (cont’d): 

Color 

Style 


Weight 

Transparency 

Priority 




























C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 





























- - - 0 100 HW2.1PA-103x71-P ODOT_Drainage.cel P 




C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 










142"x91"with 3"x1" Corrugations 










35"x24" with2-2/3"x1/2" Corrugations 




















71"x47"with 2-2/3"x1/2" Corrugations 

Color 

Style 


Weight 

Transparency 

Priority 



















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 



















Color 

Style 


Weight 

Transparency 

Priority 








Head Wall No. 2.2 for 012" RCP - - - 0 100 HW2.2-12-P ODOT_Drainage.cel P 

















C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 







Color 

Style 


Weight 

Transparency 

Priority 












14”x23" RCP 


19”x30" RCP 


22”x34" RCP 


24”x38" RCP 


27”x42" RCP 


29”x45" RCP 


32”x49" RCP 


34”x53" RCP 


38”x60" RCP 


43”x68" RCP 


48”x76" RCP 

- - - 0 100 HW2.2-14x23-P ODOT_Drainage.cel P 











C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 








53”x83" RCP 


58”x91" RCP 


63”x98" RCP 


68”x106" RCP 


72”x113" RCP 


77”x121" RCP 


82”x128” RCP 


87”x136" RCP 


92”x143" RCP 


97”x151" RCP 


106"x166" RCP 


116”x180" RCP 

Color 

Style 


DR_P_Inlet_Protection Inlet Protection 21 0 1 0 100 

DR_P_Land_Use Land Use 4 0 1 0 100 

DR_P_Paved_Gutter Paved Gutter 11 0 1 0 100 

DR_P_Sediment_Basin Sediment Basin 28 0 1 0 100 

DR_P_Staging_Area Contractor Staging Area 0 0 1 0 100 

DR_P_Storm_Sewer 

Storm Sewer Line 17 0 1 0 100 

Storm Sewer Line 17 * stormline 1 0 100 

Weight 

Transparency 

Priority 














C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 


DR_P_Text Drainage Text 0 0 1 0 500 

Weight 

Transparency 

Priority 


DR_P_Trench_Drain Trench Drain 17 trenchpr 0 0 100 P 

DR_P_Underdrain Underdrain 5 underdrainpr 1 0 100 C 

DT – DIGITAL TERRAIN MODELS - EXISTING: 

DT_X_Break_Line Break Line 4 0 0 0 -121 

DT_X_Contour_Major Major Contour Line 133 3 2 0 -120 

DT_X_Contour_Minor Minor Contour Line 131 3 0 0 -120 

DT_X_Graded_Shoulder Graded Shoulder Line 9 3 0 0 -120 

DT_X_Island Island Area 11 0 0 0 -121 

DT_X_Lattice Lattice 0 0 0 0 -121 

DT_X_Slope_Break_Line Slope Break Line 0 slopebreakex 0 0 -121 C 

DT_X_Spot_Elev Spot Elevations 0 0 0 0 -121 

DT_X_TIN_Hull Tin Hull 1 0 0 0 -121 

DT_X_Triangles Triangles 68 0 0 0 -122 

DT_X_Void Void Area 0 0 0 0 -121 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

DT – DIGITAL TERRAIN MODELS - PROPOSED: 

DT_P_Break_Line Break Line 0 0 0 0 91 

DT_P_Contour_Major Major Contour Line 6 0 3 0 92 

DT_P_Contour_Minor Minor Contour Line 4 0 1 0 92 

DT_P_Graded_Shoulder Graded Shoulder Line 9 0 1 0 92 

DT_P_Lattice Lattice 0 0 0 0 91 

Weight 

Transparency 

Priority 


DT_P_Slope_Break_Line Slope Break Line 4 slopebreakpr 1 0 92 C 

DT_P_Spot_Elevations Spot Elevations 0 0 0 0 91 

DT_P_Tie Proposed to Existing Tie Line 68 0 0 0 100 

DT_P_TIN_Hull Tin Hull 1 0 2 0 91 

DT_P_Triangles Triangles 2 0 0 0 90 

DT_P_Void Void Area 0 0 0 0 91 

DV – DIVISIONS - EXISTING: 

DV_X_Corp_Line Corporation Line 0 corp 0 0 -100 C 

DV_X_County_Line County Line 7 county 2 0 -100 C 

DV_X_Lot_Line Lot Line 4 3 0 0 -100 

DV_X_Property_Line 

DV_X_Section_VMS_Line 

Property Line 0 0 0 0 -100 

CELLS PLACED ON LEVEL DV_X_Property_Line: 

Ownership Hook - - - 0 -100 OHK ODOT_Symbols.cel C 

Property Line Marker - - - 0 -100 PLM ODOT_Symbols.cel C 

Section/VMS Line 5 2 0 0 -100 

CELLS PLACED ON LEVEL DV_X_Section_VMS_Line: 

Section Corner - - - 0 -100 SECCOR ODOT_Symbols.cel C 

Section Half/Quarter - - - 0 -100 SECHLF ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

DV – DIVISIONS – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


DV_X_Setback Building Set Back Line 11 setbackex 1 0 -100 C 

DV_X_State_Line State Line 3 state 3 0 -100 C 

DV_X_Text Divisions Text 0 0 0 0 500 

DV_X_Township_Line Township Line 2 3 1 0 -100 

EV – ENVIRONMENTAL: 

EV_Ecological_RTE_Species Rare, threatened or Endangered Species 192 2 0 0 0 

EV_Ecological_Special_Interest Environmental Special Interest 192 0 0 0 0 

EV_Ecological_Streams Regulated streams not readily distinguished 23 6 0 0 0 

EV_Ecological_Text Ecological Text 0 0 1 0 500 

EV_Ecological_Wetlands Wetland Boundaries 23 stream 1 0 0 C 

EV_HazMat_Plume Contamination Plume 3 0 0 0 0 

EV_HazMat_Site_Known Known HazMat Site 4 0 0 0 0 

EV_HazMat_Site_Potential Potential HazMat Site 176 0 0 0 0 

EV_HazMat_Text HazMat Text 0 0 1 0 500 

EV_Historical_Districts Historic Districts 19 0 0 0 0 

EV_Historical_Landmarks Historic Landmarks 30 2 0 0 0 

EV_Historical_Sites Historic Individual Sites or Buildings 22 0 0 0 0 

EV_Historical_Text Historic Text 0 0 1 0 500 

EV_Noise_Individual_Sites Individual Noise Sensitive Sites 143 0 0 0 0 

EV_Noise_Residential Residential Noise Sensitive Areas 141 0 0 0 0 

EV_Noise_Text Noise Text 0 0 1 0 500 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




GE_X_Cells 

GE_X_CL_10 

GE_X_CL_100 

GE_X_CL_1000 

GE_X_CL_20 

GE_X_CL_200 

GE_X_CL_2000 

GE_X_CL_5 

GE_X_CL_50 

GE_X_CL_500 


Color 

Style 

GE – GEOMETRY - EXISTING: 

Geometry Symbols 4 0 0 0 -100 

CELLS PLACED ON LEVEL GE_X_Cells: 

Weight 

Transparency 

Priority 


Curve to Spiral - - - 0 -100 PC ODOT_Symbols.cel C 

Point of Compound Curvature - - - 0 -100 PC ODOT_Symbols.cel C 

Point of Curve - - - 0 -100 PC ODOT_Symbols.cel C 

Point on Curve - - - 0 -100 PC ODOT_Symbols.cel C 

Point on Tangent - - - 0 -100 PC ODOT_Symbols.cel C 

Point of Tangency - - - 0 -100 PC ODOT_Symbols.cel C 

Spiral to Curve - - - 0 -100 PC ODOT_Symbols.cel C 

Spiral to Tangent - - - 0 -100 PC ODOT_Symbols.cel C 

Tangent to Spiral - - - 0 -100 PC ODOT_Symbols.cel C 

Point of Intersection - - - 0 -100 PI ODOT_Symbols.cel C 

Centerline or Baseline of Construction, 

10 Scale 


100 Scale 


1000 Scale 


20 Scale 


200 Scale 


2000 Scale 


5 Scale 


50 Scale 


500 Scale 

0 cl10 0 0 500 P 

0 cl100 0 0 500 P 

0 cl1000 0 0 500 P 

0 cl20 0 0 500 P 

0 cl200 0 0 500 P 

0 cl2000 0 0 500 P 

0 cl5 0 0 500 P 

0 cl50 0 0 500 P 

0 cl500 0 0 500 P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




GE_P_Cells 

GE_P_CL_10 

GE_P_CL_100 

GE_P_CL_1000 

GE_P_CL_20 

GE_P_CL_200 

GE_P_CL_2000 

GE_P_CL_5 

GE_P_CL_50 

GE_P_CL_500 


Color 

Style 

GE – GEOMETRY - PROPOSED: 

Geometry Symbols 3 0 1 0 100 

CELLS PLACED ON LEVEL GE_P_Cells: 

Weight 

Transparency 

Priority 


Curve to Spiral - - - 0 100 PCP ODOT_Symbols.cel C 

Point of Compound Curvature - - - 0 100 PCP ODOT_Symbols.cel C 

Point of Curve - - - 0 100 PCP ODOT_Symbols.cel C 

Point on Curve - - - 0 100 PCP ODOT_Symbols.cel C 

Point on Tangent - - - 0 100 PCP ODOT_Symbols.cel C 

Point of Tangency - - - 0 100 PCP ODOT_Symbols.cel C 

Spiral to Curve - - - 0 100 PCP ODOT_Symbols.cel C 

Spiral to Tangent - - - 0 100 PCP ODOT_Symbols.cel C 

Tangent to Spiral - - - 0 100 PCP ODOT_Symbols.cel C 

Point of Intersection - - - 0 100 PIP ODOT_Symbols.cel C 


10 Scale 


100 Scale 

Centerline or Baseline or Construction, 

1000 Scale 


20 Scale 


200 Scale 


2000 Scale 


5 Scale 


50 Scale 


500 Scale 

GE_P_Driveway_CL Centerline for Driveways 0 7 1 0 100 

0 cl10 1 0 500 P 

0 cl100 1 0 500 P 

0 cl1000 1 0 500 P 

0 cl20 1 0 500 P 

0 cl200 1 0 500 P 

0 cl2000 1 0 500 P 

0 cl5 1 0 500 P 

0 cl50 1 0 500 P 

0 cl500 1 0 500 P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

GK – GEOPAK: 

Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

GK_Cells Profile and Cross Section Cells 2 0 0 50 -110 

GK_Clip_Borders GEOPAK Sheet Clipping Borders 0 0 0 0 0 

GK_Drainage_Nodes GEOPAK Drainage Node Locations 0 0 4 0 0 

GK_Patterns GEOPAK Pattern Lines 0 0 0 0 0 

GK_Patterns2 GEOPAK Pattern Lines 1 0 0 0 0 




GK_Shapes GEOPAK Superelevation Shapes 0 0 0 50 -110 

GK_Shapes2 GEOPAK Superelevation Shapes 0 0 0 50 -110 




GK_Visualization GEOPAK COGO Visualization 6 0 1 0 200 

GM – GEOMEDIA (County Maps) - EXISTING: 

GM_X_Adjacent_County Adjacent County Boundaries 0 3 3 0 11 

GM_X_Adjacent_County_Text Adjacent County Name 0 0 2 0 11 

GM_X_Airport_Class_1 Airport Class 1 Symbol 5 0 0 0 13 



GM_X_Airport_Location_Class_1 Airport Tower Class 1 Database Location 5 0 10 0 0 







Color 

Style 


GM_X_Airport_Text_Class_1 Airport Name Class 1 5 0 0 0 13 



GM_X_City_Street City Street 0 0 0 0 8 

GM_X_City_Street_Text City Street Name 0 0 0 0 8 

GM_X_Corporation Corporation Boundary 0 1 1 75 4 

GM_X_Corporation_Text Corporation Name 0 0 1 0 5 

GM_X_County County Boundary 0 3 3 0 11 

GM_X_County_Road County Road 2 0 2 0 3 

GM_X_County_Road_Text County Road Name 2 0 0 0 3 

GM_X_County_ROW County Boundary ROW Only 2 3 1 0 3 

GM_X_County_Subdivision County Subdivision Streets 0 0 0 0 3 

GM_X_County_Subdivision_Text County Subdivision Streets Text 0 0 0 0 3 

GM_X_County_Text County Name 0 0 2 0 11 

GM_X_Hydro Dams, Locks, etc. 6 0 0 0 9 

GM_X_Hydro_Text Dams, Locks, etc. Text 6 0 0 0 9 

GM_X_Interchange_Ramps Interchange Ramps Only 3 0 1 0 12 

Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

GM_X_Interstate_Location Interstate Route Database Shield Location 0 0 1 0 0 

GM_X_Interstate_Route Interstate Route Alignment 3 0 4 0 12 

GM_X_Interstate_Shield Interstate Route Shield 0 0 0 0 13 

GM_X_Major_Lake Major Lake 1 0 1 0 11 

GM_X_Major_Lake_Text Major Lake Name 1 0 0 0 11 

GM_X_Major_River Major River 1 0 1 0 11 

GM_X_Major_River_Text Major River Name 1 0 0 0 11 

GM_X_Minor_Lake Minor Lake 1 0 0 0 3 

GM_X_Minor_Lake_Text Minor Lake Name 1 0 0 0 3 

GM_X_Minor_River Minor River 1 0 0 0 3 





Color 

Style 


GM_X_Minor_River_Text Minor River Name 1 0 0 0 3 

GM_X_Municipal_Street Municipal Street 0 0 0 0 3 

Weight 

Transparency 

Priority 


GM_X_Rail_Line Railroad 0 rr2 1 0 10 C 

GM_X_Rail_Line_Text Railroad Name 0 0 0 0 10 

GM_X_Rural_Islands Boundary within a Boundary 0 1 1 0 4 

GM_X_Section Section 0 5 0 0 1 

GM_X_Section_Text Section Number 0 0 0 0 1 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

GM_X_State_Location State Route Database Shield Location 0 0 1 0 0 

GM_X_State_Route State Route Alignment 3 0 2 0 12 

GM_X_State_Shield State Route Shield 0 0 0 0 13 

GM_X_Township Township Boundary 0 3 2 0 2 

GM_X_Township_Road Township Road 168 0 2 0 3 

GM_X_Township_Road_Text Township Road Name 168 0 0 0 3 

GM_X_Township_ROW Township Boundary ROW Only 168 3 1 0 3 

GM_X_Township_Subdivision Township Streets 168 0 0 0 3 

GM_X_Township_Subdivision_Text Township Street Names 168 0 0 0 3 

GM_X_Township_Text Township Name Text 0 0 1 0 6 

GM_X_Unincorporated Unincorporated Symbol 3 0 0 0 7 

GM_X_Unincorporated_Location Unincorporated Database Location 4 0 10 0 7 

GM_X_Unincorporated_Text Unincorporated Name 0 0 0 0 7 

GM_X_US_Location US Route Database Shield Location 0 0 1 0 0 

GM_X_US_Route US Route Alignment 3 0 3 0 12 

GM_X_US_Shield US Route Shield 0 0 0 0 13 





Color 

Style 

GM – GEOMEDIA (County Maps) - PROPOSED: 

GM_P_County_Alignment County Highway 2 3 2 0 3 

GM_P_Interstate_Alignment Interstate Route 3 3 4 0 12 

Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

GM_P_Interstate_Location Interstate Route Database Shield Location 0 0 1 0 0 

GM_P_Interstate_Shield Interstate Route Shield 0 0 0 0 13 

GM_P_State_Alignment State Route 3 3 2 0 12 

GM_P_State_Location State Route Database Shield Location 0 0 1 0 0 

GM_P_State_Shield State Route Shield 0 0 0 0 13 

GM_P_Township_Alignment Township Highway 168 3 2 0 3 

GM_P_US_Alignment US Route 3 3 3 0 12 

GM_P_US_Location US Route Database Shield Location 0 0 1 0 0 

GM_P_US_Shield US Route Shield 0 0 0 0 13 

GT – GEOTECHNICAL - EXISTING: 

GT_X_Coal_Seam_1 Coal Outcrop Line and Seam No. 1 0 seamno1 0 0 -100 C 



GT_X_Coal_Seam_3A Coal Outcrop Line and Seam No. 3A 0 seamno3A 0 0 -100 C 

GT_X_Coal_Seam_3B Coal Outcrop Line and Seam No. 3B 0 seamno3B 0 0 -100 C 











Color 

Style 

GT – GEOTECHNICAL – EXISTING (cont’d): 

Weight 

Transparency 

Priority 









GT_X_Groundwater Geotechnical Groundwater Line 1 6 1 0 -100 

GT_X_Mine_Cells 

Mine Symbols 6 0 0 0 -100 

CELLS PLACED ON LEVEL GT_X_Mine_Cells: 

Deep Mine Entry Air or PumpShaft - - - 0 -100 MINEAPSH ODOT_Symbols.cel C 

Deep Mine Entry Drift - - - 0 -100 MINEDR ODOT_Symbols.cel C 

Deep Mine Entry Drift with Discharge Left - - - 0 -100 MINEDRDL ODOT_Symbols.cel C 

Deep Mine Entry Drift with Discharge Right - - - 0 -100 MINEDRDR ODOT_Symbols.cel C 

Deep Mine Entry Shaft - - - 0 -100 MINEENTSH ODOT_Symbols.cel C 

Deep Mine Entry Slope - - - 0 -100 MINESL ODOT_Symbols.cel C 

Deep Mine Entry Slope with Discharge Left - - - 0 -100 MINESLDL ODOT_Symbols.cel C 

Deep Mine Entry Slope with Discharge Right - - - 0 -100 MINESLDR ODOT_Symbols.cel C 

Mine Subsidence Point - - - 0 -100 MINESUB ODOT_Symbols.cel C 

GT_X_Mine_Highwall Surface Mine Highwall 0 highwall 0 0 -100 C 

GT_X_Mine_Subsidence_Lt Mine Subsidence Line Left 0 minesublt 0 0 -100 C 

GT_X_Mine_Subsidence_Rt Mine subsidence Line Right 0 minesubrt 0 0 -100 C 

GT_X_Piling_Cells 

Geotechnical Piling Symbols 5 2 0 0 -100 

CELLS PLACED ON LEVEL GT_X_Piling_Cells: 

Steel Beam Pile for Soil Retention - - - 0 -100 BEAM_PILE ODOT_Geotech.cel C 

Steel Pipe Pile for Soil Retention - - - 0 -100 PIPE_PILE ODOT_Geotech.cel C 

GT_X_Rock_Outcrop Rock Outcrop Line 0 rockoutcrop 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





GT_X_Rock_Outcrop_Cells 

Color 

Style 

GT – GEOTECHNICAL – EXISTING (cont’d): 

Rock Outcrop Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL GT_X_Rock_Outcrop_Cells: 

Weight 

Transparency 

Priority 


Rock Outcrop Symbol - - - 0 -100 R_OUTCROP_SYM ODOT_Geotech.cel C 

GT_X_Shear_Surface Geotechnical Shear Surface 6 5 0 0 -100 

GT_X_Surface_Features 

Limits of Man-made fill, Dumps, Waste Pits, 

Excavations, Low-Lying poorly drained soils, 

Landslides, Grazing Land, Cultivated Land 

CELLS PLACED ON LEVEL GT_X_Surface_Features: 

12 2 1 0 100 

Cattail - - - 0 100 CATTAIL ODOT_Geotech.cel C 

GT_X_Surface_Features_Text Surface Features Text 0 0 0 0 500 

GT_X_Wells 

Well Symbols 3 3 0 0 -100 

CELLS PLACED ON LEVEL GT_X_Wells: 

Monitoring Well - - - 0 -100 MWELL ODOT_Symbols.cel C 

GT – GEOTECHNICAL - HISTORIC: 

GT_Historic_Cells Geotechnical Historic Symbols 0 0 1 0 101 

GT_Historic_Soil_Boring 

Soil Boring Cells 12 0 1 0 101 

CELLS PLACED ON LEVEL GT_Historic_Soil_Boring: 

Soil Boring Historic - - - 0 101 SOILB_HIST ODOT_Geotech.cel C 

GT_Historic_Soil_Layers Geotechnical Soil Layers and Symbols 0 0 0 0 101 

GT_Historic_Text Geotechnical Text 0 0 1 0 500 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

GT – GEOTECHNICAL - INSTRUMENTED: 

GT_Instrumented_Cells Geotechnical Instrumented Symbols 0 0 1 0 101 

GT_Instrumented_Soil_Boring 

Soil Boring Cells 12 0 1 0 101 

CELLS PLACED ON LEVEL GT_Instrumented_Soil_Boring: 

Weight 

Transparency 

Priority 


Soil Boring Instrumented - - - 0 101 SOILB_INST ODOT_Geotech.cel C 

GT_Instrumented_Soil_Layers Geotechnical Soil Layers 0 0 0 0 101 

GT_Instrumented_Text Geotechnical Text 0 0 1 0 500 

GT_Project_Cells 

GT_Project_Soil_Boring 

GT – GEOTECHNICAL - PROJECT: 

Geotechnical Project Symbols 0 0 1 0 101 

CELLS PLACED ON LEVEL GT_Project_Cells: 

Rock Outcrop Section - - - 0 101 R_OUTCROP_SECT ODOT_Geotech.cel C 

Scalped Section - - - 0 101 SCALPED_SECT ODOT_Geotech.cel C 

Soil Boring Cells - Project 12 0 1 0 101 

CELLS PLACED ON LEVEL GT_Project_Soil_Boring: 

Soil Boring Project - - - 0 101 SOILB_PROJ ODOT_Geotech.cel C 

GT_Project_Soil_Layers Geotechnical Soil Layers - Project 0 0 0 0 101 

GT_Project_Text Geotechnical Text - Project 0 0 1 0 500 

GT_Target_Soil_Boring 

Soil Boring Cells – Target 

(Staked & Prop. Locations) 

CELLS PLACED ON LEVEL GT_Target_Soil_Boring: 

GT – GEOTECHNICAL - TARGET: 

1 0 1 0 100 

Soil Boring Target - - - 0 100 SOILB_TARGET ODOT_Geotech.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

HY – HYDRAULICS - EXISTING: 

Weight 

Transparency 

Priority 


HY_X_Spring Spring Line 11 stream 0 0 -100 C 

HY_X_Spring_Cells 

Spring Symbols 11 0 0 0 -100 

CELLS PLACED ON LEVEL HY_X_Spring_Cells 

Spring Head Developed Left - - - 0 -100 SPRINGDL ODOT_Symbols.cel C 

Spring Head Developed Right - - - 0 -100 SPRINGDR ODOT_Symbols.cel C 

Spring Head Undeveloped Left - - - 0 -100 SPRINGUL ODOT_Symbols.cel C 

Spring Head Undeveloped Right - - - 0 -100 SPRINGUR ODOT_Symbols.cel C 

HY_X_Text Hydraulics Text 0 0 0 0 500 

HY_X_Water_Edge Bogs, Lake, Pond, River, Stream Edge Line 11 stream 0 0 -100 C 

HY_X_Water_Well 

Water Well Symbols 11 0 1 0 -100 

CELLS PLACED ON LEVEL HY_X_Water_Well: 

Water Well Drilled w/out Well Log - - - 0 -100 WW ODOT_Symbols.cel C 

Water Well Dug - - - 0 -100 WWD ODOT_Symbols.cel C 

Water Well Drilled with Well Log - - - 0 -100 WWL ODOT_Symbols.cel C 

HY_X_Wetland_Area Swamp/Wetland Area Outline 11 stream 0 0 -100 C 

HY_X_Wetland_Cells 

Swamp/Wetland Symbols 11 0 0 0 -100 

CELLS PLACED ON LEVEL HY_X_Wetland_Cells: 

Swamp/Wetland Symbol - - - 0 -100 SWAMP ODOT_Symbols.cel C 

HY – HYDRAULICS - PROPOSED: 

HY_P_Text Hydraulics Text 0 0 1 0 500 

HY_P_Water_Edge Lake, Pond, River, Stream Edge Line 11 stream 1 0 100 C 

HY_P_Water_Well 

Water Well Symbols 11 0 3 0 100 

CELLS PLACED ON LEVEL HY_P_Water_Well: 

Water Well Drilled with Well Log - - - 0 100 WWLP ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

HY – HYDRAULICS – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 


HY_P_Wetland_Area Swamp/Wetland Area Outline 11 stream 1 0 100 C 

HY_P_Wetland_Cells 

Swamp/Wetland Symbols 11 0 1 0 100 

CELLS PLACED ON LEVEL HY__P_Wetland_Cells: 

Swamp/Wetland Symbol - - - 0 100 SWAMPP ODOT_Symbols.cel C 

LT – LIGHTING - EXISTING: 

LT_X_Cantilever_Support Cantilever Support 11 2 0 0 -100 

LT_X_Circuit Lighting Circuit 3 2 0 0 -100 

LT_X_Conc_Work_Pad Lighting Concrete Work Pad 20 2 0 0 -100 

LT_X_Conduit Lighting Conduit 3 conduitex 0 0 -100 C 

LT_X_Control_Center 

Lighting Control Center/Power Service 

Symbols 

CELLS PLACED ON LEVEL LT_X_Control_Center: 

3 0 0 0 -100 

Control Center/Power Service - - - 0 -100 CCPS ODOT_Symbols.cel C 

LT_X_Foundation Light Foundation 0 1 0 0 -100 

LT_X_Luminaires 

Luminaire Symbols 4 0 0 0 -100 

CELLS PLACED ON LEVEL LT_X_Luminaires: 

Conventional Ground Mounted Luminaire - - - 0 -100 CGM ODOT_Symbols.cel C 

Conventional Structure Mounted Luminaire - - - 0 -100 CSM ODOT_Symbols.cel C 

High Mast Luminaire Asymmetric - - - 0 -100 HMA ODOT_Symbols.cel C 

High Mast Luminaire Long and Narrow - - - 0 -100 HMLN ODOT_Symbols.cel C 

High Mast Luminaire Symmetric - - - 0 -100 HMS ODOT_Symbols.cel C 

Low Mast Luminaire Asymmetric - - - 0 -100 LMA ODOT_Symbols.cel C 

Low Mast Luminaire Long and Narrow - - - 0 -100 LMLN ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





LT_X_Luminaires (cont’d) 

LT_X_Poles 

LT_X_PullBox 

CELLS PLACED ON LEVEL LT_X_Luminaires (cont’d): 

Color 

Style 

LT – LIGHTING – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


Low Mast Luminaire Symmetric - - - 0 -100 LMS ODOT_Symbols.cel C 

Post Top Luminaire - - - 0 -100 PTOP ODOT_Symbols.cel C 

Underpass Luminaire - - - 0 -100 UND ODOT_Symbols.cel C 

Light Pole Symbols 4 0 0 0 -100 

CELLS PLACED ON LEVEL LT_X_Poles: 

Light Pole - - - 0 -100 LPOLE ODOT_Symbols.cel C 

Lighting Pull Box Symbols 3 0 0 0 -100 

CELLS PLACED ON LEVEL LT_X_PullBox: 

Pull Box/Junction Box - - - 0 -100 PBJB ODOT_Symbols.cel C 

LT_X_Support Light Support 11 1 0 0 -100 

LT_X_Text Lighting Text 0 0 0 0 500 

LT – LIGHTING - PROPOSED: 

LT_P_Cantilever_Support Cantilever Support 11 0 1 0 100 

LT_P_Circuit2 Lighting Circuit 2-Conductor 4 cond2 1 0 100 C 

LT_P_Circuit3 Lighting Circuit 3-Conductor 4 cond3 1 0 100 C 

LT_P_Conc_Work_Pad Lighting Concrete Work Pad 20 0 1 0 100 

LT_P_Conduit Lighting Conduit Line 3 conduitpr 1 0 100 C 

LT_P_Conduit_Cells 

LT_P_Control_Center 

Lighting Conduit Symbols 4 0 1 0 100 

CELLS PLACED ON LEVEL LT_P_Conduit_Cells: 

Conduit Stub - - - 0 100 CSTUB ODOT_Symbols.cel C 

Lighting Control Center Symbols 3 0 0 0 100 

CELLS PLACED ON LEVEL LT_P_Control_Center: 

Control Center/Power Service - - - 0 100 CCPSP ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

LT – LIGHTING – PROPOSED (cont’d): 

LT_P_Foundation Light Foundation 0 0 1 0 100 

LT_P_Intensity_1 Luminaire Level 1 Patterns for Design 1 0 1 0 100 

LT_P_Intensity_2 Luminaire Level 2 Patterns for Design 1 0 2 0 100 

LT_P_Luminaires 

LT_P_Poles 

LT_P_PullBox 

Luminaire Symbols 4 0 0 0 100 

CELLS PLACED ON LEVEL LT_P_Luminaires: 

Weight 

Transparency 

Priority 


Conventional Ground Mounted Luminaire - - - 0 100 CGMP ODOT_Symbols.cel C 

Conventional Structure Mounted Luminaire - - - 0 100 CSMP ODOT_Symbols.cel C 

High Mast Luminaire Asymmetric - - - 0 100 HMAP ODOT_Symbols.cel C 

High Mast Luminaire Long and Narrow - - - 0 100 HMLNP ODOT_Symbols.cel C 

High Mast Luminaire Symmetric - - - 0 100 HMSP ODOT_Symbols.cel C 

Low Mast Luminaire Asymmetric - - - 0 100 LMAP ODOT_Symbols.cel C 

Low Mast Luminaire Long and Narrow - - - 0 100 LMLNP ODOT_Symbols.cel C 

Low Mast Luminaire Symmetric - - - 0 100 LMSP ODOT_Symbols.cel C 

Post Top Luminaire - - - 0 100 PTOPP ODOT_Symbols.cel C 

Underpass Luminaire - - - 0 100 UNDP ODOT_Symbols.cel C 

Light Pole Symbols 4 0 0 0 100 

CELLS PLACED ON LEVEL LT_P_Poles: 

Light Pole - - - 0 100 LPOLEP ODOT_Symbols.cel C 

Lighting Pull Box Symbols 3 0 0 0 100 

CELLS PLACED ON LEVEL LT_P_PullBox: 

Pull Box/Junction Box - - - 0 100 PBJBP ODOT_Symbols.cel C 

LT_P_Support Light Support 11 0 1 0 100 

LT_P_Text Lighting Text 0 0 1 0 500 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




MT_X_Cells 


Color 

Style 

MT – MAINTENANCE OF TRAFFIC - EXISTING: 

Maintenance of Traffic Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL MT_X_Cells: 

Weight 

Transparency 

Priority 


Barricade Type III - - - 0 -100 BARRICADEX ODOT_Symbols.cel P 

Changeable Message Sign - - - 0 -100 CMESSAGE_SGNX ODOT_Symbols.cel P 

Flashing Arrow Panel 48” - - - 0 -100 FARROW_48X ODOT_Symbols.cel C 



Lane Arrow Left - - - 0 -100 PMLFTX_MT ODOT_Symbols.cel P 

Lane Arrow Left-Thru - - - 0 -100 PMLTX_MT ODOT_Symbols.cel P 

Lane Arrow Left-Thru-Right - - - 0 -100 PMLTRX_MT ODOT_Symbols.cel P 

Lane Arrow Right - - - 0 -100 PMRTX_MT ODOT_Symbols.cel P 

Lane Arrow Thru - - - 0 -100 PMTHRX_MT ODOT_Symbols.cel P 

Lane Arrow Right-Thru - - - 0 -100 PMTRX_MT ODOT_Symbols.cel P 

MT_X_Channelizing_Line Maintenance of Traffic Channelizing Line 0 0 1 0 -100 

MT_X_CL_20 

MT_X_CL_30 

MT_X_CL_40 

MT_X_CL_50 

Maintenance of Traffic Centerline and 

Stations, 20 Scale 







0 cl20 0 0 500 P 

0 cl20 0 0 500 P 

0 cl50 0 0 500 P 

0 cl50 0 0 500 P 

MT_X_CL_Dashed Maintenance of Traffic Centerline, Dashed 4 lane 0 0 -100 P 

MT_X_CL_Dashed_II 

MT_X_CL_Double_Solid 

MT_X_CL_Pass_Proh_LT 

MT_X_CL_Pass_Proh_RT 

Maintenance of Traffic Centerline, 

Dashed Class II 


Double Solid 


Passing Prohibited Left 


Passing Prohibited Right 

4 motclass2 0 0 -100 P 

4 dsolidcl 0 0 -100 P 

4 ppleft 0 0 -100 P 

4 ppright 0 0 -100 P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

MT – MAINTENANCE OF TRAFFIC – EXISTING (cont’d): 

MT_X_Crosswalk_Line Maintenance of Traffic Crosswalk Line 0 0 1 0 -100 

MT_X_Dotted_Line 

MT_X_Drums 

MT_X_Edge_Line 

Maintenance of Traffic Dotted Line, 

White, (2' Dash - 6' Gap) 


White, (3’Dash 9’ Gap) 

Weight 

Transparency 

Priority 


0 dotted 0 0 -100 P 

0 * dotted3 0 0 -100 P 


Yellow, (3’Dash 9’ Gap) * 4 * dotted3 0 0 -100 P 

Maintenance of Traffic Drums 6 0 0 0 -100 

MOT Drums at 5' Spacing 6 * motdrum5 0 0 -100 P 














CELLS PLACED ON LEVEL MT_X_Drums: 

MOT Drum - - - 0 -100 DRUMX ODOT_Symbols.cel P 

Maintenance of Traffic Edge Line, White 0 0 0 0 -100 

Maintenance of Traffic Edge Line. Yellow * 4 0 0 0 -100 

MT_X_Gore_Marking Maintenance of Traffic Gore Marking 0 0 0 0 -100 

MT_X_GR_Bar 

Maintenance of Traffic Barrier Design 

Guardrail 

9 bargrpr 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

MT – MAINTENANCE OF TRAFFIC – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


MT_X_GR_Lt Maintenance of Traffic Guardrail Left 9 grltpr 0 0 -100 C 

MT_X_GR_Rt Maintenance of Traffic Guardrail Right 9 grrtpr 0 0 -100 C 

MT_X_Island 

Maintenance of Traffic Island, White 0 0 0 0 -100 

Maintenance of Traffic Island, Yellow * 4 0 0 0 -100 

MT_X_Lane_Line Maintenance of Traffic Lane Line 0 lane 0 0 -100 P 

MT_X_Lane_Line_II Maintenance of Traffic Lane Line Class II 0 motclass2 0 0 -100 P 

MT_X_PCB 

Maintenance of Traffic Portable Concrete 

Barrier 

MT_X_Signal Maintenance of Traffic Signal 2 0 0 0 -100 

MT_X_Stop_Line Maintenance of Traffic Stop Bar 0 0 3 0 -100 

MT_X_Temp_Road Maintenance of Traffic Temporary Road 6 0 1 0 -100 

MT_X_Text Maintenance of Traffic Text 0 0 0 0 500 

MT_X_Traffic_Attenuator Maintenance of Traffic Attenuator 9 0 0 0 -100 

MT_X_Transverse_Line 

Maintenance of Traffic Transverse Line, 

White 

0 motpcb 1 0 -100 P 

0 0 0 0 -100 


Yellow * 4 0 0 0 -100 

MT_X_Work_Area Maintenance of Traffic Work Area 0 0 0 0 -100 

MT_P_Cells 

MT – MAINTENANCE OF TRAFFIC - PROPOSED: 

Maintenance of Traffic Symbols 0 0 0 0 100 

CELLS PLACED ON LEVEL MT_P_Cells: 

Barricade Type III - - - 0 100 BARRICADEP ODOT_Symbols.cel P 

Changeable Message Sign - - - 0 100 CMESSAGE_SGNP ODOT_Symbols.cel P 

Flashing Arrow Panel 48” - - - 0 100 FARROW_48P ODOT_Symbols.cel C 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




MT_P_Cells (cont’d) 


CELLS PLACED ON LEVEL MT_P_Cells (cont’d): 

Color 

Style 

MT – MAINTENANCE OF TRAFFIC – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 



Lane Arrow Left - - - 0 100 PMLFTP_MT ODOT_Symbols.cel P 

Lane Arrow Left-Thru - - - 0 100 PMLTP_MT ODOT_Symbols.cel P 

Lane Arrow Left-Thru-Right - - - 0 100 PMLTRP_MT ODOT_Symbols.cel P 

Lane Arrow Right - - - 0 100 PMRTP_MT ODOT_Symbols.cel P 

Lane Arrow Thru - - - 0 100 PMTHRP_MT ODOT_Symbols.cel P 

Lane Arrow Right-Thru - - - 0 100 PMTRP_MT ODOT_Symbols.cel P 

MT_P_Channelizing_Line Maintenance of Traffic Channelizing Line 0 0 2 0 100 

MT_P_CL_20 

MT_P_CL_30 

MT_P_CL_40 

MT_P_CL_50 









0 cl20 1 0 500 P 

0 cl20 1 0 500 P 

0 cl50 1 0 500 P 

0 cl50 1 0 500 P 

MT_P_CL_Dashed Maintenance of Traffic Centerline, Dashed 4 lane 1 0 100 P 

MT_P_CL_Dashed_II 

MT_P_CL_Double_Solid 

MT_P_CL_Pass_Proh_LT 

MT_P_CL_Pass_Proh_RT 


Dashed Class II 


Double Solid 


Passing Prohibited Left 


Passing Prohibited Right 

MT_P_Crosswalk_Line Maintenance of Traffic Crosswalk Line 0 0 2 0 100 

MT_P_Dotted_Line 


White, (2' Dash - 6' Gap) 

4 motclass2 1 0 100 P 

4 dsolidcl 1 0 100 P 

4 ppleft 1 0 100 P 

4 ppright 1 0 100 P 

0 dotted 1 0 100 P 


Yellow, (2' Dash - 6' Gap) * 4 dotted 1 0 100 P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





MT_P_Dotted_Line (cont’d) 

MT_P_Drums 

MT_P_Edge_Line 


White, (3’Dash 9’ Gap) 

Color 

Style 


Weight 

Transparency 

Priority 


0 * dotted3 1 0 100 P 


Yellow, (3’Dash 9’ Gap) * 4 * dotted3 1 0 100 P 

Maintenance of Traffic Drums 6 0 0 0 100 

MOT Drums at 5' Spacing 6 * motdrum5 0 0 100 P 














CELLS PLACED ON LEVEL MT_P_Drums: 

MOT Drum - - - 0 100 DRUM ODOT_Symbols.cel P 

Maintenance of Traffic Edge Line, White 0 0 1 0 100 

Maintenance of Traffic Edge Line. Yellow * 4 0 1 0 100 

MT_P_Gore_Marking Maintenance of Traffic Gore Marking 0 0 1 0 100 

MT_P_GR_Bar 

Maintenance of Traffic Barrier Design 

Guardrail 

9 bargrpr 1 0 100 C 

MT_P_GR_Lt Maintenance of Traffic Guardrail Left 9 grltpr 1 0 100 C 

MT_P_GR_Rt Maintenance of Traffic Guardrail Right 9 grrtpr 1 0 100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




MT_P_Island 


Color 

Style 


Maintenance of Traffic Island, White 0 0 0 0 100 

Maintenance of Traffic Island, Yellow * 4 0 0 0 100 

Weight 

Transparency 

Priority 


MT_P_Lane_Line Maintenance of Traffic Lane Line 0 lane 1 0 100 P 

MT_P_Lane_Line_II Maintenance of Traffic Lane Line Class II 0 motclass2 1 0 100 P 

MT_P_PCB 

Maintenance of Traffic Portable Concrete 

Barrier 

MT_P_Signal Maintenance of Traffic Signal 2 0 1 0 100 

MT_P_Stop_Line Maintenance of Traffic Stop Bar 0 0 4 0 100 

MT_P_Temp_Road Maintenance of Traffic Temporary Road 6 0 2 0 100 

MT_P_Text Maintenance of Traffic Text 0 0 1 0 500 

MT_P_Traffic_Attenuator Maintenance of Traffic Attenuator 9 0 1 0 100 

MT_P_Transverse_Line 


White 

0 motpcb 2 0 100 P 

0 0 1 0 100 


Yellow * 4 0 1 0 100 

MT_P_Work_Area Maintenance of Traffic Work Area 0 0 0 0 100 

PF – PROFILES - EXISTING: 

PF_X_Ground_Line Existing Ground Line 2 2 1 0 -100 

PF_X_Text Profile Text 0 0 0 0 500 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

PF – PROFILES - PROPOSED: 

PF_P_Grade_Line Profile Grade Line 0 0 2 0 100 

PF_P_Sta_Elev_Text 

Station and Elevation text along horizontal 

and vertical axis 

0 0 1 0 500 

PF_P_Text Profile Text 0 0 1 0 500 

PM_X_Cells 

PM – PAVEMENT MARKING - EXISTING: 

Pavement Marking Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL PM_X_Cells: 

Weight 

Transparency 

Priority 


Dual Left Turn Arrows - - - 0 -100 PMDLT ODOT_Symbols.cel P 

Delineator Marker - - - 0 -100 PMDM ODOT_Symbols.cel P 

Symbol Handicap Alternate Special Size - - - 0 -100 PMHA ODOT_Symbols.cel P 

Symbol Handicap Standard Size - - - 0 -100 PMHS ODOT_Symbols.cel P 

Lane Arrow Left - - - 0 -100 PMLFT ODOT_Symbols.cel P 

Lane Arrow Left-Thru - - - 0 -100 PMLT ODOT_Symbols.cel P 

Lane Arrow Left-Thru-Right - - - 0 -100 PMLTR ODOT_Symbols.cel P 

Word on Pavement "ONLY", 6 Foot - - - 0 -100 PMON6 ODOT_Symbols.cel P 

Word on Pavement "ONLY", 8 Foot - - - 0 -100 PMON8 ODOT_Symbols.cel P 

Symbol Preferential Lane - - - 0 -100 PMPR ODOT_Symbols.cel P 

Raised Pavement Marker, 

1-Way Reflector 



- - - 0 -100 PMRM1 ODOT_Symbols.cel P 

- - - 0 -100 PMRM2 ODOT_Symbols.cel P 

Symbol Railroad Crossing, 7 Foot - - - 0 -100 PMRR7 ODOT_Symbols.cel P 



C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




PM_X_Cells (cont’d) 


CELLS PLACED ON LEVEL PM_X_Cells (cont’d): 

Color 

Style 

PM – PAVEMENT MARKING – EXISTING (cont’d): 

Weight 

Transparency 

Priority 





Symbol Railroad Crossing, Alternative- 

Narrow 

- - - 0 -100 PMRR_ALTX ODOT_Symbols.cel P 

Lane Arrow Right - - - 0 -100 PMRT ODOT_Symbols.cel P 

Word on Pavement "SCHOOL", 6 Foot - - - 0 -100 PMSC6 ODOT_Symbols.cel P 

Word on Pavement SCHOOL", 8 Foot - - - 0 -100 PMSC8 ODOT_Symbols.cel P 

Word on Pavement SCHOOL", 10 Foot - - - 0 -100 PMSC10 ODOT_Symbols.cel P 

Word on Pavement "STOP", 6 Foot - - - 0 -100 PMST6 ODOT_Symbols.cel P 

Word on Pavement "STOP", 8 Foot - - - 0 -100 PMST8 ODOT_Symbols.cel P 

Lane Arrow Thru - - - 0 -100 PMTHR ODOT_Symbols.cel P 

Lane Arrow Right-Thru - - - 0 -100 PMTR ODOT_Symbols.cel P 

Pavement Marking Symbol 

Bicyclist 4 Foot 





- - - 0 -100 PM_BCYCLIST4X ODOT_Symbols.cel P 



Pavement Marking Bicyclist Detector - - - 0 -100 PM_BCYCLIST_DETX ODOT_Symbols.cel P 

Pavement Marking Symbol Bike 4 Foot - - - 0 -100 PM_BIKE4X ODOT_Symbols.cel P 



Legend/Word on Pavement 

“BIKE” 44 Inches 


“LANE” 44 Inches 

Pavement Marking Ramp 

Pavement Arrow 

- - - 0 -100 PM_LGD_BIKE44X ODOT_Symbols.cel P 

- - - 0 -100 PM_LGD_LANE44X ODOT_Symbols.cel P 

- - - 0 -100 PM_RAMP_ARWX ODOT_Symbols.cel P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




PM_X_Cells (cont’d) 


CELLS PLACED ON LEVEL PM_X_Cells (cont’d): 

Pavement Marking Lane 

Reduction Arrow 

Color 

Style 


Weight 

Transparency 

Priority 


- - - 0 -100 PM_RDUCTION_ARWX ODOT_Symbols.cel P 

Pavement Marking Speed Hump 6 Foot - - - 0 -100 PM_SPD_HUMP6X ODOT_Symbols.cel P 

Pavement Marking Speed Hump 12 Foot - - - 0 -100 PM_SPD_HUMP12X ODOT_Symbols.cel P 

Pavement Marking Wrong Way Arrow - - - 0 -100 PM_WRONGWY_ARWX ODOT_Symbols.cel P 

Pavement Marking Yield Ahead 

Triangle 13 Foot 



Pavement Marking Yield Triangle 

Minimum Base 12 In. 


Maximum Base 24 in. 

- - - 0 -100 PM_YIELD_AHD13X ODOT_Symbols.cel P 

- - - 0 -100 PM_YIELD_AHD20X ODOT_Symbols.cel P 

- - - 0 -100 PM_YIELD_MIN ODOT_Symbols.cel P 

- - - 0 -100 PM_YIELD_MAX ODOT_Symbols.cel P 

Truncated Dome (Generic Pattern) - - - 0 -100 TDOME ODOT_Symbols.cel P 

PM_X_Channelizing_Line Channelizing Line 0 0 1 0 -100 

PM_X_CL_Dashed Centerline, Dashed 4 lane 0 0 -100 P 

PM_X_CL_Double_Solid Centerline, Double Solid 4 dsolidcl 0 0 -100 P 

PM_X_CL_Pass_Proh_Lt Centerline, Passing Prohibited Left 4 ppleft 0 0 -100 P 

PM_X_CL_Pass_Proh_Rt Centerline, Passing Prohibited Right 4 ppright 0 0 -100 P 

PM_X_Crosswalk Crosswalk Line 0 0 0 0 -100 

PM_X_Dotted_Line 

Dotted Line, (2' Dash - 6' Gap) 0 dotted 0 0 -100 P 

Dotted Line, (3' Dash - 9' Gap) 0 * dotted3 0 0 -100 P 

PM_X_Edge_Line Edge Line 4 0 0 0 -100 

PM_X_Island Island, White 0 0 0 0 -100 

PM_X_Lane_Line Lane Line 0 lane 0 0 -100 P 

PM_X_Parking_Lot_Stall Parking Lot Stall Marking Line 0 5 0 0 -100 

PM_X_Stop_Line Stop Bar 0 0 2 0 -100 

PM_X_Surveyed_Line 

Generic paint line on pavement 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

3 0 2 0 -100 





Color 

Style 


PM_X_Transverse_Line Transverse Line 0 0 0 0 -100 

Weight 

Transparency 

Priority 


PM_X_Yield_Line Yield Line 0 yieldex 0 0 -100 P 

PM_P_Cells 

PM – PAVEMENT MARKING - PROPOSED: 

Pavement Marking Symbols 0 0 1 0 100 

CELLS PLACED ON LEVEL PM_P_Cells: 

Dual Left Turn Arrows - - - 0 100 PMDLTP ODOT_Symbols.cel P 

Delineator Marker - - - 0 100 PMDMP ODOT_Symbols.cel P 

Symbol Handicap Alternate Special Size - - - 0 100 PMHAP ODOT_Symbols.cel P 

Symbol Handicap Standard Size - - - 0 100 PMHSP ODOT_Symbols.cel P 

Lane Arrow Left - - - 0 100 PMLFTP ODOT_Symbols.cel P 

Lane Arrow Left-Thru - - - 0 100 PMLTP ODOT_Symbols.cel P 

Lane Arrow Left-Thru-Right - - - 0 100 PMLTRP ODOT_Symbols.cel P 

Word on Pavement "ONLY", 6 Foot - - - 0 100 PMON6P ODOT_Symbols.cel P 

Word on Pavement "ONLY", 8 Foot - - - 0 100 PMON8P ODOT_Symbols.cel P 

Symbol Preferential Lane - - - 0 100 PMPRP ODOT_Symbols.cel P 





- - - 0 100 PMRM1P ODOT_Symbols.cel P 

- - - 0 100 PMRM2P ODOT_Symbols.cel P 

Symbol Railroad Crossing, 7 Foot - - - 0 100 PMRR7P ODOT_Symbols.cel P 





C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




PM_P_Cells (cont’d) 


CELLS PLACED ON LEVEL PM_P_Cells (cont’d): 

Color 

Style 

PM – PAVEMENT MARKING – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 



Symbol Railroad Crossing, Alternative- 

Narrow 

- - - 0 100 PMRR_ALTP ODOT_Symbols.cel P 

Lane Arrow Right - - - 0 100 PMRTP ODOT_Symbols.cel P 

Word on Pavement "SCHOOL", 6 Foot - - - 0 100 PMSC6P ODOT_Symbols.cel P 

Word on Pavement SCHOOL", 8 Foot - - - 0 100 PMSC8P ODOT_Symbols.cel P 

Word on Pavement SCHOOL", 10 Foot - - - 0 100 PMSC10P ODOT_Symbols.cel P 

Word on Pavement "STOP", 6 Foot - - - 0 100 PMST6P ODOT_Symbols.cel P 

Word on Pavement "STOP", 8 Foot - - - 0 100 PMST8P ODOT_Symbols.cel P 

Lane Arrow Thru - - - 0 100 PMTHRP ODOT_Symbols.cel P 

Lane Arrow Right-Thru - - - 0 100 PMTRP ODOT_Symbols.cel P 







- - - 0 100 PM_BCYCLIST4X ODOT_Symbols.cel P 



Pavement Marking Bicyclist Detector - - - 0 100 PM_BCYCLIST_DETX ODOT_Symbols.cel P 

Pavement Marking Symbol Bike 4 Foot - - - 0 100 PM_BIKE4X ODOT_Symbols.cel P 




“BIKE” 44 Inches 


“LANE” 44 Inches 

Pavement Marking Ramp 

Pavement Arrow 

Pavement Marking Lane 

Reduction Arrow 

- - - 0 100 PM_LGD_BIKE44X ODOT_Symbols.cel P 

- - - 0 100 PM_LGD_LANE44X ODOT_Symbols.cel P 

- - - 0 100 PM_RAMP_ARWX ODOT_Symbols.cel P 

- - - 0 100 PM_RDUCTION_ARWX ODOT_Symbols.cel P 

Pavement Marking Speed Hump 6 Foot - - - 0 100 PM_SPD_HUMP6X ODOT_Symbols.cel P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




PM_P_Cells (cont’d) 


CELLS PLACED ON LEVEL PM_P_Cells (cont’d): 

Color 

Style 


Weight 

Transparency 

Priority 


Pavement Marking Speed Hump 12 Foot - - - 0 100 PM_SPD_HUMP12X ODOT_Symbols.cel P 

Pavement Marking Wrong Way Arrow - - - 0 100 PM_WRONGWY_ARWX ODOT_Symbols.cel P 






Minimum Base 12 In. 


Maximum Base 24 in. 

- - - 0 100 PM_YIELD_AHD13X ODOT_Symbols.cel P 

- - - 0 100 PM_YIELD_AHD20X ODOT_Symbols.cel P 

- - - 0 100 PM_YIELD_MIN_P ODOT_Symbols.cel P 

- - - 0 100 PM_YIELD_MAX_P ODOT_Symbols.cel P 

Truncated Dome (Generic Pattern) - - - 0 100 TDOMEP ODOT_Symbols.cel P 

PM_P_Channelizing_Line Channelizing Line 0 0 2 0 100 

PM_P_CL_Dashed Centerline, Dashed 4 lane 1 0 100 P 

PM_P_CL_Double_Solid Centerline, Double Solid 4 dsolidcl 1 0 100 P 

PM_P_CL_Pass_Proh_Lt Centerline, Passing Prohibited Left 4 ppleft 1 0 100 P 

PM_P_CL_Pass_Proh_Rt Centerline, Passing Prohibited Right 4 ppright 1 0 100 P 

PM_P_Crosswalk Crosswalk Line 0 0 2 0 100 

PM_P_Dotted_Line 

PM_P_Edge_Line 

PM_P_Island 

Dotted Line, White, (2’ Dash – 6’ Gap) 0 dotted 1 0 100 P 

Dotted Line, Yellow, (2’ Dash – 6’ Gap) * 4 dotted 1 0 100 P 

Dotted Line, White, (3' Dash - 9' Gap) 0 * dotted3 1 0 100 P 

Dotted Line, Yellow, (3' Dash - 9' Gap) * 4 * dotted3 1 0 100 P 

Edge Line, White 0 0 1 0 100 

Edge Line, Yellow * 4 0 1 0 100 

Island, White 0 0 1 0 100 

Island, Yellow * 4 0 1 0 100 

PM_P_Lane_Line Lane Line 0 lane 1 0 100 P 

PM_P_Parking_Lot_Stall Parking Lot Stall Marking Line 0 0 2 0 100 

PM_P_Stop_Line Stop Bar 0 0 4 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 


Appendix A – CADD Information Table Revised April 20, 2012 



Color 

Style 


PM_P_Text Pavement Marking Text 0 0 1 0 500 

PM_P_Transverse_Line 

Transverse Line, White 0 0 2 0 100 

Transverse Line, Yellow * 4 0 2 0 100 

Weight 

Transparency 

Priority 


PM_P_Yield_Line Yield Line 0 yieldpr 1 0 100 P 

PV – PAVEMENT - EXISTING: 

PV_X_Bikeway Bikeway 12 1 0 0 -100 

PV_X_Curb Curb 10 1 0 0 -100 

PV_X_Driveway Driveways 0 5 0 0 -100 

PV_X_EOP Edge of Pavement 0 3 0 0 -100 

PV_X_Field_Drive Field Drive 2 5 0 0 -100 

PV_X_Joint Pavement Joint 7 0 0 0 -100 

PV_X_Parking_Lot Parking Lot 0 5 0 0 -100 

PV_X_Saw_Cut_Line Saw Cut Line 25 0 0 0 -100 

PV_X_Shoulder Shoulder/Berm Line 6 5 0 0 -100 

PV_X_Shoulder_Rumble_Strip Shoulder Rumble Strip 26 rumblestrip 0 0 -100 P 

PV_X_Steps Steps 10 1 0 0 -100 

PV_X_Text Pavement Text 0 0 0 0 500 

PV_X_Walk Sidewalk 10 5 0 0 -100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

PV – PAVEMENT - PROPOSED: 

PV_P_Bikeway Bikeway 12 0 1 0 100 

PV_P_Curb Curb 10 0 1 0 100 

PV_P_Curb_Ramp Curb Ramp 10 0 1 0 100 

PV_P_Drive Driveways 8 0 1 0 100 

PV_P_EOP Edge of Pavement 0 0 2 0 100 

PV_P_Field_Drive Field Drive 2 0 1 0 100 

PV_P_Joint Pavement Joint 7 0 1 0 100 

PV_P_Parking_Lot Parking Lot 1 0 1 0 100 

PV_P_Saw_Cut_Line Saw Cut Line 25 0 1 0 100 

PV_P_Shoulder Shoulder/Berm Line 6 0 1 0 100 

PV_P_Shoulder_Barrier Shoulder Barrier 9 0 1 0 100 

Weight 

Transparency 

Priority 


PV_P_Shoulder_Rumble_Strip Shoulder Rumble Strip 26 rumblestrip 1 0 100 P 

PV_P_Steps Steps 9 0 1 0 100 

PV_P_Text Pavement Text 0 0 1 0 500 

PV_P_Walk Sidewalk 13 0 1 0 100 

RC – RECREATIONAL - EXISTING: 

RC_X_Golf_Course Golf Course Features 69 5 0 0 -100 

RC_X_Misc 

Miscellaneous Athletic and Recreational 

Features 

92 0 0 0 -100 

RC_X_Pool Private or Public Swimming Pools 60 6 0 0 -100 

RC_X_Text Recreational Text 0 0 0 0 500 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

RD – ROADWAY - EXISTING: 

RD_X_Anchor_Assembly Anchor Assembly Symbols 9 5 0 0 -100 

RD_X_Bedrock Bedrock 10 2 0 0 -100 

RD_X_Bumper_Block Parking Lot Block (Bumper Block) 0 2 0 0 -100 

RD_X_Cells 

Roadway Miscellaneous Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL RD_X_Cells: 

Weight 

Transparency 

Priority 


Air Conditioner - - - 0 -100 AC ODOT_Symbols.cel C 

Stationary Barbeque Grill - - - 0 -100 BBQ ODOT_Symbols.cel C 

Yard Light - - - 0 -100 BUDLIT ODOT_Symbols.cel C 

Flag Pole - - - 0 -100 FLAGP ODOT_Symbols.cel C 

Mail Box - - - 0 -100 MB ODOT_Symbols.cel C 

News Paper Box - - - 0 -100 PB ODOT_Symbols.cel C 

Parking Meter - - - 0 -100 PM ODOT_Symbols.cel C 

Post - - - 0 -100 POST ODOT_Symbols.cel C 

Headstone (Grave Marker) - - - 0 -100 RIP ODOT_Symbols.cel C 

Large Rock - - - 0 -100 ROCK ODOT_Symbols.cel C 

Satellite Dish - - - 0 -100 SATD ODOT_Symbols.cel C 

Sprinkler Head - - - 0 -100 SPKHD ODOT_Symbols.cel C 

Tower - - - 0 -100 TOWER ODOT_Symbols.cel C 

RD_X_Concrete_Barrier Concrete Barrier 43 3 0 0 -100 

RD_X_Concrete_Pad Concrete Pad 43 5 0 0 -100 

RD_X_Fence Fence Line 8 fenceex 0 0 -100 C 

RD_X_Gate Gate 8 gateex 0 0 -100 C 

RD_X_GR_Bar Guardrail Barrier Design 9 bargrex 0 0 -100 C 

RD_X_GR_Cable_Bar Guardrail Cable Barrier 9 grcableex 0 0 -100 C 

RD_X_GR_Lt Guardrail Left 9 grltex 0 0 -100 C 

RD_X_GR_Rt Guardrail Right 9 grrtex 0 0 -100 C 

RD_X_Misc_Items Miscellaneous Items 3 3 1 0 -100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

RD – ROADWAY – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


RD_X_Noise_Wall Noise Wall 40 noisewallex 0 0 -100 P 

RD_X_RR_1 Railroad line for 1:1 to 1:50 Scale 5 rr 0 0 -100 C 

RD_X_RR_2 Railroad line for 1:100 and over Scale 5 rr2 0 0 -100 C 

RD_X_RR_Cells 

Railroad Symbols 3 0 0 0 -100 

CELLS PLACED ON LEVEL RD_X_RR_Cells: 

Railroad Point of Switch - - - 0 -100 RRAILPS ODOT_Symbols.cel C 

Railroad Crossing - - - 0 -100 RRC ODOT_Symbols.cel C 

Railroad Point Rails Cross in Switch - - - 0 -100 RRFROG ODOT_Symbols.cel C 

Railroad Gate - - - 0 -100 RRG ODOT_Symbols.cel C 

Railroad Crossing Signal - - - 0 -100 RRS ODOT_Symbols.cel C 

RD_X_Text Roadway Text 0 0 0 0 500 

RD_X_Wall Retaining Wall 10 1 0 0 -100 

RD – ROADWAY - PROPOSED: 

RD_P_Anchor_Assembly Anchor Assembly Symbols 9 0 1 0 100 

RD_P_Cells 

Roadway Miscellaneous Symbols 0 0 0 0 100 

CELLS PLACED ON LEVEL RD_P_Cells: 

Guardrail Left Side - - - 0 100 GRLT ODOT_Symbols.cel C 

Guardrail Right Side - - - 0 100 GRRT ODOT_Symbols.cel C 

Mail Box - - - 0 100 MBP ODOT_Symbols.cel C 

New Paper Box - - - 0 100 PBP ODOT_Symbols.cel C 

Parking Meter - - - 0 100 PMP ODOT_Symbols.cel C 

Post - - - 0 100 POSTP ODOT_Symbols.cel C 

Sprinkler Head - - - 0 100 SPKHDP ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





RD_P_Concrete_Barrier 

Color 

Style 

RD – ROADWAY – PROPOSED (cont’d): 

Concrete Barrier 43 0 1 0 100 

Weight 

Transparency 

Priority 


Type D1 Single Slope Concrete Barrier, Left 43 * sscbD1lt 1 0 100 P 

Type D1 Single Slope Concrete Barrier, Right 43 * sscbD1rt 1 0 100 P 

Type D Single Slope Concrete Barrier, Left 43 * sscbDlt 1 0 100 P 

Type D Single Slope Concrete Barrier, Right 43 * sscbDrt 1 0 100 P 

RD_P_Fence Fence Line 8 fencepr 1 0 100 C 

RD_P_Gate Gate 8 gatepr 1 0 100 C 

RD_P_GR_Bar Guardrail Barrier Design 9 bargrpr 1 0 100 C 

RD_P_GR_Bar_Replaced Guardrail Barrier Design Replaced 9 bargrex/pr 1 0 100 C 

RD_P_GR_Cable_Bar Guardrail Cable Barrier 9 grcablepr 1 0 100 C 

RD_P_GR_Lt Guardrail Left 9 grltpr 1 0 100 C 

RD_P_GR_Lt_Replaced Guardrail Left Replaced 9 grltex/pr 1 0 100 C 

RD_P_GR_Rt Guardrail Right 9 grrtpr 1 0 100 C 

RD_P_GR_Rt_Replaced Guardrail Right Replaced 9 grrtex/pr 1 0 100 C 

RD_P_Median_Barrier 

Median Barrier 43 0 1 0 100 

Type B or C Single Slope Concrete Barrier 43 * sscbB 1 0 100 P 

Type B1 or C1 Single Slope Concrete Barrier 43 * sscbB1 1 0 100 P 

RD_P_Noise_Wall Noise Wall 40 noisewallpr 1 0 100 P 

RD_P_RR_1 Railroad line for 1:1 to 1:50 Scale 5 rr 1 0 100 C 

RD_P_RR_2 Railroad line for 1:100 and over Scale 5 rr2 1 0 100 C 

RD_P_Text Roadway Text 0 0 1 0 500 

RD_P_Wall Retaining Wall 10 0 1 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

RS – RASTER: 

RS_Raster1 Raster Attachment 0 0 0 0 -500 



RW – RIGHT OF WAY - EXISTING: 

Weight 

Transparency 

Priority 


RW_X_CL_10 Right of Way Centerline, 10 Scale 5 cl10 0 0 500 P 









RW_X_Esmt_A Aerial Easement 5 esmtaex 2 0 -100 C 

RW_X_Esmt_CH Channel Easement 5 esmtchex 2 0 -100 C 

RW_X_Esmt_ES Enhancement Scenic Easement 5 esmtesex 2 0 -100 C 

RW_X_Esmt_FL Flowage Easement 5 esmtflex 2 0 -100 C 

RW_X_Esmt_General 

Easement Line with no standard easement 

name 

5 esmtgenex 2 0 -100 C 

RW_X_Esmt_LA Limited Access Easement 5 esmtlaex 2 0 -100 C 

RW_X_Esmt_PB Protective Water Course Easement 5 esmtpbex 2 0 -100 C 

RW_X_Esmt_PS Protective Scenic Easement 5 esmtpsex 2 0 -100 C 

RW_X_Esmt_RR Railroad Easement 5 esmtrrex 2 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

RW – RIGHT OF WAY – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


RW_X_Esmt_RS Removal Scenic Easement 5 esmtrsex 2 0 -100 C 

RW_X_Esmt_SC Scenic Easement 5 esmtscex 2 0 -100 C 

RW_X_Esmt_SH Standard Highway Easement 5 esmtshex 2 0 -100 C 

RW_X_Esmt_SL Slope Easement 5 esmtslex 2 0 -100 C 

RW_X_Esmt_SW Sewer Easement 5 esmtswex 2 0 -100 C 

RW_X_Esmt_U Utility Easement 5 esmtuex 2 0 -100 C 

RW_X_Fee_RW Right of Way Fee 5 rowex 2 0 -100 C 

RW_X_Fee_WL Right of Way Fee with Limitation of Access 5 rowlaex 2 0 -100 C 

RW_X_Text Right of Way Text 0 0 0 0 500 

RW – RIGHT OF WAY - PROPOSED: 

RW_P_CL_10 Right of Way Centerline, 10 Scale 12 cl10 1 0 500 P 









RW_P_Const_Limits Construction Limits 10 constlimit 0 0 100 C 

RW_P_Esmt_A Aerial Easement 12 esmtapr 3 0 100 C 

RW_P_Esmt_CH Channel Easement 12 esmtchpr 3 0 100 C 

RW_P_Esmt_FL Flowage Easement 12 esmtflpr 3 0 100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

RW – RIGHT OF WAY – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 


RW_P_Esmt_LA Limited Access Easement 12 esmtlapr 3 0 100 C 

RW_P_Esmt_RR Railroad Easement 12 esmtrrpr 3 0 100 C 

RW_P_Esmt_SC Scenic Easement 12 esmtscpr 3 0 100 C 

RW_P_Esmt_SH Standard Highway Easement 12 esmtshpr 3 0 100 C 

RW_P_Esmt_SL Slope Easement 12 esmtslpr 3 0 100 C 

RW_P_Esmt_SW Sewer Easement 12 esmtswpr 3 0 100 C 

RW_P_Esmt_TMP Temporary Easement 12 esmtmppr 3 0 100 C 

RW_P_Esmt_U Utility Easement 12 esmtupr 3 0 100 C 

RW_P_Fee_RW Right of Way Fee 12 rowpr 3 0 100 C 

RW_P_Fee_WL Right of Way Fee with Limitation of Access 12 rowlapr 3 0 100 C 

RW_P_Prelim_RW Preliminary Engineering Right of Way Line 3 rowpe 3 0 100 C 

RW_P_Text Right of Way Text 0 0 1 0 500 

RW_P_WA Work Agreement Limits 12 roworkagreepr 3 0 100 C 

SC – SCRATCH: 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

SC_Scratch1 Scratch Level - Does Not Plot 0 0 0 0 0 





SC_Scratch6 Scratch Level - Plots 0 0 0 0 0 








Color 

Style 

SC – SCRATCH (cont’d): 


Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

SC_Scratch11 Scratch Level – Does Not Plot 0 0 0 0 0 










SC_Shading1 

SC_Shading2 

SC_Shading3 

Shading Level used to fill shapes with a 

shade of Gray. 





41 0 0 0 -200 

43 0 0 0 -200 

45 0 0 0 -200 





Color 

Style 

SG – SIGNALS - EXISTING: 

SG_X_Conc_Work_Pad Signal Concrete Work Pad 30 2 0 0 -100 

SG_X_Conduit Signal Conduit 0 5 0 0 -100 

SG_X_Controllers 

SG_X_Detection 

Signal Controller Symbols 0 3 0 0 -100 

CELLS PLACED ON LEVEL SG_X_Controllers: 

Weight 

Transparency 

Priority 


Signal Controller Base Mounted - - - 0 -100 CBM ODOT_Symbols.cel C 

Signal Controller Pole Mounted - - - 0 -100 CPM ODOT_Symbols.cel C 

Loop, Video, Microwave, etc. Detection 29 2 0 0 -100 

CELLS PLACED ON LEVEL SG_X_Detection: 

Signal Pedestrian Push Button - - - 0 -100 PEDPB ODOT_Symbols.cel C 

Signal Radar or Microwave Detector - - - 0 -100 SG_DET_RADAR_MICROW_X ODOT_Symbols.cel C 

Signal Video Camera Detector - - - 0 -100 SG_DET_VCAMERA_X ODOT_Symbols.cel C 

Signal Spread Spectrum Radio - - - 0 -100 SG_SSRADIO_X ODOT_Symbols.cel C 

SG_X_Foundation Signal Foundation 16 1 0 0 -100 

SG_X_Heads 

Signal Head Symbols 4 0 0 0 -100 

CELLS PLACED ON LEVEL SG_X_Heads: 

Signal Pedestrian Head 1-Way - - - 0 -100 PED1 ODOT_Symbols.cel C 

Signal Pedestrian Head 2-Way - - - 0 -100 PED2 ODOT_Symbols.cel C 

Signal Head for Mast Arm - - - 0 -100 SHMA ODOT_Symbols.cel C 

Signal Head for Mast Arm, 

3-Unit with Arrows 


4 or 5-Unit with Arrows 

- - - 0 -100 SHMA3 ODOT_Symbols.cel C 

- - - 0 -100 SHMA5 ODOT_Symbols.cel C 

Signal Head for Span Wire - - - 0 -100 SHSW ODOT_Symbols.cel C 

Signal Head for Span Wire, 




- - - 0 -100 SHSW3 ODOT_Symbols.cel C 

- - - 0 -100 SHSW5 ODOT_Symbols.cel C 

SG_X_Interconnect_Cable Signal/Traffic Interconnect Cable 0 interconnectex 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




SG_X_Manhole 


Color 

Style 

SG – SIGNALS – EXISTING (cont’d): 

Signal/Traffic Manhole Symbols 3 0 0 0 -100 

CELLS PLACED ON LEVEL SG_X_Manhole: 

Weight 

Transparency 

Priority 


Signal/Traffic Manhole - - - 0 -100 TRAFFIC_MH ODOT_Symbols.cel C 

SG_X_Mast_Arm Mast Arm 0 1 1 0 -100 

SG_X_Messenger_Wire Messenger Wire 3 0 0 0 -100 

SG_X_Poles 

SG_X_PullBox 

Signal Strain/Support Pole Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL SG_X_Poles: 

Signal Pedestal Support Pole - - - 0 -100 SPED ODOT_Symbols.cel C 

Signal Strain/Support Pole - - - 0 -100 SPOLE ODOT_Symbols.cel C 

Signal Pull Box Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL SG_X_PullBox: 

Signal Pull Box - - - 0 -100 SIGPB ODOT_Symbols.cel C 

SG_X_Text Signal Text 0 0 0 0 500 

SG_X_Wiring 

Loop Detector Lead-in, Signal, Distribution, 

Power & Service Cable 

3 1 0 0 -100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

SG – SIGNALS - PROPOSED: 

SG_P_Conc_Work_Pad Signal Concrete Work Pad 30 0 1 0 100 

SG_P_Conduit Signal Conduit 0 0 1 0 100 

SG_P_Controllers 

SG_P_Detection 

Signal Controller Symbols 0 0 1 0 100 

CELLS PLACED ON LEVEL SG_P_Controllers: 

Weight 

Transparency 

Priority 


Signal Controller Base Mounted - - - 0 100 CBMP ODOT_Symbols.cel C 

Signal Controller Pole Mounted - - - 0 100 CPMP ODOT_Symbols.cel C 

Loop, Video, Microwave, etc. Detection 29 0 1 0 100 

CELLS PLACED ON LEVEL SG_P_Detection: 

Angular Design Detection Loop - - - 0 100 ADD_LOOP ODOT_Symbols.cel C 

Signal Pedestrian Push Button - - - 0 100 PEDPBP ODOT_Symbols.cel C 

Signal Radar or Microwave Detector - - - 0 100 SG_DET_RADAR_MICROW_P ODOT_Symbols.cel C 

Signal Video Camera Detector - - - 0 100 SG_DET_VCAMERA_P ODOT_Symbols.cel C 

Signal Spread Spectrum Radio - - - 0 100 SG_SSRADIO_P ODOT_Symbols.cel C 

SG_P_Foundation Signal Foundation 16 0 1 0 100 

SG_P_Heads 

Signal Head Symbols 4 0 1 0 100 

CELLS PLACED ON LEVEL SG_P_Heads: 

Signal Pedestrian Head 1-Way - - - 0 100 PED1P ODOT_Symbols.cel C 

Signal Pedestrian Head 2-Way - - - 0 100 PED2P ODOT_Symbols.cel C 

Signal Head for Mast Arm - - - 0 100 SHMAP ODOT_Symbols.cel C 





- - - 0 100 SHMA3P ODOT_Symbols.cel C 

- - - 0 100 SHMA5P ODOT_Symbols.cel C 

Signal Head for Span Wire - - - 0 100 SHSWP ODOT_Symbols.cel C 





- - - 0 100 SHSW3P ODOT_Symbols.cel C 

- - - 0 100 SHSW5P ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

SG – SIGNALS – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 


SG_P_Interconnect_Cable Signal/Traffic Interconnect Cable 0 interconnectpr 1 0 100 C 

SG_P_Manhole 

Signal/Traffic Manhole Symbols 3 0 1 0 100 

CELLS PLACED ON LEVEL SG_P_Manhole: 

Signal/Traffic Manhole Adjusted 

or Reconstructed 

- - - 0 100 TRAFFIC_MHA ODOT_Symbols.cel C 

Signal/Traffic Manhole - - - 0 100 TRAFFIC_MHP ODOT_Symbols.cel C 

SG_P_Mast_Arm Mast Arm 0 0 2 0 100 

SG_P_Messenger_Wire Messenger Wire 3 0 1 0 100 

SG_P_Poles 

SG_P_PullBox 

Signal Strain/Support Pole Symbols 0 0 1 0 100 

CELLS PLACED ON LEVEL SG_P_Poles: 

Signal Pedestal Support Pole - - - 0 100 SPEDP ODOT_Symbols.cel C 

Signal Strain/Support Pole - - - 0 100 SPOLEP ODOT_Symbols.cel C 

Signal Pull Box Symbols 0 0 1 0 100 

CELLS PLACED ON LEVEL SG_P_PullBox: 

Signal Pull Box - - - 0 100 SIGPBP ODOT_Symbols.cel C 

SG_P_Text Signal Text 0 0 1 0 500 

SG_P_Wiring 

Loop Detector Lead-in, Signal, Distribution, 

Power & Service Cable 

0 0 1 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

SH – SHEETS: 

SH_Border Sheet Border 0 0 3 0 0 

Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

SH_Cut_Line Sheet Cut Line 0 3 0 0 0 

SH_Data 

Sheet Data 0 0 0 0 0 

CELLS PLACED ON LEVEL SH_Data: 

North Arrow - - - 0 0 NARROW ODOT_Sheets.cel C 

North Arrow - - - 0 0 NORTH ODOT_RW.cel C 

Surveyor’s Seal - - - 0 0 SEAL ODOT_RW.cel C 

SH_Major_Grid_Line Sheet Major Grid Line 44 0 1 0 -480 

SH_Masking 

Masking Level used to plot filled shapes 

white to mask any elements underneath. 

255 0 0 0 500 

SH_Minor_Grid_Line Sheet Minor Grid Line 40 0 0 0 -490 

SH_Text 

Sheet Text and Plan Sheet Annotation 0 0 1 0 500 

CELLS PLACED ON LEVEL SH_Text: 

Basis of Bearing Note - - - 0 500 BEARIN ODOT_RW.cel P 

Recording Block - - - 0 500 BLOCK ODOT_RW.cel C 

Calculated Area Note - - - 0 500 CALC_AREA ODOT_RW.cel P 

Centerline Monument Note - - - 0 500 CLMON ODOT_RW.cel C 

Conventional Symbols for 

2006 R/W Manual 

- - - 0 500 CONV_SYMBOLS ODOT_RW.cel P 

Curve Table for Parcels - - - 0 500 CURTAB ODOT_RW.cel C 

Encroachment Note - - - 0 500 ENCROA ODOT_RW.cel P 

Ex. R/W Certification - - - 0 500 EX_RW_CERTIF ODOT_RW.cel C 

LPA Ex. R/W Certification - - - 0 500 EX_RW_CERTIF_LPA ODOT_RW.cel C 

Method used to determine the 

Ex. R/W Width 

- - - 0 500 EXCLRW ODOT_RW.cel C 

Grantee Note - - - 0 500 GRANTE ODOT_RW.cel P 

Grid To Ground Table - - - 0 500 GRID ODOT_RW.cel C 

LA Declaration Note - - - 0 500 LADECL ODOT_RW.cel P 

D-50 Values Table - - - 0 500 LOG_D50 ODOT_Geotech.cel P 

Set Inside Construction Limits - - - 0 500 MONU_2B_DISTURBED ODOT_RW.cel C 




SH_Text (cont’d) 


CELLS PLACED ON LEVEL SH_Text (cont’d): 

Color 

Style 

SH – SHEETS (cont’d): 

Weight 

Transparency 

Priority 


Monument Legend - - - 0 500 MONU_LEGEND ODOT_RW.cel C 

Standard Monument Table to be filled in - - - 0 500 MONU_TABLE ODOT_RW.cel C 

Net Residue Calculation - - - 0 500 NET_RESID ODOT_RW.cel P 

Net Take Calculation - - - 0 500 NET_TAKE ODOT_RW.cel P 

Structure Note for Geotech - - - 0 500 NOTE1 ODOT_Geotech.cel P 

Names & Dates of Plan Prepared By - - - 0 500 PLAN_PREP_BY ODOT_RW.cel P 

Survey Control used for the Project - - - 0 500 PROJ_CONTROL ODOT_RW.cel P 

Prop. R/W Certification - - - 0 500 PR_RW_CERTIF ODOT_RW.cel C 

Brief Description of the Project Work - - - 0 500 PROJ_DESC ODOT_RW.cel P 

Temp. Easement Registration of Use Note - - - 0 500 REGIST ODOT_RW.cel P 

Character that Denotes Removal Items - - - 0 500 REMOVAL_ITEM ODOT_RW.cel P 

Standard Revision Block - - - 0 500 REVISI ODOT_RW.cel C 

R/W Plan Certification of 

Ex. & Prop. Work 

LPA R/W Plan Certification of 

Ex. & Prop. Work 

- - - 0 500 RW_PLAN_CERTIF ODOT_RW.cel C 

- - - 0 500 RW_PLAN_CERTIF_LPA ODOT_RW.cel C 

Summary of Soil Test Data - - - 0 500 SOIL_TEST_DATA ODOT_Geotech.cel P 

Structure Key - - - 0 500 STRUC_KEY ODOT_RW.cel P 

Summary Sheet Revision Block - - - 0 500 SUM_REV ODOT_RW.cel P 

List of Parcel Identifiers with Take Types - - - 0 500 

TYPES_OF_TITLE_ 

LEGEND 

ODOT_RW.cel P 

Temporary Parcel Duration - - - 0 500 TEMP_DURA ODOT_RW.cel P 

Total Number of Tabulations - - - 0 500 TOTAL ODOT_RW.cel P 

Utility Note - - - 0 500 UTILIT ODOT_RW.cel P 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

SN – SIGNS - EXISTING: 

SN_X_Billboard Billboard Sign 4 2 1 0 -100 

SN_X_Cantilever_Overhead Cantilever Overhead Sign Support- Existing 11 2 1 0 -100 

SN_X_Foundation 

Sign Foundation and Symbols 0 1 0 0 -100 

CELLS PLACED ON LEVEL SN_X_Foundation: 

Weight 

Transparency 

Priority 


Sign Support Foundation 30” - - - 0 -100 SSFN_30X ODOT_Symbols.cel P 

Sign Support Foundation 36” - - - 0 -100 SSFN_36X ODOT_Symbols.cel P 

Sign Truss Support Foundation 

TC-7.65, 4’-5” 


TC-7.65, 5’-7” 


TC-7.65, 6’-7” 


TC-15.115, 5’-3” 


TC-15.115, 6’-7” 

SN_X_Private Private Signs 20 0 0 0 -100 

SN_X_Public 

Public Sign Symbols 2 0 0 0 -100 

CELLS PLACED ON LEVEL SN_X_Public: 

- - - 0 -100 STFN_7.65-45X ODOT_Symbols.cel P 





1-Post Sign Back to Back - - - 0 -100 SGN1B ODOT_Symbols.cel C 

1-Post Sign - - - 0 -100 SGN1P ODOT_Symbols.cel C 

4 Signs on 1-Support - - - 0 -100 SGN1S ODOT_Symbols.cel C 

2-Post Sign Back to Back - - - 0 -100 SGN2B ODOT_Symbols.cel C 


4 Signs on 2-Supports - - - 0 -100 SGN2S ODOT_Symbols.cel C 


Sign Luminaire - - - 0 -100 SGNL ODOT_Symbols.cel C 

SN_X_Structure_Mount Overhead Structure Mounted Sign 11 2 1 0 -100 

SN_X_Text Signing Text 0 0 0 0 500 

SN_X_Truss_Overhead Truss Overhead Sign Support 11 2 1 0 -100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

SN – SIGNS - PROPOSED: 

SN_P_Cantilever_Overhead Cantilever Overhead 10 0 2 0 100 

SN_P_Foundation 

SN_P_Signs 

Sign Foundations and Symbols 0 0 1 0 100 

CELLS PLACED ON LEVEL SN_P_Foundation: 

Weight 

Transparency 

Priority 


30” Sign Support Foundation - - - 0 100 SSFN_30P ODOT_Symbols.cel P 

36” Sign Support Foundation - - - 0 100 SSFN_36P ODOT_Symbols.cel P 


TC-7.65, 4’-5” 


TC-7.65, 5’-7” 


TC-7.65, 6’-7” 


TC-15.115, 5’-3” 


TC-15.115, 6’-7” 

Public Sign Symbols 10 0 1 0 100 

CELLS PLACED ON LEVEL SN_P_Signs: 

- - - 0 100 STFN_7.65-45P ODOT_Symbols.cel P 





1-Post Sign Back to Back - - - 0 100 SGN1BP ODOT_Symbols.cel C 

1-Post Sign - - - 0 100 SGN1PP ODOT_Symbols.cel C 

4 Signs on 1-Support - - - 0 100 SGN1SP ODOT_Symbols.cel C 

2-Post Sign Back to Back - - - 0 100 SGN2BP ODOT_Symbols.cel C 


4 Signs on 2-Supports - - - 0 100 SGN2SP ODOT_Symbols.cel C 


SN_P_Structure_Mount Structure Mounted Sign 10 0 2 0 100 

SN_P_Text Signing Text 0 0 1 0 500 

SN_P_Truss_Overhead Truss Overhead Sign 10 0 2 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




ST_Details 

ST_Text 


Standard Construction Drawing/Plan Insert 

Sheet Details 

Standard Construction Drawing/Plan Insert 

Sheet Text and Dimensions 

Color 

Style 

ST – STANDARD CONSTRUCTION & PLAN INSERT DRAWINGS: 

0 0 1 0 0 

0 0 1 0 500 

SV – SURVEY – DATA ACQUISITION: 

SV_DA_Control_Point Data Acquisition Control Point 5 0 0 0 0 

SV_DA_Crossing Data Acquisition Crossing Break Line 3 0 2 0 500 

SV_DA_Locator Data Acquisition Point Locator 2 0 1 50 0 

SV_DA_Observation Data Acquisition Observation Line 9 2 0 50 -500 

SV_DA_Setup Data Acquistion Setup Line 7 0 0 50 -500 

SV – SURVEY - EXISTING: 

SV_X_Break_Lines Ground Break Line 7 2 0 0 -100 

SV_X_Center_of_Pavt Pavement Crown 7 4 0 0 -100 

Weight 

Transparency 

Priority 


SV_X_CL_Survey_100 Centerline of Survey, 100 Scale 0 cl100 0 0 500 P 







C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





SV_X_Control_Cells_Found 

Color 

Style 

SV – SURVEY – EXISTING (cont’d): 

Control Symbols Found 0 0 0 0 -100 

CELLS PLACED ON LEVEL SV_X_Control_Cells_Found: 

Weight 

Transparency 

Priority 


Benchmark Found - - - 0 -100 BM ODOT_Symbols.cel C 

Chiseled Benchmark Found - - - 0 -100 BMCHS ODOT_Symbols.cel C 

Drill Hole Found - - - 0 -100 DHOLE ODOT_Symbols.cel C 

Government Point Found - - - 0 -100 GOVD ODOT_Symbols.cel C 

Gin Spike Found - - - 0 -100 GSPK ODOT_Symbols.cel C 

Tacked Hub Found - - - 0 -100 HUBT ODOT_Symbols.cel C 

Mag Nail Found - - - 0 -100 MNAIL ODOT_Symbols.cel C 

P.K. Nail Found - - - 0 -100 PKNAIL ODOT_Symbols.cel C 

Carpenter Nail Found - - - 0 -100 NAIL ODOT_Symbols.cel C 

R.R. Spike Found - - - 0 -100 RRSPK ODOT_Symbols.cel C 

Default Circle Symbol placed by 

GEOPAK Survey 

Default Triangle Symbol placed by 

GEOPAK Survey 

- - - 0 -100 

- - - 0 -100 

SV_X_Edge_of_Slip Edge of Slip 8 2 0 0 -100 

SV_X_FDO For Direction only 0 0 0 0 -100 

SV_X_Finish_Floor Finished Floor Elevation 13 0 0 0 -100 

SV_X_Grid 

Grid Mark Symbols 1 0 0 0 -100 

CELLS PLACED ON LEVEL SV_X_Grid: 

Grid and or Tick Mark - - - 0 -100 GTM ODOT_Symbols.cel C 

SV_X_LiDAR_Check_Spots LiDAR Check Spots 0 0 1 0 -100 

SV_X_Mon_Cells_Found 

Monument Symbols Found 0 0 0 0 -100 

CELLS PLACED ON LEVEL SV_X_Mon_Cells_Found: 

Axle Found - - - 0 -100 AXLE ODOT_Symbols.cel C 

Iron Pin Found no I.D. Cap - - - 0 -100 IPF ODOT_Symbols.cel C 

Iron Pin Found with I.D. Cap - - - 0 -100 IPID ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





SV_X_Mon_Cells_Found (cont’d) 

CELLS PLACED ON LEVEL SV_X_Mon_Cells_Found (cont’d): 

Color 

Style 

SV – SURVEY – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


Iron Pipe Found - - - 0 -100 IPIPE ODOT_Symbols.cel C 

Concrete Monument Found - - - 0 -100 MON ODOT_Symbols.cel C 

Monument Box Found - - - 0 -100 MONBX ODOT_Symbols.cel C 

Mine Spike Found - - - 0 -100 MSPK ODOT_Symbols.cel C 

Corner Stone Found - - - 0 -100 STONE ODOT_Symbols.cel C 

T Bar Found - - - 0 -100 TBAR ODOT_Symbols.cel C 

SV_X_Occupation_Line Occupation Line 1 2 0 0 -100 

SV_X_Original_Ground Original Ground Line 2 2 0 0 -100 

SV_X_Random_Point 

Random Ground Shot Location 0 0 0 0 -100 

CELLS PLACED ON LEVEL SV_X_Random_Point: 

Random Ground Shot Elevation - - - 0 -100 X ODOT_Symbols.cel C 

SV_X_Shot_Marker Survey Point Location 4 0 0 0 -100 

SV_X_Text Survey Text 0 0 0 80 500 

SV_X_Text_Comment Survey Comments 0 0 0 0 500 

SV_X_Text_Description Survey Descriptions 0 0 0 0 500 

SV_X_Text_Elevation Survey Point Elevations 0 0 0 0 500 

SV_X_Text_Name Survey Point Names 0 0 0 0 500 

SV_X_Toe_of_Slope Toe of Slope 12 2 0 0 -100 

SV_X_Top_of_Bank Top of Bank 9 2 0 0 -100 

SV_X_Void_Area Generic Void Area 0 0 0 0 -100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




SV_P_Aerial_Targets 


SV_P_Control_Cells_Set 

SV_P_Mon_Cells_Set 

Color 

Style 

SV – SURVEY - PROPOSED: 

Aerial Target Symbols 4 0 0 0 100 

CELLS PLACED ON LEVEL SV_P_Aerial_Targets: 

Weight 

Transparency 

Priority 


Aerial Target Full, Main Line - - - 0 100 FCTRL ODOT_Symbols.cel C 

Aerial Target Wing Point, Off Main Line - - - 0 100 VCTRL ODOT_Symbols.cel C 

Control Symbols Set 0 0 0 0 100 

CELLS PLACED ON LEVEL SV_P_Control_Cells_Set: 

Chiseled Benchmark Set - - - 0 100 BMCHSS ODOT_Symbols.cel C 

Drill Hole Set - - - 0 100 DHOLES ODOT_Symbols.cel C 

Government Point Set - - - 0 100 GOVDS ODOT_Symbols.cel C 

Gin Spike Set - - - 0 100 GSPKS ODOT_Symbols.cel C 

Tacked Hub Set - - - 0 100 HUBTS ODOT_Symbols.cel C 

Mag Nail Set - - - 0 100 MNAILS ODOT_Symbols.cel C 

P.K. Nail Set - - - 0 100 PKNALS ODOT_Symbols.cel C 

R.R. Spike Set - - - 0 100 RRSPKS ODOT_Symbols.cel C 

Monument Symbols Set 0 0 0 0 100 

CELLS PLACED ON LEVEL SV_P_Mon_Cells_Set: 

Iron Pipe Set - - - 0 100 IPIPES ODOT_Symbols.cel C 

Iron Pin Set with I.D. Cap - - - 0 100 IPS ODOT_Symbols.cel C 

Monument Box Set - - - 0 100 MONBXP ODOT_Symbols.cel C 

Concrete Monument Set - - - 0 100 MONP ODOT_Symbols.cel C 

Mine Spike Set - - - 0 100 MSPKS ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

TR – TRUCK PATHS: 

TR_Text Truck Turning Path Text 0 0 1 0 500 

TR_Turning_Path1 Truck Turning Path 1 0 0 0 0 450 








TX – TEXT - EXISTING: 

TX_X_1 Text, Generic, 1 Scale 0 0 0 0 500 










Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





Color 

Style 

TX – TEXT - PROPOSED: 

TX_P_1 Text, Generic, 1 Scale 0 0 1 0 500 










TX_P_Misc Text, Generic, Miscellaneous Scale 0 0 1 0 500 

UT – UTILITIES - EXISTING: 

Weight 

Transparency 

Priority 


UT_X_Cable_TV Cable TV Line 6 cabletvex 0 0 -100 C 

UT_X_Cable_TV_Cells 

Cable TV Symbols 6 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Cable_TV_Cells: 

Cable TV Amplifier - - - 0 -100 CTVA ODOT_Symbols.cel C 

UT_X_Cable_TV_FO Fiber Optic Cable TV Line 6 foctvex 0 0 -100 C 

UT_X_Cable_TV_Text Cable TV Text 0 0 0 0 500 

UT_X_Cistern 

Cistern Symbols 1 2 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Cistern: 

Cistern - - - 0 -100 CISTERN ODOT_Symbols.cel C 

UT_X_Electric Electric Line 3 elecex 0 0 -100 C 

UT_X_Electric_Cells 

Electric Symbols 3 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Electric_Cells: 

Electric Riser/Pull Box - - - 0 -100 EBOX ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





UT_X_Electric_Cells (cont’d) 

CELLS PLACED ON LEVEL UT_X_Electric_Cells (cont’d): 

Color 

Style 

UT – UTILITIES – EXISTING (cont’d): 

Weight 

Transparency 

Priority 


Electric Meter - - - 0 -100 EM ODOT_Symbols.cel C 

Electric Manhole - - - 0 -100 EMH ODOT_Symbols.cel C 

Electric Pad Mounted Transformer - - - 0 -100 ETRANS ODOT_Symbols.cel C 

Electric Vault - - - 0 -100 EVLT ODOT_Symbols.cel C 

Power Line Marker - - - 0 -100 PMRK ODOT_Symbols.cel C 

Power Pole - - - 0 -100 PP ODOT_Symbols.cel C 

UT_X_Electric_Text Electric Text 0 0 0 0 500 

UT_X_Exposed_Pipes 

Exposed Pipes 

(Typically used for Aerial Mapping) 

0 2 0 0 -100 

UT_X_FO Generic Fiber Optic Line 6 foex 0 0 -100 C 

UT_X_Gas Gas Line 4 gasex 0 0 -100 C 

UT_X_Gas_Cells 

Gas Symbols 4 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Gas_Cells: 

Gas Meter - - - 0 -100 GM ODOT_Symbols.cel C 

Gas Manhole - - - 0 -100 GMH ODOT_Symbols.cel C 

Gas Line Marker - - - 0 -100 GMRK ODOT_Symbols.cel C 

Gas Service Stop - - - 0 -100 GSS ODOT_Symbols.cel C 

Gas Valve - - - 0 -100 GV ODOT_Symbols.cel C 

Gas Line Vent - - - 0 -100 GVENT ODOT_Symbols.cel C 

Gas Well - - - 0 -100 GWELL ODOT_Symbols.cel C 

UT_X_Gas_Text Gas Text 0 0 0 0 500 

UT_X_Leach_Bed Leach Bed Area 2 stream 0 0 -100 C 

UT_X_Misc_Cells 

Miscellaneous Utility Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Misc_Cells: 

Guywire Anchor (Deadman) - - - 0 -100 DM ODOT_Symbols.cel C 

Filter Bed - - - 0 -100 FBD ODOT_Symbols.cel C 

Petroleum Pump - - - 0 -100 GPUMP ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





UT_X_Misc_Cells (cont’d) 

CELLS PLACED ON LEVEL UT_X_Misc_Cells (cont’d): 

Color 

Style 


Weight 

Transparency 

Priority 


Power & Light Pole - - - 0 -100 PLP ODOT_Symbols.cel C 

Telecom & Light Pole - - - 0 -100 TLGT ODOT_Symbols.cel C 

Telecom, Light & Power Pole - - - 0 -100 TLPW ODOT_Symbols.cel C 

Tank Filler Cap - - - 0 -100 TNKCAP ODOT_Symbols.cel C 

Telecom & Power Pole - - - 0 -100 TPW ODOT_Symbols.cel C 

UT_X_Oil Oil Line 4 oilex 0 0 -100 C 

UT_X_Oil_Cells 

Oil Symbols 4 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Oil_Cells: 

Oil Tank - - - 0 -100 OTANK ODOT_Symbols.cel C 

Oil Well - - - 0 -100 OWELL ODOT_Symbols.cel C 

UT_X_San_Storm_Line Combination Sanitary/Storm Sewer Line 10 combsanstormex 0 0 -100 C 

UT_X_Sanitary_Cells 

Sanitary Symbols 2 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Sanitary_Cells: 

Septic Tank - - - 0 -100 SEPTC ODOT_Symbols.cel C 

Sanitary Sewer Manhole - - - 0 -100 SMH ODOT_Symbols.cel C 

Sanitary Sewer Line Marker - - - 0 -100 SSMRK ODOT_Symbols.cel C 

Sanitary Sewer Valve - - - 0 -100 SV ODOT_Symbols.cel C 

Sanitary Sewer Line Vent - - - 0 -100 SVENT ODOT_Symbols.cel C 

Sanitary Sewer Manhole No. 1 - - - 0 -100 MH1D-X-SAN ODOT_Drainage.cel P 

UT_X_Sanitary_Line Sanitary Sewer Line 2 sanex 0 0 -100 C 

UT_X_Sanitary_Pressure_Line Sanitary Sewer Pressure Line 2 san 0 0 -100 C 

UT_X_Sanitary_Text Sanitary Sewer Text 0 0 0 0 500 

UT_X_Tank Tank 4 2 0 0 -100 

UT_X_Telecom Telecommunication Line 6 teleex 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




UT_X_Telecom_Cells 


Color 

Style 


Telecommunication Symbols 6 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Telecom_Cells: 

Weight 

Transparency 

Priority 


Cellular Phone Tower - - - 0 -100 CELLTOWER ODOT_Symbols.cel C 

Telephone Pay - - - 0 -100 PPHONE ODOT_Symbols.cel C 

Telephone Booth - - - 0 -100 TBTH ODOT_Symbols.cel C 

Telecommunication Pole - - - 0 -100 TELP ODOT_Symbols.cel C 

Telecommunication Manhole - - - 0 -100 TMH ODOT_Symbols.cel C 

Telecommunication Line Marker - - - 0 -100 TMRK ODOT_Symbols.cel C 

Telephone Pedestal - - - 0 -100 TPED ODOT_Symbols.cel C 

Telecommunication Vault - - - 0 -100 TVLT ODOT_Symbols.cel C 

UT_X_Telecom_FO Fiber Optic Telecommunication Line 6 foteleex 0 0 -100 C 

UT_X_Telecom_Text Telecommunication Text 0 0 0 0 500 

UT_X_Unknown_Cells 

Unknown Object Symbols 0 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Unknown_Cells: 

Unknown Pull Box - - - 0 -100 UBOX ODOT_Symbols.cel C 

Unknown Manhole - - - 0 -100 UMH ODOT_Symbols.cel C 

Unknown Object - - - 0 -100 UOBJ ODOT_Symbols.cel C 

Unknown Pole - - - 0 -100 UP ODOT_Symbols.cel C 

Unknown Utility Valve - - - 0 -100 UVALVE ODOT_Symbols.cel C 

Unknown Well - - - 0 -100 UWELL ODOT_Symbols.cel C 

UT_X_Water Water Line 11 waterex 0 0 -100 C 

UT_X_Water_Cells 

Water Symbols 11 0 0 0 -100 

CELLS PLACED ON LEVEL UT_X_Water_Cells: 

Fire Hydrant - - - 0 -100 FH ODOT_Symbols.cel C 

Water Gate Valve - - - 0 -100 WGV ODOT_Symbols.cel C 

Water Line Marker - - - 0 -100 WLM ODOT_Symbols.cel C 

Water Meter - - - 0 -100 WM ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





UT_X_Water_Cells (cont’d) 

CELLS PLACED ON LEVEL UT_X_Water_Cells (cont’d): 

Color 

Style 


Weight 

Transparency 

Priority 


Water Manhole - - - 0 -100 WMH ODOT_Symbols.cel C 

Water Service Stop - - - 0 -100 WSS ODOT_Symbols.cel C 

Water Line Vent - - - 0 -100 WVENT ODOT_Symbols.cel C 

UT_X_Water_Text Water Text 0 0 0 0 500 

UT – UTILITIES - PROPOSED: 

UT_P_Electric Electric Line 3 elec 1 0 100 C 

UT_P_Electric_Cells 

Electric Symbols 3 0 1 0 100 

CELLS PLACED ON LEVEL UT_P_Electric_Cells: 

Electric Riser/Pull Box - - - 0 100 EBOXP ODOT_Symbols.cel C 

Electric Manhole - - - 0 100 EMHP ODOT_Symbols.cel C 

Electric Vault - - - 0 100 EVLTP ODOT_Symbols.cel C 

Power Pole - - - 0 100 PPP ODOT_Symbols.cel C 

UT_P_Electric_Text Electric Text 0 0 1 0 500 

UT_P_FO Generic Fiber Optic Line 6 fopr 1 0 100 C 

UT_P_Gas Gas Line 4 gas 1 0 100 C 

UT_P_Gas_Cells 

Gas Symbols 4 0 1 0 100 

CELLS PLACED ON LEVEL UT_P_Gas_Cells: 

Gas Service Stop - - - 0 100 GSSP ODOT_Symbols.cel C 

Gas Valve - - - 0 100 GVP ODOT_Symbols.cel C 

UT_P_Gas_Text Gas Text 0 0 1 0 500 

UT_P_Leach_Bed Leach Bed Area 9 stream 1 0 100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




UT_P_Misc_Cells 


Color 

Style 

UT – UTILITIES – PROPOSED (cont’d): 

Miscellaneous Utility Symbols 0 0 1 0 100 

CELLS PLACED ON LEVEL UT_P_Misc_Cells: 

Weight 

Transparency 

Priority 


Power & Light Pole - - - 0 100 PLPP ODOT_Symbols.cel C 

Telecom & Light Pole - - - 0 100 TLGTP ODOT_Symbols.cel C 

Telecom, Light & Power Pole - - - 0 100 TLPWP ODOT_Symbols.cel C 

Telecom & Power Pole - - - 0 100 TPWP ODOT_Symbols.cel C 

UT_P_Sanitary Sanitary Line 9 san 1 0 100 C 

UT_P_Sanitary_Cells 

Sanitary Symbols 9 0 1 0 100 

CELLS PLACED ON LEVEL UT_P_Sanitary_Cells: 

Septic Tank - - - 0 100 SEPTCP ODOT_Symbols.cel C 

Sanitary Sewer Manhole Adjusted or 

Reconstructed 

- - - 0 100 SMHA ODOT_Symbols.cel C 

Sanitary Sewer Manhole - - - 0 100 SMHP ODOT_Symbols.cel C 

UT_P_Sanitary_Text Sanitary Text 0 0 1 0 500 

UT_P_Telecom Telecommunication Line 6 tele 1 0 100 C 

UT_P_Telecom_Cells 

Telecommunication Symbols 6 0 1 0 100 

CELLS PLACED ON LEVEL UT_P_Telecom_Cells: 

Telecommunication Pole - - - 0 100 TELPP ODOT_Symbols.cel C 

Telecommunication Manhole - - - 0 100 TMHP ODOT_Symbols.cel C 

Telephone Pedestal - - - 0 100 TPEDP ODOT_Symbols.cel C 

Telecommunication Vault - - - 0 100 TVLTP ODOT_Symbols.cel C 

UT_P_Telecom_Text Telecommunication Text 0 0 1 0 500 

UT_P_Water Water Line 11 water 1 0 100 C 

UT_P_Water_Cells 

Water Symbols 11 0 1 0 100 

CELLS PLACED ON LEVEL UT_P_Water_Cells: 

Fire Hydrant - - - 0 100 FHP ODOT_Symbols.cel C 

Water Gate Valve - - - 0 100 WGVP ODOT_Symbols.cel C 

Water Manhole Adjusted or Reconstructed - - - 0 100 WMHA ODOT_Symbols.cel C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 





UT_P_Water_Cells (cont’d) 

CELLS PLACED ON LEVEL UT_P_Water_Cells (cont’d): 

Color 

Style 

UT – UTILITIES – PROPOSED (cont’d): 

Weight 

Transparency 

Priority 


Water Manhole - - - 0 100 WMHP ODOT_Symbols.cel C 

Water Meter - - - 0 100 WMP ODOT_Symbols.cel C 

Water Surface Elevation Marker - - - 0 100 WSELEV ODOT_Symbols.cel C 

Water Service Stop - - - 0 100 WSSP ODOT_Symbols.cel C 

UT_P_Water_Text Water Text 0 0 1 0 500 

VG_X_Cells 

VG – VEGETATION - EXISTING: 

Vegetation Symbols 2 0 0 0 -100 

CELLS PLACED ON LEVEL VG_X_Cells: 

Evergreen Tree - - - 0 -100 ETREE ODOT_Symbols.cel C 

Evergreen Tree with 1' Radius for Scaling - - - 0 -100 ETREES ODOT_Symbols.cel C 

Shrub - - - 0 -100 SHRUB ODOT_Symbols.cel C 

Stump - - - 0 -100 STUMP ODOT_Symbols.cel C 

Deciduous Tree - - - 0 -100 TREE ODOT_Symbols.cel C 

Tree with 1' Radius for Scaling - - - 0 -100 TREES ODOT_Symbols.cel C 

VG_X_Flower_Bed Flower Bed or Planter 2 1 0 0 -100 

VG_X_Shrub_Line_Lt Shrub Line, clockwise 2 shrublt 0 0 -100 C 

VG_X_Shrub_Line_Rt Shrub Line, counter-clockwise 2 shrubrt 0 0 -100 C 

VG_X_Text Vegetation Text 0 0 0 0 500 

VG_X_Tree_Line_Lt Tree Line, clockwise 2 treelt 0 0 -100 C 

VG_X_Tree_Line_Rt Tree Line, counter-clockwise 2 treert 0 0 -100 C 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 




VG_P_Cells 


Color 

Style 

VG – VEGETATION - PROPOSED: 

Vegetation Symbols 2 0 1 0 100 

CELLS PLACED ON LEVEL VG_P_Cells: 

Weight 

Transparency 

Priority 


Evergreen Tree - - - 0 100 ETREEP ODOT_Symbols.cel C 

Overlay for Items to be Removed 

(e.g. Tree or Stump) 

- - - 0 100 RMVD ODOT_Symbols.cel C 

Shrub - - - 0 100 SHRUBP ODOT_Symbols.cel C 

Deciduous Tree - - - 0 100 TREEP ODOT_Symbols.cel C 

VG_P_Landscape_limits Landscape Limits 2 0 1 0 100 

VG_P_Text Vegetation Text 0 0 1 0 500 

XS – CROSS SECTION - EXISTING: 

XS_X_Ground_Line Cross Section Ground Line 2 2 1 0 -100 

XS_X_Pavt Cross Section Pavement and Shoulders 11 3 0 0 -100 

XS – CROSS SECTION - PROPOSED: 

XS_P_Annotation Cross Section Annotation 0 0 1 0 500 

XS_P_Barrier Cross Section Barrier 44 0 1 0 100 

XS_P_Barrier_Surface 

Cross Section Barrier Surface 

(not typically shown on final plans) 

44 0 1 0 100 

C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

XS_P_Boundary Cross Section Boundary (does not plot) 131 2 1 0 -110 




XS_P_Curb 

XS_P_Curb_Surface 


Cross Section Curb 

(for reference only) 

Cross Section Curb Surface 


Color 

Style 

XS – CROSS SECTION – PROPOSED (cont’d): 

44 0 0 0 100 

44 0 1 0 100 

XS_P_Ditch_Bottom Cross Section Ditch Bottom 1 0 2 0 100 

XS_P_Earthwork_Shapes 

XS_P_Excavation_Limits 

Cross Section GEOPAK Earthworks Shapes 

(does not plot) 

Cross Section GEOPAK Earthwork Excavation 

Limits (used for computation only, does not 

plot) 

XS_P_Finished_Grade Cross Section Finished Grade Line 2 0 2 0 100 

XS_P_Finished_Grade_Seeded 

XS_P_Headwall 

XS_P_Headwall_Surface 

XS_P_Pavt_Layers 

XS_P_Pavt_Surface 

Cross Section Finished Grade Line Seeded 

(used for computation only, does not plot) 

Cross Section Headwall 


Cross Section Headwall Surface 


Cross Section Pavement Layers 


Cross Section Pavement Surface 


Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

1 0 0 50 -110 

6 0 2 0 -100 

2 0 2 0 100 

44 0 1 0 100 

44 0 1 0 100 

37 0 0 50 -110 

37 0 1 0 100 

XS_P_Ret_Wall Cross Section Retaining Wall 44 0 1 0 100 

XS_P_Ret_Wall_Surface 

XS_P_Shoulder_Layers 

XS_P_Shoulder_Surface 

Cross Section Retaining Wall Surface 


Cross Section Shoulder Layers 


Cross Section Shoulder Surface 


44 0 1 0 100 

40 0 0 50 -110 

40 0 1 0 100 

XS_P_Special_Benching Cross Section Special Benching 4 0 2 0 100 

XS_P_Subgrade Cross Section Subgrade 7 0 2 0 100 

XS_P_Text_Info 

XS_P_Text_MarkedPoint 

Cross Section Information Text 


Cross Section Marked Point Location Text 


0 0 1 0 500 

4 0 1 0 500 





XS_P_Text_WarningMsg 

Cross Section Warning Message Text 


Color 

Style 

XS – CROSS SECTION – PROPOSED (cont’d): 

XS_P_Undercut Cross Section Undercut 8 0 2 0 100 

XS_P_Undercut2 Cross Section Undercut 8 0 1 0 100 

Weight 

Transparency 

Priority 


C = Cosmetic 

P = Physical 

Levels Do Not 

Plot 

3 0 1 0 500 


Appendix E – Electronic Submission Checklist January 18, 2013 

The following checklist may be used by the District to determine if electronically submitted files 

meet the requirements of The Location and Design Manual, Volume 3 – Highway Plans, Section 

1500. 

1. The project classification per the PDP (Old and New) is: 

Project Submitted Remarks 

Minimal Existing Plans and Designer Office Calcs Required 

Minor 

< 1.0 acre earth disturbed area – See item 2 below 

(unless waived by DPEA) 

Minor > 1.0 acre earth disturbed area – See item 2 below 

Major See items 2 through 5 below 

Path 1 Existing Plans and Designer Office Calcs Required 

Path 2-5 

See items 2 through 5 below (unless waived by DPEA 

for Path 2 only) 

2. Have the following files been submitted? 

Files Required for All Projects Submitted 

Existing Plans 

Designer Office Calculations 

MicroStation DGN Files 

(See Figure 304-1 for File Name Type Codes shown in parenthesis below) 

Required Basemap Design Files: 

Existing Roadway (BA, BC, or BE) 

Proposed Roadway (BP) 

Right-of-Way (BR) 

Profiles (BF) 

GEOPAK Cross Section Cells (Roadway) (XC) 

Optional Discipline Specific Basemap Design Files: 

(required for electronic submission if referenced to the plan sheets) 

Bridge (BS) 

Drainage (BD) 

Environmental (BV) 

Landscaping (BL) 

Lighting (BH) 

Maintenance of Traffic (BM) 

Signals (BG) 

Geotechnical (BI) 

Traffic Control (BT) 

Utilities (BU) 

Submitted 

ODOT CADD Engineering Standards E-1

Sheet Design Files (verify all reference files are included): 

Site Plan (DE) 

Plan (GP), Profile (GF), or Plan & Profile Sheets (GP) 

Cross Section Sheets (XS) 

Intersection/Interchange Details (GI) 

Appendix E – Electronic Submission Checklist 

GEOPAK Files Submitted 

Coordinate Geometry Database (.gpk) 

Existing Ground Triangle Model (.tin) 

ASCII Files Submitted 

Horizontal Alignments (see 504.2) 

Vertical Alignments (see 504.3) 

Monuments (see 504.6) 

LandXML Files Submitted 

Horizontal Alignments (see 504.4) 

Vertical Alignments (see 504.4) 

Existing Ground Triangle Model (see 504.5) 

3. Major and Paths 2, 3, 4, and 5 Projects: 

Note – Major and Paths 2, 3, 4, and 5 projects follow the same file submittals as Minor Projects in 

addition to the specific files listed below. (Unless waived by DPEA for Path 2 only) 

ASCII Files Submitted 

GEOPAK Cross Section Staking Reports (see 504.7) 

LandXML Files Submitted 

Proposed Triangle Model (see 504.5) (if specified in 

scope) 

GEOPAK Files Submitted 

Proposed Triangle Model (.tin) (if specified in scope) 

4. File check: 

Do the DGN files match the mylars? Yes No 

Do the chains and profiles match the plans? Yes No 

5. Provide a Zip file as per Section 504.8 for all the applicable files referenced 

above. 

E-2 ODOT CADD Engineering Standards

APPENDIX F – Level Scale Factors Revised July 20, 2007 

Bridge Sheet Suggested Standards – Level Scale Factors 

For all lines except as listed in Table 2 below 

Reference Scale Line Type Scale Factor Effective Scale 

*Two 2.000 0.500 1.000 

One 1.000 1.000 1.000 

Three-Quarter 0.750 1.333 1.000 

*Five-Eights 0.625 1.600 1.000 

Half 0.500 2.000 1.000 

Three-Eights 0.375 2.667 1.000 

One-Quarter 0.250 4.000 1.000 

Ten 0.100 10.000 1.000 

Twenty 0.050 20.000 1.000 

Forty 0.025 40.000 1.000 

Fifty 0.020 50.000 1.000 

* Do not have an Annotaion Scale 

Table 1 

For bridge centerlines and construction joints - LONG 

Reference Scale Line Type Scale Factor Effective Scale 

*Two 2.000 1.000 2.000 

One 1.000 2.000 2.000 

Three-Quarter 0.750 2.667 2.000 

*Five-Eights 0.625 3.200 2.000 

Half 0.500 4.000 2.000 

Three-Eights 0.375 5.333 2.000 

One-Quarter 0.250 8.000 2.000 

Ten 0.100 20.000 2.000 

Twenty 0.050 40.000 2.000 

Forty 0.025 80.000 2.000 

Fifty 0.020 100.000 2.000 

* Do not have an Annotaion Scale 

ODOT CADD Engineering Standards 

Table 2 

F-1

This page intentionally left blank.

CADD Engineering Standards - Ohio Department of Transportation

Create successful ePaper yourself

Delete template?

Save as template?