InRoads Design Guidelines

InRoads Design Guidelines
Georgia Department of Transportation
Office of Design Policy & Support
Developed By Product Version Document Revision Release Date
Office of Design Policy & Support InRoads Suite V8i Edition Version _1.03 04-01-11
Revision History
Date
07-01-10 07-15-10
Revision Number
1.00 1.01
By
CJB - HAC HAC - CJB
Section
All 1-4,1-13
Description
All Removed bullet about the GDOT 3D Working File.dgn & replace Figure L1-6 to remove the setup for the quantity manager. Changed QA documents to reflect PDF extensions Revised the Description for BEARING & DISTANCE. This preference is no longer set up to display Distance. Changed Engineering Software Standards & Support to Office of Design Policy & Support throughout document. Corrected several miscellaneous typing errors. Revised Starting a Project in InRoads Section to correct a Project file location error. Added Survey Control Codes to Property Survey Styles Filter table. Added Bridge Hydraulics Preference to Preferences Table. Revised Bearing & Distance Preference. Added four Style Sheet Descriptions: GDOT GPS Grading, HEC RAS Bridge Features, HEC RAS Cross Section Geometry & GDOT StaElevOffset.
09-15-10
1.02
HAC-CJB
1-4 2-21
All
04-01-11
1.03
HAC-CJB
1-6
2-8
2-22
3-7 14-8
ii
Date
04-01-11
Revision Number
1.03
By
HAC-CJB
Section
15-2,15-3, 15-11&15-15
Description
Added GDOT GPS Grading Report Style Sheet Information. Corrected various typo errors.
ALL
iii
Preface
Design Processing consists of the generation of Design Data for Construction Plan and Right of Way Plan Deliverables and coordination/oversight of other Plan Deliverables. Designers utilize the InRoads platform for the generation of the Design database(s) used in the development of highway project plans. MicroStation is the CADD platform utilized for the generation of highway project plans. These Design Guidelines have been developed as part of the statewide GDOT implementation of MicroStation V8i and InRoads V8i. The intent of this document is to provide guidelines and standards for generating Design Data in InRoads V8i. These guidelines must be followed in detail in order to conform to the current GDOT standards for producing the required design data for plan deliverables. Updates to this document will be made periodically when minor revisions, additional information, and/or enhancements are added.
If there is any approved deviation from the standard file and data naming/feature style conventions as prescribed by this document - a detailed description of the deviation(s) and approved reasons for the deviation(s) shall be documented and included with the project files in electronic format.
iv
Contact Information
To submit any comments or questions regarding the information contained in this document, please contact the Office of Design Policy & Support team by email at the following address: [email protected] In the Email Subject Header, please reference the InRoads Design Guidelines.
This Page Left Intentionally Blank
vi
Table of Contents
TABLE OF CONTENTS
1. PROJECT INITIALIZATION STANDARDS .................................................................................................. 1-2 1.1 1.2 1.3 1.3.1 1.3.2 1.4 1.4.1 1.4.2 1.5 1.6 1.7 1.8 1.9 1.9.1 1.9.2 2. GDOT STANDARD FILES MICROSTATION AND INROADS ........................................................................... 1-3 STANDARD PROJECT STRUCTURE ................................................................................................................... 1-5 STARTING A DESIGN PROJECT IN INROADS .................................................................................................... 1-6 Copy and Rename the SDE DGN Files and SDE InRoads Files ............................................................. 1-6 Copy the Standards folder which is downloaded from InRoadsALLV8i.exe ...................................... 1-8 STARTING MICROSTATION V8I AND INROADS V8I ....................................................................................... 1-9 Steps to Create a Design Working DGN File .................................................................................... 1-10 Steps to open an existing Design Working DGN File ........................................................................ 1-13 OVERVIEW OF INROADS INTERFACE ............................................................................................................ 1-14 INROADS PROJECT DEFAULTS ...................................................................................................................... 1-15 DESIGN DEFAULT PREFERENCES .................................................................................................................. 1-17 INROADS LOCKS........................................................................................................................................ 1-19 APPLICATION AND VARIABLE MANAGER ADD-INS ..................................................................................... 1-21 Steps to select the Application Add-Ins: ................................................................................................. 1-21 Steps to select the Variable Manager Add-Ins: ...................................................................................... 1-22
STANDARD CONVENTIONS ............................................................................................................................ 2-2 2.1 2.1.1 2.1.2 2.2 2.2.1 2.2.2 2.3 2.4 2.5 2.5.1 2.5.2 2.5.3 2.6 2.7 PROJECT AND FILE NAMING CONVENTIONS ................................................................................................... 2-3 Standard Project Naming Conventions .................................................................................................... 2-3 Standard File Naming Conventions .......................................................................................................... 2-4 STANDARD GEOMETRY OBJECT NAMES AND FEATURE STYLES ................................................................... 2-5 Standard Design and Survey Object Naming Conventions...................................................................... 2-6 Standard Geometry Survey and Design Feature Style Conventions........................................................ 2-8 STANDARD DESIGN FEATURE STYLES .......................................................................................................... 2-11 STANDARD FILE INFORMATION .................................................................................................................... 2-15 STANDARD PREFERENCE FILE (XIN) AND GDOT PREFERENCES ................................................................ 2-16 Standard Preference File (XIN) Configuration ...................................................................................... 2-16 Standard Preference File (XIN) Details ................................................................................................. 2-17 GDOT Preferences .................................................................................................................................. 2-18 GDOT STANDARD INROADS PHOTOGRAMMETRIC FEATURE CODES.......................................................... 2-30 GDOT STANDARD INROADS FIELD SURVEY FEATURE CODES ................................................................... 2-31
3.
HORIZONTAL ALIGNMENTS ......................................................................................................................... 3-2 3.1 3.2 3.3 3.4 3.5 3.6 HORIZONTAL ALIGNMENT OVERVIEW ........................................................................................................... 3-3 HORIZONTAL ALIGNMENT AND COGO POINT NAMES/FEATURE STYLES .................................................... 3-4 COGO POINTS AND ALIGNMENT POINTS ....................................................................................................... 3-6 VIEW HORIZONTAL ANNOTATION PREFERENCES .......................................................................................... 3-7 VIEW HORIZONTAL ANNOTATION FILTERS .................................................................................................... 3-9 REVIEWING HORIZONTAL ALIGNMENTS ...................................................................................................... 3-10
4.
VERTICAL ALIGNMENTS ................................................................................................................................ 4-2 4.1 4.2 4.3 4.4 4.5 VERTICAL ALIGNMENT OVERVIEW ................................................................................................................ 4-3 VERTICAL ALIGNMENT NAMES AND FEATURE STYLES ................................................................................. 4-4 VERTICAL ALIGNMENT PREFERENCES ........................................................................................................... 4-5 VERTICAL ALIGNMENT ANNOTATION PREFERENCES .................................................................................... 4-6 REVIEWING VERTICAL ALIGNMENTS ............................................................................................................. 4-7
5.
IMPORT GRAPHICS AND PLACE CURVE TABLES ................................................................................. 5-2 5.1 5.2 5.3 5.4 IMPORT GRAPHICS OVERVIEW........................................................................................................................ 5-3 IMPORT GRAPHICS - NAMES/FEATURE STYLES .............................................................................................. 5-4 CURVE TABLE OVERVIEW .............................................................................................................................. 5-5 CURVE TABLE PREFERENCES ......................................................................................................................... 5-6
vii
Table of Contents
6.
PROFILE SHEETS ............................................................................................................................................... 6-2 6.1 6.2 6.3 6.4 PROFILE SHEETS OVERVIEW ........................................................................................................................... 6-3 PLAN AND PROFILE GENERATOR INFORMATION ............................................................................................ 6-4 VERTICAL ALIGNMENT PREFERENCES ........................................................................................................... 6-5 VERTICAL ALIGNMENT ANNOTATION PREFERENCES .................................................................................... 6-6
7.
COMPONENT AND TEMPLATE CREATION .............................................................................................. 7-2 7.1 7.2 7.3 7.4 7.5 7.6 COMPONENT AND TEMPLATE CREATION OVERVIEW..................................................................................... 7-3 ITL TEMPLATE LIBRARY AND NAMING CONVENTIONS ................................................................................. 7-4 GDOT STANDARD COMPONENTS................................................................................................................... 7-5 GDOT STANDARD POINT NAMES .................................................................................................................. 7-6 GDOT STANDARD FEATURE STYLES ........................................................................................................... 7-10 GDOT COMPONENT HELP FILES .................................................................................................................. 7-12
8.
ROADWAY DESIGNER ...................................................................................................................................... 8-2 8.1 8.2 8.3 8.4 8.5 8.6 8.7 ROADWAY DESIGNER OVERVIEW .................................................................................................................. 8-3 ROADWAY DESIGNER WORKFLOW ................................................................................................................ 8-4 IRD (ROADWAY DESIGN) NAMING CONVENTIONS........................................................................................ 8-5 CORRIDOR NAMING CONVENTIONS................................................................................................................ 8-6 SUPERELEVATION PROCESS WORKFLOW ....................................................................................................... 8-7 DESIGN SURFACE NAMING CONVENTIONS/PREFERENCE .............................................................................. 8-8 BOGUS SURFACE NAMING CONVENTIONS FOR TARGET ALIASING ............................................................... 8-9
9.
CROSS SECTION SHEETS/ANNOTATION GENERATION ...................................................................... 9-2 9.1 9.2 9.3 9.4 9.5 CROSS SECTION SHEETS/ANNOTATION OVERVIEW ....................................................................................... 9-3 FINISHED DESIGN SURFACE (.DTM) PREFERENCE ........................................................................................ 9-4 CROSS SECTION SHEET SCALE FACTOR ......................................................................................................... 9-5 CROSS SECTION SHEET PREFERENCES............................................................................................................ 9-6 CROSS SECTION SHEET ANNOTATION PREFERENCES..................................................................................... 9-7
10.
CONSTRUCTION LIMITS ............................................................................................................................... 10-2 CONSTRUCTION LIMITS, DITCHES AND DITCH FLOW ARROWS OVERVIEW ................................................ 10-3 CONSTRUCTION LIMITS FEATURE STYLES ................................................................................................... 10-4 ROADWAY DITCHES FEATURE STYLE .......................................................................................................... 10-5 DITCH FLOW ARROW PREFERENCE .............................................................................................................. 10-6 DITCH FLOW ARROW ANNOTATE FEATURE STYLE ..................................................................................... 10-7 CONSTRUCTION LIMITS DGN AND DITCHES/DITCH FLOW ARROWS DGN ................................................ 10-8
10.1 10.2 10.3 10.4 10.5 10.6 11.
EARTHWORK .................................................................................................................................................... 11-2 EARTHWORK OVERVIEW .............................................................................................................................. 11-3 MICROSTATION VIEW ATTRIBUTES SETTING ............................................................................................ 11-4 CROSS SECTION PREFERENCES ..................................................................................................................... 11-5 GDOT EARTHWORK VOLUMES PREFERENCE .............................................................................................. 11-6 GDOT EARTHWORK VOLUME REPORT........................................................................................................ 11-7
11.1 11.2 11.3 11.4 11.5 12.
REQUIRED RIGHT OF WAY .......................................................................................................................... 12-2 RIGHT OF WAY OVERVIEW ........................................................................................................................... 12-3 R/W ALIGNMENT AND COGO POINT NAMES/FEATURE STYLES ................................................................ 12-4 R/W COGO POINTS AND ALIGNMENT POINTS ............................................................................................ 12-6 R/W VIEW HORIZONTAL ANNOTATION PREFERENCE.................................................................................. 12-7 R/W VIEW HORIZONTAL ANNOTATION FILTERS ......................................................................................... 12-8 REVIEWING HORIZONTAL R/W ALIGNMENTS .............................................................................................. 12-9 R/W DGN FILE GENERATION..................................................................................................................... 12-10 R/W AND EASEMENT TABLES (STYLE SHEETS) ......................................................................................... 12-11 R/W DEED (STYLE SHEETS) ....................................................................................................................... 12-12
12.1 12.2 12.3 12.4 12.5 12.6 12.7 12.8 12.9
viii
Table of Contents
13.
SURVEY ENHANCEMENTS ........................................................................................................................... 13-2 SURVEY ENHANCEMENTS OVERVIEW .......................................................................................................... 13-3 SURVEY ENHANCEMENTS TO THE DTM ....................................................................................................... 13-6 SURVEY ENHANCEMENTS TO THE ALG ....................................................................................................... 13-7 SURVEY ENHANCEMENTS TO THE DGN ....................................................................................................... 13-8
13.1 13.2 13.3 13.4 14.
INROADS STYLE SHEETS .............................................................................................................................. 14-2 INROADS STYLE SHEETS OVERVIEW............................................................................................................ 14-3 LOCATION OF GDOT STYLE SHEETS............................................................................................................ 14-4 LOCATION OF GDOT STYLE SHEET HELP FILES .......................................................................................... 14-5 DESCRIPTIONS OF GDOT STYLE SHEETS ..................................................................................................... 14-6
14.1 14.2 14.3 14.4 15.
ADDITIONAL FILE DELIVERABLES .......................................................................................................... 15-2
15.1 ADDITIONAL FILE DELIVERABLES OVERVIEW ............................................................................................. 15-3 15.2 INROADS FILE DELIVERABLES TO GDOT .................................................................................................... 15-4 15.2.1 Write Stakeout Data to a Data Collector ................................................................................................ 15-5 15.2.2 Generate GDOT Deed File(s) ................................................................................................................. 15-6 15.2.3 InRoads Project Data Sheet(s) ................................................................................................................ 15-7 15.2.4 GDOT InRoads Design Data Quality Assurance Checklist ................................................................... 15-9 15.3 INROADS FILE DELIVERABLES TO CONTRACTORS ..................................................................................... 15-11 15.3.1 Alignment File Descriptions ................................................................................................................. 15-12 15.3.2 Alignment Report Files ......................................................................................................................... 15-13 15.3.3 End-Area Report Files ........................................................................................................................... 15-14 15.3.4 GPS Grading Report Files ..................................................................................................................... 15-15 16. CONVERTING PROJECTS FROM CAICE TO INROADS ....................................................................... 16-2 CAICE TO INROADS CONVERSION CRITERIA OVERVIEW............................................................................ 16-3 CAICE PHOTOGRAMMETRY/SURVEY DATA CONVERSION.......................................................................... 16-4 CAICE DESIGN DATA CONVERSION ............................................................................................................ 16-5
16.1 16.2 16.3
ix
Table of Figures
TABLE OF FIGURES
Figure 1-1 Starting MicroStation V8i and InRoads V8i ..............................................................1-10 Figure 1-2 MicroStation New File Window.................................................................................1-11 Figure 1-3 Main MicroStation V8i Window ................................................................................1-12 Figure 1-4 Main InRoads V8i Window ........................................................................................1-12 Figure 1-5 Starting MicroStation V8i and InRoads V8i ..............................................................1-13 Figure 1-6 Project Defaults ...........................................................................................................1-16 Figure 1-7 Design Default Settings ..............................................................................................1-18 Figure 3-1 Review Horizontal Alignment ....................................................................................3-10 Figure 4-1 Review Vertical Alignment ..........................................................................................4-7 Figure 12-1 Review Horizontal Alignment ..................................................................................12-9
xi
Table of Tables
TABLE OF TABLES
Table 1.1 .............................................................................................................................................1-5 Table 1.2 .............................................................................................................................................1-7 Table 1.3 .............................................................................................................................................1-7 Table 1.4 .............................................................................................................................................1-8 Table 1.5 .............................................................................................................................................1-9 Table 1.6 ...........................................................................................................................................1-15 Table 1.7 ...........................................................................................................................................1-19 Table 1.8 ...........................................................................................................................................1-20 Table 2.1 .............................................................................................................................................2-3 Table 2.2 .............................................................................................................................................2-4 Table 2.3 .............................................................................................................................................2-6 Table 2.4 .............................................................................................................................................2-6 Table 2.5 .............................................................................................................................................2-7 Table 2.6 .............................................................................................................................................2-7 Table 2.7 .............................................................................................................................................2-9 Table 2.8 ...........................................................................................................................................2-10 Table 2.9 ...........................................................................................................................................2-12 Table 2.10 .........................................................................................................................................2-13 Table 2.11 .........................................................................................................................................2-15 Table 2.12 .........................................................................................................................................2-16 Table 3.1 .............................................................................................................................................3-4 Table 3.2 .............................................................................................................................................3-4 Table 3.3 .............................................................................................................................................3-5 Table 3.4 .............................................................................................................................................3-7 Table 3.5 .............................................................................................................................................3-8 Table 3.6 .............................................................................................................................................3-8 Table 3.7 .............................................................................................................................................3-9 Table 4.1 .............................................................................................................................................4-4 Table 4.2 .............................................................................................................................................4-4 Table 4.3 .............................................................................................................................................4-5 Table 4.4 .............................................................................................................................................4-6 Table 4.5 .............................................................................................................................................4-6 Table 5.1 .............................................................................................................................................5-4 Table 5.2 .............................................................................................................................................5-4 Table 5.3 .............................................................................................................................................5-6 Table 6.1 .............................................................................................................................................6-4 Table 6.2 .............................................................................................................................................6-5 Table 6.3 .............................................................................................................................................6-6 Table 6.4 .............................................................................................................................................6-6 Table 7.1 .............................................................................................................................................7-4 Table 7.2 .............................................................................................................................................7-5 Table 7.3 .............................................................................................................................................7-6 Table 7.4 ...........................................................................................................................................7-10 Table 8.1 .............................................................................................................................................8-5
Table of Tables
Table 8.2 .............................................................................................................................................8-6 Table 8.3 .............................................................................................................................................8-8 Table 8.4 .............................................................................................................................................8-8 Table 8.5 .............................................................................................................................................8-9 Table 9.1 .............................................................................................................................................9-4 Table 9.2 .............................................................................................................................................9-5 Table 9.3 .............................................................................................................................................9-6 Table 9.4 .............................................................................................................................................9-7 Table 10.1 .........................................................................................................................................10-4 Table 10.2 .........................................................................................................................................10-5 Table 10.3 .........................................................................................................................................10-6 Table 10.4 .........................................................................................................................................10-7 Table 10.5 .........................................................................................................................................10-8 Table 11.1 .........................................................................................................................................11-4 Table 11.2 .........................................................................................................................................11-5 Table 11.3 .........................................................................................................................................11-6 Table 11.4 .........................................................................................................................................11-7 Table 12.1 .........................................................................................................................................12-4 Table 12.2 .........................................................................................................................................12-4 Table 12.3 .........................................................................................................................................12-5 Table 12.4 .........................................................................................................................................12-7 Table 12.5 .........................................................................................................................................12-8 Table 12.6 ...................................................................................................................................... 12-10 Table 12.7 ...................................................................................................................................... 12-11 Table 12.8 ...................................................................................................................................... 12-12 Table 13.1 .........................................................................................................................................13-8 Table 14.1 .........................................................................................................................................14-6 Table 15.1 .........................................................................................................................................15-5 Table 15.2 .........................................................................................................................................15-6 Table 15.3 ...................................................................................................................................... 15-12 Table 15.4 ...................................................................................................................................... 15-13 Table 15.5 ...................................................................................................................................... 15-14 Table 15.6 ...................................................................................................................................... 15-15
Overview
These Guidelines cover the GDOT standards for generating Design Data by utilizing the MicroStation V8i and InRoads V8i software(s). The procedures depict the Project Initialization Standards and Conventions to create an InRoads Design Project to GDOT format and the processes to create/generate the files which are to be submitted as deliverables to the Construction and Right of Way Offices. For detailed Design Processing instructions please refer to the Training Manual: Introduction to InRoads for Design Document Content Below is a list of topics covered in this document: Project Initialization Standards Standard Conventions Horizontal Alignments Vertical Alignments Import Graphics and Place Curve Tables Profile Sheets Component and Template Creation Roadway Designer Cross Section Sheets/Annotation Generation Construction Limits Earthwork Required Right of Way Survey Enhancements InRoads Style Sheets Additional File Deliverables Converting Projects from CAiCE to InRoads
xi
1.
Project Initialization Standards
1. Project Initialization Standards

Project Initialization Standards have been established in order to promote consistency and assist in the organization of project data. These standard project schemes help to ensure uniformity for all users who may work on the project. This section covers the following topics:
GDOT Standard Files (MicroStation and InRoads) Standard Project Structure Starting MicroStation V8i and InRoads V8i Overview of InRoads Interface InRoads Project Defaults Design Default Preferences InRoads Locks Application and Variable Manager Add-Ins Initiating a Design Project in InRoads
1-2
1.1 GDOT Standard Files MicroStation and InRoads

In order to conform to current policy for plan deliverables GDOT provides the requisite files needed to standardize InRoads and MicroStation to GDOT requirements. The first step in the development of an InRoads and MicroStation Project is to ensure that these standard files are being utilized. Instructions for downloading/installing the executables are included on the GDOT R.O.A.D.S. web page (see the links depicted below). These files are required for any Survey/Design Data Projects generated for GDOT. MicroStation Standard Files Location For Internal GDOT Users a server location has been established to map a drive (an N:\ Drive) in order to access the latest MicroStation Files. Once the internal user maps the N:\ drive all of the standard MicroStation Files will be available through this mapped drive. MicroStation Standard Files Location For External Users - a MicroStation V8i (CaddALLV8i.exe) executable file is available and located in a download executable which can be accessed from the GDOT R.O.A.D.S. web page. This executable contains all of the GDOT MicroStation V8i standard files. This file can be downloaded by navigating to the MicroStation and InRoads links from the following location:
http://www.dot.ga.gov/doingbusiness/PoliciesManuals/roads/software/Pages/default.aspx
InRoads Standard Files Location For Internal and External Users - an InRoadsALL executable file (InRoadsALLV8i.exe) is available and located in a download executable which can be accessed from the GDOT R.O.A.D.S. web page. This executable contains all of the GDOT InRoads V8i standard files. This file can be downloaded by navigating to the MicroStation and InRoads links from the following location:
1-3
The InRoadsALLV8i.exe file contains all of the standard GDOT files which are required to generate projects to GDOT standards. The user will perform the following steps to extract and set-up the GDOT Standard InRoads Files: 1. Close MicroStation V8i and InRoads V8i if they are still open. 2. Navigate to the InRoads links from the following web page:
3. Save the InRoadsALLV8i.exe file to the hard drive and then double click the file. 4. The self-extractor will download the GDOT InRoads Standard Files to the following locations: a. C:\InRoads Data\Standards\ GDOT_Standard V8i.xin GDOT_Standard V8i.itl Project_Data_Sheet_MultipleAlign.docm Photogrammetry_InRoads QA.pdf Survey Data Processing_InRoads QA.pdf Design Data_InRoads QA.pdf b. C:\InRoads Data\Component Documentation GDOT Component Description Help Documentation c. C:\InRoads Data\Style Sheet Documentation GDOT Style Sheet Help Documentation d. C:\Program Files\Bentley\InRoads Group V8.11\XML Data\GDOT\ GDOT Style Sheets 5. For detailed instructions on downloading and installing InRoadsALLV8i.exe navigate to the InRoads links from the GDOT R.O.A.D.S. web page and click on the Downloading and Running InRoadsALLV8i.pdf document for installing these standard files.
1-4
1.2 Standard Project Structure

