CADD Engineering Standards - Ohio Department of Transportation
CADD Engineering Standards - Ohio Department of Transportation CADD Engineering Standards - Ohio Department of Transportation
January 18, 2013 503 Project Index File 503.1 General Whenever files are submitted or exchanged with the Department, a Project Index file in Microsoft Excel format shall be provided containing design file and coordinate geometry information as shown in Figure 503-1 and Figure 503-2. The Project Index file is also required for internal projects when the project is archived. ODOT provides a custom program, ODOT_ProjectIndex.mvba that can be used to create the Project Index File. This program, including documentation, is available on the ODOT CADD Standards Website. The program automatically establishes hyperlinks to facilitate opening design files by selecting the file name within the Project Index File. The Hyperlink Base directory may also be updated to specify the location where the project is located. See the program documentation for information regarding updates to the Hyperlink base directory. The program is based on the ODOT standard file structure and file naming convention listed in this manual. Any modifications to the file structure or file names will render the program nonfunctional. Plan sheet descriptions should include station ranges where appropriate. The Project Index file shall be stored in the \admin\spreadsheets directory using the following naming convention: nnnnnIndex.xls nnnnn = Five digit PID Number Figure 503-1 94 ODOT CADD Engineering Standards
Figure 503-2 504 CADD File Requirements for Design and Construction 504.1 General January 18, 2013 Section 1503 of The Location and Design Manual, Volume Three – Highway Plans details the file types required for CADD and electronic files submitted to the Department for Minimal, Minor, and Major projects as defined by the Old Project Development Process (PDP) Manual and Paths 2, 3, 4, and 5 for the New PDP. When electronic files are required, the files shall conform to the requirements detailed throughout this manual with the additional requirements specified in this section. 504.2 Horizontal Alignment ASCII Reports When horizontal alignment reports in ASCII text format are required, the following information shall be included in the ASCII reports: • A listing of all COGO elements contained in the chain. • Northing and Easting coordinates, and stations for all horizontal key points (PI, PC, PT, SC, CS, CC, etc.) • Bearings and distances between all key points. • Curve and Spiral data containing the information defined in the Location and Design Manual, Volume 3 - Highway Plans, Figures 1303-1 and 1303-2. • Station Equation values and coordinates. • All stations, distances, and coordinates shall be shown to three decimal places. • All bearings shall be shown to one tenth of one second. ODOT CADD Engineering Standards 95
- 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 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: 502.2 Saved View January 18, 2013 W
- 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: Appendix A - CADD Information Table
- Page 124 and 125: Appendix A - CADD Information Table
- Page 126 and 127: Appendix A - CADD Information Table
- Page 128 and 129: Appendix A - CADD Information Table
- Page 130 and 131: Appendix A - CADD Information Table
- Page 132 and 133: Appendix A - CADD Information Table
- Page 134 and 135: Appendix A - CADD Information Table
- Page 136 and 137: Appendix A - CADD Information Table
- Page 138 and 139: Appendix A - CADD Information Table
- Page 140 and 141: Appendix A - CADD Information Table
- Page 142 and 143: Appendix A - CADD Information Table
- Page 144 and 145: Appendix A - CADD Information Table
- Page 146 and 147: Appendix A - CADD Information Table
- Page 148 and 149: Appendix A - CADD Information Table
- Page 150 and 151: Appendix A - CADD Information Table
January 18, 2013<br />
503 Project Index File<br />
503.1 General<br />
Whenever files are submitted or exchanged with the <strong>Department</strong>, a Project Index file in Micros<strong>of</strong>t Excel<br />
format shall be provided containing design file and coordinate geometry information as shown in Figure<br />
503-1 and Figure 503-2. The Project Index file is also required for internal projects when the project is<br />
archived.<br />
ODOT provides a custom program, ODOT_ProjectIndex.mvba that can be used to create the Project<br />
Index File. This program, including documentation, is available on the ODOT <strong>CADD</strong> <strong>Standards</strong> Website.<br />
The program automatically establishes hyperlinks to facilitate opening design files by selecting the file<br />
name within the Project Index File. The Hyperlink Base directory may also be updated to specify the<br />
location where the project is located. See the program documentation for information regarding updates<br />
to the Hyperlink base directory.<br />
The program is based on the ODOT standard file structure and file naming convention listed in this<br />
manual. Any modifications to the file structure or file names will render the program nonfunctional.<br />
Plan sheet descriptions should include station ranges where appropriate.<br />
The Project Index file shall be stored in the \admin\spreadsheets directory using the following naming<br />
convention:<br />
nnnnnIndex.xls<br />
nnnnn = Five digit PID Number<br />
Figure 503-1<br />
94 ODOT <strong>CADD</strong> <strong>Engineering</strong> <strong>Standards</strong>
Change language