CADD Engineering Standards - Ohio Department of Transportation
CADD Engineering Standards - Ohio Department of Transportation CADD Engineering Standards - Ohio Department of Transportation
January 18, 2013 304 File Naming Conventions 304.1 General The efficient sharing and transfer of information from consultants/contractors to ODOT and vice versa relies on the use of a systematic file naming convention. This section outlines a consistent, comprehensive file naming convention for graphic and associated files used in the CADD environment, which shall be used for all projects. With such large quantities of data being created, it is essential that operators create their new files with names that signify the content of each. Therefore, each sheet of the plan shall be contained in its own separate design file. Standard naming conventions shall be used for all design files, standard input files and GEOPAK criteria files. Document all file names, both standard and project specific, in the Project Index file (See Section 503 Project Index File). In the event a particular file type for the project is not addressed by this manual, use the file naming convention as a template for selecting an appropriate name or contact the Office of CADD and Mapping Services, CADD Section for assistance. In order to avoid conflicting attachments of reference files, there shall be no duplicate file names within the project directory structure or copies of the same file within the project directory. It is not permissible to copy the same basemap design files into multiple discipline specific sub-directories. 304.2 File Extensions Standard file name extensions for information submitted to or exchanged with ODOT shall be as follows: File Type Extension MicroStation design files .dgn MicroStation cell libraries .cel MicroStation/GEOPAK Resource file .rsc GEOPAK Criteria files .x GEOPAK Cross Section Input files .inp GEOPAK GPK Files .gpk GEOPAK Triangle Models .tin Postscript Sheet Image Files .ps Adobe Acrobat Files .pdf Microsoft Word Documents .doc or .docx Microsoft Excel Spreadsheets .xls or .xlsx Microsoft Project files .mpp XML files .xml For file types not listed above, the default file extension defined by the software shall be used. 72 ODOT CADD Engineering Standards
304.3 File Name Format January 18, 2013 ODOT has defined the following naming convention to be used on all design files submitted to, or exchanged with the Department. It is not permissible to use special characters (i.e. @, #, -, >, +, %, etc.) in file names. Standard Plan Insert sheets shall retain the name designated by the issuing office. Standard Design File Naming Format nnnnnaa###.dgn nnnnn = Five (5) digit PID Number aa = Two (2) letter code identifying the plan sheet type ### (see Figure 304-1 File Name Type Codes) = Three (3) digit number identifying the number of drawings of the same type. The three digit number is required even if there is only one drawing of a particular type in the plan set. Examples: 12345BE001.dgn 12345GP005.dgn Bridge Design File Naming Format rrr_nnnnsaa###.dgn rrr = Three (3) digit route number nnnn = Four (4) digit SLM of the structure without the decimal point. s = One (1) digit code (For twin structures: L for Left, R for Right. C for collector/distributor roads or twin structures combined in the same directory, P for Ramps.) aa = Two (2) digit Bridge plan sheet type ### (see Figure 304-1 File Name Type Codes) = Three (3) digit number identifying the number of drawings of the same type. The three digit number is required even if there is only one drawing of a particular type in the plan set. Examples: 071_0546LPI002.dgn 071_0546RSP001.dgn Wall Design File Naming Format nnnnn_yyyaa###.dgn nnnnn = Five (5) digit PID Number yyy = Three (3) digit wall number (three digits required and maximum). aa = Two (2) digit wall plan sheet type ### (see Figure 304-1 File Name Type Codes) = Three (3) digit number identifying the number of drawings of the same type. The three digit number is required even if there is only one drawing of a particular type in the plan set. Examples: 12345_001WP005.dgn 12345_001WS001.dgn ODOT CADD Engineering Standards 73
- 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 and 78: 303.2.4 Referencing Models January
- Page 79: January 18, 2013 Final plan sheets
- 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: 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
304.3 File Name Format<br />
January 18, 2013<br />
ODOT has defined the following naming convention to be used on all design files submitted to, or<br />
exchanged with the <strong>Department</strong>.<br />
It is not permissible to use special characters (i.e. @, #, -, >, +, %, etc.) in file names.<br />
Standard Plan Insert sheets shall retain the name designated by the issuing <strong>of</strong>fice.<br />
Standard Design File Naming Format<br />
nnnnnaa###.dgn<br />
nnnnn = Five (5) digit PID Number<br />
aa = Two (2) letter code identifying the plan sheet type<br />
###<br />
(see Figure 304-1 File Name Type Codes)<br />
= Three (3) digit number identifying the number <strong>of</strong> drawings <strong>of</strong><br />
the same type. The three digit number is required even if<br />
there is only one drawing <strong>of</strong> a particular type in the plan set.<br />
Examples:<br />
12345BE001.dgn<br />
12345GP005.dgn<br />
Bridge Design File Naming Format<br />
rrr_nnnnsaa###.dgn<br />
rrr = Three (3) digit route number<br />
nnnn = Four (4) digit SLM <strong>of</strong> the structure without the decimal point.<br />
s = One (1) digit code (For twin structures: L for Left, R for Right. C for<br />
collector/distributor roads or twin structures combined in the same<br />
directory, P for Ramps.)<br />
aa = Two (2) digit Bridge plan sheet type<br />
###<br />
(see Figure 304-1 File Name Type Codes)<br />
= Three (3) digit number identifying the number <strong>of</strong> drawings <strong>of</strong><br />
the same type. The three digit number is required even if<br />
there is only one drawing <strong>of</strong> a particular type in the plan set.<br />
Examples:<br />
071_0546LPI002.dgn<br />
071_0546RSP001.dgn<br />
Wall Design File Naming Format<br />
nnnnn_yyyaa###.dgn<br />
nnnnn = Five (5) digit PID Number<br />
yyy = Three (3) digit wall number (three digits required and<br />
maximum).<br />
aa = Two (2) digit wall plan sheet type<br />
###<br />
(see Figure 304-1 File Name Type Codes)<br />
= Three (3) digit number identifying the number <strong>of</strong> drawings <strong>of</strong><br />
the same type. The three digit number is required even if<br />
there is only one drawing <strong>of</strong> a particular type in the plan set.<br />
Examples:<br />
12345_001WP005.dgn<br />
12345_001WS001.dgn<br />
ODOT <strong>CADD</strong> <strong>Engineering</strong> <strong>Standards</strong> 73