The standard File Structure for InRoads is a Project Folder (which is named for the PI # of the Project Example: 123456) located as a sub-folder under C:\InRoads Data Example: C:\InRoads Data\123456. The Project Files are then located directly under the PI # Example: C:\InRoads Data\123456 -- This Project Folder contains the individual InRoads Data Files. (See Table 1.1)
Table 1.1 InRoads Project Structure InRoads Project Structure InRoads Project Structure (Example) C:\InRoads Data\PI Number C:\InRoads Data\123456
Some examples of InRoads Data File Types are: 1. .DTM ------- (Digital Terrain Model File) contains Surface data 2. .FWD ------- (Survey File) contains Field Survey data 3. .ALG-------- (Geometry File) contains Geometric Point, Horizontal and Vertical data 4. .IRD -------- (Roadway Design File) contains the Design Surface data 5. .RWK------- (Project File) contains project data for InRoads files in ASCII format 6. .ITL--------- (InRoads Template File) contains InRoads Templates for cross-sections 7. .SDB-------- (Drainage File) contains the InRoads Storm and Sanitary data
It is highly recommended to backup the Project Folder (which contains these individual data files) after each work session to your Group Account on the GDOT Server if you are a GDOT Employee (or to an appropriate Business Server if you are a GDOT Consultant).
1-5
1.3 Starting a Design Project in InRoads

After creating the Design Project folder of C:\InRoads Data\PI Number, the Designer will copy the data received from the SDE to the C:\InRoads Data\PI Number folder. The Designer will then copy the Standards folder (which is downloaded through the InRoadsALLV8i.exe executable) to the C:\InRoads Data\PI Number folder. 1.3.1 Copy and Rename the SDE DGN Files and SDE InRoads Files
The Designer will receive from the SDE (Survey Data Engineer) some or all of the following eight electronic files. These files will be made available for copying from SDECommon for Internal GDOT Users. These files will be located on SDECommon under the applicable Project PI Number in a sub-folder named SDE. PI#_SDE.alg (InRoads Geometry file) PI#_SDE.dtm (InRoads Digital Terrain Model) PI#_TOPO.dgn (Existing Topo features) PI#_PROP.dgn (Existing Property Information) PI#_UTLE.dgn (Existing Utility features) PI#_PSR.xls or .psr or .mdb (Property Statistics Report) PI#_Hydraulics.docx (Hydraulics report) PI#_Misc.txt (Miscellaneous information SDE deems important. This file may not be included.) 1. The Designer will copy this SDE folder to the PI# folder on the group account for backup. The Designer is not to work directly from these files but from copies of them. 2. The Designer will also copy this SDE folder to the InRoads Data\ PI Number folder. The Designer will then copy the individual files located in the SDE folder directly to the following path: C:\InRoads Data\PI Number and rename the files according to the examples depicted below.
1-6
**DGN Files The DGN Files received from the SDE contain an underbar (_) in the file name. The reason for this is to assist in differentiating DGN data received from the SDE from that of the Design DGN files. This will assist in organization of data during the enhancement processes. The Designer must rename the DGN files from the SDE naming convention to the Design naming convention in order for the MicroStation customized Macros to function correctly and to conform to the current EDG (Electronic Data Guidelines). If the Designer does not rename the DGN files (and remove the underbars) the GDOT MicroStation Macros may not function. Table 1.2 Re-name SDE DGN Files SDE DGN FILE NAME Rename To
PI#_TOPO.dgn PI#_PROP.dgn PI#_UTLE.dgn
DESIGN DGN FILE NAME

PI#TOPO.dgn PI#PROP.dgn PI#UTLE.dgn
**InRoads Files The InRoads Files received from the SDE must be renamed internally AND externally to the Design Naming Convention.
Table 1.3 Re-name SDE InRoads Files SDE INROADS FILE NAME
PI#_SDE.alg PI#_SDE.dtm
Rename To

DESIGN INROADS FILE NAME

PI#_Design.alg PI#_Exist.dtm
**For detailed instructions regarding the above re-naming process -- please refer to Lab 2 in the Design Training Manual: Introduction to InRoads for Design Training Guide.
1-7
1.3.2 Copy the Standards folder which is downloaded from InRoadsALLV8i.exe Important Step: After installing InRoadsALLV8i.exe the user will copy the Standards folder under C:\InRoads Data\ to the Project Location. The rest of the Standard Files will remain in the default install location. Whenever a new Project is created the Designer will download and install InRoadsALLV8i.exe. The files will be extracted to the Default Location(s). The Designer will then perform the following step:
The user will copy the C:\InRoads Data\Standards Folder to the InRoads Data\PI# \ folder. (Example: C:\InRoads Data\123456\Standards). The reason for copying the Standards folder to the Project Folder is that the XIN and ITL are project specific and need to be modified during the life of the project. The XIN and the ITL will be submitted with the Design Project data so that other users will have access to the Templates/Components in the ITL and any project specific preferences or filters that may be added to the XIN.
Table 1.4 Copy Standards Folder to Project Folder

C:\InRoads Data\Standards Copy To C:\InRoads Data\PI #
1-8
1.4 Starting MicroStation V8i and InRoads V8i

The user will be working in both MicroStation V8i (the CADD Software) and InRoads Suite V8i (the Survey/Design Software). The MicroStation CADD Software is used for the viewing and manipulation of graphics derived from InRoads. The InRoads Software is the database in which the Surveying/Design data is created and processed. The user will select the standard GDOT 3D seed file to use as the seed DGN in order to create the three dimensional Working DGN file. This Working DGN file is used to display the temporary and/or permanent graphics in InRoads. This section details the following processes: Steps to Create a Design Working DGN File Steps to Open an Existing Design Working DGN File
The Working DGN file will be saved to the following folder location: C:\InRoads Data\PI Number\Standards
Table 1.5 Standard Naming Convention of the Working DGN File Working DGN File Name C:\InRoads Data\PI Number\Standards GDOT 3D Working File.dgn
The MicroStation software will open first before InRoads. After the MicroStation Splash Screen appears, the MicroStation Manager dialog (See Figure 1-1) will open so that a Working DGN file can be created or an existing Working DGN file can be opened. The InRoads software can then be initiated.
1-9
1.4.1 Steps to Create a Design Working DGN File The DesignWorking DGN file will be created from the GDOT_V8_3D.dgn seed file. Following are the steps to create a Design Working DGN File: 1. From the desktop, double-click on the GDOT MicroStation V8i Edition icon.
Double click on the icon labeled GDOT MicroStation V8i Edition.
2. After the MicroStation Splash Screen appears, the MicroStation Manager dialog box will open. (See Figure 1-1).
New File Icon
Figure 1-1 Starting MicroStation V8i and InRoads V8i
3. In the MicroStation Manager dialog box, click on the New File icon (See Figure 1-1) depicted above. The New File command will be used to create the Working DGN file. 4. After the New File command is selected, the MicroStation New File dialog box will open. (See Figure 1-2).
1-10
Click in the Save in: Pulldown - and browse to the C:\InRoads Data\PI Number\ Standards location to save the new Working DGN file In the File name: Pulldown enter GDOT 3D Working File.dgn In the Save as type: Pulldown select MicroStation DGN Files (*.dgn) In the Seed: Field - ensure the seed file name is GDOT_V8_3D.dgn The Seed File should already be entered in the field based on the current MicroStation configuration. The inputs should now be similar to the screen capture depicted in Figure 1-2 (as shown below).
Figure 1-2 MicroStation New File Window
5. Click the Save command button and the MicroStation Manager dialog box will appear. 6. In the MicroStation Manager Dialog box highlight the file just created (GDOT 3D Working File.dgn) and click the Open button. 7. The MicroStation V8i interface will then finish opening. 8. In the Main MicroStation Pull-down Menu click on the InRoads pull-down:
1-11
9. Then select InRoads Suite and the InRoads V8i interface will open. Once InRoads and MicroStation are up and running, the desktop should look similar to that of Figure 1-3 and Figure 1-4.
Figure 1-3 Main MicroStation V8i Window
Figure 1-4 Main InRoads V8i Window
1-12
1.4.2 Steps to open an existing Design Working DGN File If the Design Working DGN file has been created previously use the following steps to open a Design Working DGN File:
1. From the desktop, double-click on the GDOT MicroStation V8i Edition icon.
Double click on the icon labeled GDOT MicroStation V8i Edition.
2. After the MicroStation Splash Screen appears, the MicroStation Manager dialog box will open. (See Figure 1-5).
Figure 1-5 Starting MicroStation V8i and InRoads V8i
3. In the MicroStation Manager dialog box, browse to the C:\InRoads Data\PI Number\Standards location and highlight the (GDOT 3D Working File.dgn) and click the Open button. 4. The MicroStation V8i interface will then finish opening. Then select InRoads>>InRoads Suite from the Main MicroStation Pull-down Menu. Once InRoads and MicroStation are up and running, the desktop should look similar to that of the previous screen captures depicted in Figure 1-3 and Figure 1-4. 1-13
1.5 Overview of InRoads Interface

As mentioned previously - the user will be working in both the InRoads Design Software and the MicroStation CADD Software. The InRoads Software is the database in which the Design data is created and processed.
Shown below is a diagram which depicts the InRoads Explorer objects and a brief overview of the InRoads Explorer Interface:
Workspace Bar
Menu Bar
Toolbars
Feedback Pane
Status Bar
Scroll Bar
Workspace Bar Contains all of the InRoads Project Data information Menu Bar Contains the pull-down menus to access InRoads commands Toolbars Contains default and customized toolbars to access InRoads commands Feedback Pane Contains details of selected Project Data from the Workspace Bar Scroll Bar Enables the user to view more of the InRoads Explorer Interface. (The Scroll Bar may not be visible if the InRoads Interface is already viewed to extents). Status Bar Contains InRoads messages and prompts (Please note: InRoads may direct you to locate something graphically in MicroStation -- some of these prompts may display in the MicroStation Status Bar instead). It is very important that the user review both the InRoads and the MicroStation Status Bar for prompts and information.
1-14
1.6 InRoads Project Defaults

The InRoads Project Defaults setting allows you to define the default folder locations for projects. A Project Default configuration can then be saved for each project so that multiple projects can be accessed. This configuration allows you to easily navigate between projects. Once the Project Folder locations are saved in the Configuration, the projects can then be accessed by selecting the appropriate Project Configuration Name. The Project Defaults also contain the location for selecting the standard GDOT InRoads Preference File (GDOT_StandardV8i.xin). The standard Project Default configuration for Design projects will be PI#_Design. Each Design Project Default will consist of this naming structure in order to easily navigate between projects. (See Table 1.3) **Once the Project Default Location is set for a particular project this will also be the default folder location whenever the InRoads commands of FileSave and FileClose are used. Table 1.6 Project Defaults Configuration Project Default Structure Project Default Structure (Example) PI Number_Design 123456_Design
Following are the steps to create a Design Project Default Configuration (Substitute the appropriate PI # as required): 1. Click FileProject Defaults from the InRoads pull-down menu to access the Set Project Defaults dialog box. 2. Click New and enter 123456_Design in the New Configuration dialog box. Then click OK. 3. Under the Default Preferences section - Click in the Preferences (*.xin): field and then click the Browse button to navigate to the following file: C:\\InRoads Data\123456\Standards\GDOT_Standard V8i.xin file and click Open. 4. Under the Default Directory Paths Section - Click in the Project Default Directory: field and then click the Browse button to navigate to the folder: C:\InRoads Data\123456\. Next - click Open. 5. Under the Default Directory Paths Section copy and paste the following text into each entry field shown below: C:\InRoads Data\123456\
1-15
Report Directory: - C:\InRoads Data\123456\ Projects (*.rwk): - C:\InRoads Data\123456\ Surfaces(*.dtm): - C:\InRoads Data\123456\ Geometry Projects: (*.alg): - C:\InRoads Data\123456\ Template Libraries:(*.itl): - C:\InRoads Data\123456\ Roadway Design: (*.ird): - C:\InRoads Data\123456\ Survey Data: (*.fwd): - C:\InRoads Data\123456\ Drainage: (*.sdb): - C:\InRoads Data\123456\ 6. Under the Default Directory Paths Section - Click in the Style Sheet (*.xsl): field and then click the Browse button to navigate to the folder: C:\Program Files\Bentley\InRoads Group V8.11\XML Data\GDOT\. Next - click Open. The Project Defaults should look similar to the screen capture depicted in Figure 1-6 (as shown below).
Figure 1-6 Project Defaults
7. Click Apply and then click Close. 1-16
1.7 Design Default Preferences

The Design Default Preferences must be loaded in InRoads in order to conform to standards for the processing of Design Projects. This is a very important step to ensure that standards are followed for all Design data that will be processed. The Design Default Preference loads the Precision Settings, Tolerances, Units and Formats, Default Point and Alignment Numbering scheme(s), etc. Once the Design Default Preference is loaded the project will retain these settings each time the project is accessed. Following are the steps to set the Design Default Preferences: 1. Click ToolsOptions from the InRoads pull-down menu to access the Options dialog box. 2. In the Options dialog box - click on the General Tab and the General Tab dialog box will appear.
General Tab
3. In the General Tab dialog box select the pull-down next to Preferred Preference Name:
Select Design Default to load the Design Default Preference Settings. 4. In the General Tab dialog box click the command button named Preferences (Located at the bottom of the dialog box) and the Preferences dialog box will open.
1-17
5. In the Preferences dialog box select Design Default. Then click Load and then click Close. 6. The Design Default Preference should now correspond to the screen capture depicted in Figure 1-7 (as shown below).
Ensure that the Refresh Command Settings on Preference Change is checked:
Figure 1-7 Design Default Settings
7. Click Apply and then click Close. The Design Default Preference is now loaded. This Preference loads the appropriate data for ALL of the tabs in the Options dialog box. The individual tabs (Tolerances, Geometry, Units and Format, etc.) will automatically be configured for use in Design calculations. The Point and Alignment Numbering scheme(s) are also automatically configured for the standard Design conventions in the Design Default Preference. These individual tab options will NOT need to change. Once the Design Default Preference is loaded the project will retain these settings each time the project is accessed on this computer. These settings are specific to this computer Profile/XIN file. If the Project is accessed on another computer these settings may need to be re-applied in order to load the correct Design Default Preference.
1-18
1.8 InRoads Locks

InRoads contains several Locks which are used by many InRoads commands to control different aspects of the selection and viewing of data as well as the reporting of data. There are basically two types of Locks On/Off Locks and Switch Locks. (Switch Locks contain different modes but one mode is always active and the user can switch between modes). Both types of Locks can be changed by the user as the situation dictates during the course of the database generation. These locks affect many commands so it is very important that the user understand the use of these locks. If an InRoads command does not function as expected when utilizing the Surface Viewing or Reporting commands -- a Lock may have been inadvertently turned on/off. The following section contains a brief overview of some of the InRoads Locks. Only the Locks pertaining to the Design aspect will be reviewed. As mentioned previously the Locks may be changed as situations dictate but the settings depicted in the following section are applicable for most Design Projects. It is a very important step to ensure that the Locks are set accordingly. (See Table 1.4) Following are the steps to access the InRoads Locks: Click ToolsLocks from the InRoads pull-down menu. Each time a Lock is changed the pull-down menu will close and the user must click on ToolsLocks again to access the Locks pull-down.
Table 1.7 InRoads Locks Settings

Feature Filter Feature Highlight Style Pencil/Pen Delete Ink Locate Point Snap Element Snap Station Report Cogo Audit Trail Toolbar
Unchecked Unchecked Unchecked Set to Pencil Unchecked Set to Features Checked Unchecked Unchecked Checked Unchecked Checked 1-19
Project Initialization Standards Following is a brief overview of the InRoads Locks: (See Table 1.5)
Table 1.8 InRoads Locks Overview Feature Filter displays or obscures Surface Features based on a filter (also controls Survey Style Filter) Feature Highlight highlights the feature in plan view when selected from a list Style determines if a dialog box is displayed for a surface command or cross sections Pencil/Pen controls the redisplaying of Graphics Delete Ink allows redisplayed graphics to replace graphics in pen mode Locate controls if Locate Buttons snap to Graphics or Features Point Snap controls the ability to snap to points in a Geometry Project Element Snap controls the ability to snap to elements in a Geometry Project Station controls the Stationing as it pertains to Cross Sections Report controls if Report is displayed or not displayed in a dialog box Cogo Audit Trail controls the reporting of coordinate geometry results to a text file Toolbar displays or turns off the Locks Toolbar
1-20
1.9 Application and Variable Manager Add-Ins

InRoads contains several Application and Variable Manager Add-Ins which must be selected and added to the InRoads Program in order to access the standard GDOT customized menu applications/translators for Design. Once the Application and Variable Manager Add-Ins are selected the settings are written to registry keys in the users profile. This ensures that each time InRoads is accessed in the user profile -- these settings will already be available. These add-ins will only need to be added once and will then be accessible in all of the InRoads Modules and InRoads Projects. The Application and Variable Manager Add-Ins must be set accordingly in order to access the required GDOT Survey/Design commands and translators. This section details the following processes: Steps to select the Application Add-Ins Steps to select the Variable Manager Add-Ins 1.9.1 Steps to select the Application Add-Ins: 1. Click ToolsApplication Add-Ins from the InRoads pull-down menu and the following dialog box will appear:
2. Select the following Application Add-Ins by clicking an In:
by the appropriate Add-
3. Click OK to accept the settings and to close out of the dialog box. 1-21
Project Initialization Standards 1.9.2 Steps to select the Variable Manager Add-Ins:
1. Click ToolsVariable Manager from the InRoads pull-down menu and the following dialog box will appear:
2. Select the following Variable Manager Add-Ins by clicking an Variable:
by the appropriate
3. Click Apply to accept the settings and then click Close to close out of the dialog box.
1-22
2.
Standard Conventions
2. Standard Conventions
This section provides an overview of the GDOT standard Project, File and Geometry Object naming conventions utilized for Design. A Design Feature Styles Table is provided which lists the applicable Feature Styles available for use in Design, the GDOT Preference File (.XIN) is reviewed and the Standard Preferences are discussed. The Photogrammetry/Survey Feature Code Tables are also provided as Reference Information so that the Designer can refer to these Feature Codes/Styles when working with Existing Survey/Mapping Data. This section covers the following topics:
Standard Project Names and File Names Standard Geometry Object Names and Feature Styles Standard Design Feature Styles Standard File Information Standard Preference File (XIN) and GDOT Preferences GDOT Standard InRoads Photogrammetry Feature Codes GDOT Standard InRoads Field Survey Feature Codes
2-2
2.1 Project and File Naming Conventions

As mentioned previously in Section One - in order to ensure Project and File Naming consistency and uniformity standard Project and File Naming conventions have been established. The Designer must follow these naming procedures in order to conform to GDOT standards and policies. This section details the following Standard Naming Conventions: Standard Project Naming Conventions Standard File Naming Conventions
2.1.1 Standard Project Naming Conventions The standard File Structure for InRoads is a Project Folder named for the PI Number of the project. The InRoads Design Files will be located directly under this PI Number. This is the folder location where the core Design File data is located. When submitting project deliverables to Construction (District Earthwork Coordinators) submit the entire Project Folder (Example: the PI Number Folder and the associated files). This will ensure that all of the applicable files are submitted to the end-user. (See Table 2.1)
Table 2.1 Standard Project Naming Conventions InRoads Project Structure InRoads Project Structure (Example) C:\InRoads Data\PI Number C:\InRoads Data\123456
2-3
2.1.2 Standard File Naming Conventions InRoads contains several different file types but the Design data will usually consist of file types pertaining to the .ALG (Geometry File), the .DTM (Digital Terrain Models), the .IRD (Roadway Design Files), the .ITL (InRoads Template File) and the associated .DGN (MicroStation Design File) deliverables. Following are the applicable file naming conventions (See Table 2.2). Table 2.2 Standard File Naming Conventions File Type 3D Working DGN file The 3D Working DGN File is used as the standard DGN file for producing graphics in InRoads. File Name
GDOT 3D Working File.dgn
Example Name(s)
GDOT 3D Working File.dgn
PI#_ Design.alg ALG - Geometry File The Design ALG file contains the Existing Survey Geometry Data and the Proposed Design Geometry Data.
123456_Design.alg
DTM - Existing DTM File The Existing DTM file contains the Original Mapping and/or Field Survey DTM data. DTM - Proposed DTM File(s) The Proposed DTM(s) naming convention is PI#_Corridor Name.dtm. There can be several Proposed DTM Files including the Mainline and each associated Side Road. ITL InRoads Template Library File A standard GDOT ITL File named GDOT_StandardV8i.itl is provided. The Designer will copy this file to the Project Directory and rename it to PI#.itl. IRD InRoads Roadway Design File The IRD File is named PI#.ird and contains the Proposed Corridors and the Roadway Design for Cross Sections.
PI#_ Exist.dtm
123456_Exist.dtm
PI#_Corridor Name.dtm
123456_SR100 SPUR.dtm 123456_SR22.dtm
PI#.itl
123456.itl
PI#.ird
123456.ird
2-4
2.2
Standard Geometry Object Names and Feature Styles
The following section details the Standard Design and Survey Geometry Object Naming Conventions. The SDE provides the existing survey data in the Geometry Project (.ALG). This survey data consists of Property data, Existing Right of Way, Alignment data, etc. Basically it is survey which is Geometry related and which is used in the creation of the property, alignment and COGO database. This Geometry data will not be represented in the DTM. All other Survey Data will be imported into the Surface Project (.DTM) and will be represented as Surface Features. (The Designer may review this process by reading the Introduction to InRoads for Survey Data Processing Training Guide which depicts the process to filter data to import into the Geometry Project (.ALG). The Designer will store all of the proposed Geometry Data (Cogo Points, Alignment Points, Horizontal Alignments and Vertical Alignments) in the Design ALG File. NOTE: Please note that the term Horizontal Alignments represents not only Centerline Alignments but also Right of Way Alignments, Easement Alignments, Edge of Pavement Alignments, Ditch Alignments, etc. NOTE: Please note that Curves are not separate objects in InRoads - but are actually part of the Horizontal Alignment. The Curves have no name assigned to them in the Alignment. When generating curve tables for plan sheets the Designer will manually name the Curve Table(s) Curve Numbers. This is described in more detail in the Design Training Lab 5.
2-5
2.2.1 Standard Design and Survey Object Naming Conventions InRoads contains several different object types such as Cogo Points, Alignment Points, Horizontal Alignments and Vertical Alignments. Following are the applicable object naming conventions (See Tables 2.3 2.5). The Designer shall follow the guidelines below when storing design geometry objects in InRoads. These guidelines must be followed in order to conform to current GDOT standards and policies. Use only one prefix (DE) for points in InRoads and begin point numbering at 10000 (i.e. DE10000). This eliminates the possibility of duplicate points going back to the Data Collector for staking of survey data.
A. Design Object Names and Point/Alignment Ranges: The Design Geometry Objects consist of Cogo Points, Alignment Points, Horizontal Alignments and Vertical Alignments. The Designer will store Proposed Construction Centerlines, Required R/W Alignments, Easement Alignments, Edge of Pavement Alignments, etc. The following Naming Conventions will be used. Table 2.3 Standard Design Geometry Object Names Object Type *Design Cogo Points *Design Horizontal Alignment Points **Design Horizontal Alignments ***Design Vertical Alignments DE DE DE DE Prefix Starting Number 10000 (Max. = 99999) 10000 (Max. = 99999) 1 1
* All Design Cogo Points and Design Horizontal Alignment Points must be named with a prefix of DE and begin with the number 10000 (e.g., first design point = DE10000). **All Design Horizontal Alignments must be named with a prefix of DE and begin with the number 1, (e.g., DE1). ***It is suggested that the Design Vertical Alignment (which corresponds with the Horizontal Alignment) be named the same as the associated Horizontal Alignment. Table 2.4 Design Point & Alignment Ranges to Use Cogo/Alignment Points Horizontal/Vertical Alignments Range 10,000 to 99,999 Range 1 to no Limitations for Alignments -- but must have the DE Prefix 2-6
B. Survey Object Names and Point/Alignment Ranges: The SDE stores any computed and/or existing survey points with No prefixes. Any computed Alignments will be stored with an SV prefix to represent a Survey stored Alignment. The reason that Survey (field collected and computed points) do not contain pre-pended prefixes is to reduce the possibility of duplicate points going back to the data collector and to ensure that duplicate points are not submitted to the Designer when additional enhancements are added during the life of the project. Another reason is to prevent the Designers Points and Alignments from being overwritten when additional enhancements are added to the Designers Geometry Project Database. *Please note that it is a requirement for the SDE to pre-pend the SV Prefix to all computed Alignments. This includes Parcel Alignments, Existing Centerline Alignments, Existing R/W Alignments, etc.
Table 2.5 Standard Survey Geometry Object Names Object Type Survey Cogo Points Prefix Survey (SDE) = No Prefix Starting Number 1 1 1
Survey Horizontal Alignment Points Survey (SDE) = No Prefix SV Survey Horizontal Alignments
Point Numbers 1 9999 are reserved for survey collecting and survey data processing. Point numbering should be done consecutively and if more points are required the numbering should continue consecutively as needed. When additional survey data is gathered in the field, the point numbers should begin with the lowest number that has not already been submitted to design. Designers Point numbering range begins at 10,000. Points 10,000 and above are reserved for Design. If the total number of survey points has reached the 9,999 point limit, the Survey Data Engineer should contact the Designer and obtain the next starting point number. A gap in point numbering should only exist where the location survey points total less than 9,999. All other numbering gaps should be minimized. Table 2.6 Survey Point & Alignment Ranges to Use Cogo/Alignment Points Horizontal/Vertical Alignments Range 1 to 9,999 Range 1 to no Limitations for Alignments -- but must have the SV Prefix
2-7
2.2.2 Standard Geometry Survey and Design Feature Style Conventions The following Section details the Feature Styles used for Survey and Design Objects. When storing Survey and Design Geometry Objects the applicable Feature Styles must be utilized in order to view the correct symbology, cells, etc. for each of the elements. This ensures that the data conforms to the correct Level and Symbology as depicted by the Electronic Data Guidelines and for use in Plans Production utilities. The following existing Property codes/styles (which are composed of data which is used for the generation of Property and Alignment information) is processed by the SDE and submitted to the Designer in the ALG File. All Codes which are not listed in the table below will be imported into the Surface Project (.DTM File). The Survey Control Codes are imported into both the .ALG and the .DTM Files.
Property and Alignment Codes Survey Style Filter

PROP_E_RWM PROP_E_RWC PROP_E_RWU PROP_E_RWE PROP_E_POEL PROP_E_PCF PROP_E_PPOL PROP_E_PPC PROP_E_APOT PROP_E_APC PROP_E_APOC PROP_E_APT PROP_E_API PROP_E_ACL PROP_E_BCOL PROP_E_BCTL PROP_E_BLDL PROP_E_BLLL PROP_E_BSL Right-of-Way Marker Found Right-of-Way Point Computed Right-of-Way Utility Company Right-of-Way Prescription Pt Point on Easement Line Property Corner Found Property Point on Line Property Point Computed Point in Tangent, Existing Point of Curvature, Existing Point on Curve, Existing Point of Tangency, Existing Point of Intersection Alignment Centerline County Line City Limit Line Land District Line Land Lot Line State Line TOPO_E_SNGSCM TOPO_E_SLCM TOPO_E_SLCD TOPO_E_SDCD TOPO_E_SCCHK TOPO_E_SBNCHMK NGS Control Mon.
Loc. Cont. Mon. Loc. Cont. Delta Dist. Cont. Delta Cont. Re-shot Benchmark
2-8
A. Survey Feature Styles for Points and Alignments The Standard Feature Styles the SDE uses when storing Points and Alignments for the Existing Centerline Alignments, Existing R/W, Property, etc. are named according to the type of Point or Alignment which is to be stored. The following Table lists the applicable Feature Style(s) the SDE (Survey Data Engineer) utilizes when storing the Existing Point and Alignment data: (See Table 2.7)
Table 2.7 Feature Styles For Geometry Survey Points and Alignments PROP_E_ACL PROP_E_ACL-PC-PT PROP_E_APC PROP_E_API PROP_E_APOC PROP_E_APOT PROP_E_APT PROP_E_PCF PROP_E_ACL PROP_E_RWE PROP_E_POEL PROP_E_PPC PROP_E_PPOL PROP_E_RWC PROP_E_RWE PROP_E_RWM PROP_E_RWRR PROP_E_RWU
Existing/Computed Points
Existing Centerline Alignment Existing R/W Alignment
Existing Property (Parcel) Alignment PROP_E_PAR
2-9
B. Design Feature Styles for Points and Alignments The Standard Feature Styles to use when storing Design Points and Alignments for the Proposed Centerline Alignments, Proposed R/W and Easements, etc. will be named according to the type of Point or Alignment which is to be stored. The following Table lists the applicable Feature Style(s) the Designer utilizes when storing Design Points and Alignment data: (See Table 2.8) Table 2.8 Feature Styles For Geometry Design Points and Alignments DRNG_P_Ditch REQD_P_DWESMT MAIN_P_CONSTCL REQD_P_PESMT Proposed Design Points MAIN_P_EOP REQD_P_REQD Feature Style MAIN_P_EPSHLDR REQD_P_RWRM MAIN_P_SHLDR REQD_P_TESMT MAIN_P_SIDECL STE_P_DETCL Proposed Centerline Alignments Descriptions Feature Style (C/L Roadway Name) Mainline Centerline Sideroad Centerline Detour Centerline Proposed Right of Way Feature Style R/W Monument Reqd. R/W Perm. Const. Esmt. Temp. Const. Esmt. Driveway Esmt. Miscellaneous Feature Style Edge of Pavement Edge of Paved Shoulder Edge of Shoulder Ditch Centerline Other MAIN_P_EOP MAIN_P_EPSHLDR MAIN_P_SHLDR DRNG_P_Ditch (User-Defined) REQD_P_RWRM REQD_P_REQD REQD_P_PESMT REQD_P_TESMT REQD_P_DWESMT** MAIN_P_CONSTCL MAIN_P_SIDECL STE_P_DETCL Ex: C/L HWY 100 Ex: C/L PEQUANOC DR. Ex: C/L US 78 Descriptions
(Feature Style Parcel #/Parcel Align)
N/A Ex: REQD R/W PAR 33/SV29 Ex: PESMT PAR 44/SV67 Ex: TESMT PAR 23/SV88 Ex: DWESMT PAR 14/SV30 Descriptions
(Feature Style Roadway Name)
Ex: EOP HWY 100 Ex: EPSHLDR PEQUANOC DR. Ex: SHLDR US 78 Ex: Ditch HWY 100 User Defined
** The Feature Style of REQD_P_DWESMT will be used for all other types of easements (that are not listed above) and be noted as such on plans by the Engineer. 2-10
2.3
Standard Design Feature Styles
The following section details the Standard Design Feature Styles which are available in the GDOT_Standard V8i.xin file. These Feature Styles conform to the Electronic Data Guidelines and represent the InRoads Named Symbology and the associated MicroStation ByLevel Symbology. These Feature Styles must be utilized to conform to GDOT Standard Conventions and for use in Plans Productions Utilities. If a Feature Style is used which is not available in the GDOT XIN File an InRoads Default Symbology with a color of White will appear. It is very important to use the GDOT standard Feature Styles to ensure that the InRoads Data is generated correctly for use in InRoads, MicroStation and Plans Production Utilities. These Feature Styles are used in Geometry Objects, Components, Component Points and Proposed DTMs. The following Table contains the applicable Design Feature Styles to use for Design. NOTE: There are also Feature Styles available for use in Survey and Photogrammetry. Please refer to the InRoads Survey Data Processing Guidelines and the Photogrammetry Guidelines for Tables listing these Feature Styles.
2-11
Table 2.9 Feature Styles -- GDOT Geometry Design Points and Alignments
Feature Style Description
DRNG_P_Ditch MAIN_P_CONSTCL MAIN_P_EOP MAIN_P_EPSHLDR MAIN_P_SHLDR MAIN_P_SIDECL REQD_P_DWESMT REQD_P_PESMT REQD_P_REQD REQD_P_RWRM REQD_P_TESMT STE_P_DETCL
Ditch-Drainage Proposed Construction centerline Proposed Road Edge of Pavement Proposed edge of paved shoulder Proposed Shoulder lines Proposed Side or Cross road centerline Required Driveway Easement Required Permanent Easement Required R/W Required Right of Way Marker Required Temporary Easement Proposed Detour centerline
2-12
Table 2.10 Feature Styles GDOT Design Components and Component Points
Feature Style Description
DRNG_P_Ditch LIMT_P_CUT LIMT_P_CUT_Const-Limit LIMT_P_FILL LIMT_P_FILL_Const-Limit MAIN_P_Barrier-Median-Side MAIN_P_Barrier-Noise-Wall MAIN_P_Barrier-Retain-Wall MAIN_P_Barrier_PAY_4940_TP20 MAIN_P_Barrier_PAY_4940_TP21 MAIN_P_Barrier_PAY_4940_TP22 MAIN_P_Barrier_PAY_TP_S1 MAIN_P_Barrier_PAY_TP_S2 MAIN_P_Barrier_PAY_TP_S3 MAIN_P_Barrier_PAY_TP_S3A MAIN_P_Barrier_PAY_TP_S3B MAIN_P_Barrier_Side_PAY_TP_2-S MAIN_P_Barrier_Side_PAY_TP_2-SA MAIN_P_Barrier_Side_PAY_TP_2-SB MAIN_P_Barrier_Side_PAY_TP_2-SC MAIN_P_Barrier_Side_PAY_TP_6-S MAIN_P_Barrier_Side_PAY_TP_6-SA MAIN_P_Barrier_Side_PAY_TP_6-SB MAIN_P_Barrier_Side_PAY_TP_6-SC MAIN_P_Barrier_Side_PAY_TP_7-CS MAIN_P_Barrier_Side_PAY_TP_7-WS MAIN_P_CONSTCL MAIN_P_CROWN MAIN_P_Curb MAIN_P_Curb_PAY_9032B Dowel TP2 MAIN_P_Curb_PAY_9032B Dowel TP3 MAIN_P_Curb_PAY_9032B Dowel TP7 MAIN_P_Curb_PAY_9032B HeaderTP1 MAIN_P_Curb_PAY_9032B HeaderTP2 MAIN_P_Curb_PAY_9032B HeaderTP3
Ditch - Drainage Cut Limits Cut Limits Fill Limits Fill Limits Proposed median or side barrier Proposed noise barrier wall Propose retaining wall 4940 TP20 CONCRETE BARRIER 4940TP21 CONCRETE BARRIER 4940 TP22 CONCRETE BARRIER TP S1 SPECIAL DESIGN CONCRETE BARRIER TP S2 SPECIAL DESIGN CONCRETE BARRIER TP S3 SPECIAL DESIGN CONCRETE BARRIER TP S3A SPECIAL DESIGN CONCRETE BARRIER TP S3B SPECIAL DESIGN CONCRETE BARRIER TP 2-S SIDE CONCRETE BARRIER TP 2-SA SIDE CONCRETE BARRIER TP 2-SB SIDE CONCRETE BARRIER TP 2-SC SIDE CONCRETE BARRIER TP 6-S SIDE CONCRETE BARRIER TP 6-SA SIDE CONCRETE BARRIER TP 6-SB SIDE CONCRETE BARRIER TP 6-SC SIDE CONCRETE BARRIER TP 7-CS or 7-RS SIDE CONCRETE BARRIER TP 7-WS SIDE CONCRETE BARRIER Proposed Construction centerline Crown Point Proposed Curb 9032B TP2 CONC DOWELED INTEGRAL CURBS 6" THK 9032B TP3 CONC DOWELED INTEGRAL CURBS 8" THK 9032B TP7 CONC DOWELED INTEGRAL CURBS 6" THK 9032B TP1 4"HEADER CURB 9032B TP2 6"HEADER CURB 9032B TP3 8"HEADER CURB
2-13
Feature Style
Description
MAIN_P_Curb_PAY_9032B HeaderTP4 MAIN_P_Curb_PAY_9032B HeaderTP6 MAIN_P_Curb_PAY_9032B HeaderTP7 MAIN_P_Curb_PAY_9032B REdge 6" MAIN_P_Curb_PAY_9032B REdge 8" MAIN_P_Curb_PAY_9032B TP1 6" MAIN_P_Curb_PAY_9032B TP1 8" MAIN_P_Curb_PAY_9032B TP2 6" MAIN_P_Curb_PAY_9032B TP2 8" MAIN_P_Curb_PAY_9032B TP3 6" MAIN_P_Curb_PAY_9032B TP3 8" MAIN_P_Curb_PAY_9032B TP4 6" MAIN_P_Curb_PAY_9032B TP4 8" MAIN_P_Curb_PAY_9032B TP7 6" MAIN_P_Curb_PAY_9032B TP7 8" MAIN_P_Driveway MAIN_P_EEOP MAIN_P_EOP MAIN_P_EPSHLDR MAIN_P_Guardrail MAIN_P_Median_PAY_9032B_4"THK MAIN_P_Misc-Const-Feat MAIN_P_SHLDR MAIN_P_SIDECL MAIN_P_Sidewalk MAIN_P_Slope-break REQD_P_DWESMT REQD_P_PESMT REQD_P_REQD REQD_P_RWRM REQD_P_TESMT STE_P_DETCL
9032B TP4 10"HEADER CURB 9032B TP6 6"HEADER CURB 9032B TP6 7"HEADER CURB 9032B 6" RAISED EDGE WITH CONCRETE GUTTER 9032B 8" RAISED EDGE WITH CONCRETE GUTTER 9032B TP1 30" CURB & GUTTER 6"THK 9032B TP1 30" CURB & GUTTER 8"THK 9032B TP2 30" CURB & GUTTER 6"THK 9032B TP2 30" CURB & GUTTER 8"THK 9032B TP3 30" CURB & GUTTER 6"THK 9032B TP3 30" CURB & GUTTER 8"THK 9032B TP4 30" CURB & GUTTER 6"THK 9032B TP4 30" CURB & GUTTER 8"THK 9032B TP7 CURB & GUTTER 6"THK 9032B TP7 CURB & GUTTER 8"THK Driveway Exist Pavement Edge Proposed Road Edge of Pavement Proposed edge of paved shoulder Proposed guardrail 9032B CONCRETE MEDIAN 4"THK PAY ITEM Proposed misc. construction feature Proposed Shoulder lines Proposed Side or Cross road centerline Proposed Sidewalk Slope break point Required Driveway Easement Required Permanent Easement Required R/W Required Right of Way Marker Required Temporary Easement Proposed Detour centerline
2-14
2.4 Standard File Information

Following is a brief overview of the most common InRoads file types the Designer will utilize: (See Table 2.11) Table 2.11 Standard File Information Overview GDOT 3D Working File.dgn This DGN file is created from the GDOT 3D seed file (GDOT_V8_3D.dgn) and is used to display the temporary and or/permanent graphics in InRoads. .FWD (SDE File Only! This File is not provided to Design.) The .FWD file contains the imported Field Survey Data (.ASC File Data). Basically this file is an Electronic Field Book in which the .ASC File data is imported so that the survey data can be exported to the .DTM (Surface) and .ALG (Geometry) files. .DTM The Exist DTM file contains all of the Surface Features imported from AMSA and/or ASC File(s). The appropriate Surface Features are triangulated in order to form an Existing Ground Surface (TIN Model) for use in Survey and Design. The Designer will create a Proposed DTM File(s) which will contain the Proposed Ground Surface data. .ALG The .ALG (Geometry File) contains all of the Geometry related data such as Property, Existing R/W, Existing Centerline Alignments, Proposed Horizontal/Vertical Alignments and R/W and Easement Alignments for use in Design. .ITL The .ITL is the InRoads Template File which contains all of the Templates and Components for cross sections. This file is specific to each individual InRoads Project and should be submitted as a deliverable during project submission to the Earthwork Coordinator during Construction. .IRD The .IRD is the InRoads Roadway Design File which contains the Design Surface Data (the corridors and the associated cross sections which are generated to a Design Surface). .RWK The .RWK (InRoads Project File) contains project data for InRoads files in ASCII format. The .RWK file is a text file which can be edited to reflect the path of the Project Files so that all of the Files will be opened when the InRoads Project File (.RWK) is opened. .SDB The .SDB (InRoads Drainage File) contains the InRoads Storm and Sanitary data.
2-15
2.5 Standard Preference File (XIN) and GDOT Preferences

The following section details the GDOT Standard Preference File GDOT_Standard V8i.xin and the various InRoads Preferences that have been established for use in the Design Process.
2.5.1 Standard Preference File (XIN) Configuration InRoads Standards for Design have been set up in a Preference file (also known as an XIN file). This preference file contains the Georgia Department of Transportations standards for Feature Codes, Feature Styles, Feature Filters, Dialog Box Settings, Linestyles, Lineweights, colors, and numerous other settings. The XIN file is basically a compilation of INI Files (Initialization files) which controls the standardization of the InRoads settings and display options. This preference file is critical for use in the InRoads Design Process and for accurate Digital Terrain Model/ Geometry Objects creation. The XIN file is used in conjunction with MicroStation V8is ByLevel settings and configuration files to assist in the viewing of project data and in the generation of plan file deliverables. The standard GDOT XIN file is named GDOT_Standard V8i.xin and is included in the InRoadsALLV8i.exe download. After downloading and executing the InRoadsALLV8i.exe a Standards folder is created directly under the C:\InRoads Data folder. The Designer will copy this Standards folder to the Project Folder: (See Example in Table 2.12)
Table 2.12 Name and Location of the GDOT Standard XIN File GDOT Standard XIN File C:\InRoadsData\123456\Standards\GDOT_Standard V8i.xin
NOTE: The XIN file contains Named Symbology and Feature Styles which correspond with the ByLevel Settings in MicroStation. Please note that if any modifications or additional Feature Styles/Named Symbology are added by the user to the XIN the MicroStation Levels may not view with the correct Symbology for those modified Feature Styles. It is advisable to NOT add additional Named Symbology or Styles in order for the XIN file to be consistent with the current MicroStation ByLevel settings so that utilities for Plans Productions will function correctly.
2-16
2.5.2 Standard Preference File (XIN) Details The XIN File contains the GDOT configuration settings for use in Design/Survey. These settings contain the current GDOT standards for plan development and processing of Design/Survey Data. Following are some of the Configuration Settings contained in the XIN: Named Symbology This controls how elements such as points, lines, text, etc. appear in plan, cross section and profile views in MicroStation. The GDOT named symbology is also set to ByLevel which references the Level Settings for Symbology in the MicroStation DGNLIB. ByLevel controls the Symbology (weight, color, linestyle) and the Named Level on which the elements are located. The Named Symbology can also be set in the InRoads Named Symbology Manager by selecting each symbology (color, weight, linestyle, etc.) separately but GDOT uses the ByLevel Symbology to correspond with the DGNLIB Levels. (The Named Symbology determines How an element is viewed). Feature Styles InRoads contains Features which represent elements such as points, lines, arcs, spirals, etc. The Feature Style for each Geometry, Survey, DTM and Component element is used to determine how the elements view. The elements can be set to view in plan view, profile, cross section, DTM, etc. The Feature Style references the associated Named Symbology to view the element with the appropriate corresponding Symbology. The Feature Style determines Where the element is viewed. Preferences When using commands in the InRoads dialog boxes it is useful to set Preferences which can be loaded later without having to re-enter information into the dialog boxes. Preferences are basically entries in dialog boxes which can be saved and then selected to automatically configure the settings of a dialog box without manual re-entry. Filters Filters are commands in dialog boxes which can be used to filter selections of data based on set criteria. This can include selection of Points, Alignments, Features or other entities by using a filter based on the entities Style, Name, etc. These are some of the GDOT standards that have been configured for use in the XIN file. These settings are used to assist in the Design process to ensure that standards are consistent for development of GDOT project plans.
2-17
2.5.3
GDOT Preferences As mentioned previously - Preferences are entries in dialog boxes which can be saved and then selected later to automatically configure the settings of a dialog box without manual re-entry. The following Table lists the GDOT Preferences available in the GDOT XIN file. These Preferences will be discussed in more detail in each of the applicable Sections of the Survey and Design Guidelines.
Preference Name Dialog Name Dialog Location Description
10 Scale Work Sec 1x Vert Exg
Create Cross Section Annotate Profile
100h_10v Profile
Evaluation Cross Section Create Cross Section Preferences Evaluation Profile Annotate Profile Preferences Evaluation Profile Create Profile Preferences Evaluation Profile Create Profile Preferences Survey Fieldbook Data Survey Options Preferences Drafting Plan and Profile Generator Preferences
X-Section Grid (10 Scale) for Earthwork and End-Area reports. For use on projects with small footprints. Most situations will require using the 50 Scale Work Sec 2x Vert Exg Preference. Sets settings for 100 Scale Horizontal and 10 Scale Vertical viewing of existing and proposed Profile elevations on the Profile plan sheets. Use when annotating Profiles for Profile sheets using the 50 Scale Single Profile Preference in the Plan and Profile Generator. Loads grid settings, station formats, fonts and symbology for use in plotting a Profile at 100 Horizontal Scale and 10 Vertical Scale. This Preference is also referenced in the Plan & Profile Generator when generating 50 Scale Single Profile Sheets. Loads grid settings, station formats, fonts and symbology for use in plotting a Profile at 100 Horizontal Scale and 10 Vertical Scale. Same as 100h_10v_SHEETS except grid is not drawn. For use during temporary viewing of Profile during vertical alignment design. Sets Cell Scale, Text Scale, and Line Scale for viewing survey planimetrics for 20 Scale projects.
100h_10v_SHEETS
Create Profile
100h_10v_WORKING
Create Profile
20 Scale
Survey Options
20 Scale Double Profile
Plan and Profile Generator
Used for generating 20 Scale Double Profile Sheets.
2-18
Preference Name
Dialog Name
Dialog Location
Description
20 Scale Plan
20 Scale Plan & Profile
20 Scale Single Profile
20h_10v Profile
Plan and Profile Generator Plan and Profile Generator Plan and Profile Generator Annotate Profile
Drafting Plan and Profile Generator Preferences Drafting Plan and Profile Generator Preferences Drafting Plan and Profile Generator Preferences Evaluation Profile Annotate Profile Preferences
To be developed.
Used for generating 20 Scale Plan & Profile Sheets.
Used for generating 20 Scale Single Profile Sheets.
20h_5v_SHEETS
Create Profile
Evaluation Profile Create Profile Preferences
20h_5v_WORKING
Create Profile
50 Scale
Survey Options
Survey Fieldbook Data Survey Options Preferences
Sets settings for 20 Scale Horizontal and 10 Scale Vertical viewing of existing and proposed Profile elevations on the Profile plan sheets. Use when annotating Profile for Profile sheets using the 20 Scale Single Profile, 20 Scale Double Profile, and 20 Scale Plan & Profile Preferences in the Plan and Profile Generator. Loads grid settings, station formats, fonts and symbology for use in plotting a Profile at 20 Horizontal Scale and 5 Vertical Scale. This Preference is also referenced in the Plan & Profile Generator when generating 20 Scale Single Profile Sheets, 20 Scale Double Profile Sheets and 20 Scale Plan and Profile Sheets. Loads grid settings, station formats, fonts and symbology for use in plotting a Profile at 20 Horizontal Scale and 5 Vertical Scale. Same as the 20h_5v_SHEETS Preference except the grid is not drawn. For use during temporary viewing of Profile during vertical alignment design. Sets Cell Scale, Text Scale, and Line Scale for viewing survey planimetrics for 50 Scale projects.
2-19
Preference Name
Dialog Name
Dialog Location
Description
50 Scale Double Profile
Plan and Profile Generator Plan and Profile Generator Plan and Profile Generator Plan and Profile Generator Create Cross Section Annotate Profile
Drafting Plan and Profile Generator Preferences Drafting Plan and Profile Generator Preferences Drafting Plan and Profile Generator Preferences Drafting Plan and Profile Generator Preferences Evaluation Cross Section Create Cross Section Preferences Evaluation Profile Annotate Profile Preferences
Used for generating 50 Scale Double Profile Sheets.
50 Scale Plan
To be developed.
50 Scale Plan & Profile
Used for generating 50 Scale Plan & Profile Sheets.
50 Scale Single Profile
Used for generating 50 Scale Single Profile Sheets.
X-Section Grid (50 Scale) for Earthwork and End-Area reports. Most situations will require using this Preference.
50h_10v Profile
50h_10v_SHEETS
Create Profile
Sets settings for 50 Scale Horizontal and 10 Scale Vertical viewing of existing and proposed Profile elevations on the Profile plan sheets. Use when annotating Profile for Profile sheets using the 50 Scale Double Profile, and 50 Scale Plan & Profile Preferences in the Plan and Profile Generator. Loads grid settings, station formats, fonts and symbology for use in plotting a Profile at 50 Horizontal Scale and 10 Vertical Scale. This Preference is also referenced in the Plan & Profile Generator when generating 50 Scale Double Profile Sheets and 50 Scale Plan and Profile Sheets.
2-20
Preference Name
Dialog Name
Dialog Location
Description
50h_10v_WORKING
Create Profile
Loads grid settings, station formats, fonts and symbology for use in plotting a Profile at 50 Horizontal Scale and 10 Vertical Scale. Same as the 50h_10v_SHEETS Preference except the grid is not drawn. For use during temporary viewing of Profile during vertical alignment design. Loads settings for viewing Horizontal Alignment Stationing and Curve Data.
ACL
View Stationing
Geometry View Geometry Stationing Preferences
ACL Cogo Point Feature Styles
Curve Set Geometry View Annotation Geometry Curve Set Annotation Preferences Geometry Geometry View Selection Geometry Filter Horizontal Annotation Filter Preferences
For use by the Survey Data Engineer (SDE) when creating the ACL centerline alignment. The Preference is used in the Geometry Selection Filter when only points with the following Feature Styles are desired to be viewed. PROP_E_API,PROP_E_APT,PROP_E_APC,PROP_E_APOT,PROP _E_APOC
BEARING & DISTANCE
View Geometry View Horizontal Geometry Annotation Horizontal Annotation Preferences
Loads settings into the View Horizontal Annotation dialog to label the bearing when viewing Roadway alignments with the feature styles MAIN_P_CONSTCL, MAIN_P_SIDECL, and PROP_E_ACL. Although DISTANCE is part of the Preference name the distance is no longer set up to be labeled.
2-21
Preference Name
Dialog Name
Dialog Location
Description
BOGUS SURFACE
View Triangles /
Surface View Surface Triangles Preferences. Surface Surface Properties Advanced Surface View Surface Annotate Feature Preferences Geometry View Geometry Stationing Preferences
Surface Properties
Bridge Hydraulics
Annotate Feature View Stationing/
Used for viewing surface triangles of Bogus Surfaces (surfaces created by the designer for the temporary filling of obscured areas). The Bogus Surface Preference loads settings to view the surface as pink, easily distinguishing it as a Bogus Surface. The Bogus Surface Preference is used in both the View Triangles dialog and the Surface Properties dialog. The Surface Properties dialog ensures the pink surface is displayed when viewing existing ground Profiles and Cross Sections. Loads settings into the Annotate Feature dialog to annotate selected Bridge Features in the Surface for use in Bridge Hydraulics. 50 Scale settings for viewing Stationing and Curve Set Annotation for Mainline Construction Centerline Alignments.
CONSTCL
CONSTCL 20 SCALE
Default Design Default
Curve Set Geometry View Annotation Geometry Curve Set Annotation Preferences View Geometry View Stationing Geometry Stationing Preferences Default Preference Options Tools Options Preferences
20 Scale settings for viewing Stationing of Mainline Construction Centerline Alignments.
Original Equipment Manufacturers default settings. For use by Design. Loads proper point numbering and prefixes, precision, abbreviations, sight distance settings, factors, tolerances Units and formats for GDOT projects.
2-22
Preference Name
Dialog Name
Dialog Location
Description
DETCL
View Stationing/
50 Scale settings for viewing Stationing and Curve Set Annotation for Detour Centerline Alignments.
DETCL 20 Scale
Curve Set Geometry View Annotation Geometry Curve Set Annotation Preferences View Geometry View Stationing Geometry Stationing Preferences Annotate Feature View Triangles View Triangles/ Surface View Surface Annotate Feature Preferences Surface View Surface Triangles Preferences Surface View Surface Triangles Preferences Surface View Surface Contours Preferences Surface View Surface Label Contours Preferences
20 Scale settings for viewing Stationing for Detour Centerline Alignments.
Ditch Flow Arrows
ENHANCEMENTS
Loads settings into the Annotate Feature dialog to place the Ditch Flow Arrow cell on user selected features. The settings ensure the Ditch Flow Arrow cell point in the direction of flow. For use by the SDE when viewing enhancements to obscured areas for inclusion into the Existing DTM. For use when viewing the Existing DTM.
EXISTING
View Contours Existing Majors Label Contours
For use in labeling individual Major Contour Elevations of Existing ground surfaces.
2-23
Preference Name
Dialog Name
Dialog Location
Description
Existing Minors
Label Contours
FINISH
View Triangles/
Surface View Surface Label Contours Preferences Surface View Surface Triangles Preferences Surface View Surface Contours Preferences Surface View Surface Label Contours Preferences Surface View Surface Label Contours Preferences Modeler Create Template Right mouse click over the Template to Display and select Display Preferences Evaluation Volumes End-Area Volume Preferences
For use in labeling individual Minor Contour elevations of Existing ground surfaces.
For use when viewing Final DTM Surfaces.
View Contours Finished Majors Label Contours
For use in labeling individual Major Contour Elevations of Finished Design Surfaces.
Finished Minors
Label Contours
For use in labeling individual Minor Contour Elevations of Finished Design Surfaces.
GDOT
Display Template
Loads settings for viewing a component or template in MicroStation.
GDOT Earthwork Volumes
End-Area Volumes
Loads settings for generating the GDOT Earthwork Volumes Report.
2-24
Preference Name
Dialog Name
Dialog Location
Description
GDOT Profiles
Narrow 10h 10v
NO BEARING & DISTANCE
OEM_Default
Geometry View Geometry Vertical Annotation Evaluation Cross Section Create Cross Section Preferences View Geometry View Horizontal Geometry Annotation Horizontal Annotation Preferences Surface View Surface Triangles Preferences View Vertical Annotation Create Cross Section
Settings for proper viewing of vertical curve data on the Profile Plan Sheets. Loads settings for creating Narrow Cross Section Sheets at a 10 Horizontal to 10 Vertical Scale. The Global Scale Factor must be set separately to 10.0000 for proper viewing. Loads settings into the View Horizontal Annotation dialog to turn off labeling the bearing and distance when viewing alignments.
Original Equipment Manufacturers default settings.
Prop.dgn Alignments
Geometry Selection Filter
Geometry View Geometry Horizontal Annotation Filter Preferences
For use by the SDE when creating the PI#_PROP.dgn file for delivery to the Design Office. The Preference filters the Feature Styles to the 13 Features Styles listed here: PROP_E_ACL,PROP_E_BCOL,PROP_E_BCTL,PROP_E_BGMD, PROP_E_BLDL,PROP_E_BLLL,PROP_E_BMISC,PROP_E_BSL, PROP_E_PAR,PROP_E_POEL,PROP_E_RWE,PROP_E_RWRR, PROP_E_RWU
2-25
Preference Name
Dialog Name
Dialog Location
Description
Prop.dgn Points
Geometry View Geometry Horizontal Annotation Filter Preferences
For use by the SDE when creating the PI#_PROP.dgn file for delivery to the Design Office. The Preference filters the Feature Styles to the 22 Features Styles listed here: PROP_E_APC,PROP_E_API,PROP_E_APOC,PROP_E_APOT, PROP_E_APT,PROP_E_BCOL,PROP_E_BCTL,PROP_E_BGMD, PROP_E_BLDL,PROP_E_BLLL,PROP_E_BMISC,PROP_E_BSL, PROP_E_PAR,PROP_E_PCF,PROP_E_POEL,PROP_E_PPC, PROP_E_PPOL,PROP_E_RWC,PROP_E_RWE,PROP_E_RWM, PROP_E_RWRR,PROP_E_RWU
REQD.dgn Alignments
Geometry View Geometry Horizontal Annotation Filter Preferences Geometry View Geometry Horizontal Annotation Filter Preferences
For use in creating the PI#REQD.dgn file. The Preference filters the Feature Styles to the 4 Features Styles listed here: REQD_P_DWESMT,REQD_P_PESMT,REQD_P_REQD,REQD_P_ TESMT For use in creating the PI#REQD.dgn file. The Preference filters the Feature Styles to the 5 Features Styles listed here: REQD_P_DWESMT,REQD_P_PESMT,REQD_P_REQD,REQD_P_ TESMT,REQD_P_RWRM
REQD.dgn Points
2-26
Preference Name
Dialog Name
Dialog Location
Description
SIDECL
View Stationing/
50 Scale settings for viewing Stationing and Curve Set Annotation for Side Road Construction Centerline Alignments.
SIDECL 20 SCALE
Stakeout Survey Data
Curve Set Geometry View Annotation Geometry Curve Set Annotation Preferences View Geometry View Stationing Geometry Stationing Preferences Geometry Tools XML Reports Selection CTRL + Stakeout Filter Filter Preferences
20 Scale settings for viewing Stationing for Side Road Construction Centerline Alignments.
Used to create the Stakeout Report. The Preference filters the Feature Styles to the following 20 Feature Styles. PROP_E_PAR,PROP_E_RWE,PROP_E_RWM,PROP_E_RWC, PROP_E_RWU,PROP_E_POEL,PROP_E_PPC,PROP_E_PCF, TOPO_E_SNGSCM,TOPO_E_SLCM,TOPO_E_SLCD, TOPO_E_SDCD,TOPO_E_SBNCHMK,REQD_P_*, MAIN_P_CONSTCL,MAIN_P_SIDECL
Surface Check MPCKGRD
Tools XML Reports Surface Check Filter Preferences
Used by the District Survey Party Chiefs and the Consultant Compliance Supervisor in the Office of Design Policy and Support/Location Bureau to generate a GDOT Surface Check Report. The Surface Check MPCKGRD Preference is used to filter the Feature Styles for the First Check Points - Include: field to include only the Feature Style: TOPO_E_MPCKGRD
2-27
Preference Name
Dialog Name
Dialog Location
Description
Surface Check MPCKPAV
Tools XML Reports Surface Check Filter Preferences
Used by the District Survey Party Chiefs and the Consultant Compliance Supervisor in the Office of Design Policy and Support/Location Bureau and Support to generate a GDOT Surface Check Report. The Surface Check MPCKPAV Preference is used to filter Feature Styles for the Second Check Points - Include: field to include only the Feature Style: TOPO_E_MPCKPAV For use by Photogrammetry and Survey. Loads proper point numbering and prefixes, precision, abbreviations, sight distance settings, factors, tolerances Units and formats for GDOT projects. Loads settings for creating Wide Cross Section sheets at a 10 Horizontal to 10 Vertical Scale. The Global Scale Factor must be set separately to 10.0000 for proper viewing. Used for annotating the existing ground elevation on the Cross Sections at the centerline alignment.
Survey Default
Options
Tools Options Preferences Evaluation Cross Section Create Cross Section Preferences Evaluation Cross Section Annotate Cross Section Preferences Evaluation Cross Section Annotate Cross Section Preferences Evaluation Cross Section Annotate Cross Section Preferences
Wide 10h 10v
Create Cross Section Annotate Cross Section Annotate Cross Section Annotate Cross Section
XSEC TEXT CL. EL. GROUND
XSEC TEXT EL. DIAGONAL
Used for the annotation of proposed elevations in which the text must be viewed diagonally. (i.e. Roadway Profile.)
XSEC TEXT EL. HORIZONTAL
Used for the annotation of proposed elevations in which the text must be viewed horizontally. (i.e. Roadway Ditches.)
2-28
Preference Name
Dialog Name
Dialog Location
Description
XSEC TEXT EL. VERTICAL
Annotate Cross Section
Evaluation Cross Section Annotate Cross Section Preferences
Used for the annotation of proposed elevations in which the text must be viewed vertically.
XSEC TEXT - OFFSET
Annotate Cross Section
Evaluation Cross Section Annotate Cross Section Preferences
User for the annotation of offset distances as measured from the centerline. (i.e. Slopestakes/Construction Limits.)
XSEC TEXT OFFSET/EL. VERTICAL
Annotate Cross Section Annotate Cross Section Annotate Cross Section
XSEC TEXT SLOPES %
XSEC TEXT SLOPES x:y
Evaluation Cross Section Annotate Cross Section Preferences Evaluation Cross Section Annotate Cross Section Preferences Evaluation Cross Section Annotate Cross Section Preferences
Used for the annotation of offset distances as measured from the centerline. The elevation at the offset is also placed. This form of annotation is not required on the final Cross Section plans. It is provided to be used as desired during the design process. Used for the annotation of slopes that require a percentage be used rather than a ratio (i.e. Pavement Cross Slopes).
Used for the annotation of slopes that require a ratio be used rather than a percentage (i.e. Ditch Slopes, Front Slopes, Back Slopes, etc.).
2-29
2.6 GDOT Standard InRoads Photogrammetric Feature Codes

The following spreadsheet is for informational use only so that the Designer will have a reference for the Photogrammetry Feature Codes if needed. The spreadsheet contains the standard Numeric AMSA Codes and the associated InRoads Alpha Codes for use in Photogrammetry. The Triangulate (Yes/No) column is for informational use only. This column denotes the status of the Alpha Code and lists whether it is triangulated or not triangulated in the DTM Surface.
GDOT STANDARD PHOTOGRAMMETRY CODES

AMSA Code Description InRoads Alpha Code Triangulate (Yes/No)
1 2 27 28 33 34 35 57 96 97 127 128 150 151 155 157 159
TERRAIN POINT ON BREAK LINE RANDOM TERRAIN POINT EDGE OF ASPHALT PAVEMENT EDGE OF ASPHALT SHOULDER CURB & GUTTER, TOP CURB & GUTTER, F/L V-GUTTER DRAINAGE OBSCURE AREA WALL FACE, TOP WALL FACE, BOTTOM LIMIT LINE CONSTRUCTION BOUNDARY, ACTV JOB LIMIT LINE DITCH FLOW LINE TOP OF RAIL ROAD RAIL SEW LINE OBSCURE AREA
TPBL TRP TEAP TEAS TCGT TCGF TVG DOBSC TWFT TWFB TLIML TCBA MJLL MDITCHFL TRCRE MSEWLINE MOBSC
Y Y Y Y Y Y Y Y Y Y N Y N Y Y Y Y
2-30
2.7 GDOT Standard InRoads Field Survey Feature Codes

The following spreadsheet is for informational use only so that the Designer will have a reference for the Field Survey Feature Codes if needed. The spreadsheet contains the standard Numeric SMI Codes and the associated InRoads Alpha Codes for use in Field Survey. The InRoads Feature Style is depicted for use by Survey Data Engineers and Designers. The Point Type and Chain Type Triangulate (Yes/No) column(s) are for informational use only. This column denotes the status of the Alpha Code and lists whether it is triangulated or not triangulated in the DTM Surface and whether it is a Point Type or a Chain Type.
InRoads Alpha Code InRoads Feature Style Point Type Triangulate (Y/N) Chain Type Triangulate (Y/N)
SMI Code
Description
Group Code
Ground Elevations
1 2 3 4 5 6 7 8 9 10 15 16 17 18 19 20 TERRAIN POINT ON BREAK LINE RANDOM TERRAIN POINT TPBL TRP RWM RWC RWU RWE POEL PCF PPOL PPC APOT APC APOC APT API ACL 2-31 TOPO_E_TPBL TOPO_E_TRP PROP_E_RWM PROP_E_RWC PROP_E_RWU PROP_E_RWE PROP_E_POEL PROP_E_PCF PROP_E_PPOL PROP_E_PPC PROP_E_APOT PROP_E_APC PROP_E_APOC PROP_E_APT PROP_E_API PROP_E_ACL Y Y N N N N N N N N N N N N N N
4 2 1 1 1 3 1 1 1 1 1 1 1 1 1 3
Property and Right-of-Way

RIGHT-OF-WAY MARKER FOUND RIGHT-OF-WAY POINT COMPUTED RIGHT-OF-WAY UTILITY COMPANY RIGHT-OF-WAY PRESCRIPTION PT POINT ON EASEMENT LINE PROPERTY CORNER FOUND PROPERTY POINT ON LINE PROPERTY POINT COMPUTED
Alignment
POINT ON TANGENT, EXISTING POINT OF CURVATURE, EXISTING POINT ON CURVE, EXISTING POINT OF TANGENCY, EXISTING POINT OF INTERSECTION ALIGNMENT CENTERLINE
SMI Code
Description
InRoads Alpha Code
InRoads Feature Style
Point Type Triangulate (Y/N)
Chain Type Triangulate (Y/N)
Group Code
Roadways
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 EDGE OF DIRT ROAD EDGE OF ASPHALT DRIVE EDGE OF CONCRETE DRIVE EDGE OF ASPHALT PAVEMENT EDGE OF ASPHALT SHOULDER EDGE OF CONCRETE PAVEMENT EDGE SURFACE TREATMENT ROAD CURB, ASPHALT CURB, HEADER CURB & GUTTER, TOP CURB & GUTTER, F/L V-GUTTER BRIDGE APPROACH SLAB, EDGE BRIDGE END, CENTER BRIDGE END, CORNER BRIDGE COLUMN, CENTER BRIDGE COLUMN, EDGE BRIDGE GUTTER LINE BRIDGE CENTERLINE ENDROLL BRIDGE CAP TEDR TEAD TECD TEAP TEAS TECP TEST TAC THC TCGT TCGF TVG TBAS TBRDGCEN TBRDGCOR TCOLC TCOLE TBGL TBCL TENDROLL TBCAP TOPO_E_TEDR TOPO_E_TEAD TOPO_E_TECD TOPO_E_TEAP TOPO_E_TEAS TOPO_E_TECP TOPO_E_TEST TOPO_E_TAC TOPO_E_THC TOPO_E_TCGT TOPO_E_TCGF TOPO_E_TVG TOPO_E_TBAS TOPO_E_TBRDGCEN TOPO_E_TBRDGCOR TOPO_E_TCOLC TOPO_E_TCOLE TOPO_E_TBGL TOPO_E_TBCL TOPO_E_TENDROLL TOPO_E_TBCAP Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N N Y N
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 1 1 4 4 4 2
2-32
SMI Code
Description
InRoads Alpha Code
Group Code
Drainage
45 47 49 50 51 52 53 54 55 56 57 59 60 61 62 63 SINGLE CATCH BASIN, Gutr F/L DOUBLE CATCH BASIN, Gutr F/L DROP INLET, TOP SPUR DIKE TOP OF WATER ELEVATION STREAM CENTER, F/L STREAM EDGE STREAM BANK TOP DAM, TOP DAM, TOE OBSCURED AREA HEAD WALL, END CULVERT, WINGWALL END EDGE OF WATER SWAMP EDGE WETLAND BOUNDARY DCB DDCB DDI DSPURDK DWE DSC DSE DSB DDT DADB DOBSC DHWE DCWE DEW DSWE DWB TOPO_E_DCB TOPO_E_DDCB TOPO_E_DDI TOPO_E_DSPURDK TOPO_E_DWE TOPO_E_DSC TOPO_E_DSE TOPO_E_DSB TOPO_E_DDT TOPO_E_DADB TOPO_E_DOBSC TOPO_E_DHWE TOPO_E_DCWE TOPO_E_DEW TOPO_E_DSWE TOPO_E_DWB N N N Y N Y Y Y Y Y Y N N N N N
2 2 2 4 2 4 4 4 4 4 4 3 3 3 3 3
2-33
SMI Code
Description
InRoads Alpha Code
Group Code
Utilities
68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 STRAIN POLE ELECTRICAL BOX OVERHEAD ELECTRICAL LINE OVERHEAD TELEPHONE LINE POWER POLE, CENTER LIGHT POLE, CENTER TELEPHONE POLE, CENTER TELEPHONE PEDESTAL, CENTER GUY POLE, CENTER POLE ANCHOR YARD LIGHT, ELECTRICAL YARD LIGHT, GAS WATER METER, CENTER WATER VALVE FIRE HYDRANT, CENTER MANHOLE STORM SEWER, TOP MANHOLE STORM SEWER, F/L MANHOLE, TELEPHONE, TOP MANHOLE, ELECTRICAL, TOP MANHOLE, SANITARY SEWER, TOP MANHOLE, SANITARY SEWER, F/L SANITARY SEWER LINE, CENTER GAS METER, CENTER GAS VALVE, CENTER USTRPOL UELBOX UOEL UOTL UPP ULP UTP UTPD UGP UPGA UYLE UYLG UWM UWV UFH UMHST UMHSTF UMHT UMHE UMHSS UMHSSF USSL UGM UNGV 2-34 TOPO_E_USTRPOL TOPO_E_UELBOX TOPO_E_UOEL TOPO_E_UOTL TOPO_E_UPP TOPO_E_ULP TOPO_E_UTP TOPO_E_UTPD TOPO_E_UGP TOPO_E_UPGA TOPO_E_UYLE TOPO_E_UYLG TOPO_E_UWM TOPO_E_UWV TOPO_E_UFH TOPO_E_UMHST TOPO_E_UMHSTF TOPO_E_UMHT TOPO_E_UMHE TOPO_E_UMHSS TOPO_E_UMHSSF TOPO_E_USSL TOPO_E_UGM TOPO_E_UNGV N N N N N N N N N N N N N N N N N N N N N N N N
1 3 3 3 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 1 1 1
SMI Code
Description
InRoads Alpha Code
Group Code
Utilities
92 93 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 115 GAS VENT PIPE GAS LINE MARKER UNGVP UNGLM TWF TWFT TWFB TIRRPVTP TIRRLMT TSC TGMW TGFV TGVP TGP TGST TGPI TCAN TBLD TBLDRL THCR THRL TMHCR TMHRL TWL TOPO_E_UNGVP TOPO_E_UNGLM TOPO_E_TWF TOPO_E_TWFT TOPO_E_TWFB TOPO_E_TIRRPVTP TOPO_E_TIRRLMT TOPO_E_TSC TOPO_E_TGMW TOPO_E_TGFV TOPO_E_TGVP TOPO_E_TGP TOPO_E_TGST TOPO_E_TGPI TOPO_E_TCAN TOPO_E_TBLD TOPO_E_TBLDRL TOPO_E_THCR TOPO_E_THRL TOPO_E_TMHCR TOPO_E_TMHRL TOPO_E_TWL N N N Y Y N N N N N N N N N N N N N N N N N
1 1 3 4 4 1 1 1 1 1 1 1 3 3 3 3 3 3 3 3 3 3
General Topo
WALL FACE WALL FACE, TOP WALL FACE, BOTTOM IRRIGATION PIVOT POINT IRRIGATION LIMITS SIGN, CENTER GASOLINE MONITORING WELL GASOLINE FILLER VALVE GASOLINE VENT PIPE GASOLINE PUMP GASOLINE STORAGE TANK, END GASOLINE PUMP ISLAND CANPOY BUILDING CORNER BUILDING ROOF LINE CORNER HOUSE CORNER HOUSE ROOF LINE CORNER MOBILE HOME CORNER MOBILE HOME ROOF LINE CORNER WOODS LINE
2-35
SMI Code
Description
InRoads Alpha Code
Group Code
General Topo
116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 CULTIVATION LINE FENCE, FIELD WIRE FENCE, BARB WIRE FENCE, WOOD RAILROAD, TOP OF RAIL RAILROAD, CENTERLINE CEMETERY LINE GRAVE GUARDRAIL SIGN, END SATELLITE DISH LIMIT LINE CONSTRUCTION BOUNDARY, ACTV CONSTRUCTION BOUNDARY, FIND TCUL TFFW TFBW TFW TRCR TRCL TCEM TGRV TGR TSE TSATDSH TLIML TCBA TCBF BCOL BCTL BLDL BLLL BSL TOPO_E_TCUL TOPO_E_TFFW TOPO_E_TFBW TOPO_E_TFW TOPO_E_TRCR TOPO_E_TRCL TOPO_E_TCEM TOPO_E_TGRV TOPO_E_TGR TOPO_E_TSE TOPO_E_TSATDSH TOPO_E_TLIML TOPO_E_TCBA TOPO_E_TCBF PROP_E_BCOL PROP_E_BCTL PROP_E_BLDL PROP_E_BLLL PROP_E_BSL N N N N N N N N N N N Y Y Y N N N N N
3 3 3 3 4 3 3 3 3 3 1 4 4 4 3 3 3 3 3
Boundaries
COUNTY LINE CITY LIMIT LINE LAND DISTRICT LINE LAND LOT LINE STATE LINE
2-36
SMI Code
Description
InRoads Alpha Code
Group Code
New Codes
**152 **153 **154 **156 **158 160 161 **162 **163 **164 **165 **166 **167 **168 **169 **170 171 172 173 174 175 176 177 178 179 HIGH WATER MARK FLOOR ELEVATION EDGE OF DIRT DRIVE GATE UNCOVERED DECK MAP CHECK GROUND MAP CHECK PAVEMENT VINYL (PVC) FENCE FUEL TANK PAVE DITCH BRICK COLUMN SEPTIC TANK CENTER STEPS HISTORICAL MONUMENT FLAG POLE DRAIN LINES DHWM TFE TEDD TG TUD MPCKGRD MPCKPAV TVF TFT DPD TBC DSTC TS THM TFP DDL XXA XXB XXC XXD XXE XXF XXG XXH XXI 2-37 TOPO_E_DHWM TOPO_E_TFE TOPO_E_TEDD TOPO_E_TG TOPO_E_TUD TOPO_E_MPCKGRD TOPO_E_MPCKPAV TOPO_E_TVF TOPO_E_TFT TOPO_E_DPD TOPO_E_TBC TOPO_E_DSTC TOPO_E_TS TOPO_E_THM TOPO_E_TFP TOPO_E_DDL TOPO_E_XXA TOPO_E_XXB TOPO_E_XXC TOPO_E_XXD TOPO_E_XXE TOPO_E_XXF TOPO_E_XXG TOPO_E_XXH TOPO_E_XXI N N Y N N N N N N Y N N N N N N Y Y Y Y Y Y Y N N
2 2 4 3 3 2 2 3 3 4 3 1 3 3 1 3
Surveyor Defined
Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value
4 4 4 4 4
4 4 3 3
SMI Code
Description
InRoads Alpha Code
Group Code
Surveyor Defined
180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value Surveyor Defined Value XXJ XXK XXL XXM XXN XXO XXP XXQ XXR XXS XXT XXU XXV XXW XXX XXY XXZ XXZA XXZB XXZC TOPO_E_XXJ TOPO_E_XXK TOPO_E_XXL TOPO_E_XXM TOPO_E_XXN TOPO_E_XXO TOPO_E_XXP TOPO_E_XXQ TOPO_E_XXR TOPO_E_XXS TOPO_E_XXT TOPO_E_XXU TOPO_E_XXV TOPO_E_XXW TOPO_E_XXX TOPO_E_XXY TOPO_E_XXZ TOPO_E_XXZA TOPO_E_XXZB TOPO_E_XXZC N N N N N Y Y Y Y Y Y Y N N N N N N N N 3 3 3 3 3 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1
2-38
SMI Code
Description
InRoads Alpha Code
Group Code
Dimension Codes: (Drainage)

200 201 202 **203 210 211 212 213 225 227 235 236 237 240 241 242 243 244 245 250 DRAINAGE PIPE, F/L, C DRAINAGE PIPE, F/L, M DRAINAGE PIPE, F/L, P CULVERT END, F/L DPC DPM DPP DCEF TSW TFCL TTRE TWELL TDR TDD TMPR TKMP TMPH SNGSCM SLCM SLCD SDCD SCCHK SBNCHMK MISC 2-39 TOPO_E_DPC TOPO_E_DPM TOPO_E_DPP TOPO_E_DCEF TOPO_E_TSW TOPO_E_TFCL TOPO_E_TTRE TOPO_E_TWELL TOPO_E_TDR TOPO_E_TDD TOPO_E_TMPR TOPO_E_TKMP TOPO_E_TMPH TOPO_E_SNGSCM TOPO_E_SLCM TOPO_E_SLCD TOPO_E_SDCD TOPO_E_SCCHK TOPO_E_SBNCHMK TOPO_E_MISC N N N N N N N N N N N N N N N N N N N N
4 4 4 4
Dimension Codes (General Topo)

SIDEWALK, CENTER FENCE, CHAIN LINK TREE, CENTER WELL
3 3 1 1
Dimension Codes (Roadway)

DIRT ROAD, C/L DIRT DRIVE, C/L MILE POST, RAILROAD KM POST, HIGHWAY MILE POST, HIGHWAY
3 3 1 1 1
Survey control
NGS CONTROL MONUMENT LOCATION CONTROL MONUMENT LOCATION CONTROL DELTA DISTRICT CONTROL DELTA CONTROL RE-SHOT FOR CHECK BENCHMARK MISCELLANEOUS
2 2 2 2 2 2 2
3.
Horizontal Alignments
3. Horizontal Alignments
This section provides a brief overview of the requirements for Horizontal Alignments, Horizontal Alignment Points and COGO Points. For detailed Horizontal Alignment information please refer to Lab 3 in the Design Training Labs. This section covers the following topics:
Horizontal Alignment Overview Horizontal Alignment and COGO Point Names/Feature Styles COGO Points and Alignment Points View Horizontal Annotation Preferences View Horizontal Annotation Filters Reviewing Horizontal Alignments
3-2
3.1 Horizontal Alignment Overview

In InRoads the term Horizontal Alignment refers to all linear elements, open or closed, such as centerlines, right of way parcels, edge of pavements, etc. Horizontal Alignments consist of COGO points, linear elements and curves. Curves are not independent entities but are considered part of the Alignment. In order to generate Horizontal Alignments to GDOT standard conventions the following information should be adhered and followed.
a) All Centerline Horizontal Alignments must have a Feature Style assigned of MAIN_P_CONSTCL, MAIN_P_SIDECL or STE_P_DETCL for the correct Symbology and Stationing to view correctly. b) All Right of Way and Easement Alignments must have a Feature Style assigned of REQD_P_DWESMT, REQD_P_PESMT, REQD_P_REQD or REQD_P_TESMT for the Right of Way Tables to generate correctly. c) Any additional Horizontal Alignments such as Ditch Centerlines, Edge of Pavements, etc. must be assigned the appropriate Feature Style for the Symbology and Levels to view correctly in MicroStation. d) All Horizontal Alignment Names and COGO Point Names must begin with a DE Prefix. All Points must begin numbering at DE10000. Horizontal Alignment numbering may begin at DE1. e) All Horizontal Alignment Points must be converted to COGO Points. f) Designers should not use the Existing Centerline Alignment provided by Survey as the Design Alignment but should create a new Design Alignment either by copying and renaming the Existing Centerline Alignment and assigning an appropriate Feature Style or by creating a new Design Centerline Alignment from scratch. g) When working on a Horizontal Alignment ensure that it is set as the Active Alignment. h) When storing curve data in Horizontal Alignments ensure that all the curves are tangent and points are equated at the PC and PT of all curves. i) Make sure to save the ALG file periodically when changes are made. InRoads does not save data on the fly - data is saved in temporary memory. The ALG file must be manually saved in order to retain Design modifications.
3-3
3.2 Horizontal Alignment and COGO Point Names/Feature Styles

