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 If a bridge basemap is used, a separate basemap design file is required for each bridge on the project. A basemap is also used for profiles and cross section graphics. Unlike plan view basemap files, profile and cross section basemap design files shall contain both the existing and proposed information in one file. The profile basemap may be used to plot all the profiles for the entire project in one file. It is not necessary to create separate profile basemaps for each alignment in the project. Profiles should always be plotted in their own design file and never combined with any other basemap. After generating the profile basemap, do not delete the profile cell. The profile cell is placed on the level “GK_Cells” as defined by the Configuration Variable GPK_LEVEL_PROFILE_CELL and can be toggled on or off using Level Manager, if required. If the configuration variable is not defined, the profile cell is placed on the level “Default”. A separate cross section basemap should be used for each alignment in the project. Cross sections for multiple alignments should never be plotted in the same cross section basemap. Cross sections should always be plotted in their own design file and never combined with any other basemap. After generating the cross sections, do not delete the cross section cells. Cross section cells are placed on the “GK_Cells” level as defined by the Configuration Variable GPK_LEVEL_XS_CELL and can be toggled on or off using Level Manager, if required. If the configuration variable is not defined, cross section cells are placed on the level Default. All basemap design files shall be stored in the appropriate discipline specific basemaps sub-directory and shall not be copied into another sub-directory for editing or referencing. See Section 302.1 Standard Directory Structure, for guidance on maintaining Survey Basemaps for Roadway and Bridge Projects. Standard design file names for Basemaps are detailed in Section 304.3 File Name Format. 303.4 Sheet Design Files Sheet design files are used to assemble the plan sheets that are used for plotting a set of plans. The Sheet design files are assembled by referencing Design models from the necessary basemap design files to the sheet model of the sheet file. Sheet border cells and annotation are typically placed in the sheet model. For Roadway projects including the Bridge site plan and Geotechnical Exploration sheets when attaching basemap Design models to the Sheet models the user shall not scale, move, or rotate the basemap reference attachment. Basemap Design models shall be attached using the MicroStation Coincident- World setting. If a rotated plot view is required, the user shall rotate the sheet design file view for proper plot orientation. The sheet border cells shall be placed in the rotated view. All reference file clipping shall be done in the rotated view. For Bridge sheets, a single design file may include both existing and proposed plan view information. When developing Bridge profiles (including profiles for culverts greater than 10 feet in diameter or span), place the profile in a design model. Reference the profile from the Design model into the Sheet model (Site Plan or Culvert Detail sheet). All profile labeling shall be completed in the Sheet model. 70 ODOT CADD Engineering Standards
January 18, 2013 Final plan sheets shall be in the Sheet Model. No items other than what is shown on the final plotted sheet are allowed to be shown in the Sheet Model. Any detail shown in the final plotted sheet shall be represented at a 1:1 scale in either the Design model or Sheet model of the corresponding file. The purpose of having the existing details drafted or referenced at a 1:1 scale is to facilitate the electronic transmission of design data (via email or equivalent) without providing the entire project directory. If necessary, the designer can merge the referenced details within the design file. Each plan sheet shall be contained within the Sheet Model. Therefore, each plan sheet will be separated into individual design files when submitted to the Department. When sheet design files are submitted to the Department, no other graphics are permitted in the Sheet model other than the graphics representing the final plotted sheet. All extra graphics used to generate the sheet, or old versions of the sheet, should be deleted or moved to a design model. No extra reference attachments that are not a part of the final sheet are permitted to be attached to the sheet model. In order to ensure that reference file attachments are maintained when moving project files from the original project directory to another location, such as a CD for submission or to an archive directory, references shall be attached using relative paths. The user shall not use MicroStation or GEOPAK options to “Save Full Path” for reference attachments. All completed sheet design files submitted to or exchanged with ODOT shall use references where applicable. It is not recommended that users copy referenced graphics into the sheet files for the completed sheet design files submitted to ODOT. ODOT CADD Engineering Standards 71
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 and 58: 208 Seed Files 208.1 General Januar
Page 59 and 60: 211 Working Units 211.1 General Jan
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: 303.2.4 Referencing Models January
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 128 and 129:
Appendix A - CADD Information Table
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?