CADD Engineering Standards - Ohio Department of Transportation

More documents

Recommendations

Info

$Page 1 of 8 Traffic Survey Report 12/29/2006 file://X:\TC\Traffic ...$

January 18, 2013 209 GEOPAK Design and Computation Manager Database 209.1 General The primary purpose of the GEOPAK Design and Computation Manager (D&C Manager) is to assist the user with the placement of MicroStation elements according to a set of predefined CADD standards. ODOT provides a standard D&C Manger database, ODOT.ddb that has been configured according to the CADD standards outlined in this manual. The ODOT.ddb can be obtained from the ODOT CADD Standards website. The D&C Manager can be used to facilitate the placement of curvilinear features or point features represented by cells according to ODOT standards. For more information on the use of the GEOPAK Design and Computation Manager, see the ODOT GEOPAK Road 1 Training Guide on the ODOT CADD Standards website. Users are not permitted to edit the ODOT.ddb. 210 GEOPAK Survey Manager Database 210.1 General The GEOPAK Survey Manager Database is primarily used to assist the user with mapping field survey codes to the appropriate MicroStation symbology according to a predefined set of CADD Standards and Survey field codes. 210.2 Survey Field Codes ODOT has developed a set of standardized field codes for all survey data submitted to the Department. The list of standard field codes for ODOT projects can be obtained from the ODOT CADD Standards website. Users are not permitted to use other field codes to supplement the ODOT code list for any project related survey data submitted to or exchanged with ODOT. 210.3 Survey Manager Database ODOT has developed a standard Survey Manager Database, ODOT.smd, for use with GEOPAK Survey Software to map the field codes contained within a set of survey data to the appropriate symbology in a MicroStation design file according to the CADD Standards set forth within this manual. The ODOT.smd can be obtained from the ODOT CADD Standards website. Users are not permitted to edit ODOT.smd. 50 ODOT CADD Engineering Standards
211 Working Units 211.1 General January 18, 2013 MicroStation lets you draw in "real world" units; feet, inches, meters, etc. These real world units are called working units. Working units are expressed as Master Units (the largest units in common use in a design file, such as feet) and fractional Sub Units (such as inches). The default definition for a foot in MicroStation is the International Foot. The U.S. Survey Foot definition can be defined by use of a unit definition file. ODOT has developed a standard unit definition file, ODOT_Units.def, to define the U.S. Survey Foot as the standard Master Unit. This file can be obtained from the ODOT CADD Standards website. The active unit definition file is specified by the configuration variable MS_CUSTOMUNITDEF. MicroStation design files used in plan preparation shall use the following standard working units as defined in the ODOT seed files and in ODOT_Units.def: Unit Names Label Master Unit: Survey Feet ‘ Sub Unit: Inches “ The ODOT seed files have been defined with a standard resolution setting of 12000 per Survey Foot. This setting shall not be changed by the user. ODOT’s seed files are set up with the standard working units described above. Deviation from these working units is not permitted. 212 Global Origin 212.1 General Elements in the design file are drawn by placing data points. Each data point placed in the design plane has associated X (easting), Y (northing) and Z (elevation, 3D files only) positions or coordinates. The design plane is simply a Cartesian coordinate system upon which your design model lies. In the ODOT Seed files, the point called the Global Origin is set to the design plane's exact center (178,956.9707, 178,956.9707) and assigned the coordinates 0,0 (2D files) and 0,0,0 (3D files). The Global Origin is defined in ODOT’s Seed Files and should never be changed for ODOT projects. ODOT CADD Engineering Standards 51
Page 1:
Ohio Department of Transportation C
Page 5 and 6:
Table of Contents January 18, 2013
Page 7 and 8: January 18, 2013 307 GEOPAK Project
Page 9 and 10: 100 GENERAL 101 Introduction Januar
Page 11 and 12: 200 CADD STANDARDS 201 Installation
Page 13 and 14: Alternate Configuration Files There
Page 15 and 16: 202.3 ByLevel Considerations Januar
Page 17 and 18: Bridge General Gen - SV Bridge Pres
Page 19 and 20: 202.5 Priority and Transparency Jan
Page 21 and 22: January 18, 2013 You do not need to
Page 23 and 24: Transparency January 18, 2013 Trans
Page 25 and 26: January 18, 2013 The Transparency v
Page 27 and 28: 204.2 Types of Line Styles ODOT CAD
Page 29 and 30: January 18, 2013 The following deta
Page 31 and 32: GEOPAK Placement (Existing and Prop
Page 33 and 34: Survey Processing (Existing Basemap
Page 35 and 36: January 18, 2013 When attaching Ref
Page 37 and 38: Bridge Design Files: January 18, 20
Page 39 and 40: 206.3 Cell Libraries January 18, 20
Page 41 and 42: ODOT CADD Standards contain two (2)
Page 43 and 44: January 18, 2013 The following proc
Page 45 and 46: January 18, 2013 The following opti
Page 47 and 48: Survey Processing (Existing Basemap
Page 49 and 50: January 18, 2013 Changing the Annot
Page 51 and 52: 207.2 Text Size January 18, 2013 St
Page 53 and 54: January 18, 2013 Selecting a Text S
Page 55 and 56: January 18, 2013 In order to apply
Page 57: 208 Seed Files 208.1 General Januar
Page 61 and 62: 214 GEOPAK Criteria Files 214.1 Gen
Page 63 and 64: 300 FILE MANAGEMENT 301 General 301
Page 65 and 66: January 18, 2013 Figure 302-1 Minor
Page 67 and 68: January 18, 2013 Figure 302-3 Proje
Page 69 and 70: January 18, 2013 Figure 302-9 Struc
Page 71 and 72: 303 References 303.1 General Januar
Page 73 and 74: 303.2.1 Types of Models January 18,
Page 75 and 76: 303.2.3 Model Properties January 18
Page 77 and 78: 303.2.4 Referencing Models January
Page 79 and 80: January 18, 2013 Final plan sheets
Page 81 and 82: 304.3 File Name Format January 18,
Page 83 and 84: Supplemental Description Examples:
Page 85 and 86: January 18, 2013 4. To save these c
Page 87 and 88: Figure 304-1 File Name Type Codes B
Page 89 and 90: SIGNAL SHEETS Notes - CN General Su
Page 91 and 92: 306.2 GEOPAK COGO Element Names Jan
Page 93 and 94: COGO Right of Way Elements Chains R
Page 95 and 96: (1) Project Name: For this example,
Page 97 and 98: 400 PLOTTING 401 General 401.1 Gene
Page 99 and 100: 401.2.3 Shading The following are o
Page 101 and 102: 502.2 Saved View January 18, 2013 W
Page 103 and 104: Figure 503-2 504 CADD File Requirem
Page 105 and 106: January 18, 2013 A sample ASCII rep
Page 107 and 108: 504.3 Vertical Alignment ASCII Repo
Page 110 and 111:
January 18, 2013 Each horizontal al
Page 112 and 113:
January 18, 2013 504.6 Monumentatio
Page 114 and 115:
January 18, 2013 Left Offset/Right
Page 116 and 117:
January 18, 2013 The XS Reports dia
Page 118 and 119:
January 18, 2013 Select the Apply b
Page 120 and 121:
Appendix A - CADD Information Table
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 321 and 322:
Appendix E - Electronic Submission
Page 323 and 324:
APPENDIX F - Level Scale Factors Re
show all

CADD Engineering Standards - Ohio Department of Transportation

Create successful ePaper yourself

Delete template?

Save as template?