Horizontal Alignments and COGO Points must be stored with a DE Prefix and must be stored in a certain Point/Horizontal Alignment Number range along with the appropriate Feature Style. See the following Tables (Tables 3.1, 3.2 and 3.3) for a list of the required naming conventions.
Table 3.1 Standard Design Geometry Object Names Object Type *Design Cogo Points *Design Horizontal Alignment Points **Design Horizontal Alignments ***Design Vertical Alignments DE DE DE DE Prefix Starting Number 10000 (Max. = 99,999) 10000 (Max. = 99,999) 1 1
* All Design Cogo Points and Design Horizontal Alignment Points must be named with a prefix of DE and begin with the number 10000 (e.g., first design point = DE10000). **All Design Horizontal Alignments must be named with a prefix of DE and begin with the number 1, (e.g., DE1). ***It is suggested that the Design Vertical Alignment (which corresponds with the Horizontal Alignment) be named the same as the associated Horizontal Alignment. Table 3.2 Design Point & Alignment Ranges to Use Cogo/Alignment Points Horizontal/Vertical Alignments Range 10,000 to 99,999 Range 1 to no Limitations for Alignments -- but must have the DE Prefix
3-4
Table 3.3 Feature Styles For Geometry Design Points and Alignments DRNG_P_Ditch REQD_P_DWESMT MAIN_P_CONSTCL REQD_P_PESMT Proposed Design Points MAIN_P_EOP REQD_P_REQD Feature Style MAIN_P_EPSHLDR REQD_P_RWRM MAIN_P_SHLDR REQD_P_TESMT MAIN_P_SIDECL STE_P_DETCL Proposed Centerline Alignments Descriptions Feature Style (C/L Roadway Name) Mainline Centerline Sideroad Centerline Detour Centerline Proposed Right of Way Feature Style R/W Monument Reqd. R/W Perm. Const. Esmt. Temp. Const. Esmt. Driveway Esmt. Miscellaneous Feature Style Edge of Pavement Edge of Paved Shoulder Edge of Shoulder Ditch Centerline Other MAIN_P_EOP MAIN_P_EPSHLDR MAIN_P_SHLDR DRNG_P_Ditch (User-Defined) REQD_P_RWRM REQD_P_REQD REQD_P_PESMT REQD_P_TESMT REQD_P_DWESMT** MAIN_P_CONSTCL MAIN_P_SIDECL STE_P_DETCL Ex: C/L HWY 100 Ex: C/L PEQUANOC DR. Ex: C/L US 78 Descriptions
N/A Ex: REQD R/W PAR 33/SV29 Ex: PESMT PAR 44/SV67 Ex: TESMT PAR 23/SV88 Ex: DWESMT PAR 14/SV30 Descriptions
** Note: All other Types of Miscellaneous Easements should use the REQD_P_DWESMT Feature Style.
3-5
3.3 COGO Points and Alignment Points

InRoads has the capability to store both COGO Points (which are northing and easting coordinates) and the ability to store Alignments Points (which are just coordinates with an assigned name not independent Points). It is a required GDOT standard that all Points must be stored as COGO Points. If Alignment Points are stored it is the Designers responsibility to convert these Points to COGO Points. In order to view the correct Point Cells and Symbology COGO Points must be stored instead of Alignment Points in order to generate the correct Symbology, Level, etc. for plans productions. Following is a brief overview of COGO Points versus Alignment Points. ***IMPORTANT DISCUSSION*** It is very important to discuss some differences between InRoads and what you are familiar with in CAiCE. InRoads has different kinds of points. Alignment points and COGO points are two types of points to be aware of. Alignment points are nothing more than names assigned to coordinates in an alignment and do not exist in the COGO points buffer. In order to satisfy GDOT plan presentation requirements, prepare R/W tables and properly add enhanced survey data to your project. -- Surveyors and Designers alike must ensure that all alignments have a corresponding COGO point stored. At some point this may cause you problems as you branch out and experiment with other InRoads commands because not all InRoads commands store COGO points. Some only assign Alignment Point names and must be converted to COGO points. Some dont assign Alignment Point names or store COGO points and must be assigned Alignment Point names and then be converted to COGO points. As such we recommend that you adhere closely to the methods presented in the tutorials concerning centerlines, R/W and property. We bring this up because it is possible to view points at the same time as viewing Alignments without having to populate the Cogo Points in the View Horizontal Annotation command. Viewing points in this manner would not apply the correct attributes to the points -- therefore you must view the Cogo points separately.
3-6
3.4 View Horizontal Annotation Preferences

In order to view Horizontal Alignments to GDOT Standards there are several Preferences which must be set. These Preferences set the viewing of Alignments (Bearing & Distance or No Bearing & Distance) options, the Stationing/Tic Marks and the Curve Data Tables. The following Tables depict the available Preferences, Locations and Descriptions to set the Preferences.
Table 3.4 Preference View Horizontal Annotation

Location: Geometry View Geometry Horizontal Annotation (Preferences Button) Preference Name Description
BEARING & DISTANCE
Loads settings into the View Horizontal Annotation dialog to label the bearing when viewing Roadway alignments with the feature styles MAIN_P_CONSTCL, MAIN_P_SIDECL, and PROP_E_ACL. Although DISTANCE is part of the Preference name the distance is no longer set up to be labeled. Displays NO Bearing & Distance information for all Horizontal Alignments.
3-7
InRoads Design Guidelines Table 3.5 Preference View Stationing
Location: Geometry View Geometry Stationing (Preferences Button) Preference Name Description
ACL Displays the Stationing, Tics and Curve Data at a 50 Scale for PROP_E_ACL Horizontal Alignments. ACL 20 SCALE Displays the Stationing, Tics and Curve Data at a 20 Scale for PROP_E_ACL Horizontal Alignments. CONSTCL Displays the Stationing, Tics and Curve Data at a 50 Scale for MAIN_P_CONSTCL Horizontal Alignments. CONSTCL 20 SCALE Displays the Stationing, Tics and Curve Data at a 20 Scale for MAIN_P_CONSTCL Horizontal Alignments. DETCL Displays the Stationing, Tics and Curve Data at a 50 Scale for STE_P_DETCL Horizontal Alignments. DETCL 20 SCALE Displays the Stationing, Tics and Curve Data at a 20 Scale for STE_P_DETCL Horizontal Alignments. SIDECL Displays the Stationing, Tics and Curve Data at a 50 Scale for MAIN_P_SIDECL Horizontal Alignments. SIDECL 20 SCALE Displays the Stationing, Tics and Curve Data at a 20 Scale for MAIN_P_SIDECL Horizontal Alignments.
Table 3.6 Preference Curve Set Annotation

Location: Geometry View Geometry Curve Set Annotation (Preferences Button) Preference Name Description
ACL CONSTCL DETCL SIDECL
Displays the Curve Data Table for PROP_E_ACL to GDOT Standards. Displays the Curve Data Table for MAIN_P_CONSTCL to GDOT Standards. Displays the Curve Data Table for STE_P_DETCL to GDOT Standards. Displays the Curve Data Table for MAIN_P_SIDECL to GDOT Standards.
3-8
3.5 View Horizontal Annotation Filters

Geometry Selection Filters can be used to select specific Alignments and COGO Points. Once selected and filtered the Alignments and/or COGO Points will view and/or can be used for the generation of specific Style Sheets based on the criteria selected. The following Tables depict the available Filters, Locations and Descriptions to set the Filters.
Table 3.7 Geometry Selection Filter Preferences for Horizontal Alignments and COGO Points
Location: Geometry View Geometry Horizontal Annotation (Filter Button)
Then in the Geometry Selection Filter select the Preferences Button.

Filter Name Description
ACL Cogo Point Feature Styles Prop.dgn Alignments Prop.dgn Points REQD.dgn Alignments REQD.dgn Points Stakeout Survey Data Surface Check MPCKGRD Surface Check MPCKPAV
Loads the Filter to select and view the Feature Style Points for the generation of the ACL Existing Centerline. (Used by the SDE) Loads the Filter to select and view the Feature Style Alignments for the production of the PROP DGN File. (Used by the SDE) Loads the Filter to select and view the Feature Style Points for the production of the PROP DGN File. (Used by the SDE) Loads the Filter to select and view the Feature Style Alignments for the production of the REQD DGN File. Loads the Filter to select and view the Feature Style Points for the production of the REQD DGN File. Loads the Filter to select the Feature Style Points for use in the GDOT Stakeout Report Style Sheet. Loads the Filter to select the TOPO_E_MPCKGRD Feature Style Points for use in the GDOT Surface Check Style Sheet. Loads the Filter to select the TOPO_E_MPCKPAV Feature Style Points for use in the GDOT Surface Check Style Sheet.
3-9
3.6 Reviewing Horizontal Alignments

The Horizontal Alignments description can be reviewed and printed by using the Geometry Review Horizontal command. Following is the process for reviewing/describing Horizontal Alignments: Ensure that the Horizontal Alignment you want to describe is the Active Horizontal Alignment. In InRoads, Select Geometry Review Horizontaland the Review Horizontal Alignment description appears. The user may also print the description by using the Print button on the Review Horizontal Alignment dialog. (See Figure 3-1).
Figure 3-1 Review Horizontal Alignment
3-10
4.
Vertical Alignments
Vertical Alignments
4. Vertical Alignments
This section provides a brief overview of the requirements for generating Existing Ground Profiles (Terrain Profiles) and Design Vertical Alignments. For detailed Vertical Alignment information please refer to Lab 4 in the Design Training Labs. This section covers the following topics:
Vertical Alignment Overview Vertical Alignment Names and Feature Styles Vertical Alignment Preferences Vertical Alignment Annotation Preferences Reviewing Vertical Alignments
4-2
Vertical Alignments
4.1 Vertical Alignment Overview

In InRoads the term Vertical Alignment refers to the Proposed Design Profile. A Vertical Alignment is created for each associated Horizontal Alignment. A proposed Horizontal Alignment and an Existing DTM must be available before creating an Existing Profile and a Proposed Vertical Alignment. In order to generate Vertical Alignments to GDOT standard conventions the following information should be adhered and followed.
a) All Vertical Alignments should be named the same as the associated Horizontal Alignment. Example: Horizontal Alignment = DE7 then the Vertical Alignment should be named DE7. b) A parent/child relationship exists in InRoads between the Horizontal and Vertical Alignments. A Vertical Alignment is a child of the Horizontal Alignment. Multiple Vertical Alignments may exist for a single Horizontal Alignment -therefore it is important to have the correct Vertical Alignment active along with the active Horizontal Alignment before doing any work. c) Before PVIs can be added to the Vertical Alignment, a Profile Window must be created. This is also how the Terrain Profile is created. In InRoads, the Terrain Profile is not stored as a permanent object as in CAiCE. The Terrain Profile is created on the fly from the DTM and must be recreated each time you want to view it. d) The 100h_10v_WORKING, 20h_5v_WORKING and 50h_10v_WORKING Preferences views all the same information as the 100h_10v_ SHEETS, 20h_5v_ SHEETS and 50h_10v_SHEETS Preferences -- yet adds a grid to assist in the Vertical Alignment design. This is for the temporary viewing of the profile during the design of the project. e) Permanent viewing of the Profile and Vertical Alignment for plan generation and plotting is covered in Chapter 6 which depicts the use of the Profile Generator in InRoads. f) Adding PVIs to a Vertical Alignment requires that you have an active Horizontal Alignment, Vertical Alignment and a Profile window in the MicroStation drawing file. g) Make sure to save the ALG file which contains the Vertical Alignment(s) periodically when changes are made. InRoads does not save data on the fly - data is saved in temporary memory. The ALG file must be manually saved in order to retain Design modifications.
4-3
Vertical Alignments
4.2 Vertical Alignment Names and Feature Styles

Vertical Alignments must be stored with a DE Prefix and should be named the same as the associated Horizontal Alignment. Example: Horizontal Alignment = DE7 then the Vertical Alignment should be named DE7. The appropriate Feature Style should be used which corresponds with the Horizontal Alignment Feature Style. (See Tables 4.1 and 4.2).
Table 4.1 Standard Vertical Alignment Names Object Type Vertical Alignment Prefix DE Starting Number 1
Table 4.2 Feature Styles For Geometry Vertical Alignments Proposed Vertical Alignment Descriptions Feature Style (C/L Roadway Name) Mainline Centerline Sideroad Centerline Detour Centerline Miscellaneous Feature Style Edge of Pavement Edge of Paved Shoulder Edge of Shoulder Ditch Centerline Other MAIN_P_EOP MAIN_P_EPSHLDR MAIN_P_SHLDR DRNG_P_Ditch (User-Defined) MAIN_P_CONSTCL MAIN_P_SIDECL STE_P_DETCL Ex: C/L HWY 100 Ex: C/L PEQUANOC DR. Ex: C/L US 78 Descriptions
4-4
Vertical Alignments
4.3 Vertical Alignment Preferences

In order to generate/view Vertical Alignments to GDOT Standards Preferences must be set. These Preferences set the viewing/creation of Vertical Alignments when using the Evaluation Profile Create Profile dialog. (See Table 4.3). Table 4.3 Preference Create Profile
Location: Evaluation Profile Create Profile (Preferences Button) Preference Name Description
100h_10v_SHEETS
100h_10v_WORKING
20h_5v_SHEETS
20h_5v_WORKING
50h_10v_SHEETS
50h_10v_WORKING
Used for Vertical Alignment Sheet generation. This Preference should be used for Plans Production only. Preference loads setting for a 100 Scale Horizontal and 10 Scale Vertical (100h_10v_SHEET) plans production Sheet generation. Used for Vertical Alignment Design and depicts a grid to assist in Profile Design. Preference loads setting for a 100 Scale Horizontal and 10 Scale Vertical (100h_10v_WORKING) working grid. Used for Vertical Alignment Sheet generation. This Preference should be used for Plans Production only. Preference loads setting for a 20 Scale Horizontal and 5 Scale Vertical (20h_5v_SHEET) plans production Sheet generation. Used for Vertical Alignment Design and depicts a grid to assist in Profile Design. Preference loads setting for a 20 Scale Horizontal and 5 Scale Vertical (20h_5v_WORKING) working grid. Used for Vertical Alignment Sheet generation. This Preference should be used for Plans Production only. Preference loads setting for a 50 Scale Horizontal and 10 Scale Vertical (50h_10v_SHEET) plans production Sheet generation. Used for Vertical Alignment Design and depicts a grid to assist in Profile Design. Preference loads setting for a 50 Scale Horizontal and 10 Scale Vertical (50h_10v_WORKING) working grid.
4-5
Vertical Alignments
4.4 Vertical Alignment Annotation Preferences

In order to annotate Vertical Alignments to GDOT Standards Two different sets of Preferences must be set. One set of Preferences annotates the Terrain Profile and Vertical Alignment Elevations (Existing and Proposed Profiles). The other set of Preferences annotates the Vertical Alignment Curve Data. (See Tables 4.4 and 4.5).
Table 4.4 Preference Annotate Profile (Existing and Proposed Elevations)

Location: Evaluation Profile Annotate Profile (Preferences Button) Preference Name Description
100h_10v_Profile 20h_10v_Profile 50h_10v_Profile
Used for Annotation of Existing and Proposed Profile Elevations for a 100 Scale Horizontal and 10 Scale Vertical Profile (100h_10v_Profile). Used for Annotation of Existing and Proposed Profile Elevations for a 20 Scale Horizontal and 10 Scale Vertical Profile (20h_10v_Profile). Used for Annotation of Existing and Proposed Profile Elevations for a 50 Scale Horizontal and 10 Scale Vertical Profile (50h_10v_Profile).
Table 4.5 Preference Annotate Profile (Proposed Curve Data)

Location: Geometry View Geometry Vertical Annotation (Preferences Button) Preference Name Description
GDOT Profiles
Used for Annotation of Proposed Vertical Curve Data for all Scales.
4-6
Vertical Alignments
4.5 Reviewing Vertical Alignments

The Vertical Alignments description can be reviewed and printed by using the Geometry Review Vertical command. Following is the process for reviewing/describing Vertical Alignments: Ensure that the Vertical Alignment you want to describe is the Active Vertical Alignment. In InRoads, Select Geometry Review Verticaland the Review Vertical Alignment description appears. The user may also print the description by using the Print button on the Review Vertical Alignment dialog. (See Figure 4-1).
Figure 4-1 Review Vertical Alignment
4-7
5.
Import Graphics and Place Curve Tables
5. Import Graphics and Place Curve Tables

This section provides a brief overview of the process to Import Graphics from MicroStation and the process to Place Curve Table Information in MicroStation. For detailed Import Graphics and Place Curve Table information please refer to Lab 5 in the Design Training Labs. This section covers the following topics:
Import Graphics Overview Import Graphics - Names/Feature Styles Curve Table Overview Curve Table Preferences
5-2
5.1 Import Graphics Overview

The following section depicts an overview of the Import Graphics process and Naming/Feature Style conventions utilized to add Graphics from MicroStation into InRoads. There may be situations where Geometry graphics will need to be imported from a MicroStation DGN file into the InRoads ALG file. Examples are edge of pavement alignments or centerline alignments. In order to generate/ import Graphics to GDOT standard conventions the following information should be adhered and followed.
a) All Centerline Graphics should be imported and assigned a Feature Style of MAIN_P_CONSTCL, MAIN_P_SIDECL or STE_P_DETCL. b) Any additional Horizontal Alignments such as Ditch Centerlines, Edge of Pavements, etc. must be assigned the appropriate Feature Style for the Symbology and Levels to view correctly in MicroStation. c) All imported Horizontal Alignment Names and Alignment Point Names must begin with a DE Prefix. All Points must begin numbering at DE10000. Horizontal Alignment numbering may begin at DE1. d) All Horizontal Alignment Points must be converted to COGO Points. e) When importing Graphics using the Import Geometry dialog, Join Elements and All Selected Elements Added to Single Alignment should be checked. f) Names must be assigned to the Coordinates in the Alignment to create Alignment Points. g) All Alignment Points must then be converted to COGO Points. h) Make sure to save the ALG file periodically when changes are made. InRoads does not save data on the fly - data is saved in temporary memory. The ALG file must be manually saved in order to retain Design modifications.
5-3
5.2 Import Graphics - Names/Feature Styles

When importing graphics from MicroStation, all Alignments must be stored with a DE Prefix and Numbering may begin at DE1 or the next available number. The appropriate Feature Style should be used which corresponds with the Horizontal Alignment Feature Style. (See Tables 5.1 and 5.2). Table 5.1 Import Graphics - Standard Design Geometry Object Names Object Type Design Cogo Points Design Horizontal Alignment Points Design Horizontal Alignments Design Vertical Alignments DE DE DE DE Prefix Starting Number 10000 (Max. = 99,999) 10000 (Max. = 99,999) 1 or next available number 1 or next available number
Table 5.2 Import Graphics - Feature Styles For Geometry Horizontal Alignments Descriptions Proposed Vertical Alignment Feature Style (C/L Roadway Name) Mainline Centerline Sideroad Centerline Detour Centerline Miscellaneous Feature Style Edge of Pavement Edge of Paved Shoulder Edge of Shoulder Ditch Centerline Other MAIN_P_EOP MAIN_P_EPSHLDR MAIN_P_SHLDR DRNG_P_Ditch (User-Defined) MAIN_P_CONSTCL MAIN_P_SIDECL STE_P_DETCL Ex: C/L HWY 100 Ex: C/L PEQUANOC DR. Ex: C/L US 78 Descriptions
5-4
5.3 Curve Table Overview

In order to correspond with the GDOT Plan Presentation Guide, Curve Tables are required for each Horizontal Alignment. The Curve Tables depict the Curve Data for each curve of the Alignment(s). In order to generate/ import Graphics to GDOT standard conventions the following information should be adhered and followed. Following is the Curve information which is required in the Curve Data Tables:
a) Curve Data Table Required Information o CURVE Number o P.I. Station o P.I. Coordinates o or DELTA (Deflection angle) o D (Degree of Curve) o T (Tangent Length) o L (Length of Curve) o R (Radius) o E (External distance) o e (Superelevation in percent)
b) The Symbology and Level of the Curve Tables are based on the Feature Style of the Horizontal Alignment. c) If there is more than one curve in an Alignment the Curve Table assigns each curve a name of Curve 1, Curve 2, etc. When viewing more than one Alignment the second alignment will also name the curve in it Curve 1, Curve 2, etc. It is the Designers responsibility to manually modify each curve table in MicroStation to assign the Curve another Number. For Example: If Alignment DE7 contains three curves (and associated curve tables) all of the curve tables will be given the curve number of Curve 1, Curve 2 and Curve 3. When viewing Alignment DE31, these Curves will also be named Curve 1, Curve 2 and Curve 3. The Designer will need to edit the Curve Table number in MicroStation in order to rename each successive curve (per alignment) as Curve 1, Curve 2, Curve 3, etc. so that there will not be duplicate Curve Table Numbers/Names on a plan sheet. d) The Preferences for the Curve Tables are the Feature Styles of (ACL) PROP_E_ACL, (CONSTCL) MAIN_P_CONSTCL, (DETCL) STE_P_DETCL and (SIDECL) MAIN_P_SIDECL.
5-5
5.4 Curve Table Preferences

In order to view Horizontal Curves to GDOT Standards Preferences must be set. These Preferences set the viewing of the Curve Data Table based on the Feature Style of the Alignments and Curve Data. The following Table depicts the available Preferences for Curve Data Tables. (See Table 5.3 below).
Table 5.3 Preference Curve Set Annotation

Location: Geometry View Geometry Curve Set Annotation (Preferences Button) Preference Name Description
ACL CONSTCL DETCL SIDECEL
Loads the Curve Table Preference for the Feature Style of PROP_E_ACL. Loads the Curve Table Preference for the Feature Style of MAIN_P_CONSTCL. Loads the Curve Table Preference for the Feature Style of STE_P_DETCL. Loads the Curve Table Preference for the Feature Style of MAIN_P_SIDECL.
5-6
6.
Profile Sheets
Profile Sheets
6. Profile Sheets
This section provides a brief overview of the requirements for generating Profile Sheets. For detailed Profile Sheet information please refer to Lab 6 in the Design Training Labs. This section covers the following topics:
Profile Sheets Overview Plan and Profile Generator Information Vertical Alignment Preferences Vertical Alignment Annotation Preferences
6-2
Profile Sheets
6.1 Profile Sheets Overview

The following section depicts an overview of the methods used to generate Profile Sheets in InRoads in order to correspond to the Plan Presentation Guide and the Electronic Data Guidelines. The Plan and Profile Generator is used in InRoads to produce cut Profile Sheets. In order to generate Profile Sheets to GDOT standard conventions the following information should be adhered and followed.
a) An Existing Terrain DTM must exist and a Proposed Vertical Alignment must exist in the ALG file in order to use the Plan and Profile Generator to create Profile Sheets. b) The Plan and Profile Generator depicts the Terrain Profile, Vertical Alignment, Annotation and Profile Grid and generates cut Profile Sheets based on the selection of the applicable Scale Preference. c) The Create Profile Preferences of 100h_10v_ SHEETS, 20h_5v_ SHEETS and 50h_10v_SHEETS are used for the generation of Profile Sheets. d) The Plan and Profile Generator Preferences for creation of Profile Sheets consists of 20 and 50 Scale Double Profile and Single Profile Options. e) The Plan and Profile Generator Preferences set the options in the dialog box for creation of the Profile Sheets but there are certain situations where the Designer will need to change the settings in the dialog box to ensure that the Profile data and annotation fits on the Profile Sheets. Not all situations for set-up of Profile Sheets can be automated without some modifications to spacing and Profile elevation shifts. The Plan and Profile Generator references the Create Profile dialog to draw the Profile in MicroStation. The user may also need to go to the Preferences on the Create Profile dialog and modify the window clearance in order for the Plan and Profile Generator to center the profile on the Profile Sheet. f) The Plan and Profile Generator utilizes three DGN files to create the cut Profile Sheets. The DGNs are the Master DGN File, the Host File and the Seed Host File.
6-3
Profile Sheets
6.2 Plan and Profile Generator Information

The generation of Profile Sheets is accomplished by using the Plan and Profile Generator command in InRoads. This command uses DGN and Host files to generate the cut Profile Sheets. In order to understand the process -- the following information regarding the creation of Profile Sheets is discussed. Master DGN File - a new MicroStation DGN file that is created which will contain the actual Terrain Profile, Vertical Alignment and Annotation. o The recommended File Naming Structure is PI#PR##.dgn. o (PI# = the Project Number, PR## = the Profile Name). Host File a MicroStation DGN file which is used to create the Cut Profile Sheet(s). This file contains the grid cell and the clipping elements. It is the actual Cut Profile Sheet(s) which uses the Master DGN file as a Reference File. o The recommended File Naming Structure is PI#PR##S1.dgn. o (PI# = the Project Number, PR## = the Profile Name, S= Sheet). The S stands for Sheet and will be incremented 1, 2, 3, etc. automatically by the Plan and Profile Generator command. Seed Host File a MicroStation DGN file which is used as the seed file to create the Host File. This is the GDOT_V8_3D.dgn file which contains the standard GDOT DGN Library, cell libraries, etc. o (Note: In this table the Seed Host File is named GDOT 3D Working File.dgn).
Table 6.1 Plan and Profile Generator DGN Files - Standard DGN File Names DGN Type
Master DGN File Host File Seed Host File
DGN File Name PI#PR##.dgn PI#PR##S1.dgn GDOT_V8_3D.dgn
Example PI# = the Project Number, PR## = the Profile Name PI# = the Project Number, PR## = the Profile Name, S= Sheet). GDOT 3D Working File.dgn.
RECAP: o PI#PR##.dgn = DGN File which contains the Terrain Profile, Vertical Alignment and Annotation o PI#PR##S1.dgn, PI#PR##S2.dgn, PI#PR##S3.dgn = DGN File(s) which are the Cut Profile Sheets. o GDOT 3D Working File.dgn = DGN File which is the standard GDOT Seed File. 6-4
Profile Sheets
6.3 Vertical Alignment Preferences

In order to generate/view Vertical Alignments to GDOT Standards Preferences must be set. These Preferences set the viewing/creation of Vertical Alignments when using the Evaluation Profile Create Profile dialog. (See Table 6.2). Table 6.2 Preference Create Profile
Location: Evaluation Profile Create Profile (Preferences Button) Preference Name Description
100h_10v_SHEETS
100h_10v_WORKING
20h_5v_SHEETS
20h_5v_WORKING
50h_10v_SHEETS
50h_10v_WORKING
Used for Vertical Alignment Sheet generation. This Preference should be used for Plans Production only. Preference loads setting for a 100 Scale Horizontal and 10 Scale Vertical (100h_10v_SHEET) plans production Sheet generation. Used for Vertical Alignment Design and depicts a grid to assist in Profile Design. Preference loads setting for a 100 Scale Horizontal and 10 Scale Vertical (100h_10v_WORKING) working grid. Used for Vertical Alignment Sheet generation. This Preference should be used for Plans Production only. Preference loads setting for a 20 Scale Horizontal and 5 Scale Vertical (20h_5v_SHEET) plans production Sheet generation. Used for Vertical Alignment Design and depicts a grid to assist in Profile Design. Preference loads setting for a 20 Scale Horizontal and 5 Scale Vertical (20h_5v_WORKING) working grid. Used for Vertical Alignment Sheet generation. This Preference should be used for Plans Production only. Preference loads setting for a 50 Scale Horizontal and 10 Scale Vertical (50h_10v_SHEET) plans production Sheet generation. Used for Vertical Alignment Design and depicts a grid to assist in Profile Design. Preference loads setting for a 50 Scale Horizontal and 10 Scale Vertical (50h_10v_WORKING) working grid.
6-5
Profile Sheets
6.4 Vertical Alignment Annotation Preferences

In order to annotate Vertical Alignments to GDOT Standards Two different sets of Preferences must be set. One set of Preferences annotates the Terrain Profile and Vertical Alignment Elevations (Existing and Proposed Profiles). The other set of Preferences annotates the Vertical Alignment Curve Data. (See Tables 6.3 and 6.4).
Table 6.3 Preference Annotate Profile (Existing and Proposed Elevations)

Location: Evaluation Profile Annotate Profile (Preferences Button) Preference Name Description
100h_10v_Profile 20h_10v_Profile 50h_10v_Profile
Used for Annotation of Existing and Proposed Profile Elevations for a 100 Scale Horizontal and 10 Scale Vertical Profile (100h_10v_Profile). Used for Annotation of Existing and Proposed Profile Elevations for a 20 Scale Horizontal and 10 Scale Vertical Profile (20h_10v_Profile). Used for Annotation of Existing and Proposed Profile Elevations for a 50 Scale Horizontal and 10 Scale Vertical Profile (50h_10v_Profile).
Table 6.4 Preference Annotate Profile (Proposed Curve Data)

Location: Geometry View Geometry Vertical Annotation (Preferences Button) Preference Name Description
GDOT Profiles
Used for Annotation of Proposed Vertical Curve Data for all Scales.
6-6
7.
Component and Template Creation
7. Component and Template Creation

This section provides a brief overview of the requirements for creating Components and Templates. For detailed Component and Template information please refer to Lab 7 in the Design Training Labs. This section covers the following topics:
Component and Template Creation Overview ITL Template Library and Naming Conventions GDOT Standard Components GDOT Standard Point Names GDOT Standard Feature Styles GDOT Component Help Files
7-2
7.1 Component and Template Creation Overview

The following section depicts an overview of the components and templates used to generate cross sections in InRoads. In order to create and utilize GDOT Components and Templates to GDOT standard conventions the following information should be adhered and followed.
a) The InRoads Template Library (.ITL) is where the Designer creates all the Components necessary to generate a complete Template such as shoulders, travel lanes, barriers, medians and end conditions. b) The InRoads Template Library is included in the InRoadsALLV8i.exe file download. The Designer will copy the Template Library (GDOT_Standard V8i.itl) to the Project Directory and rename the file to PI#.itl (Ex. 123456.itl). c) Once the Designer modifies the PI#.itl file and creates the components and templates this ITL file is always submitted as a deliverable with the project so that anyone who works on the project will have the Template Library that contains the associated project components and templates. d) There are five types of Components which can be created: Simple, Constrained, Unconstrained, Null Point and End Condition. e) The GDOT Standard ITL file contains the following Component Categories: Barriers, Curb and Gutter, End Conditions, Medians, Shoulders and Travel Lanes. f) The Designer is provided a Point Name List and Feature Styles to utilize in the development and/or modifications to the Components. It is important to use the standard GDOT Feature Styles so that Cross Section Annotation will generate correctly.
7-3
7.2 ITL Template Library and Naming Conventions

The InRoads Template Library is included in the InRoadsALLV8i.exe file download. The Designer will copy the Template Library (GDOT_Standard V8i.itl) to the Project Directory and rename the file to the following: (See Table 7.1). Table 7.1 ITL Naming Convention GDOT Standard ITL
GDOT_Standard V8i.itl
Rename To PI#.itl 123456.itl
Example
The PI#.itl file will be project specific and will be submitted to the Earthwork Coordinator when the project is let to construction. It is very important for anyone who works on (or inherits the project) to receive the associated ITL file so that they will have access to the same Components and Point Names used to create the original Templates. The Designer will need to add additional Components, Templates and Point Names to the ITL file during the course of Project design to cover design situations that are not represented in the Standard GDOT Template Library. It is very important that the Designer use the same Feature Styles as those provided in the ITL. Component and Point Names may need to be added but always use one of the provided Feature Styles contained in the XIN file. Following is a list of the five types of components that are provided in InRoads: 1. Simple: A Simple Component is a simple prefabricated closed rectangular shape. This is useful for the quick setup of rectangular shapes like a travel lane. 2. Constrained: A Constrained Component is placed one point at a time and can be either a closed or open shape. It is useful for making objects of differing shapes such as curb and gutter. The points in Constrained Components can be set to behave in a particular manner by selection of the differing constraint options. The default constraint is set to be Horizontal and Vertical to the previous point placed. 3. Unconstrained: An Unconstrained Component is placed one point at a time, the same as a Constrained Component, but is placed with no constraint defaults applied. The constraints of points composing both Constrained and Unconstrained Components can be edited after placement to apply whatever constraints the user desires. 4. Null Point: Null Point Components are placed unconstrained to other components and are typically edited to control the behavior of other points. Null Points can be edited to behave as Display Switches in order to display different components under differing conditions such as Type S Barrier switching between the S1, S2 or S3 variations. 5. End Condition: End Condition Components are used to tie to a surface - typically the existing surface. Cut/Fill slopes are the typical type components created with End Condition Components. End Condition Components can be designed with ditches incorporated and that widen for guardrail when certain conditions are met. 7-4
7.3 GDOT Standard Components

GDOT supplies a standard Template Library (ITL) named GDOT_Standard V8i.itl. This Library contains the Component Categories: Barriers, Curb and Gutter, End Conditions, Medians, Shoulders and Travel Lanes. The following Table lists the Categories and individual components provided in the GDOT_Standard V8i.itl file. (See Table 7.2). . Table 7.2 GDOT Standard Components
Location: GDOT_Standard V8i.itl Category Component
Barriers
TP 7 WS, CS & RS Barrier TP S1, S2 & S3 Median Barrier TP T Guardrail TP W Guardrail Type 2S Type 6S 5 Sidewalk 9032B TP 2 CURB & GUTTER 9032B TP 2 DOWELED INTEGRAL CURB 9032B TP 2 HEADER CURB 9032B TP 7 CURB & GUTTER 9032B TP 7 DOWELED INTEGRAL CURB 9032B TP 7 HEADER CURB GACUTFIL 9032B Concrete Median 4 thk MBCL MedianFBD-Low
Curb and Gutter
End Conditions Medians
Shoulders
Inside Shoulder Outside Shoulder Full Depth Outside Shoulder Partial Depth Paving Under Guardrail Asphalt o Asphalt Lane PGL to LANE Concrete o Concrete Lane Inside o Concrete Lane Outside Edge
Travel Lanes
7-5
7.4 GDOT Standard Point Names

The GDOT_Standard V8i.itl Library contains the Component Categories: Barriers, Curb and Gutter, End Conditions, Medians, Shoulders and Travel Lanes. Each of the Components listed in the previous Table 7.2 contain individual Component Points. The following Table lists the Component Points which compose each of these Components. (See Table 7.3). . Table 7.3 GDOT Component Points
(Category: Barriers) Point Name GR GRL IMBB IMBT LIPS LMBF LMBFB LMBFT LMBGSB LMBGST LMBT LMBX OMBB OMBT OPS RIPS RMBF RMBFB RMBFT RMBGSB RMBGST RMBT RMBX S1 S2 SB6B SB6T SBB Point Name Description Guardrail Guardrail Location Insertion Point Inside Median Barrier Bottom Inside Median Barrier Top Left Inside Paved Shoulder Left Median Barrier Face Left Median Barrier Face Bottom Left Median Barrier Face Top Left Median Barrier Glare Screen Bottom Left Median Barrier Glare Screen Top Left Median Barrier Top Left Median Barrier "X" Point Outside Median Barrier Bottom Outside Median Barrier Top Outside Paved Shoulder Right Inside Paved Shoulder Right Median Barrier Face Right Median Barrier Face Bottom Right Median Barrier Face Top Right Median Barrier Glare Screen Bottom Right Median Barrier Glare Screen Top Right Median Barrier Top Right Median Barrier "X" Point Type S1 Median Barrier Type S2 Median Barrier Side Barrier Type 6 Bottom Side Barrier Type 6 Top Side Barrier Back
7-6

SBBB SBBLB SBBLT SBBRB SBBRT SBFB SBFT SBKLB SBKLT SBKRB SBKRT SBT SBX Side Barrier Back Bottom Side Barrier Base Left Bottom Side Barrier Base Left Top Side Barrier Base Right Bottom Side Barrier Base Right Top Side Barrier Face Bottom Side Barrier Face Top Side Barrier Key Left Bottom Side Barrier Key Left Top Side Barrier Key Right Bottom Side Barrier Key Right Top Side Barrier Top Side Barrier "X" Point
(Category: Curb and Gutter) Point Name BSW BSWB FSW FSWB OBC OBCB OCFC OEP OFC OFCB OGFL Point Name Description Back of Sidewalk Back of Sidewalk Bottom Front of Sidewalk Front of Sidewalk Bottom Outside Back of Curb Outside Back of Curb Bottom Outside Chamfer Face of Curb Outside Edge of Pavement Outside Face of Curb Outside Face of Curb Bottom Outside Gutter Flow Line
(Category: End Conditions) Point Name CUT FILL GRL IDT ODT OPS OS Point Name Description Limit of Cut Limit of Fill Guardrail Location Insertion Point Inside Ditch Bottom Outside Ditch Bottom Outside Paved Shoulder Outside Shoulder
7-7

(Category: Medians) Point Name DTCTR LMDBS LMDFS LMEB LMET MBCL MBCLB RMDBS RMDFS RMEB RMET Point Name Description Ditch Center Left Median Ditch Back Slope Left Median Ditch Fore Slope Left Median Edge Bottom Left Median Edge Top Median Barrier Center Line Median Barrier Center Line Bottom Right Median Ditch Back Slope Right Median Ditch Fore Slope Right Median Edge Bottom Right Median Edge Top
(Category: Shoulders) Point Name EIS EISB EISB EISBB EISGAB EISIB EOS IEP IEPB IEPBB IEPGAB IEPIB IS OEP OEPB OEPBB OEPGAB OEPIB OPS OPSB OPSBB OPSGAB Point Name Description Edge of Inside Shoulder Edge of Inside Shoulder Bottom Edge of Inside Shoulder Bottom Edge of Inside Shoulder Base Bottom Edge of Inside Shoulder Graded Aggregate Base (bottom) Edge of Inside Shoulder Intermediate Bottom Edge of Outside Shoulder Inside Edge of Pavement Inside Edge of Pavement Bottom Inside Edge of Pavement Base Bottom Inside Edge of Pavement Graded Aggregate Base (bottom) Inside Edge of Pavement Intermediate Bottom Inside Shoulder Outside Edge of Pavement Outside Edge of Pavement Bottom Outside Edge of Pavement Base Bottom Outside Edge of Pavement Graded Aggregate Base (bottom) Outside Edge of Pavement Intermediate Bottom Outside Paved Shoulder Outside Paved Shoulder Bottom Outside Paved Shoulder Base Bottom Outside Paved Shoulder Graded Aggregate Base (bottom)
7-8

OPSIB OS OSB OSIB Outside Paved Shoulder Intermediate Bottom Outside Shoulder Outside Shoulder Bottom Outside Shoulder Intermediate Bottom
(Category: Travel Lanes) Point Name IEP IEPB IEPGAB IEPIB LANE LANEB LANEBB LANEGAB LANEIB OEP OEPB OEPGAB OEPI OEPIB PGL PGLB PGLBB PGLGAB PGLIB Point Name Description Inside Edge of Pavement Inside Edge of Pavement Bottom Inside Edge of Pavement Graded Aggregate Base (bottom) Inside Edge of Pavement Intermediate Bottom Lane Lane Bottom Lane Base Bottom Lane Graded Aggregate Base (bottom) Lane Intermediate Bottom Outside Edge of Pavement Outside Edge of Pavement Bottom Outside Edge of Pavement Graded Aggregate Base (bottom) Outside Edge of Pavement Intermediate Outside Edge of Pavement Intermediate Bottom Profile Grade Line Profile Grade Line Bottom Profile Grade Line Base Bottom Profile Grade Line Aggregate Base (bottom) Profile Grade Line Intermediate Bottom
7-9
7.5 GDOT Standard Feature Styles

The GDOT_Standard V8i.itl Library references the GDOT XIN file in order to apply the Feature Styles for the Components and the Component Points. It is very important that the Designer use the same Feature Styles as that provided in the ITL. Component and Point Names may need to be added but always use the provided Feature Styles contained in the XIN file in order to annotate cross-sections to GDOT Standards. The following Table lists the Feature Styles which compose each of these Components and Component Points. (See Table 7.4).
Table 7.4 GDOT Feature Styles for Components and Component Points
Feature Style Name DRNG_P_Ditch LIMT_P_CUT LIMT_P_CUT_Const-Limit LIMT_P_FILL LIMT_P_FILL_Const-Limit MAIN_P_Barrier-Median-Side MAIN_P_Barrier-Noise-Wall MAIN_P_Barrier-Retain-Wall MAIN_P_Barrier_PAY_4940_TP20 MAIN_P_Barrier_PAY_4940_TP21 MAIN_P_Barrier_PAY_4940_TP22 MAIN_P_Barrier_PAY_TP_S1 MAIN_P_Barrier_PAY_TP_S2 MAIN_P_Barrier_PAY_TP_S3 MAIN_P_Barrier_PAY_TP_S3A MAIN_P_Barrier_PAY_TP_S3B MAIN_P_Barrier_Side_PAY_TP_2-S MAIN_P_Barrier_Side_PAY_TP_2-SA MAIN_P_Barrier_Side_PAY_TP_2-SB MAIN_P_Barrier_Side_PAY_TP_2-SC MAIN_P_Barrier_Side_PAY_TP_6-S MAIN_P_Barrier_Side_PAY_TP_6-SA MAIN_P_Barrier_Side_PAY_TP_6-SB MAIN_P_Barrier_Side_PAY_TP_6-SC MAIN_P_Barrier_Side_PAY_TP_7-CS MAIN_P_Barrier_Side_PAY_TP_7-WS
Feature Style Description Ditch - Drainage Cut Limits (Assign to End Condition Components) Cut Limits (Assign to LAST Point in the End Condition) Fill Limits (Assign to End Condition Components) Fill Limits (Assign to LAST Point in the End Condition) Proposed median or side barrier Proposed noise barrier wall Propose retaining wall 4940 TP20 CONCRETE BARRIER 4940TP21 CONCRETE BARRIER 4940 TP22 CONCRETE BARRIER TP S1 SPECIAL DESIGN CONCRETE BARRIER TP S2 SPECIAL DESIGN CONCRETE BARRIER TP S3 SPECIAL DESIGN CONCRETE BARRIER TP S3A SPECIAL DESIGN CONCRETE BARRIER TP S3B SPECIAL DESIGN CONCRETE BARRIER TP 2-S SIDE CONCRETE BARRIER TP 2-SA SIDE CONCRETE BARRIER TP 2-SB SIDE CONCRETE BARRIER TP 2-SC SIDE CONCRETE BARRIER TP 6-S SIDE CONCRETE BARRIER TP 6-SA SIDE CONCRETE BARRIER TP 6-SB SIDE CONCRETE BARRIER TP 6-SC SIDE CONCRETE BARRIER TP 7-CS or 7-RS SIDE CONCRETE BARRIER TP 7-WS SIDE CONCRETE BARRIER
7-10

MAIN_P_CONSTCL MAIN_P_CROWN MAIN_P_Curb MAIN_P_Curb_PAY_9032B Dowel TP2 MAIN_P_Curb_PAY_9032B Dowel TP3 MAIN_P_Curb_PAY_9032B Dowel TP7 MAIN_P_Curb_PAY_9032B HeaderTP1 MAIN_P_Curb_PAY_9032B HeaderTP2 MAIN_P_Curb_PAY_9032B HeaderTP3 MAIN_P_Curb_PAY_9032B HeaderTP4 MAIN_P_Curb_PAY_9032B HeaderTP6 MAIN_P_Curb_PAY_9032B HeaderTP7 MAIN_P_Curb_PAY_9032B REdge 6" MAIN_P_Curb_PAY_9032B REdge 8" MAIN_P_Curb_PAY_9032B TP1 6" MAIN_P_Curb_PAY_9032B TP1 8" MAIN_P_Curb_PAY_9032B TP2 6" MAIN_P_Curb_PAY_9032B TP2 8" MAIN_P_Curb_PAY_9032B TP3 6" MAIN_P_Curb_PAY_9032B TP3 8" MAIN_P_Curb_PAY_9032B TP4 6" MAIN_P_Curb_PAY_9032B TP4 8" MAIN_P_Curb_PAY_9032B TP7 6" MAIN_P_Curb_PAY_9032B TP7 8" MAIN_P_Driveway MAIN_P_EEOP MAIN_P_EOP MAIN_P_EPSHLDR MAIN_P_Guardrail MAIN_P_Lane MAIN_P_Median_PAY_9032B_4"THK Main_P_Misc-Const-Feat MAIN_P_SHLDR MAIN_P_Sidewalk MAIN_P_Slope-break REQD_P_DWESMT REQD_REQD REQD_P_RWRM REQD_P_TESMT

Proposed Construction centerline Crown Point Proposed Curb 9032B TP2 CONC DOWELED INTEGRAL CURBS 6" THK 9032B TP3 CONC DOWELED INTEGRAL CURBS 8" THK 9032B TP7 CONC DOWELED INTEGRAL CURBS 6" THK 9032B TP1 4"HEADER CURB 9032B TP2 6"HEADER CURB 9032B TP3 8"HEADER CURB 9032B TP4 10"HEADER CURB 9032B TP6 6"HEADER CURB 9032B TP6 7"HEADER CURB 9032B 6" RAISED EDGE WITH CONCRETE GUTTER 9032B 8" RAISED EDGE WITH CONCRETE GUTTER 9032B TP1 30" CURB & GUTTER 6"THK 9032B TP1 30" CURB & GUTTER 8"THK 9032B TP2 30" CURB & GUTTER 6"THK 9032B TP2 30" CURB & GUTTER 8"THK 9032B TP3 30" CURB & GUTTER 6"THK 9032B TP3 30" CURB & GUTTER 8"THK 9032B TP4 30" CURB & GUTTER 6"THK 9032B TP4 30" CURB & GUTTER 8"THK 9032B TP7 CURB & GUTTER 6"THK 9032B TP7 CURB & GUTTER 8"THK Driveway Exist Pavement Edge Proposed Road Edge of Pavement Proposed edge of paved shoulder Proposed guardrail Lane Lines 9032b CONCRETE MEDIAN 4"THK PAY ITEM Proposed misc. construction feature Proposed Shoulder lines Proposed Sidewalk Slope break point Required Driveway Easement Required Right of Way Required Right of Way Marker Required Temporary Easement
7-11
7.6 GDOT Component Help Files

Help Files have been created for each of the GDOT Components. These Help Files are included in the InRoadsALLV8i.exe executable. When InRoadsALLV8i.exe is downloaded and installed Help Files are downloaded to the following location: C:\InRoads Data\Component Documentation GDOT Component Description Help Documentation These Help Files provide detailed information regarding the composition of the Component, the Default Parameters, Graphic representation and the Component Points/Feature Styles which are utilized in the Component. When inserting the Components in the Create Template dialog, the user may access the Component Help Files to assist in the design of the templates. Following is information on how to access the Component Help Files from the Create Template dialog. In the Create Template dialog - Right mouse click over the component GACUTFIL and select Template Documentation Link as shown here.
In the Template Documentation Link dialog - click the Locate button.

Locate Button
Navigate to C:\InRoads Data\Component Documentation Select a PDF Help File and click Open. In the Template Documentation Link dialog - click Open Link. Close the Component Description PDF File when finished. Click Close to close the Template Documentation Link dialog.
NOTE: Once a Component Description is opened from the Template Documentation Link dialog its path is permanently stored in memory. 7-12
8.
Roadway Designer
7-1
Roadway Designer
8. Roadway Designer
This section provides a brief overview of the requirements for using the Roadway Designer to create an IRD (Roadway Design File), add Corridors, add Superelevation and create Final Design Surfaces in InRoads. For detailed Roadway Designer information please refer to Lab 8 in the Design Training Labs. This section covers the following topics:
Roadway Designer Overview Roadway Designer Workflow IRD (Roadway Design) Naming Conventions Corridor Naming Conventions Superelevation Process Workflow Design Surface Naming Conventions/Preference Bogus Surface Naming Conventions for Target Aliasing
8-2
Roadway Designer
8.1 Roadway Designer Overview

The following section depicts an overview of the Roadway Designer processes used to generate cross sections in InRoads. In order to create an IRD, corridors and Final Design Surfaces to GDOT standard conventions the following information should be adhered and followed. a) In order to generate cross sections an IRD file, a Corridor and a Finished Design Surface must be created. The cross sections are then cut from the Finished Design Surface. b) The InRoads Roadway Design file (.IRD) should be named PI#.ird (Ex. 123456.ird). If there is a need for more IRD files (such as for alternate design situations) - the IRD file should be named PI#A.ird, PI#B.ird, etc. (Ex. 123456A.ird, 123456B.ird). c) The Corridor will be named the Roadway Name or the Alignment Name. (Ex. SR100 SPUR or DE31) based on the Designers preference. d) Superelevation in InRoads is created by adding Vertical Point Controls. This is accomplished by utilizing the Superelevation Wizard. e) Superelevation tables (.SUP) are utilized to calculate the Super required and the % Total on Tangent utilized is 2/3 (67%). f) The Superelevation tables are located in the following path: C:\Program Files\Bentley\InRoads Group V8.11\data\AASHTO 2004\imperial g) The Finished Design Surface will be named the PI#_Corridor Name (Ex. 123456_SR100 SPUR or 123456_DE31). h) The Preference used for the Finished Design Surface will be FINISH. i) If an end condition fails to solve because there is no Existing Ground Surface (an obscured area) to intersect the Designer is instructed to contact the Office of Design Policy and Support/Location Bureau to request additional DTM Coverage in that area. j) In order to place a temporary Template so that the Station at the obscured area can close Target Aliasing is utilized. Target Aliasing consists of creating a Bogus Surface in order to cut a Cross Section to form a closed area. k) The Naming Convention for the Bogus Surface used in Target Aliasing is PI#_Bogus1 (Ex. 123456_Bogus1).
8-3
Roadway Designer
8.2 Roadway Designer Workflow

The Roadway Designer is located under the InRoads Modeler menu and is where Roadway Design Files (.IRDs), Corridors, Template Drops, Point Controls, End Condition Exceptions, Superelevation and Final Surfaces are performed, assigned, created, etc. Following is the workflow and terminology of the Roadway Designer: Step 1. Create a Roadway Design File The Roadway Design File (.IRD) is where Corridors are created, Templates are added to Corridors, Point Controls and End Condition Exceptions are added and Design Surfaces are created. Step 2. Create a Corridor A Corridor is a strip of land defined by a horizontal and vertical alignment or alignments. It can be considered the projects footprint. Cross section design is performed in the Corridor and the Final Surface is created from the corridor. Step 3. Add Template Drops Template Drops are used to add Templates from the .ITL (InRoads Template Library) to specified station ranges in the Corridor. Step 4. Add Point Controls Point Controls are used in cross section design to override a points normal constraint. Example uses of Point Controls in a cross section design would be to have the point representing the outside edge of a travel lane, follow a horizontal alignment to widen for an auxiliary lane (such as a turn lane) or having a point follow a different vertical alignment for split grades. Step 5. Add End Condition Exceptions End Condition Exceptions are applied to End Conditions during cross section design when the normal behavior of an End Condition is not sufficient for actual conditions and it is not desirable to create and place new templates. Examples include steepening slopes to stay inside Right-of-Way and additional shoulder widening for guardrail anchorage. Step 6. Add Superelevation Superelevation Control Lines are added to control the Roadway cross slope in horizontal curve areas. InRoads utilizes Superelevation Tables based on the AASHTO 2004 Green Book. Step 7. Create Final Surface The creation of a Final Surface DTM is necessary in InRoads. The cross sections shown on the cross section sheets are generated from the Final Surface. The Construction Limits and the Roadway Ditches are also generated from the Final Surface.
8-4
Roadway Designer
8.3 IRD (Roadway Design) Naming Conventions

The Roadway Design File (.IRD) is where Corridors are created, Templates are added to Corridors, Point Controls and End Condition Exceptions are added and Design Surfaces are created. The IRD File (and any alternate design IRD File Names) will be named according to the PI Number. (See Table 8.1).
Table 8.1 Standard IRD (Roadway Design) File Names IRD and Alternate Design IRD Name(s) PI#.ird PI#A.ird PI#B.ird Example 123456.ird 123456A.ird (Alternate Design A) 123456B.ird (Alternate Design B)
8-5
Roadway Designer
8.4 Corridor Naming Conventions

A Corridor is a strip of land defined by a horizontal and vertical alignment or alignments. It can be considered the projects footprint. Cross section design is performed in the Corridor and the Final Surface is created from the corridor. The Corridor will be named the Roadway Name or the Alignment Name based on the Designers preference. (See Table 8.2).
Table 8.2 Standard Corridor Name (Roadway or Alignment Name) Roadway or Alignment Name Example: SR100 Spur (or) DE31
8-6
Roadway Designer
8.5 Superelevation Process Workflow

Superelevation Control Lines are added to control the Roadway cross slope in horizontal curve areas. InRoads utilizes Superelevation Tables based on the AASHTO 2004 Green Book. Superelevation in InRoads is created by the addition of Vertical Point Controls with a Superelevation control type. The addition of Superelevation Point Controls is facilitated by the use of the Superelevation Wizard and is performed after a corridor is created and templates are dropped. Once Superelevation has been added to the corridor by the Superelevation Wizard, the Superelevation Display is used to resolve Superelevation overlaps and to make any necessary edits to the Superelevation. After the Superelevation Wizard is used to add Superelevation to the Corridor, the Superelevation Display is used to resolve Superelevation overlaps and to edit the Superelevation through an intersection. Following is the Superelevation Process Workflow: 1. The Superelevation Table Wizard is used to select the Superelevation Table (Design Speed and Superelevation Rate), % Runoff on Tangent, Horizontal Curve Sets, etc. The Table Wizard is accessed through the following: In InRoads select Modeler Roadway Designer Superelevation Create Superelevation Wizard Table. 2. The Superelevation Sections Definitions window is where the Crown Point or rotational point of the Template and the Left and Right Range Points are added. The Profile Grade Point (PGL) is commonly chosen as the crown point of the Template but does not have to be. Range Points are points on the Template chosen to identify the extents to which the Superelevation is to be applied along the Template. Range Points are almost always picked at the outside edge of the travel lanes whereas the shoulder points are controlled by Shoulder Rollover Locks. The Superelevation Sections Definitions is accessed by clicking the Next > button in the Table Wizard dialog. 3. If there are any Superelevation Overlaps the Fix Superelevation Overlap dialog appears only when Superelevation Conflicts are detected in the Superelevation Calculations. If overlaps occur the Designer will need to resolve the overlaps before proceeding. 4. A Superelevation Report can be generated using a Style Sheet named GDOT Superelevation Data Report.xsl. The Style Sheet is accessed by selecting the following command: Modeler Roadway Designer Superelevation Superelevation Report. The Superelevation Data Report opens in the Bentley InRoads Report Browser and can be saved as an HTML file.
8-7
Roadway Designer
8.6 Design Surface Naming Conventions/Preference

The creation of a Final Design Surface DTM is necessary in InRoads. The cross sections shown on the cross section sheets are generated from the Final Design Surface. The Construction Limits and the Roadway Ditches are also generated from the Final Design Surface. The Design Surface will be named the PI#_Corridor Name (which can be either the Roadway Name or the Alignment Name based on the Designers preference). (See Table 8.3 and 8.4).
Table 8.3 Standard Design Surface Name (Roadway or Alignment Name) PI#_Corridor Name Example: 123456_SR100 SPUR (or) 123456_DE31
Table 8.4 Preference Final Design Surface Preference

Location: Modeler Roadway Designer Corridor Create Surface (Preferences Button) Preference Name Description
FINISH
Displays the FINISH Surface to GDOT Standard Feature Styles/Symbology.
8-8
Roadway Designer
8.7 Bogus Surface Naming Conventions for Target Aliasing

When a Templates End Condition encounters an obscured area or extends beyond the available Existing Surface, the End Condition fails to solve and is not placed. InRoads does not extend the existing ground in order to finish the placement of the Template as CAiCE users are accustomed to experiencing. When these situations are encountered, the Designer is instructed to request additional DTM coverage from the Office of Design Policy and Support/Location Bureau. The Location Bureau will provide a new DTM to the Designer with the additional coverage. Often obscured areas cannot be accurately surveyed; such is the case with bodies of water or swampy areas. In order to place a Template through these types of areas and have it solve so that construction limits may be computed -- a Bogus Surface must be created. Target Aliasing may then be used with the Bogus Surface. The creation of a Bogus Design Surface DTM is necessary in InRoads if there are obscured areas in which cross-sections cannot form a closed area for earthwork calculations. These cross sections shown on the cross section sheets are generated from the Final Design Surface and Bogus Surface. The Naming Convention for the Bogus Surface used in Target Aliasing is PI#_Bogus1.dtm (Ex. 123456_Bogus1.dtm). (See Table 8.5).
Table 8.5 Standard Bogus Surface for Target Aliasing

PI#_Bogus1.dtm
Example: 123456_Bogus1.dtm
8-9
9.
Cross Section Sheets/Annotation Generation
9. Cross Section Sheets/Annotation Generation

This section provides a brief overview of the requirements for generating and annotating Cross Section Sheets. For detailed Cross Section Sheet Generation and Annotation information please refer to Lab 9 in the Design Training Labs. This section covers the following topics:
Cross Section Sheets/Annotation Overview Finished Design Surface (.DTM) Preference Cross Section Sheet Scale Factor Cross Section Sheet Preferences Cross Section Sheet Annotation Preferences
9-2
9.1 Cross Section Sheets/Annotation Overview

The following section depicts an overview of the processes to create Cross Section Sheets and annotation of the Cross Sections to GDOT standards in InRoads. In order to generate and annotate Cross Sections the following information should be adhered and followed. a) In order to generate cross sections a minimum of an Existing Ground Surface .DTM and a Final Design Surface .DTM must exist. The cross sections are then cut from the Finished Design Surface.
b) The Cross Section sets are generated using InRoads but are saved and viewed in the MicroStation DGN file. The Cross Sections are not saved in InRoads as independent Cross Section sets which can be viewed after closing the MicroStation File. They must be regenerated from InRoads if changes or alterations are required in the cross-section design. New cross section sets must be cut and viewed as sheets in MicroStation. c) The Cross Section Cut Sheets use cells for the grids and border instead of DGN Reference Files. d) The Global Scale Factor in InRoads (for Text, Cell and Line Style) must be changed from 50 Scale to 10 Scale in order to generate the Cross Sections at the correct viewing Scale. e) The Set Name for Cross Sections defaults to the current Active Alignment name. f) There are four Preferences available for creating Cross Sections: 10 Scale Work Sec 1x Vert Exg, 50 Scale Work Sec 2x Vert Exg, Narrow 10h 10v and Wide 10h 10v. g) The Annotation of Cross Sections is a multi-step process to annotate the Profile Grade Elevations, Ditch Elevations, Slopes, Station/Offsets, etc. h) Before annotating Cross Sections the Lock for Pencil/Pen MUST be set to Pen in order to create permanent annotation of Cross Sections. i) Several Preferences have been set up to make the annotation process of Cross Sections easier. A multi-step process is required to annotate the Cross Sections to GDOT standards. j) It is very important that the standard GDOT Styles are used in the Roadway Design File (IRD). If the standard GDOT Styles are not used the Cross Sections may not annotate correctly.
9-3
9.2 Finished Design Surface (.DTM) Preference

In order to generate Cross Sections to GDOT Standards a Finished Design Surface (.DTM) must first be created. The Finished Design Surface Preference should be loaded before creating the DTM. This Preference sets the viewing/creation of the Finished Design Surface and ensures that the correct DTM Settings are initiated and that the symbology and levels are set before cutting the Cross Sections. The Preference of FINISH must be selected in order for the DTM to view and generate correctly. (See Table 9.1).
Table 9.1 Preference Create Surface

Location: Modeler Roadway Designer Corridor Create Surface (Preferences Button) Preference Name Description
FINISH
The Preference used for Finished DTM Surfaces. This Preference sets the options in the Create Surface dialog to generate Design Surfaces to GDOT Standards. The Preference creates the Surface on Level FCON_P_Surface Triangles-Line and Color 9 (Grey).
9-4
9.3 Cross Section Sheet Scale Factor

The generation of Cross Section Sheets is accomplished by using the Create Cross Section command in InRoads. This command uses DGN Cross Section Cells (Narrow and Wide) to generate the cut Cross Section Sheet borders and grids. For detailed Cross Section Sheet Generation information please refer to Lab 9 in the Design Training Labs. The following table lists the Global Scale Factors for generating Cross Sections. (See Table 9.2). In order to generate Cross Sections to GDOT Standards - the Global Scale Factors must be changed from a 50 Scale to a 10 Scale for Cross Sections to view on the Grids correctly and for the annotation text to view at the correct text size.
Table 9.2 Global Scale Factor Settings (Change Settings from 50 Scale/20 Scale to 10 Scale)
Location: Tools Global Scale Factors
Global Scale Factor Type Text Cell Line Style
Scale Factor 10.0000 10.0000 10.0000
9-5
9.4 Cross Section Sheet Preferences

The generation of Cross Section Sheets is accomplished by using the Create Cross Section command in InRoads. This command contains Preferences which have been set up in order to create the cut Cross Section Sheets to GDOT Standards. In order to generate/view Cross Sections to GDOT Standards Preferences must be set. These Preferences set the viewing/creation of Cross Sections when using the Evaluation Cross Section Create Cross Section dialog. (See Table 9.3).
Table 9.3 Preference Create Cross Section

Location: Evaluation Cross Section Create Cross Section (Preferences Button) Preference Name Description
Narrow 10h 10v
Wide 10h 10v
Used for Earthwork Volumes generation. This Preference uses the built in InRoads grid for viewing cross sections so that the entire cross section is drawn at each station for accurate earthwork volume calculations. The Preference loads settings for a 10 Scale Horizontal with a 1X Vertical Exaggeration. Used for Earthwork Volumes generation. This Preference uses the built in InRoads grid for viewing cross sections so that the entire cross section is drawn at each station for accurate earthwork volume calculations. The Preference loads settings for a 50 Scale Horizontal with a 2X Vertical Exaggeration. Used for Plans Production of Cross Section Narrow Sheet generation. This Preference loads the settings into the Create Cross Section dialog to view Cross Sections in a Narrow format on the GDOT SUXSEN Cross Section plan sheet cell. The Preference loads settings for a 10 Scale Horizontal and 10 Scale Vertical (Narrow 10h 10v). Used for Plans Production of Cross Section Wide Sheet generation. This Preference loads the settings into the Create Cross Section dialog to view Cross Sections in a Wide format on the GDOT SUXSEW Cross Section plan sheet cell. The Preference loads settings for a 10 Scale Horizontal and 10 Scale Vertical (Wide 10h 10v).
9-6
9.5 Cross Section Sheet Annotation Preferences

The generation of Cross Section Sheets also consists of annotating the Cross Sections to include text for slopes, station/offset, ditch elevations, etc. This is accomplished by using the Annotate Cross Section command in InRoads. This command contains Preferences which have been set up in order to annotate Cross Section Sheets to GDOT Standards. These Preferences set the text annotation of Cross Sections when using the Evaluation Cross Section Annotate Cross Section dialog. (See Table 9.4).
Table 9.4 Preference Annotate Cross Section

Location: Evaluation Cross Section Annotate Cross Section (Preferences Button) Preference Name Description
XSEC TEXT CL EL. GROUND XSEC TEXT EL. DIAGONAL XSEC TEXT EL. HORIZONTAL XSEC TEXT EL. VERTICAL XSEC TEXT - OFFSET XSEC TEXT OFFSET/EL. VERTICAL
XSEC TEXT SLOPES % XSEC TEXT SLOPES x:y
Used for annotating the existing ground elevation on the Cross Sections at the centerline alignment. Used for the annotation of proposed elevations in which the text must be viewed diagonally. (i.e. Roadway Profile.) Used for the annotation of proposed elevations in which the text must be viewed horizontally. (i.e. Roadway Ditches.) Used for the annotation of proposed elevations in which the text must be viewed vertically. Used for the annotation of offset distances as measured from the centerline. (i.e. Slopestakes/Construction Limits.) Used for the annotation of offset distances as measured from the centerline. The elevation at the offset is also placed. This form of annotation is not required on the final cross section plans. It is provided to be used as desired during the design process. Used for the annotation of slopes that require a percentage be used rather than a ratio (i.e. pavement cross slopes). Used for the annotation of slopes that require a ratio be used rather than a percentage (i.e. ditch slopes, front slopes, back slopes, etc.).
9-7
1 0
Construction Limits
Construction Limits
10. Construction Limits

This section provides a brief overview of the requirements and processes for creating/viewing Construction Limits, Roadway Ditches and Ditch Flow Arrows. For detailed Construction Limits information please refer to Lab 10 in the Design Training Labs. This section covers the following topics:
Construction Limits, Ditches and Ditch Flow Arrows Overview Construction Limits Feature Styles Roadway Ditches Feature Style Ditch Flow Arrow Preference Ditch Flow Arrow Annotate Feature Style Construction Limits DGN and Ditches/Ditch Flow Arrows DGN
10-2
Construction Limits
10.1 Construction Limits, Ditches and Ditch Flow Arrows Overview

The following section depicts an overview of the processes to create/view Construction Limits, Ditches and annotate Ditch Flow Arrows to GDOT standards in InRoads. In order to generate/annotate Construction Limits and Roadway Ditches the following information should be adhered and followed. a) In order to generate/view Construction Limits a Finished Design Surface must exist. The Final Surface is generated in the Roadway Designer from the Roadway Design File (.IRD). b) The Final Design Surface must be the Active Surface in order to depict the Construction Limits. c) The following Feature Styles representing Features from the Design Surface should be selected for viewing in order to create the Construction Limits: LIMT_P_FILL_Const-Limit and LIMT_P_CUT_Const-Limit. There may be several Features with these Feature Styles. d) The CUT Construction Limits will be depicted as ByLevel Linestyle of Blue containing the C Cell Symbol. The FILL Construction Limits will be depicted as ByLevel Linestyle of Yellow containing the F Cell Symbol. e) After viewing the Construction Limits the DGN file will be saved as the PI#LIMT.dgn (Ex. 123456LIMT.dgn). f) In order to generate/view Ditches and Ditch Flow Arrows a Finished Design Surface must exist. The Final Surface is generated in the Roadway Designer from the Roadway Design File (.IRD). g) The Final Design Surface must be the Active Surface in order to depict the Ditches and Ditch Flow Arrows. h) The following Feature Style representing Features from the Design Surface should be selected for viewing in order to view the Roadway Ditches: DRNG_P_Ditch. There may be several Features with this Feature Style. i) In order to annotate the Ditch Flow Arrows the Preference named Ditch Flow Arrows should be selected. j) The following Feature Style representing Features from the Design Surface should be selected for viewing in order to view the Ditch Flow Arrow Cell: DRNG_P_Ditch. There may be several Features with this Feature Style. k) After viewing the Ditches and Ditch Flow Arrow cells the DGN file will be saved as the PI#DRNG.dgn (Ex. 123456DRNG.dgn).
10-3
Construction Limits
10.2 Construction Limits Feature Styles

The Construction Limits consist of MicroStation ByLevel Symbology of Linestyle color Blue containing the C cell for Cut Limits and the ByLevel Symbology of Linestyle color Yellow containing the F cell for Fill Limits. In order to generate Construction Limits to GDOT Standards the Surface Features representing the Construction Limits must be selected and viewed. The following table lists the Surface Feature Styles to select for the viewing of Construction Limits. (See Table 10.1).
Table 10.1 Feature Styles Construction Limits

Note: There may be several Features which contain these Feature Styles.
Location: Surface View Surface Features Feature Style Description
LIMT_P_FILL_Const-Limit
LIMT_P_CUT_Const-Limit
The Feature Style used to represent the FILL Limits in the MicroStation DGN File. The Feature Style is placed on ByLevel LIMT_P_STKFIL_Const-Limit-FillLine. The Feature Style used to represent the CUT Limits in the MicroStation DGN File. The Feature Style is placed on ByLevel LIMT_P_STKCUT_Const-LimitCut-Line.
10-4
Construction Limits
10.3 Roadway Ditches Feature Style

The Roadway Ditches Feature Style in the Final Design Surface must be selected and viewed in order to depict the Roadway Ditches to GDOT Standards. The ByLevel setting for the Roadway Ditches are depicted with a Symbology of Yellow. The following table lists the Surface Feature Style to select for the viewing of Roadway Ditches. (See Table 10.2).
Table 10.2 Feature Style Roadway Ditches

Note: There may be several Features which contain this Feature Style.
DRNG_P_Ditch
The Feature Style used to represent the Roadway Ditch Drainage. The Feature Style is placed on ByLevel DRNG_P_Ditch-and-Channel-Line.
10-5
Construction Limits
10.4 Ditch Flow Arrow Preference

In order to depict the Ditch Flow Arrows on the Roadway Ditches a Preference is required which sets the viewing/creation of the Arrows. When the Preference is loaded - the MicroStation cell Ditch Flow Arrow is selected. The following table lists the Preference and Cell to select for the viewing of Roadway Ditches. (See Table 10.3).
Table 10.3 Preference Ditch Flow Arrow

Location: Surface View Surface Annotate Feature (Preferences Button) Preference Name Description
Ditch Flow Arrows
Populates the selections in the Annotate Feature dialog so that that Ditch Flow Arrows are viewed to GDOT Standards. A Cell named Ditch Flow Arrow represents the direction and flow of the Roadway Ditch Drainage.
10-6
Construction Limits
10.5 Ditch Flow Arrow Annotate Feature Style

Even though the Ditch Flow Arrows Preference is loaded the Feature Style of DRNG_P_Ditch must still be selected in order to annotate the Ditch Flow Arrow Cell to GDOT Standards. The following table lists the Surface Feature Style to select for the viewing of Ditch Flow Arrows. (See Table 10.4).
Table 10.4 Feature Style Ditch Flow Arrows

Note: There may be several Features which contain this Feature Style.
DRNG_P_Ditch
The Feature Style used to represent the Ditch Flow Arrows annotation for Drainage Flow directions.
10-7
Construction Limits
10.6 Construction Limits DGN and Ditches/Ditch Flow Arrows DGN

After viewing the Construction Limits and the Ditches/Ditch Flow Arrows MicroStation DGN files should be created to graphically represent the Features. For detailed instructions on how to create the applicable DGN Files see Lab 10 in the Design Training Labs. The following table lists the standard naming conventions of the two DGN Files which are to be generated. (See Table 10.5).
Table 10.5 DGN Files Construction Limits and Roadway Ditches/Ditch Flow Arrows
Location: In MicroStation File Save As DGN File Name Example
PI#LIMT.dgn PI#DRNG.dgn
123456LIMT.dgn 123456DRNG.dgn
10-8
1 1
Earthwork
Earthwork
11. Earthwork
This section provides a brief overview of the requirements and processes for generating Earthwork Quantities and Earthwork Volume Reports. For detailed Earthwork information please refer to Lab 11 in the Design Training Labs. This section covers the following topics:
Earthwork Overview MicroStation View Attributes Setting Cross Section Preferences GDOT Earthwork Volumes Preference GDOT Earthwork Volume Report
11-2
Earthwork
11.1 Earthwork Overview

The following section depicts an overview of the processes to generate Earthwork Quantities and Earthwork Volume Reports to GDOT Standards in InRoads. In order to generate these Quantities and Volume Reports the following information should be adhered and followed. a) In order to generate Earthwork Quantities and Volume Reports Cross Section Sets must be created. The Earthwork Volumes are actually generated from the Cross Sections drawn in MicroStation; therefore, a Cross Section Set must first be drawn in MicroStation in order to calculate quantities. a) In MicroStation the View Attributes of Fill must be selected and turned on in order for the Volumes to view the Cut/Fill areas in the appropriate Fill or Cut shaded color. b) The Preference of 50 Scale Work Sec 2x Vert Exg or the 10 Scale Work Sec 1x Vert Exg uses the built in InRoads grid for viewing the Cross Sections rather than the GDOT Cross Section plan sheet cell. When viewing Cross Section Sets for Earthwork calculations and volumes one of the above listed Preferences should be used. The other GDOT Cross Section Preferences should be used only for Plans Production generation. c) The Existing and the Proposed Surfaces should be selected when creating the Cross Section Sets in order to obtain a closed area for Volume calculations. d) The Preference of GDOT Earthwork Volumes should be selected (before the calculation of volumes) in order to generate an End-Area Volumes Report to GDOT Standards. e) In order to generate/view the Earthwork Volumes Report - a Style Sheet named GDOT Earthwork Volumes.xsl should be selected. The Style Sheet is accessed by selecting the following command: Evaluation Volumes End-Area Volume. The End-Area Volumes dialog box opens. Click the Preferences button and load the GDOT Earthwork Volumes Preference. After clicking Apply the Bentley InRoads Report Browser opens. Select the Style Sheet named GDOT Earthwork Volumes.xsl. The Style Sheet can be saved as an HTML file. f) Make sure that each Cross Section at each applicable Station forms a closed area. If the areas do not close the volume calculations will be inaccurate. This is especially the case if there are obscured areas. The Designer is reminded to contact the Office of Design Policy and Support/Location Bureau for any additional survey required in the obscured areas. If these areas are not resolved inaccurate volume calculations will result.
11-3
Earthwork
11.2 MicroStation View Attributes Setting

After creating the Cross Section Sets- the Cut and Fill shaded areas should be viewed in MicroStation to ensure that each Stations Cross Sections form a closed area. All Cut Areas should be filled as Green and all Fill Areas should be filled as Blue. This will help to ensure that Volumes are being calculated correctly. The following table lists the Location in MicroStation to turn on the Fill View Attribute Setting. (See Table 11.1). Table 11.1 MicroStation Fill View Attribute Setting
MicroStation Location: Settings View Attributes
The Fill Attribute should be highlighted in Orange as shown on the left.
Volume
Shaded Color
CUT FILL
Shaded Green Fill Shaded Blue Fill
11-4
Earthwork
11.3 Cross Section Preferences

The generation of Cross Section Sheets is accomplished by using the Create Cross Section command in InRoads. This command contains Preferences which have been set up in order to create the cut Cross Section Sheets to GDOT Standards. In order to generate/view Cross Sections to GDOT Standards for Earthwork Volumes Preferences must be set. Preferences set the viewing/creation of Cross Sections when using the Evaluation Cross Section Create Cross Section dialog. Although there are additional Preferences available only the first two Preferences listed in the following table should be used for Earthwork Volume Calculations. The other Preferences are used for Cross Section Plans Production only. (See Table 11.2).
Table 11.2 Preference Create Cross Section

Location: Evaluation Cross Section Create Cross Section (Preferences Button) Preference Name Description
10 Scale Work Sec 1x Vert Exg (Use for Earthwork Volumes)
50 Scale Work Sec 2x Vert Exg (Use for Earthwork Volumes)
Narrow 10h 10v (Use for Plans Production)
Wide 10h 10v (Use for Plans Production)
Used for Earthwork Volumes generation. This Preference uses the built in InRoads grid for viewing cross sections so that the entire cross section is drawn at each station for accurate earthwork volume calculations. The Preference loads settings for a 10 Scale Horizontal with a 1X Vertical Exaggeration. Used for Earthwork Volumes generation. This Preference uses the built in InRoads grid for viewing cross sections so that the entire cross section is drawn at each station for accurate earthwork volume calculations. The Preference loads settings for a 50 Scale Horizontal with a 2X Vertical Exaggeration. Used for Plans Production of Cross Section Narrow Sheet generation. This Preference loads the settings into the Create Cross Section dialog to view Cross Sections in a Narrow format on the GDOT SUXSEN Cross Section plan sheet cell. The Preference loads settings for a 10 Scale Horizontal and 10 Scale Vertical (Narrow 10h 10v). Used for Plans Production of Cross Section Wide Sheet generation. This Preference loads the settings into the Create Cross Section dialog to view Cross Sections in a Wide format on the GDOT SUXSEW Cross Section plan sheet cell. The Preference loads settings for a 10 Scale Horizontal and 10 Scale Vertical (Wide 10h 10v).
11-5
Earthwork
11.4 GDOT Earthwork Volumes Preference

The generation of Earthwork Volumes is accomplished by using the End-Area Volumes command in InRoads. This command contains a Preference which has been set up to calculate Volumes to GDOT Standards. In order to generate the correct Volumes for GDOT the GDOT Earthwork Volumes Preference must be set. The GDOT Earthwork Volumes Preference loads settings into the End-Area Volumes dialog to generate a Volumes Report. The Preference does not load settings to apply cut/fill adjustment factors. The Preference is accessed in the Evaluation Volumes End-Area Volume (End-Area Volumes). The following table lists the GDOT Earthwork Volume Preference to select for the calculation of Earthwork Volumes. (See Table 11.3).
Table 11.3 Preference GDOT Earthwork Volumes

Location: Evaluation Volumes End-Area Volume (Preferences Button) Preference Name Description
GDOT Earthwork Volumes
Used for Earthwork Volumes generation. This Preference loads the GDOT Standard Settings in the End-Area Volumes dialog for use in calculating Earthwork Volumes. The Preference does not load settings to apply cut/fill adjustment factors
11-6
Earthwork
11.5 GDOT Earthwork Volume Report

The generation of the Earthwork Volume Report is accomplished by using the GDOT Earthwork Volumes.xsl Style Sheet. This Style Sheet is accessed by selecting the following command: Evaluation Volumes End-Area Volume. The End-Area Volumes dialog box opens. Click the Preferences button and load the GDOT Earthwork Volumes Preference. After clicking Apply the Bentley InRoads Report Browser opens. Select the Style Sheet named GDOT Earthwork Volumes.xsl. The Style Sheet can be saved as an HTML file. For additional information regarding the Style Sheet review the Style Sheet Help File which is included with the InRoadsALLV8i standard files and is located in the following path: C:\InRoads Data\Style Sheet Documentation. (See Table 11.4). Table 11.4 Style Sheet Report GDOT Earthwork Volumes.xsl
Location: Evaluation Volumes End-Area Volume (Click Apply button). Style Sheet Name Description
GDOT Earthwork Volumes.xsl
The GDOT Earthwork Volumes Report.xsl Style Sheet is utilized to supply Earthwork volume information. It is used by the Designer and Earthwork Coordinator during the Design phase and Construction phase of a project. Please Refer to the GDOT Earthwork Volumes Report.xsl Style Sheet Help File for additional information.
11-7
1 2
Required Right of Way
12. Required Right of Way

This section provides a brief overview of the requirements and processes for storing R/W Parcels and generating Right of Way Tables to GDOT Standards. For detailed Right of Way information please refer to Lab 12 in the Design Training Labs. This section covers the following topics:
Right of Way Overview R/W Alignment and COGO Point Names/Feature Styles R/W COGO Points and Alignment Points R/W View Horizontal Annotation Preference R/W View Horizontal Annotation Filters Reviewing Horizontal R/W Alignments R/W DGN File Generation R/W and Easement Tables (Style Sheets) R/W Deed (Style Sheets)
12-2
12.1 Right of Way Overview

The following section depicts an overview of the processes to generate Required R/W and Easement Alignments, R/W DGN Files and R/W and Easement Tables to GDOT Standards in InRoads. Failure by the Designer to follow the correct Point and Alignment naming convention may cause problems with Survey Enhancements during the life of the project and with Stakeout Report generation. In order to generate these Required R/W and Easements the following information should be adhered and followed. a) All Right of Way and Easement Alignments must have a Feature Style assigned of REQD_P_DWESMT, REQD_P_PESMT, REQD_P_REQD or REQD_P_TESMT for the Right of Way Tables to generate correctly. b) In InRoads, the term Horizontal Alignment refers to all linear elements, open or closed, such as centerlines, right of way parcels, etc. Horizontal Alignments consist of COGO points, linear elements and curves. Curves are not independent entities but are considered part of the Alignment. c) All Right of Way Horizontal Alignment Names and COGO Point Names must begin with a DE Prefix. All Points must begin numbering at DE10000 or the next available DE Point Number. Horizontal Alignment numbering may begin at DE1. d) All Horizontal Alignment Points for Right of Way and Easements must be converted to COGO Points. e) When working on a Right of Way/Easement Alignment ensure that it is set as the Active Alignment. f) When storing curve data in Right of Way and Easement Alignments ensure that all the curves are tangent and points are equated at the PC and PT of all curves. g) Make sure to save the ALG file periodically when changes are made. InRoads does not save data on the fly - data is saved in temporary memory. The ALG file must be manually saved in order to retain Design modifications. h) Ensure that all Right of Way and Easement Alignments are stored in a clockwise direction for use in writing Deeds. i) In order to generate the R/W and Easement Tables and a Deed DescriptionStyle Sheet(s) named GDOT RW Table.xsl and GDOT Deed.xsl should be selected. The Style Sheet(s) are accessed by selecting the following command: In InRoads, select Tools XML Reports Hold down the CTRL key on your key board while Left clicking Legal Description. The GaDOT Legal Description dialog opens. The Style Sheet(s) for both the R/W Tables and the R/W Deed can be saved as .txt file(s). 12-3
12.2 R/W Alignment and COGO Point Names/Feature Styles

The Right of Way Horizontal Alignments and COGO Points must be stored with a DE Prefix and must be stored in a certain Point/Horizontal Alignment Number range along with the appropriate Feature Style. See the following Tables (Tables 12.1, 12.2 and 12.3) for a list of the required naming conventions).
Table 12.1 Standard R/W Design Geometry Object Names Object Type *R/W Cogo Points *R/W Horizontal Alignment Points **R/W Horizontal Alignments DE DE DE Prefix Starting Number 10000 (Max. = 99,999) 10000 (Max. = 99,999) 1
* All Design Cogo Points and Design Horizontal Alignment Points must be named with a prefix of DE and begin with the number 10000 (e.g., first design point = DE10000). **All Design Horizontal Alignments must be named with a prefix of DE and begin with the number 1, (e.g., DE1).
Table 12.2 R/W Design Point & Alignment Ranges to Use Cogo/Alignment Points Horizontal Alignments Range 10,000 to 99,999 Range 1 to no Limitations for Alignments -- but must have the DE Prefix
12-4
Table 12.3 Feature Styles For R/W Design Points and Alignments REQD_P_DWESMT Proposed Design Points REQD_P_PESMT Feature Style REQD_P_REQD REQD_P_RWRM REQD_P_TESMT Proposed Right of Way Descriptions Feature Style R/W Monument Reqd. R/W Perm. Const. Esmt. Temp. Const. Esmt. Driveway Esmt. REQD_P_RWRM REQD_P_REQD REQD_P_PESMT REQD_P_TESMT REQD_P_DWESMT** N/A
Ex: REQD R/W PAR 33/SV29 Ex: PESMT PAR 44/SV67 Ex: TESMT PAR 23/SV88 Ex: DWESMT PAR 14/SV30
** Note: All other Types of Miscellaneous Easements should use the REQD_P_DWESMT Feature Style.
12-5
12.3 R/W COGO Points and Alignment Points

As mentioned previously - InRoads has the capability to store both COGO Points (which are northing and easting coordinates) and the ability to store Alignments Points (which are just coordinates with an assigned name not independent Points). It is a required GDOT standard that all Points must be stored as COGO Points. If Alignment Points are stored it is the Designers responsibility to convert these Points to COGO Points. In order to view the correct Point Cells and Symbology COGO Points must be stored instead of Alignment Points in order to generate the correct Symbology, Level, etc. for plans productions. Following is a brief overview of COGO Points versus Alignment Points. ***IMPORTANT DISCUSSION*** Alignment points and COGO points are two types of points to be aware of. Alignment points are nothing more than names assigned to coordinates in an alignment and do not exist in the COGO points buffer. In order to satisfy GDOT plan presentation requirements, prepare R/W tables and properly add enhanced survey data to your project. -- Surveyors and Designers alike must ensure that all alignments have a corresponding COGO point stored. We recommend that you adhere closely to the methods presented in the tutorials concerning centerlines, R/W and property. We bring this up because it is possible to view points at the same time as viewing Alignments without having to populate the Cogo Points in the View Horizontal Annotation command. Viewing points in this manner would not apply the correct attributes to the points -- therefore you must view the Cogo points separately.
12-6
12.4 R/W View Horizontal Annotation Preference

In order to view Right of Way and/or Easement Horizontal Alignments to GDOT Standards the Preference named NO BEARING & DISTANCE should be selected. This Preference sets the viewing of Right of Way Alignments and Easement Alignments (No Bearing & Distance) options. The following Table depicts the available Preference, Location and Description to set the Preference. (See Table 12.4).
Table 12.4 Preference R/W View Horizontal Annotation

Location: Geometry View Geometry Horizontal Annotation (Preferences Button) Preference Name Description
Displays NO Bearing & Distance information for all Horizontal Alignments.
12-7
12.5 R/W View Horizontal Annotation Filters

Geometry Selection Filters can be used to select specific Alignments and COGO Points. Once selected and filtered the Alignments and/or COGO Points will view and/or can be used for the generation of specific Style Sheets based on the criteria selected. A Filter can also be used to select the Points to utilize for Stakeout of R/W and Survey Data. The following Tables depict the available Filters, Locations and Descriptions to set the Filters for R/W, Easements and Stakeout of R/W and Survey Data. (See Table 12.5).
Table 12.5 Geometry Selection Filter Preferences for R/W, Easements and Stakeout Data
Location: Geometry View Geometry Horizontal Annotation (Filter Button)
Then in the Geometry Selection Filter select the Preferences Button.

Filter Name Description
REQD.dgn Alignments REQD.dgn Points Stakeout Survey Data
Loads the Filter to select and view the Feature Style Alignments for the production of the REQD DGN File. Loads the Filter to select and view the Feature Style Points for the production of the REQD DGN File. Loads the Filter to select the Feature Style Points for use in the GDOT Stakeout Report Style Sheet.
12-8
12.6 Reviewing Horizontal R/W Alignments

The Horizontal Alignments for R/W and Easement descriptions can be reviewed and printed by using the Geometry Review Horizontal command. Following is the process for reviewing/describing Horizontal Alignments: Ensure that the Horizontal Alignment (R/W or Easement Alignment) you want to describe is the active Horizontal Alignment. In InRoads, Select Geometry Review Horizontaland the Review Horizontal Alignment description appears. The user may also print the description by using the Print button on the Review Horizontal Alignment dialog. (See Figure 12-1).
Figure 12-1 Review Horizontal Alignment
12-9
12.7 R/W DGN File Generation

After viewing the Required Right of Way and Easement Points, Cells, and Alignments a MicroStation DGN file should be created to graphically represent these Geometry Objects. For detailed instructions on how to create the applicable DGN File see Lab 12 in the Design Training Labs. The following table lists the standard naming convention of the DGN File which is to be generated. (See Table 12.6).
Table 12.6 DGN File Required Right of Way
Location: In MicroStation File Save As DGN File Name Example
PI#REQD.dgn
123456REQD.dgn
12-10
12.8 R/W and Easement Tables (Style Sheets)

The generation of the R/W and Easement Tables is accomplished by using the GDOT RW Table.xsl Style Sheet. This Style Sheet is accessed by selecting the following command: In InRoads, select Tools XML Reports Hold down the CTRL key on your key board while Left clicking Legal Description. The GaDOT Legal Description dialog opens. Enter the appropriate Alignment and Reference Alignments and then click Apply. The Bentley InRoads Report Browser opens. Select the Style Sheet named GDOT RW Table.xsl. The Style Sheet can be saved as a .txt file and then imported into MicroStation as a table. For additional information regarding the Style Sheet review the Style Sheet Help File which is included with the InRoadsALLV8i standard files and is located in the following path: C:\InRoads Data\Style Sheet Documentation. (See Table 12.7). Table 12.7 Style Sheet Report (Table) GDOT RW Table.xsl
Tools XML Reports Hold down the CTRL key on your key board while Left clicking Legal Description.
Style Sheet Name Description
GDOT RW Table.xsl
The GDOT RW Table.xsl Style Sheet is utilized to create Right-of-Way Table text files for placement in MicroStation with the GDOT Tools Include Data Table placement Macro. Please Refer to the GDOT RW Table.xsl Style Sheet Help File for additional information.
12-11
12.9 R/W Deed (Style Sheets)

The generation of the Right of Way Deed is accomplished by using the GDOT Deed.xsl Style Sheet. This Style Sheet is accessed by selecting the following command: In InRoads, select Tools XML Reports Hold down the CTRL key on your key board while Left clicking Legal Description. The GaDOT Legal Description dialog opens. Enter the appropriate Alignment and Reference Alignments and then click Apply. The Bentley InRoads Report Browser opens. Select the Style Sheet named GDOT Deed.xsl. The Style Sheet MUST BE saved as a .out file. This .out file is then used in the stand-alone Deed Writer Program to generate GDOT Deeds for purchase of Right of Way. For additional information regarding the Style Sheet review the Style Sheet Help File which is included with the InRoadsALLV8i standard files and is located in the following path: C:\InRoads Data\Style Sheet Documentation. (See Table 12.8). Table 12.8 Style Sheet Report (Table) GDOT Deed.xsl
Tools XML Reports Hold down the CTRL key on your key board while Left clicking Legal Description.
Style Sheet Name Description
GDOT Deed.xsl
The GDOT Deed.xsl Style Sheet is utilized to supply a Deed.out file to the Right-of-Way office. The Right-of-Way office utilizes the Deed.out file to generate a Deed. Please Refer to the GDOT Deed.xsl Style Sheet Help File for additional information. Please Note: The Style Sheet must be saved as a .out file for use with the GDOT Deed Writer Program.
12-12
1 3
Survey Enhancements
Survey Enhancements
13. Survey Enhancements

This section provides a brief overview of the processes to include Additional Survey Enhancements received from Photogrammetry/Survey during the Design Phase of a project. For detailed Survey Enhancement information please refer to Lab 13 in the Design Training Labs. This section covers the following topics:
Survey Enhancements Overview Survey Enhancements to the DTM Survey Enhancements to the ALG Survey Enhancements to the DGN
13-2
Survey Enhancements
13.1 Survey Enhancements Overview

The following section depicts an overview of the processes to incorporate Survey Enhancements during the Design Phase of a project according to GDOT Standards. In order to add the Survey Enhancement Data the following information should be adhered and followed. a) During the life of a Design project Additional Survey Enhancements may need to be incorporated into the project and the new survey data re-submitted to the Designer in order for the Designer to update the design database. b) All location survey data and all requests for additional survey data should be submitted to the Engineering Management Section of the Office of Design Policy and Support/Location Bureau. c) Depending on what type of enhancements are collected the SDE will process the additional survey data and send the Designer the appropriate files as required. This could result in the SDE sending the Designer all of the updated files or just certain files depending on what data were collected. d) The Designer will receive a new PI#_SDE.dtm from the SDE when Enhancements are requested and incorporated for Surface Data. After receiving the updated DTM the Designer will delete their PI#_Exist.dtm and replace it with this new one. The Designer will then rename the PI#_SDE.dtm both externally and internally to PI#_Exist.dtm (as previously described in the Design Training Lab 2). The steps outlined in Design Training Lab 13 will instruct the user how to do this. e) When the Designer requests additional property or additional existing alignment enhancements that affect the InRoads ALG file, the SDE will add or change the data in the original PI#_SDE.alg file that is kept by the Survey Office. When changes are complete, the Designer will be notified and provided with a copy of the revised PI#_SDE.alg file. The Designer will delete out all Survey Data from the PI#_Design.alg file he is working in and will import all Survey Data from the revised PI#_SDE.alg to the PI#_Design.alg he is working in, using the LandXML Translator. The steps outlined in Design Training Lab 13 will instruct the user how to do this. f) A new Enhanced DTM may not always be provided to the Designer if no changes were made to the DTM by the SDE. The SDE will only provide an Enhanced DTM if new Features have been surveyed and incorporated into the DTM. If any topographical enhancements are collected the SDE will send the Designer the new processed DTM file and the associated enhanced data in the PI#_TOPO.dgn file.
13-3
Survey Enhancements
g) A new Enhanced Survey ALG file may not always be provided to the Designer if no changes were made to the Property or Existing Alignment data by the SDE. The SDE will only provide an Enhanced ALG if new data has been surveyed and incorporated into the ALG. If any property enhancements are collected the SDE will send the Designer the new processed ALG file and the associated enhanced data in the PI#_PROP.dgn file. h) The InRoads LandXML utility is used to export the Enhanced Survey Data from the SDEs ALG File and also to import the Enhanced Survey Data into the Designers ALG File. i) The Enhanced Existing DTM received from the SDE contains all of the Surface Points, Breaklines and Features along with the triangulated data. The Enhanced Property/Existing Alignment information in the ALG received from the SDE contains all of the SV Prefix Alignments and the Survey Cogo Points. j) If only property enhancements were collected, then the SDE would send the Designer the new processed PI#_SDE.alg file and the associated enhanced data in the PI#_PROP.dgn file. k) If only topographical enhancements were collected, then the SDE would send the Designer the new processed PI#_SDE.dtm file and the associated enhanced data in the PI#_TOPO.dgn file. l) In most cases the following files (or a combination) of these files will be submitted to the Designer for use as Additional Survey Enhancements: PI#_SDE.dtm PI#_SDE.alg PI#_TOPO. dgn (if applicable) PI#_PROP.dgn (if applicable) PI#_UTLE.dgn (if applicable)
13-4
Survey Enhancements
Additional Survey Enhancement Process

(Red Dotted Line represents Additional Survey Enhancement Process Overview)
Env/Loc
DGN DTM
Additional Field Survey Enhancements
SDE
InRoads
Field Enhanced ASC File
FWD
FWD does NOT go to Design
Enhanced Topo DGN
Merged Topo DGN
DTM
Topo.dgn
ALG
Utle.dgn
Prop.dgn
Design
Designer Requests Additional Enhancements 13-5
Survey Enhancements
13.2 Survey Enhancements to the DTM

The following section depicts information regarding the DTM file submitted to the Designer whenever Survey Enhancements have been incorporated by the SDE. As mentioned previously, a new Enhanced DTM may not always be provided to the Designer if no changes were made to the DTM by the SDE. The SDE will only provide an Enhanced DTM if new Features have been surveyed and incorporated into the DTM. If any topographical enhancements are collected the SDE will send the Designer the new processed DTM file (PI#_SDE.dtm). **For detailed Survey Enhancement information (procedures and processes) please refer to Lab 13 in the Design Training Labs. Brief Overview Process: Step 1: Copy the Enhanced PI#_SDE.dtm to the Project Folder. Step 2. Delete the PI#_Exist.dtm from the Project Folder. Step 3: Rename the External Name from PI#_SDE.dtm to PI#_Exist.dtm. Step 4: Rename the InRoads Internal Name from PI#_SDE.dtm to PI#_Exist.dtm.
13-6
Survey Enhancements
13.3 Survey Enhancements to the ALG

The following section depicts information regarding the ALG file submitted to the Designer whenever Survey Enhancements have been incorporated by the SDE. As mentioned previously, a new Enhanced Survey ALG file may not always be provided to the Designer if no changes were made to the Property or Existing Alignment data by the SDE. The SDE will only provide an Enhanced ALG if new data has been surveyed and incorporated into the ALG. If any property enhancements are collected the SDE will send the Designer an enhanced PI#_SDE.alg file. **For detailed Survey Enhancement information (procedures and processes) please refer to Lab 13 in the Design Training Labs.
Brief Overview Process: Step 1: Copy the Enhanced PI#_SDE.alg to the Project Folder. Step 2. In the PI#_Design.alg delete all Alignments with an SV Prefix. Step 3: In the PI#_Design.alg delete all Points without a Prefix. Step 4: In the PI#_SDE.alg export the Survey Data using LandXML Utility. Step 5: In the PI#_Design.alg import the Survey Data using LandXML Utility.
13-7
Survey Enhancements
13.4 Survey Enhancements to the DGN

The following section depicts information regarding the DGN file(s) submitted to the Designer whenever Survey Enhancements have been incorporated by the SDE. The following DGN File(s) are updated by the SDE by merging the new data into the original PI#_TOPO.dgn, PI#_PROP.dgn and/or PI#_UTLE.dgn files depending on the data collected. The Designer may not always receive all three of the above mentioned files. The Designer will only receive the updated DGN files if changes were made to the DGN files by the SDE. If Enhanced DGN Files are provided by the SDE the Designer will overwrite his current TOPO, PROP and/or UTLE DGN Files and replace them with the new ones provided by Survey. **DGN Files The DGN Files received from the SDE contain an underbar (_) in the file name. The reason for this is to assist in differentiating DGN data received from the SDE from that of the Design DGN files. This will assist in organization of data during the enhancement processes. The Designer must rename the DGN files from the SDE naming convention to the Design naming convention in order for the MicroStation customized Macros to function correctly and to conform to the current EDG (Electronic Data Guidelines). If the Designer does not rename the DGN files (and remove the underbars) the GDOT MicroStation Macros may not function. (See Table 13.1). Table 13.1 Re-name SDE DGN Files SDE DGN FILE NAME Rename To
PI#_TOPO.dgn PI#_PROP.dgn PI#_UTLE.dgn
DESIGN DGN FILE NAME

PI#TOPO.dgn PI#PROP.dgn PI#UTLE.dgn
**For detailed instructions regarding the above re-naming process -- please refer to Lab 2 in the Design Training Manual: Introduction to InRoads for Design Training Guide.
13-8
1 4
InRoads Style Sheets
14. InRoads Style Sheets

This section provides a brief overview of the requirements and processes for generating InRoads Style Sheets to GDOT Standards. For additional information regarding the processing of Style Sheets, please refer to Lab 14 in the Design Training Labs. This section covers the following topics:
InRoads Style Sheets Overview Location of GDOT Style Sheets Location of GDOT Style Sheet Help Files Descriptions of GDOT Style Sheets
14-2
14.1 InRoads Style Sheets Overview

Style Sheets are used by InRoads to present data in a particular Report Format. The Style Sheets are XSL files which can be saved in different extensions depending on the Style Sheet used. Formats can be saved as .HTML, .ASC, .OUT, .TXT, etc. depending on the function of the Style Sheet. GDOT has several Style Sheets which can be used to generate Report Data in a format for use in submitting Report deliverables for Design, Survey, Construction, etc. In order to generate these Style Sheets to GDOT Standards the following information should be adhered and followed. a) The Style Sheet Data is based on XML (Extensible Markup Language) code which is used to generate the data from InRoads into an XSL (Extensible Style Sheet Language) Report Format. b) In order to generate Style Sheets to GDOT Standards for deliverables the Style Sheets in the following location should be utilized: C:\Program Files\Bentley\InRoads Group V8.11\XML Data\GDOT\ The above path is set as the default in the Project Defaults Command in InRoads. (The process for setting this default path is described in the next section of the Guidelines). c) Following are the categories which are available: Geometry Station Base Station Offset Clearance Stakeout Legal Description Map Check Intersecting Alignment Stations Surfaces Surface Check d) It is very important that only the Style Sheets that have the name GDOT in it are used for submitting deliverables according to GDOT Standards. The Designer may use the generic InRoads Style Sheets during the Design Process but all deliverable Reports MUST use the GDOT Style Sheets according to Design Policy.
14-3
14.2 Location of GDOT Style Sheets

As mentioned previously, in order to generate Style Sheets to GDOT Standards for deliverables the GDOT Standard Style Sheets should be utilized. The GDOT Style Sheets are included in the InRoadsALLV8i.exe download executable file. Once InRoadsALLV8i.exe is executed and installed the GDOT Style Sheets will be located in the following path: C:\Program Files\Bentley\InRoads Group V8.11\XML Data\GDOT\ In order to access these Style Sheets - the path should be set as the default path in InRoads by using the Project Defaults command. The Designer will need to enter this path in the InRoads Project by doing the following: In the InRoads pull-down select: 1. FileProject Defaults from the InRoads pull-down menu. 2. Under the Default Directory Paths Section - Click in the Style Sheet (*.xsl): field and then click the Browse button to navigate to the folder: C:\Program Files\Bentley\InRoads Group V8.11\XML Data\GDOT\. 3. Next - click Open. 4. The Current Configuration for the Style Sheets will now default to the following path: C:\Program Files\Bentley\InRoads Group V8.11\XML Data\GDOT\ 5. Click Apply.
14-4
14.3 Location of GDOT Style Sheet Help Files

GDOT Style Sheet Help Files are included in the InRoadsALLV8i.exe download executable file. Once InRoadsALLV8i.exe is executed and installed the GDOT Style Sheets will be installed and located in the following path: C:\InRoads Data\Style Sheet Documentation These GDOT Style Sheet Help Files depict detailed information regarding the usage of the Style Sheets, the format of the Style Sheets and the type of extension (.html, .txt, .asc, etc.) in which the Style Sheet should be saved.
14-5
14.4 Descriptions of GDOT Style Sheets

Customized Style Sheets have been created to GDOT Standards in order to provide Reports for InRoads Data. These Style Sheets correspond to GDOT Policy and should be utilized for Report deliverables when required. The following Table lists the current available GDOT Style Sheets, the Location to Access the Style Sheets in InRoads and a brief Description of the Style Sheets. Detailed Help Files are also available as discussed in the previous Section 14.3. (See Table 14.1). Table 14.1 Style Sheet Descriptions
Style Sheet Name (.xsl)
Location
Description
GDOT Alignment File Descriptions
Tools XML Reports Geometry Tools XML Reports Geometry
The GDOT Alignment File Descriptions.xsl Style Sheet is utilized to supply a text file description of the centerline alignments to the Contractor.
GDOT Alignment Points List
The GDOT Alignment Points List.xsl Style Sheet lists all the points in an alignment in a format that may be copied and pasted into the View Horizontal Annotation dialogs Cogo Points include: field. This function is useful during Right-of-Way plans preparation when the Cogo points in the Right-of-Way alignments need to be viewed. In InRoads V8i, viewing the Cogo points comprising the R/W alignments is the only way to ensure the proper point symbols are viewed in MicroStation.
14-6

Location
Description
GDOT Alignment Report
Tools XML Reports Geometry
The GDOT Alignment Report.xsl Style Sheet is utilized to supply Horizontal Alignment information to the Contractor for use in GPS equipment. The Report depicts the Alignment information located at 50 Foot Station intervals at a Zero Offset. The GDOT Alignment Report.xsl will contain each Horizontal Alignment with the Feature Styles of MAIN_P_CONSTCL and MAIN_P_SIDECL in the InRoads Project Database (.ALG file). The Alignments may all be generated at one time and listed in one GDOT Alignment Report.xsl. The GDOT Deed.xsl Style Sheet is utilized to supply a Deed.out file to the Right-of-Way office. The Right-of-Way office utilizes the Deed.out file to generate a Deed.
GDOT Deed
Tools XML Reports CTRL key + Legal Description Evaluation Volumes End-Area Volume Evaluation Volumes End-Area Volume
GDOT Earthwork Volumes Report
The GDOT Earthwork Volumes Report.xsl Style Sheet is utilized to supply Earthwork volume information. It is used by the Designer and Earthwork coordinator during the design phase and construction phase of a project. The GDOT End-Area Report-Compressed.xsl Style Sheet writes out an EndArea file to an ASCII text file format that is similar to the RDS format for distribution to Auditors and Contractors when a project is let to Construction. This format uses much less paper when compared to the GDOT End-Area Report-Standard.xsl. The GDOT End-Area Report-Standard.xsl Style Sheet is utilized to supply an End-Area report in a standard GDOT ASCII text file format for distribution to Contractors when a project is let to Construction.
GDOT End-Area Report Compressed
GDOT End-Area Report Standard
Evaluation Volumes End-Area Volume
14-7

Location
Description
GDOT Feature Lengths Report
Tools XML Reports Surfaces Tools XML Reports Clearance Evaluation Volumes End-Area Volume Evaluation Volumes End-Area Volume
The GDOT Feature Lengths Report.xsl Style Sheet is utilized to determine lengths of Features used in Finished surfaces. It requires the Designer to use a unique point name in the component utilized to create the surface. The GDOT Feature-StationElevationOffset Report.xsl Style Sheet is utilized to supply a Station, Elevation and Offset Report from the Roadway Centerline to selected Surface Features in the Digital Terrain Model (DTM). The GDOT Feature Volumes Report.xsl Style Sheet is utilized to supply volumes of component shapes placed in the Final design surface. This Report will only work on closed shape components. Each component for which volumes are desired must be set up with a unique Feature Style. The GDOT GPS Grading Report.xsl Style Sheet is utilized to supply an EndArea report of the Proposed Finished Surface in a standard GDOT ASCII text file format for distribution to Contractors after the award of the contract (post-award). The GDOT GPS Grading Report generates a report on the proposed Finished Surface and does not report the Existing Surface. This file is utilized by contractors to upload data for use in Automated Grading Machines. The GDOT HEC RAS Bridge Features Report.xsl Style Sheet is utilized to supply a Station, Elevation and Offset Report from the Roadway Centerline to selected Surface Features representing the existing Bridge Geometry. This Report is then used for input of the Bridge Geometry data into HEC RAS. The GDOT HEC RAS Cross Section Geometry Report.xsl Style Sheet is utilized to supply a comma delimited Station and Elevation Report from the Roadway Centerline for use in importing Cross Sectional geometric data into HEC RAS. The Cross Sectional data is reported based on the Offset Parallel Alignments/Profiles from the Roadway Centerline through a Stream Center. 14-8
GDOT FeatureStationElevationOffset Report
GDOT Feature Volumes Report
GDOT GPS Grading Report
GDOT HEC RAS Bridge Features Report
Tools XML Reports Clearance Tools XML Reports Clearance
GDOT HEC RAS Cross Section Geometry Report

Location
Description
GDOT Ponding Report
Evaluation Cross Section Cross Section Report Tools XML Reports CTRL + Legal Description Tools XML Reports CTRL + Stakeout
The GDOT Ponding Report.xsl Style Sheet is utilized to report profile stations where the longitudinal grade < 1.0% and the road cross slope < 0.5%.
GDOT RW Table
The GDOT RW Table.xsl Style Sheet is utilized to create Right-of-Way Table text files for placement in MicroStation with the GDOT Tools Include Data Table placement macro. The GDOT Stakeout Report.xsl Style Sheet is utilized to check for Duplicate Points and supply Point information to the Surveyor for use in staking out alignments and property. The Report lists the point name, easting and northing for all points with the Feature Styles listed below. When the report is saved as an ASC file it may be used to upload the points directly into the surveyors data collector for staking in the field.
PROP_E_PAR PROP_E_RWC PROP_E_PPC TOPO_E_SLCM TOPO_E_SBNCHMK MAIN_P_SIDECL PROP_E_RWE PROP_E_RWU PROP_E_PCF TOPO_E_SLCD REQD_P_* PROP_E_RWM PROP_E_POEL TOPO_E_SNGSCM TOPO_E_SDCD MAIN_P_CONSTCL
GDOT Stakeout Report
GDOT Station-Offset Report
Tools XML Reports Clearance
The GDOT Station-Offset Report.xsl Style Sheet is utilized to supply Station and Offset information of selected Cogo Points to a selected Horizontal alignment.
14-9

Location
Description
GDOT Superelevation Data Report
Modeler Roadway Designer Superelevation Superelevation Report Tools XML Reports Surface Check Report Tools XML Reports Clearance
The GDOT Superelevation Data Report.xsl Style Sheet is utilized to provide superelevation information that was applied using the Create Superelevation Wizard. The GDOT Superelevation Data Report lists the Station, Cross Slope and Point Type (Normal Crown, Zero Cross Slope, Reverse Crown, and Full Super) for each superelevation transition location. The GDOT Surface Check Report.xsl Style Sheet is utilized to verify the tolerance and accuracy of an Existing Digital Terrain Model (original terrain surface) as compared against associated field survey points.
GDOT Surface Check Report
GDOT Vertical Clearance
The GDOT Vertical Clearance Report.xsl Style Sheet is utilized to supply the vertical clearance information from selected Cogo Points to a selected Horizontal alignment.
14-10
1 5
Additional File Deliverables
15. Additional File Deliverables

This section provides a brief overview of Additional File Deliverables which are required to be submitted when using the InRoads Design Software. Several Additional Files are generated in InRoads for use by other Offices internal to GDOT. Additional Files are also provided to Contractors when a Project is complete and let to Construction. This section covers the following topics:
Additional File Deliverables Overview InRoads File Deliverables to GDOT

o o o o o o o o Write Stakeout Data to a Data Collector Generate GDOT Deed File(s) InRoads Project Data Sheet(s) GDOT InRoads Design Data Quality Assurance Checklist
InRoads File Deliverables to Contractors

Alignment File Description(s) Alignment Report File(s) End-Area Report File(s) GPS Grading Report File(s)
15-2
15.1 Additional File Deliverables Overview

The following section depicts an overview of the Style Sheets and Reports which are required as Additional File Deliverables. In order to generate these Additional File Deliverables the following information should be adhered and followed. a) The GDOT Standard Style Sheets for generating the Additional File Deliverables are located in the following path: C:\Program Files\Bentley\InRoads Group V8.11\XML Data\GDOT\. b) For Detailed Help Instructions on using the Style Sheets please see the GDOT Style Sheet Help Files which are located in the following path: C:\InRoads Data\Style Sheet Documentation c) To generate the GDOT Stakeout Report for stakeout of R/W the following Style Sheet should be used: GDOT Stakeout Report.xsl. d) To generate the Deed output files for use in writing Deeds the following Style Sheet should be used: GDOT Deed.xsl. e) To generate the Alignment File Descriptions which depict the Alignment information (including the Curve Data and Coordinate information) for Feature Styles MAIN_P_CONSTCL and MAIN_P_SIDECL - the following Style Sheet should be used: GDOT Alignment File Descriptions.xsl. f) To generate the Alignment Report files which depict the Alignment information at 50 intervals for use by Contractors the following Style Sheet should be used: GDOT Alignment Report.xsl.
g) The End-Area Report which is submitted to Contractors for use in the Earthwork process utilizes the following Style Sheet: GDOT End-Area Report-Standard.xsl. h) To generate the GPS Grading Report file(s) for use by Contractors the following Style Sheet should be used: GDOT GPS Grading Report.xsl. i) The Project Data Sheet is a required Deliverable that should list all of the pertinent InRoads Design information. This file is used by Designers to help document associated files and data for use during the Design process. This file is also submitted as a deliverable with the InRoads project files so that users who inherit the project can easily identify project data. This file is included in the InRoadsALLV8i.exe. j) A Quality Assurance Control Checklist is also required. This is a checklist that the Designer should utilize to ensure that all pertinent Design Data is included for Project Delivery. This File is included in the InRoadsALLV8i.exe. 15-3
15.2 InRoads File Deliverables to GDOT

As mentioned previously, there are several Additional File Deliverables which are required to be submitted by the Designer for use by other Offices in the Department. The following Section contains information on how to generate the following Report Files: o o o o Write Stakeout Data to a Data Collector Generate GDOT Deed File(s) InRoads Project Data Sheet(s) GDOT InRoads Design Data Quality Assurance Checklist
15-4
15.2.1 Write Stakeout Data to a Data Collector In order to write out data from InRoads to upload into a data collector to take back to the Field the GDOT Stakeout Report.xsl Style Sheet is used. The GDOT Stakeout Report.xsl Style Sheet is utilized to check for Duplicate Points and supply Point information to the Surveyor for use in staking out alignments and property. The Report lists the point name, easting and northing for all points with the Feature Styles listed below. When the report is saved as an ASC file, it may be used to upload the points (See Feature Styles listed below) directly into the surveyors data collector for staking in the field. NOTES: a) For Detailed Instructions on using the GDOT Stakeout Report.xsl Style Sheet please see the GDOT Style Sheet Help Files which are located in the following path: C:\InRoads Data\Style Sheet Documentation b) Point Prefixes are stripped from the Points in the Report in order to facilitate upload and compatibility with the Data Collector. c) To access the Style Sheet select the following from the InRoads pull-down menu: Tools XML Reports CTRL + Stakeout d) The GDOT Stakeout Report.xsl Style Sheet should be saved with an .ASC Extension. e) The Naming Convention for the GDOT Stakeout Report will be PI#_STK.asc (Example: 123456_STK.asc). f) Points with the following Feature Styles are obtained from the InRoads project database and are written to the ASC file for upload to the Data Collector.
PROP_E_PAR PROP_E_RWC PROP_E_PPC TOPO_E_SLCM TOPO_E_SBNCHMK MAIN_P_SIDECL PROP_E_RWE PROP_E_RWU PROP_E_PCF TOPO_E_SLCD REQD_P_* PROP_E_RWM PROP_E_POEL TOPO_E_SNGSCM TOPO_E_SDCD MAIN_P_CONSTCL
Table 15.1 File Naming Convention GDOT Stakeout Report

Location: Tools XML Reports CTRL + Stakeout
File Name
Example
PI#_STK.asc
123456_STK.asc
15-5
15.2.2 Generate GDOT Deed File(s) In order to write out data from InRoads to use as the Metes and Bounds description for generation of Deeds, the GDOT Deed.xsl Style Sheet is used. The GDOT Deed.xsl Style Sheet is utilized to create an output (.OUT) file which is imported into the stand-alone GDOT Deed Writer program. The Deed Writer Program is used by the Office of Right of way to create Deeds for the purchase of Right of Way on the project. NOTES: a) For Detailed Instructions on using the GDOT Deed.xsl Style Sheet please see the GDOT Style Sheet Help Files which are located in the following path: C:\InRoads Data\Style Sheet Documentation b) Points must be stored at the PC and the PT of Curves in order to generate an accurate Metes and Bounds Deed file. c) The Points must be stored in a clockwise direction to facilitate the Deed Writing process. d) To access the Style Sheet select the following from the InRoads pull-down menu: Tools XML Reports CTRL + Legal Description e) The GDOT Deed.xsl Style Sheet Report should be saved with an .OUT Extension. f) The Naming Convention for the GDOT Deed .OUT File will be Alignment Name.out (Example: DE31.out).
Table 15.2 File Naming Convention GDOT Deed

Location: Tools XML Reports CTRL + Legal Description
File Name
Example
Alignment Name.out
DE31.out
15-6
15.2.3 InRoads Project Data Sheet(s) The Project Data Sheet is used to document the design files and data contained in the InRoads Database File(s). This documentation not only assists the Designer during the Design process but also is used by other personnel who may inherit the project in latter stages to help identify the correct design files and design objects. This Project Datasheet File should be submitted as an Additional Deliverable along with the associated InRoads Project Database File(s). NOTES: a) The Project Data Sheet is included with the InRoadsALLV8i.exe download and may be found in the following location on the hard drive: C:\InRoads Data\Standards b) The Designer should create a Documentation Folder under the C:\InRoads Data\PI Number directory. The Project Data Sheet and any additional Project Documentation should be included in this folder and submitted along with the InRoads Project Database File(s). c) The following page contains a screen capture of the Project Data Sheet:
15-7
15-8
15.2.4 GDOT InRoads Design Data Quality Assurance Checklist The GDOT InRoads Design Data Quality Assurance Checklist will be documented and submitted by the Designer or Design Consultant. This document is an overall checklist to ensure that the applicable Design Deliverables are submitted to Construction (Earthwork Coordinators) and/or GDOT Design Personnel after the Design aspect of the Project is completed. Some of the areas listed in the checklist include: Design Data submitted, Proposed DTM Surface information, Geometry Data, Templates, CrossSections, etc. The Designer is to use this checklist to verify that the Project Deliverables contain all the requisite data before submittal to Earthwork Coordinators during the Field Plan Reviews, Letting and Construction Phases.
NOTES: a) The GDOT InRoads Design Data Quality Assurance Checklist is included with the InRoadsALLV8i.exe download and may be found in the following location on the hard drive: C:\InRoads Data\Standards The GDOT InRoads Design Data Quality Assurance Checklist is available for download by navigating to the MicroStation and InRoads links from the following location:
b) The Designer should create a Documentation Folder under the C:\InRoads Data\PI Number directory. The GDOT InRoads Design Data Quality Assurance Checklist and any additional Project Documentation should be included in this folder and submitted along with the InRoads Project Database File(s). c) The following page contains a screen capture of the GDOT InRoads Design Data Quality Assurance Checklist:
15-9

Georgia Department of Transportation
P.I. Number: County:
Project Description: QA Reviewer: Phone Number:
GDOT InRoads Design Data Quality Assurance Checklist

(Instructions: In the Verified Column pull down enter YES, NO or N/A for the Verification QA Status)
CATEGORY Geometry Project -- (.ALG)
TASK The Geometry Project (.ALG) is named the PI#_Design.alg All Alignments stored have the DE Prefix for the Alignment Name All Points stored have the DE Prefix and begin numbering at 10,000 All Alignment Points are converted to COGO Points in the Geometry Project All Required R/W Alignments are stored clockwise and the Alignments close The beginning and ending point of each curve is equated to a point number All Alignments and Points are stored with standard GDOT Feature Styles
VERIFIED _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____ _____
DTM Surface(s) -- (.DTM)
The Design Surface(s) DTMs are named the PI#_Corridor Name.dtm If a Bogus Surface is utilized the DTM is named PI#_Bogus1.dtm The Finish Preference is used for the Final DTM Surface Symbology The Bogus Preference is used for the Bogus DTM Surface Symbology
Template Library (.ITL)
The Project Template Library (.ITL) is named PI#.itl All templates utilized in the Project Design are included in the Template ITL The Standard GDOT Feature Styles are used for all components and points
Roadway Design (.IRD)
The Roadway Design File (.IRD) is named PI#.ird The Roadway Corridor is named PI#_Roadway Name (or Alignment Name)
Final Deliverables -Internal
Stakeout Data Report Deed (.OUT) Files InRoads Project Data Sheet GDOT InRoads Design Data Quality Assurance Checklist
Final Deliverable -Contractor Alignment File Descriptions(s) Alignment Report Files(s) End-Area Report File(s)
15-10
15.3 InRoads File Deliverables to Contractors

As mentioned previously - when a project is complete and let to construction, there are several additional File Deliverables which are required to be submitted by the Designer for use by Contractors. The following Section contains information on how to generate the following Style Sheets: o o o o Alignment File Description(s) Alignment Report File(s) End-Area Report File(s) GPS Grading Report File(s)
NOTE: The Alignment File Descriptions, Alignment Report Files and the End-Area Report Files will be provided Pre-Award of the contract. NOTE: The GPS Grading Report File(s) will be provided Post-Award of the contract.
15-11
15.3.1 Alignment File Descriptions Text file descriptions of the Alignments with Feature Styles of MAIN_P_CONSTCL (Construction Centerline) and MAIN_P_SIDECL (Sideroad Centerline) will be provided to the Contractor. These text files will list all of the applicable Centerline Alignment information including the associated Curve Data. A Filter may be used to select the Feature Styles of MAIN_P_CONSTCL and MAIN_P_SIDECL. The Descriptions can be generated for each Alignment at the same time and included in one .TXT output file.
NOTES: a) For Detailed Instructions on using the GDOT Alignment File Descriptions.xsl Style Sheet please see the GDOT Style Sheet Help Files which are located in the following path: C:\InRoads Data\Style Sheet Documentation b) A Geometry Filter can be utilized to select all of the applicable alignments with Feature Styles of MAIN_P_CONSTCL and MAIN_P_SIDECL. c) To access the Style Sheet select the following from the InRoads pull-down menu: Tools XML Reports Geometry. d) The GDOT Alignment File Descriptions.xsl Style Sheet Report should be saved with a .TXT Extension. e) The Naming Convention for the GDOT Alignment File Descriptions will be PI#_AL.txt (Example: 123456_AL.txt). f) The following Feature Styles will be written to the Alignment File Descriptions Report:
MAIN_P_CONSTCL MAIN_P_SIDECL
Table 15.3 File Naming Convention Alignment File Descriptions

Location: Tools XML Reports Geometry
File Name
Example
PI#_AL.txt
123456_AL.txt
15-12
15.3.2 Alignment Report Files Alignment Report Files will be utilized to supply alignment information to the Contractor for use in GPS equipment. This report depicts the alignment information located at 50 Foot Station intervals at a Zero offset. The report is required for each of the alignments with Feature Styles of MAIN_P_CONSTCL and MAIN_P_SIDECL.
NOTES: a) For Detailed Instructions on using the GDOT Alignment Report.xsl Style Sheet please see the GDOT Style Sheet Help Files which are located in the following path: C:\InRoads Data\Style Sheet Documentation b) A Geometry Filter can be utilized to select all of the applicable alignments with Feature Styles of MAIN_P_CONSTCL and MAIN_P_SIDECL. c) To access the Style Sheet select the following from the InRoads pull-down menu: Tools XML Reports Geometry. d) The GDOT Alignment Report.xsl Style Sheet should be saved with an .HTML Extension. e) The Naming Convention for the GDOT Alignment Report will be PI#_Alignment Report.html (Example: 123456_Alignment Report.html). f) The following Feature Styles will be written to the Alignment File Descriptions Report:
MAIN_P_CONSTCL MAIN_P_SIDECL
Table 15.4 File Naming Convention Alignment Report Files

Location: Tools XML Reports Geometry File Name Example
PI#_Alignment Report.html
123456_Alignment Report.html
15-13
15.3.3 End-Area Report Files The GDOT End-Area Report-Standard.xsl Style Sheet is utilized to supply an End-Area report in a standard GDOT ASCII text file format for distribution to Contractors when a project is let to Construction.
NOTES: a) For Detailed Instructions on using the GDOT End-Area Report-Standard.xsl Style Sheet please see the GDOT Style Sheet Help Files which are located in the following path: C:\InRoads Data\Style Sheet Documentation b) To access the Style Sheet Select the following from the InRoads pull-down menu: EvaluationVolumes End-Area Volume. c) The GDOT End-Area Report-Standard.xsl Style Sheet should be saved with an .END Extension. d) The Naming Convention for the GDOT End-Area Report-Standard.xsl will be PI#_Alignment Name.end (Example: 123456_DE31.end).
Table 15.5 File Naming Convention End-Area Report Files

Location: EvaluationVolumes End-Area Volume File Name Example
PI#_Alignment Name.end
123456_DE31.end
15-14
15.3.4 GPS Grading Report Files The GDOT GPS Grading Report.xsl Style Sheet is utilized to supply an End-Area report of the Proposed Finished Surface in a standard GDOT ASCII text file format for distribution to the Contractor after the award of the contract (post-award).
NOTES: a) For Detailed Instructions on using the GDOT GPS Grading Report.xsl Style Sheet please see the GDOT Style Sheet Help Files which are located in the following path: C:\InRoads Data\Style Sheet Documentation b) To access the Style Sheet Select the following from the InRoads pull-down menu: EvaluationVolumes End-Area Volume. c) The GDOT GPS Grading Report.xsl Style Sheet should be saved with an .END Extension. d) The Naming Convention for the GDOT GPS Grading Report.xsl will be PI#_Alignment Name_GPS.end (Example: 123456_DE31_GPS.end).
Table 15.6 File Naming Convention GPS Grading Report Files

Location: EvaluationVolumes End-Area Volume File Name Example
PI#_Alignment Name_GPS.end
123456_DE31_GPS.end
15-15
1 6
Converting Projects from CAiCE to InRoads
16. Converting Projects from CAiCE to InRoads

This section provides a brief summary of the procedures that are required to convert a CAiCE Design Project to an InRoads Design Project. This section covers the following topics:
CAiCE to InRoads Conversion Criteria Overview CAiCE Photogrammetry/Survey Data Conversion CAiCE Design Data Conversion
16-2
16.1 CAiCE to InRoads Conversion Criteria Overview

The following section depicts an overview of the criteria of determining whether a CAiCE Project is a good candidate for conversion to an InRoads Project. There are several deciding factors which must be considered and discussed before converting a CAiCE Project. It is critical that all parties involved in the decision to convert a CAiCE Project to an InRoads Project be aware of all the data, conversion processes and conversion time required. Following is an excerpt from a Design Policy Interdepartmental Correspondence which is dated April 13, 2010. The CAICE platform will continue to be maintained by the Departments Engineering Software Group to support projects already under development with CAiCE. Projects with a database collected in CAiCE prior to May 1, 2010, may be converted to InRoads. A decision to convert from CAiCE to InRoads should be made mutually between the Project Manager, Design Phase Leader, and the Statewide Location Bureau Chief. The following section depicts some criteria to keep in mind when discussing possible CAiCE to InRoads Conversions: o There is currently no automated direct process to convert a CAiCE Survey Project to an InRoads Survey Project. The only method at this time is to convert the RAW Photogrammetry Data and RAW Field Survey Data (using customized GDOT Conversion Programs) to an InRoads format. After processing this data the Survey Data Engineer must manually re-create the Property/Parcel Alignments in InRoads which can be a very time-consuming process. o There is also no automated direct process to convert CAiCE Design Data to an InRoads format. The Designer must manually re-input all the Horizontal Alignments, Vertical Alignments, Templates, Cross-Sections, and Required R/W Alignments from Reports and Plans generated from CAICE. o There is also an InRoads Software learning curve for Surveyors, Survey Data Engineers and Designers. This in turn will extend the projected project schedule for completion. o Manpower and productivity is also a consideration. Converting a CAiCE Project to InRoads will result in Survey Data Engineers and Designers having to basically start at the beginning of a Project. Although the Photogrammetry/Survey RAW data can be converted with minimal effort (and no additional Field Survey Work) the time allotted for Survey Data Engineers and Designers to recreate the InRoads work can affect much of the Project Schedule. o As mentioned in the Design Policy Excerpt in the paragraph above Project Conversion is a mutual decision that must be determined and approved by all parties involved on a case by case basis. 16-3
16.2 CAiCE Photogrammetry/Survey Data Conversion

The following section depicts an overview of the methods used to convert a CAiCE Survey Project to an InRoads Survey Project. Please Note: ALL conversions of Photogrammetry data from CAiCE to InRoads will be performed by the Office of Design Policy and Support/Location Bureau. If the Project Manager, Design Phase Leader, and the Statewide Location Bureau Chief determine a need for project conversion the Project Manager should contact the Engineering Management/Operations Manager of the Office of Design Policy and Support/Location Bureau for details. The Location Bureau will then contact the District Location Engineer and/or Survey Data Engineer for the conversion of the Field Survey Collected/Property input data from CAiCE to InRoads. ALL conversions of the Field Survey Collected and Property input data from CAiCE to InRoads will be performed by the District SDEs. It has been determined that the best method for converting CAiCE to InRoads projects is to utilize the base RAW AMSA and ASC Files (which contain the old CAiCE Feature Codes) for the conversion. Please note that any processing done in CAiCE will be lost when going back to the AMSA and/or ASC file. There are several reasons for utilizing the RAW AMSA and ASC Files instead of a direct CAiCE to InRoads Conversion: Issues with direct CAiCE to InRoads Conversion: There are significant differences between CAiCE and InRoads as it pertains to the creation of Digital Terrain Models. Although the standard TIN (Triangulated Irregular Network) method is utilized the format and naming conventions of the points and breaklines are considerably different from CAiCE. Therefore a direct DTM import from CAiCE to InRoads is not feasible. There has been a change in the AMSA and ASC Feature codes for InRoads. The AMSA and ASC codes have been updated and consolidated to correspond more closely with InRoads. CAiCE projects will contain the old CAiCE AMSA and ASC codes. Therefore the importation of CAiCE projects into InRoads is not feasible because of the discrepancy in Feature Codes. The CAiCE codes will not import into InRoads correctly. The conversion of the (CAiCE format) RAW AMSA and ASC files will ensure an accurate translation of old CAiCE Survey data to new InRoads Survey data. This will entail rebuilding the DTM and resolving any crossing segments, etc. but it will also result in an accurate conversion method. Please Note: **The SDE will also have to reproduce the input of the entire Parcel (Property Data). This will basically entail that the SDE will have to manually input all of the property into InRoads based on the existing R/W and the associated deeds/plats in order to reproduce what was in CAiCE. 16-4
16.3 CAiCE Design Data Conversion

The following section depicts an overview of the processes used to convert a CAiCE Design Project to an InRoads Design Project. Please Note: As mentioned in the Design Policy Excerpt Project Conversion is a mutual decision that must be determined and approved by all parties involved on a case by case basis. If a Project meets the decided upon criteria to convert the Photogrammetry/Survey Data must be converted following the procedure depicted in the previous Section. If Design Work Has previously been performed in CAICE: Once the Designer receives the converted Survey Project the Designer will manually reinput all of the Design Data that has been performed in CAiCE up to this point. As mentioned previously there is no direct Design Conversion. The Designer should use CAICE Reports and Plans generated from CAiCE to re-input the applicable Design Data. The Horizontal Alignments, Vertical Alignments, Templates, Cross Sections, Construction Limits, Required R/W will all have to be converted to InRoads by using manual inputs. If No Design Work Has previously been performed in CAICE: Once the Designer receives the converted Survey Project the Designer will start a Design project using the standard InRoads Design Processes. There will be no conversion of data necessary. The Survey Data will be converted to InRoads standards and the Designer will utilize the InRoads Software for all Preliminary and Final Design of the project. For Information Only: There is a utility in CAiCE and InRoads called LandXML that can export some of the Data from CAiCE to InRoads but due to the differences in the Software(s) (such as Point Naming processes, Feature Styles, DTMs, etc.) the data does not translate over without having to still perform additional manual input. The best method to utilize at this time in the conversion process is the manual re-entry of the Design Data.
16-5

InRoads Design Guidelines

Uploaded by

Copyright:

Available Formats

InRoads Design Guidelines

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

InRoads Design Guidelines

Uploaded by

Copyright:

Available Formats

InRoads Design Guidelines

Georgia Department of Transportation

Office of Design Policy & Support

Developed By Product Version Document Revision Release Date

This Page Left Intentionally Blank