How To Get Data Out Of A Section Drawing On Civil 3D 2014

WisDOT Civil 3D Help Contents IMPORTANT: STWARE PROBLEM REPORT... 5 Corridor Data Not Dynamic in Section Views (updated 04/17/2015)... 5 Explanation of the Issue... 5 Fix... 5 Remaining Issues and Workarounds... 5 Civil 3D 2014 Sites and Feature Lines Disappear (updated 04/21/2015)... 5 Explanation of the Issue... 5 Fix... 6 Remaining Issues and Workarounds... 6 Project Drawing Migration Civil 3D 2012 to 2014... 6 Project version migration... 6 Important potential changes between Civil 3D versions (updated 04/21/2015)... 6 New drawing format... 7 No backward compatibility... 7 Data Shortcut functionality changes... 7 Data Shortcut project migration Best Practices... 7 Factors to consider in project migration... 8 Before beginning the migration conversion to 2014... 8 Clean and fix 2012 Project drawings and shortcuts first... 8 Make a copy of the project before migrating... 9 Project drawing migration... 9 Order of migration operations... 9 To save drawings with Civil 3D objects that are referenced to in other drawings... 10 To save drawings that are being used only as Xrefs... 12 Updating a C3D 2012 Corridor DWG into a C3D 2014 DWG... 12 How to Re-path all subassemblies within project corridor drawings... 12 WisDOT Civil 3D 2014 User Readme... 13 Civil 3D Standards Updates... 13 Before using the New WisDOT Parts Catalog... 13 Raster Design... 13 Page 1 of 107 Last updated: 6/18/2015

WisDOT Templates for Different dwg File Types... 13 Wis-Manager Palette Group Performance Problem (updated 04/21/2015)... 14 Custom Palettes from Civil 3D 2012... 14 When Civil 3D Locks Up or crashes (updated 06/03/2015)... 14 Using the ClearAutodeskCache Tool... 16 What does this tool do?... 16 What folders does it clear?... 16 How to use this tool and when... 16 Temporary Fix for Missing Point Code Labels... 17 Explanation of the Defect with Point Code Labels... 17 Temporary Labeling Fix... 17 What to know about the WisDOT2014 Settings Profile... 18 To import or re-import the profile:... 19 Creating your own User Profile & Creating your own user Palettes (changed 04/17/2015)... 20 Project Data... 20 Translate DGN to DWG Workflow Using Civil 3D... 21 AutoCAD Civil 3D 2014... 21 Import to AutoCAD... 21 Translate DWG to DGN Workflow using Civil 3D... 23 AutoCAD Civil 3D 2014... 23 Project data workflow map (added 04/17/2015)... 29 Moving Civil 3D Project Files, Directories, and Data Shortcuts (added 04/17/2015)... 29 Transfer Files and Directories... 29 Use the Data Shortcuts Editor... 29 Reset Shortcut History and Folders... 32 Merging Civil 3D Project Files, Directories, and Data Shortcuts (added 04/17/2015)... 33 Rename Existing Directory and Transfer Files... 33 Use the Data Shortcuts Editor... 34 Merge Project Files... 37 WisDOT Subassemblies... 39 WisDOT Subassemblies and Superelevation (Civil 3D 2012 and beyond)... 39 WisDOT Subassembly Inputs... 42 Case 1 Single lane ramp, crown at lane edge, planar subgrade... 43 Case 2: Undivided Roadway with crown... 46 Page 2 of 107 Last updated: 6/18/2015

Case 3: Divided Roadway with median, baseline at median edge or center of median, crown between lanes... 47 Frequently Asked Questions... 51 Modeling... 53 Roadway Modeling Workflow Tips and Best Practices (added 04/17/2015)... 53 Roadway Modeling Tip Videos (added 06/18/2015)... 60 Modeling Crossovers... 61 Crossover Geometry... 61 Crossover Setup Surfaces... 61 Crossover Top Surface... 63 Crossover Datum Surface... 67 Pipe Networks... 70 Culvert pipes summary (updated 6/12/15)... 70 Storm Sewer Summary (updated 6/12/15)... 71 Storm and Sanitary Analysis (SSA)... 72 Project Options Settings for Storm Sewer... 72 Analysis Options Settings for Storm Sewer... 72 Other Storm Sewer Tips/Hints... 72 Sheet Layouts and Sheet Sets (added 06/03/2015)... 72 Subset Sheet Layouts... 72 Using Subset Sheet Layouts with Sheet Sets... 73 Layouts Best Practice... 76 Changing existing custom layout fields to Subset fields... 76 Exporting GIS Data (added 06/03/2015)... 77 Converting Civil 3D Parcels to GIS Shapefiles... 77 Verify the Coordinate System... 77 Export Civil 3D Objects to SDF... 77 Import SDF File into New Drawing... 78 Export Polylines with Attributes to a Shapefile... 79 WisDOT Civil 3D Linetypes (Updates added 10/05/2014)... 81 Linetype scale reference... 81 Linetype Scale... 81 MSLTSCALE... 81 Page 3 of 107 Last updated: 6/18/2015

PSLTSCALE... 82 CELTSCALE... 82 Working with Existing Files... 82 Settings for previous Templates... 82 Importing Older Linetypes into Older Drawings... 82 Workflow for Updating New Linetypes into Older Drawings... 84 Updating Layers with New ByLayer Symbology (added 10-05-14)... 86 Workflow to update Xref files with old linetypes... 90 Working with the New Template... 90 Settings for New Templates... 90 Workflows for True size Linetypes... 90 Annotative Linetypes... 91 Linetypes Best Practices... 92 Migrating blocks between Civil 3D versions (added 04/17/2015)... 92 WORKFLOW 1 Migrating a small number of blocks... 92 Start a new block library drawing with 2014 template... 92 Insert older blocks using Design Center... 93 WORKFLOW 2 Migrating many blocks... 93 Start a new block library drawing with 2014 template... 93 Insert and explode existing block library drawing... 93 Clean up the new block library drawing... 94 Data Shortcut Best Practices (added 04/17/2015)... 95 Migrating a Project From Civil 3D 2012 to Civil 3D 2014... 95 Moving a Project Location... 96 Renaming or Moving Individual Project Files... 96 Renaming Individual Drawing Objects... 96 Incorporating External Drawings into a Project... 96 Notable difference between Data Shortcuts in Civil 3D 2012 and in Civil 3D 2014... 96 Updating settings and styles in production DWG files... 97 Civil 3D Styles and Drawing Settings Update... 97 AutoCAD Standards Update... 98 Using Design Center to transfer layouts from one dwg file to another (changed 04/17/2015)... 101 Appendix A Layers that changed linetypes... 102 Page 4 of 107 Last updated: 6/18/2015

Summary There are many good things to know about using Civil 3D that don t fit well into training material. This may include tips and tricks, troubleshooting, system settings, or processes that happen very frequently, such as importing and exporting files. This is the type of material found in this document. As new versions of Civil 3D are adopted, information about new features, best practices and adoption guidelines, as well as topics described above will be added to the specific Civil 3D Version User Readme section. IMPORTANT: STWARE PROBLEM REPORT Corridor Data Not Dynamic in Section Views (updated 04/17/2015) Explanation of the Issue Civil 3D 2014 has a defect which affects corridor XREFs in section views. The corridor objects do not update dynamically in the section views after changes are made in the corridor drawing and the XREF is reloaded in the section drawing. In the WisDOT workflow, corridors are xrefed into plan sheet section view dwgs to provide automated offset/elevation labels, and slope labels. If you have a section view dwg that was developed in C3D2014, the O/E and Slope labels in the section views may not be dynamically linked to the corridor, meaning these labels may be displaying incorrect values. Any pdf plots of plan sheet section view drawings done in C3D2014 might have incorrect labels also. Fix Autodesk has issued a software fix, and this has resolved the first issue above. Corridor edits are now reflected in the section views after the XREF is reloaded. This update has been applied to internal computers. The fix for external customers is found in wisdot-c3d14win7-64-importfiles.exe Remaining Issues and Workarounds Corridor objects still linger in section views when the XREF is detached. In order to get this data out of the section views follow this procedure: Detach the XREF Save and close the section drawing Reopen the section drawing Open the SAMPLE MORE SOURCES dialog box for the sample line group, and click Apply and OK Section styles still cannot be changed in the SAMPLE MORE SOURCES dialog box. Instead, change these in the VIEW GROUP PROPERTIES which is the most likely place this would be done anyway. Also, the corridor objects remain in the section views even if the XREF is completely detached. One last issue is that section styles cannot be changed in the SAMPLE MORE SOURCES dialog box after they have been added to the section views Civil 3D 2014 Sites and Feature Lines Disappear (updated 04/21/2015) Explanation of the Issue There is a known issue with the wisdot14.dwt that was developed using the Autodesk ACAD.dwt as its starting point. Using the ACAD.dwt template causes issues with sites becoming corrupt and disappearing. Once an audit is ran, the corresponding feature lines may get removed. Page 5 of 107 Last updated: 6/18/2015

Fix There is a fix for this. The hotfix for this has been updated on WisDOT devices as of 04-2015. 1. For external use download and extract the following package: ftp://ftp.dot.wi.gov/dtsd/bpd/methods/civil3d-2014-win7-64/wisdot-c3d14win7-64-importfiles.exe. 2. Close Civil 3D 3. On the device to be updated, browse to C:\Program Files\Autodesk\Autodesk AutoCAD Civil 3D 2014 4. Change the extension of the existing AeccLand.dbx and AeccvBase.dbx files to.old, or move them to an archive location. 5. Browse to the extracted folder; \wisdot-c3d14win7-64-importfiles\autodesk-software-fixes\site- Feature-line-Fix folder 6. Copy the new AeccLand.dbx and AeccvBase.dbx files to C:\Program Files\Autodesk\Autodesk AutoCAD Civil 3D 2014. 7. The date stamp for these file should be 3/27/2015 Please refer to the following link for further information: http://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/sites-are- Disappearing-but-not-Feature-Lines-until-AUDIT.html Remaining Issues and Workarounds This fixes disappearing feature lines and sites after the fix is applied, and cannot bring back feature lines that have already disappeared. Those will need to be rebuilt. Project Drawing Migration Civil 3D 2012 to 2014 Project version migration Project migration is a choice that requires certain steps and processes be followed to ensure that all files are functioning correctly after migration. The process of changing a project between Civil 3D versions with different drawing formats needs to be thought of in terms of a complete project-based activity. This means: Additional bugs and hot fixes may need to be addressed through changes in workflows. Review the section; Important: Software Problem Report in the help document. Backward compatibility between 2012 and 2014 does not readily exist. Everyone working on a migrated project needs to be using the new version files for that project. This means not only Project Development staff, but also Technical Services, Planning, Consultants, etc. Once the decision to migrate the project is made, All DWGs, Data Shortcuts, and referenced DWGs that will still need to be edited or accessed in a project must be converted. This may require updates to base drawings created by others. The time and effort to plan and execute the project migration may require more than a few hours. Scheduling one day for project migration activities would be appropriate for most projects. Migrating project drawings involves a few more considerations besides the save-as steps and order of operations to perform the processes. Migrating all the necessary drawings can be a significant effort, and the variables described in the next sections should be recognized and understood before moving forward with the migration. Important potential changes between Civil 3D versions (updated 04/21/2015) This Civil 3D version change is referred to as a migration because of these six primary factors: Page 6 of 107 Last updated: 6/18/2015

1. Each version may use a different drawing format. 2. There may be no backward compatibility between Civil objects and dynamic capabilities 3. The dynamic relationships between civil objects may not function correctly when project data was saved from more than 1 software version. 4. Subassemblies use different source code files and are recompiled with a new path. 5. Data Shortcut functionality may have changed. 6. Project drawing files cannot be worked on while Edits to the Data Shortcuts files and accompanying drawings are being made. 7. Changes to WisDOT standards files and locations may be appreciably different in the latest version. New drawing format Civil 3D 2012 uses a 2010 DWG file format, and Civil 3D 2014 uses a 2013 DWG file format. In simple terms Civil 3D uses the DWG file not only as a place to store graphical information it also treats the DWG as something like a database file. To accomplish new functionality the files are written differently and new elements are added to the 2014 DWG files that does exist in the 2012 DWG files. The migration process relies on creating a copy of all Civil 3D files and Data Shortcut files and saving them into the new 2014 format, while keeping intact the original 2012 file. The original Civil 3D files are to be used for troubleshooting needs that may arise, and to ensure functionality was intact prior to the project migration into the 2014 format. No backward compatibility Since there is no backward compatibility of Civil 3D objects between the two DWG formats, there is no ability to turn a 2014 drawing back into a fully functioning 2012 drawing without a lengthy rebuild process. Success with a rebuild is not guaranteed to fully succeed. Data Shortcut functionality changes Migrating from Civil 3D 2012 to 2014 may require using the Data Shortcut Editor. 1. Data References are now cached within the host drawing and therefore no longer signal a broken reference. If the location of the Data Shortcut drawing or object within the drawing cannot be found, a cached version is used in the drawing. 2. You can remove a data shortcut from the Data Shortcuts collection in Toolspace, on the Prospector tab. This does not remove any data references to the source object that exist in a drawings, but it does prevent anyone from creating more references to the object. Data Shortcut project migration Best Practices 1. When migrating a project from Civil 3D version 2012 to version 2014 it is very important that you DO NOT do anything else with the project files other than migration. DO NOT move individual files within the migrated project folders. DO NOT copy individual files within the migrated project folders. DO NOT rename files or objects within these files. Following these instructions will prevent adding variables that will complicate troubleshooting. 2. Follow the How to Re-path all subassemblies within project corridor drawings and Project Drawing Migration sections below for the proper process to migrate your project drawings. If this process is followed, the data shortcuts will be migrated properly as well. 3. DO NOT perform a SAVE AS command within the data shortcut editor in an attempt to migrate the data shortcuts to the new version. This will create a copy of all of the XML files for the data shortcuts which can create a problem. This will happen automatically when the above steps are followed. Page 7 of 107 Last updated: 6/18/2015

Factors to consider in project migration WisDOT does not require project version migration as a rule. However, there are many reasons to keep up-todate on the current software version. Projects shared between in-house staff and consultant staff may require project migration to keep all staff on the same version of Civil 3D. Below are some factors to consider for the timing of a project migration. 1. The decision whether or not to migrate a project is not a black and white issue. The benefits of new software functionality and WisDOT standards may or may not outweigh the costs of migration. The completion level of design and the timeline to PS&E submittal are critical to this decision. 2. Project size and complexity will increase the level of effort necessary to migrate the project. 3. All people working on the project in Civil 3D must have the version of software being migrated to and are aware of the migration. 4. If project deadlines (30% submittal, 60% submittal, PS&E, etc.) could be jeopardized by the migration taking longer than expected, the project should not be migrated. 5. The expected time commitment to migrate the project can be absorbed by the design team. Before beginning the migration conversion to 2014 The time it will take to transfer a project will vary depending on: Amount of drawings How many drawings are consuming xrefs How many drawings are being xref d The amount of data shortcuts and drawings hosting data shortcuts The condition and version format of the original drawings The Data Shortcut project needs to be reviewed and corrected in 2012 prior to the project migration. Additional time should be expected to ensure the 2012 project is fully cleaned. All drawings and data shortcuts need to be working properly prior to going through the various migration steps outlined in the following section. Only those working directly on the migration of the project data to 2014 should be opening any of the drawings during the migration process. It is recommended that there should be a minimum amount of persons involved in doing the migrating tasks, preferably one person. The transfer is complete when all useable DWG files are saved in the 2013 format and a project integrity check has been accomplished. Clean and fix 2012 Project drawings and shortcuts first Verify that all Data Shortcuts within the 2012 project are working properly. Use the following steps as a guide to ensure that they are clean and working correctly. These steps require a working knowledge of file management and Project Data shortcut tools. These steps are required to be done in Civil 3D 2012. It is not recommended to migrate or use any of the project drawings and reference files that are not fully functional in the version they were initially created in. 1. All Data Shortcuts must be Synchronized and working properly. 2. Open the Data Shortcut project in the Civil 3D Prospector without project drawings open. a. This may require communication with the entire project team. 3. Expand the entire Data Shortcut tree for each object, and search for any Exclamation symbols. 4. Use the Right-click menu to remove or Repair Broken Shortcuts. Page 8 of 107 Last updated: 6/18/2015

a. An additional dialog may prompt to Repair All Broken Shortcuts. b. Respond yes. c. This may repair the rest of the broken Shortcuts in the project. d. Search for any more Exclamation symbols in the Data Shortcut tree in the Prospector. e. Close and reopen Civil 3D to save Data shortcut edits. 5. Review the file path for each data shortcut to be sure it is pointing to the correct file and location. Any data shortcut that is not pointing to the correct file or location needs to be corrected. Any drawing that used the incorrect data shortcut must be repaired. 6. Open each drawing that has a Data Shortcut, Data Reference or an Xreference one at a time and perform a registry application purge and a drawing audit. Registry Applications or regapps, are extended data attached to drawing objects created by civil 3D and ad-on applications. These regapps can severely bloat a drawing and make processing times very long. a. Type PURGE at the command line and press enter. b. Look at the command line and notice that there are many options under this command to choose from. Type the letter R or simply click on the word Regapps. c. When prompted to Enter name(s) to purge <*> press enter to accept the default of all. d. When prompted to Verify each name to be purged type N for no and press enter e. This will remove Regapps from the drawing f. To run the AUDIT command, type AUDIT at the command prompt and press enter g. You will then be prompted to fix any errors detected. Type Y for yes, and press enter. This will fix repairable errors found in your drawing. 7. Save each drawing. Make a copy of the project before migrating Save a copy of the entire project. The minimum for this is to create a copy of all the Civil 3D DWG files and Data Shortcut files. This project copy should be outside of the original project location, and outside of the project folder used to define the Data Shortcut project. Leave this version of the project in 2012. Use the original location to migrate to 2014. These will be the same folder structure for most projects. ( i.e. N:\PDS\C3D\12345678 ) Project drawing migration When migrating a project to a version that has a newer drawing format like Civil 3D 2012 to 2014, it is important that ALL drawing files that are being used as external references (xrefs), Data References, and Sheet production drawings be saved as a Civil 3D 2014 drawing which utilizes the 2013 DWG format. Also any drawings that is being referenced into a drawing that you will be editing with Civil 3D 2014 needs to be saved as a Civil 3D 2014 drawing. It may not be necessary to transfer drawings or files to the new version if they are not going to be used in further project development and can be archived and PDF deliverables created from them. Order of migration operations The order in which DWGs are migrated to 2014 is important because Data Shortcut objects are more likely to break if they are not migrated first. Page 9 of 107 Last updated: 6/18/2015

Save DWGs in 2014 format. The order of file migration needs to be as follows: 1. Drawings that are only being used as External References. These drawings do not have any data shortcuts or data references in them. Typical Example: mapping file 2. Drawings with only Data Shortcut source objects that do not reference other files. Typical Example: Existing Surface file 3. Drawings with Data Shortcut References and External References where the source drawings have already been migrated. Typical Example: Corridor drawing, Plan sheet drawings 4. All other drawings. These drawings do not participate in any Data Shortcut References or External References. Typical Example: Title sheet, Construction Detail sheet The steps to properly migrate files with Civil 3D objects that use Data Shortcuts is different than DWGs that don't have Data Shortcut objects. These steps are defined below. There are special instructions for Corridor files below as well. The process of saving files that are used by other files first needs to be followed throughout the flow of data for a project. In practice, this means the order of file migrations will likely occur in the WisDOT project folder structure in the following order for commonly used folders: 1. BaseData 2. Design\AliProfs 3. Design\Corridors 4. RW 5. SheetsPlan This is a simple example to give the idea of the order of folder migration. Actual order for a project may differ. The important idea is to migrate DWGs that are used by other files first, and then migrate the DWGs that are using earlier DWGs. NOTE: Visual verification of data reference objects integrity after the conversion is crucial in this process. Do not assume object have made the conversion correctly without at least a visual inspection. To save drawings with Civil 3D objects that are referenced to in other drawings 1. Start Civil 3D 2014. 2. Open the drawing that needs to be converted to a 2014 drawing. a. Verify that any data references or xref being consumed have been saved first (See Xrefs section below) 3. Save the drawing. 4. Navigate to the Data Shortcut tree in the Prospector a. In the right-click-menu select "Associate Project to Current Drawing" This step will associate the drawing to the Data Shortcut project. This process may be skipped if the Associate Project to Multiple Drawings tool is used on all the Data Shortcut drawings at once, after step 6. Page 10 of 107 Last updated: 6/18/2015

b. Verify the Working folder and the Select Project are correct in the dialog and press OK. 5. Save and close the drawing. 6. Repeat steps 2-5 above for all drawings where Data Shortcut objects are defined. 7. Verify no other users have any project drawing open. 8. With no project drawings open, synchronize and validate all Data Shortcuts in the Prospector. o Data shortcuts can become invalid if changes occur to the names or locations of drawings or reference objects. o When a data shortcut reference is broken, the icon is displayed next to the invalid data reference in Toolspace, on the Prospector tab. Validation reloads the data references if the drawing paths have not changed. Otherwise, you must repair broken references. 9. Hover over Data Shortcut in prospector, access Right-Click- menu, select Validate Data Shortcuts. Page 11 of 107 Last updated: 6/18/2015

10. If there are Broken Shortcut flags, access right-click-menu for an object that is flagged and select Repair Broken Shortcuts. You will need to browse and find the correct path and drawing where the object for the shortcut resides. If prompted to Repair All Broken Shortcuts select Yes/OK. 11. Close Civil 3D. To save drawings that are being used only as Xrefs 1. Start Civil 3D 2014 2. Open the 2012 drawing that needs to be converted. 3. Type XR at the command line to expose the External Reference palette. 4. If any of the files that are used as an xref have not be migrated, perform the following: a. Holding down the shift key select all the xref drawings in the File Reference List. Note: you do not need to select all the drawings at once if the list is long. It may process better if you divide you selection into multiple groups and then repeat steps 4-6. b. Right-click and select Open in the menu. c. Once the drawings are opened, there will be a tab for each drawing below the ribbon. d. Right-click on a tab to select a drawing. Note: select only the drawings that were opened from the xref list. e. Once the drawing is opened press the X on the tab. f. Select YES when prompted to Save changes to drawing. g. Repeat until all the drawing tabs have been closed and saved. 5. Save the original drawing that was opened. 6. You can now reopen the drawing to be edited. Updating a C3D 2012 Corridor DWG into a C3D 2014 DWG How to Re-path all subassemblies within project corridor drawings The following sequence should be applied to each project corridor drawing saved to Civil 3D 2014. 1. These steps should not be taken until all other steps in the sections above have been completed. 2. Open the corridor drawing in Civil3D 2014. 2. Synchronize all Data Shortcuts. 3. If the Event Viewer has been populated through any of these first steps, all the events should be cleared before proceeding. 4. Rebuild the corridor. If the Event Viewer shows events, clear the Event Viewer and then: o Open the Corridor Properties dialog and go to the Parameters tab Uncheck all the regions. Page 12 of 107 Last updated: 6/18/2015

Press Apply to rebuild the corridor with no regions constructed. Recheck all the regions. Press OK to rebuild the corridor with all regions constructed. Check the construction of the corridor in plan and corridor section editor. 5. In the rare case where the Event Viewer still shows events, review the Warning Descriptions, looking for:.net subassembly project, module, or class not found. If this error is found, please email Methods Development at dotcaesupport@dot.wi.gov. o The warning will also show the generic subassembly name. 6. If the drawing has more than one corridor, follow steps 3-5 corridor one at a time, for each corridor. 7. Repeat steps 2-6 for each drawing that has a corridor. 8. Remember to save the drawing after each corridor rebuilds correctly and before closing drawing. 9. Once corridors are built, verify all Data references are rebuilt in the drawing. 10. Close the drawing. WisDOT Civil 3D 2014 User Readme Civil 3D Standards Updates Internal staff should not use the ftp standards content for Civil 3D 2014. Customizations files can break. Updating Civil 3D 2012 from the ftp site still works. Before using the New WisDOT Parts Catalog It is strongly recommended to watch the parts catalog training material found in 125-010. Raster Design Included with your Civil 3D 2014 install is AutoCAD Raster Design 2014. Methods does not have training or workflow documentation for Raster Design. More information concerning Raster Design functionality can be found at http://www.autodesk.com/products/autodesk-autocad-raster-design/overview# To run AutoCAD Raster Design 2014 click on the icon on the desktop, Raster Design 2014 on AutoCAD 2014 English, or go to Start>All Programs>Autodesk>AutoCAD Raster Design 2014 and select Raster Design 2014 on AutoCAD 2014 English. WisDOT Templates for Different dwg File Types WisDOT file templates are stored in C:\WisDOT\Stnd\C3D2014\DrawingTemplates If you are creating a Plat DWG, Use WisDOT14-plat.dwt to create the new file If you are creating a Pipe Network DWG, Use WisDOT14-pipe.dwt to create the new file If you are creating a Survey Point DWG and/or Survey Figures DWG, Use WisDOT14-etopog.dwt to create the new file For all other DWG file types, Use WisDOT14.dwt If you need Civil 3D Styles from another DWT, use the Import Style command which is found on the Manage ribbon. DO NOT IMPORT STYLES WITH THE IMPORT SETTGS OPT TURNED ON! Page 13 of 107 Last updated: 6/18/2015

Wis-Manager Palette Group Performance Problem (updated 04/21/2015) The Wis-Manager palette group, which includes blocks from the WisDOT block library, has been expanded in Civil 3D 2014. The slow performance issues have been resolved, and the palettes should open and perform as expected. Custom Palettes from Civil 3D 2012 There is no simple way to import Civil 3D 2012 custom palettes into Civil 3D 2014. Palette migration requires a multi-step process. Training material for creating, archiving, and recovering palettes is in development. Methods Development recommends waiting for this training, or contacting CAE Support for help before creating your custom palettes in Civil 3D 2014. This method will include exporting each palette object and then importing each palette object into a new palette defined and located in a specific user location. When Civil 3D Locks Up or crashes (updated 06/03/2015) Follow these steps to restart your session: 1. You may first need to use the Task Manager to end the current session of Civil 3D. 2. Make sure all sessions of Civil 3D are closed. 3. Restart Civil 3D using the Civil_3D_2014_WisDOT icon on the desktop. 4. Once Civil 3D has completed the initialization startup process the Drawing Recovery Manager should be open. Page 14 of 107 Last updated: 6/18/2015

a. If the Drawing Recovery Manager does not open go to the Drawing Utilities in the File pull-down menu and select Open the Drawing Recovery Manager. 5. Select every file or file grouping in the recovery pane, use the right-mouse-click menu, and delete. a. There should be no need to keep this list populated. Ignoring this step because you do not know where the other drawings in the list came from is meaningless. If you do not know, who does? These are specific to your computer user profile. 6. After you have deleted all the files and groupings listed, or if there were no files listed, close the Drawing Recovery Manager by pressing the X. 7. Close Civil 3D. Make sure all sessions of Civil 3D are closed. 8. Open the Windows Browser and type %temp% in the path field. Page 15 of 107 Last updated: 6/18/2015

a. This will set the path to your local user folder. 9. Select all the files in this folder and delete them. If you get a message that a file cannot be deleted, select the option to skip the file. a. Browse to C:\WisDOT\Stnd\Temp, then select all the files in this folder and delete them b. Optionally for the two previous steps, if you have the ClearAutodeskCache tool on your desktop or in C:\WisDOT\Stnd\C3D2014\Appdata\Profiles\Shortcut use this tool. It will do the previous step automatically. 10. Empty the Recycle Bin, after verifying any other files already in the trash are not needed. 11. Open Civil 3D. 12. At the Command Line key-in RECOVER. In the dialog that appears, select the last current drawing you were in when Civil 3D locked or crashed, and choose open. 13. Save the drawing once recovery is finished. 14. Repeat the last two steps one at a time for each drawing that may have been opened when the lock or crash occurred. 15. If the original drawing had xrefs attached to it, review the source drawing of each xref to ensure they can be opened by repeating the steps 12 and 13 on these drawings. If you experience a crash again at any point through these steps, start from the beginning of these steps. If you are still experiencing frequent crashes, contact DOT CAE Support at DOTCAESupport@dot.wi.gov You should now be able to work on your drawing again. Choosing to not work through these steps lessens your ability to be productive. Using the ClearAutodeskCache Tool The ClearAutodeskCache tool is an icon located on your desktop. If you do not have or see this icon on your desktop, please contact DOT CAE Support for help. What does this tool do? Running this tool will delete files and folders created in the temporary folder locations used by Civil3D to store temporary files use by the program while it is running. These files under normal circumstances will be removed by Civil3D once the program is closed. If an error or crash occurs, or memory resources reach a maximum level, these files that are created will not get removed, and when the size of these files gets large enough it will begin degrade the programs ability to properly use the resources that are available. The old AutoCAD phrase for this is clear the cache. What folders does it clear? For Civil3D 2012 it clears the files in: C:\Users\~username~\AppData\Local\Temp In Civil3D 2014 it clears the files in: C:\WisDOT\Stnd\Temp How to use this tool and when To use this tool, make sure all instances of Civil3D are closed, then double click the icon on the desktop and press the Start button on the Small dialog that appears. Once all the files have been deleted the dialog will show Cached Page 16 of 107 Last updated: 6/18/2015

Cleared. Press the Exit button to close the dialog. The ClearAutodeskCache can be used at any time that Civil3D is not running, and must be run if a crash of Civil3D occurs. This tool should also be used as maintenance and run on a regular basis during heavy Civil3D use at about once per week. This tool should also be used as the first way to troubleshoot sudden problems that seem to appear out of nowhere. The it was just working and now it is not type of problems. Temporary Fix for Missing Point Code Labels Explanation of the Defect with Point Code Labels A defect within AutoCAD Civil 3D 2014 has been found in which point code labels are not applied to certain subassembly points in cross section views when the corridor file is an external reference. However, these same point code labels, using the same code set style for the assembly, will show up in the source corridor drawing. Point labels are only missing where sample lines are not precisely located on a corridor frequency within each region and baseline. This is an issue which Autodesk is working to correct, but in the meantime the following fix is suggested. Temporary Labeling Fix The simplest workaround for getting the point code labels to display in cross section views is to set the <no codes> point code to use the desired label style within the code set style in the cross section drawing. The workflow is as follows: 1. Open the drawing in which the point code labels are not showing, and click on the Settings tab of Toolspace. 2. Expand the General menu. Within the General menu expand the Multipurpose Styles menu, and within that expand the Code Set Styles menu. 3. Right click on the Code Set Style you are using in your section views and select Edit. Page 17 of 107 Last updated: 6/18/2015

4. When the Code Set Style dialog box appears, locate the <no codes> point code, and set the label style for that code to the desired label style for the missing point labels. 5. Click Apply and OK to save the changes to the code set style. The point codes should now be labeled. NOTE: This will result in the labeling of any points without point codes associated with them. What to know about the WisDOT2014 Settings Profile MDU will need to update the Settings Profile on occasions to maintain standards tools. There are no plans or need to make any edits or updates to the CUI files or any of the workspaces associated with them. This means the user can create their own or edit workspaces without these being automatically updated or overwritten. The WisDOT2014 settings profile will always needs to be imported manually by the user. This is to ensure that any edits made by the user are not automatically overwritten. The following section will give directions on how to Page 18 of 107 Last updated: 6/18/2015

import and re-import WisDOT2014 profile after the previous imports, how to maintain their preference changes made to the WisDOT204 profile, and how to create and manage their own user profile. The user should be aware that the WisDOT2014 profile import file (not the profile but the file to create the profile) is automatically updated to reflect any path or especially palette changes each time Civil 3D is started. Some of these updates will not show up until the WisDOT2014 profile is re-imported which will overwrite the existing profile. Reference the Whatsnew document for changes that may require the WisDOT 2014 profile be reimported. The Whatsnew document can be found in the WisDOT Civil 3D Environment Help dialog, or at ftp://ftp.dot.wi.gov/dtsd/bpd/methods/civil3d-2014-win7-64/whatsnew-ex.pdf There is no way to merge Settings Profiles at this time so after re-importing the WisDOT2014 profile, all user defined settings will need to be reset manually. To import or re-import the profile: 1. Type OP at the command line, and the Options dialog will open Navigate to the Profiles tab If the Current profile label does not show <<C3D_Imperial>> as current, double click on the <<C3D_Imperial>> profile in the available profile list to set it current. The wisdot2014 profile cannot be set as current during this pocess. select the Import button Browse to Select the file WisDOT2014.arg 2. In the Import Profile dialog, change the name to <<WisDOT2014>>, and verify the Include path information is checked. Select the Apply & Close button Page 19 of 107 Last updated: 6/18/2015

3. In the Available profiles list highlight <<WisDOT2014>> and press the Set Current button Press the Apply button at the bottom of the dialog and then press OK. Creating your own User Profile & Creating your own user Palettes (changed 04/17/2015) Below are the directions to create your own user palette, which requires that you create your own User Profile. It is not required that you create your own user palette, but without a user palette you cannot add any content to a palette. The user palettes are not shared or updated like the wisdot standards palettes and are for your own personal use. 1. Confirm the existence of the folder C:\WisDOT\Stnd\users\Myc3d2014\Mypalettes a. If you do not have a C:\WisDOT\Stnd\users\Myc3d2014\Mypalettes folder already created, STOP. Do not continue. Contact DOTCAE Support for assistance. 2. Launch Civil 3D 2014, and right-click in model space and choose "options" 3. Click on the Profiles tab and click "Add to list" 4. Name your new profile MyProfile 5. Select MyProfile in the list and click "Set Current" 6. Click on the files tab and remove all entries under the Tool Palettes File Locations 7. Click Browse to add the new location with the same path as above... C:\WisDOT\Stnd\users\Myc3d2014\Mypalettes 8. Click "Apply" and then go back to the Profiles tab 9. Click on "Export" and navigate to C:\WisDOT\Stnd\users\Myc3d2014 and save the.arg file as MyProfile.arg. Press OK to close the dialog. 10. Open the ToolPalette. The palette should be empty. If the ToolPalette is not empty please review the previous steps. Use the right-click-menu to rename the New Palette to MyPalette or other suitable name. 11. Close Civil 3D 12. Navigate to C:\Users\<username>\AppData\Roaming\Autodesk\C3D 2014\enu\Support\Profiles. If you find a folder named \MyProfile, open the folder and delete the file Profile.aws a. If you do not find the folder and file above just continue with the following steps. 13. Launch Civil 3D 2014 again, right-click and choose "options" and go to the Profiles tab, set MyProfile current and then Export the.arg once more as described in step 9. 14. Create a new palette and add objects to the palette as you need. Note: The <<WisDOT2014>> profile will always be the startup profile, and you will need to set your MyProfile as the current profile before you can access your personal palettes. The Civil 3D 2014 update process will not update your MyProfile. Project Data Page 20 of 107 Last updated: 6/18/2015

Translate DGN to DWG Workflow Using Civil 3D This workflow document will outline the steps involved to translate a MicroStation DGN file to AutoCAD 2012 DWG file format. The workflow will be Civil 3D based and the final deliverable will be the DWG file. The DGN import and export capabilities are designed to provide a fundamental exchange of information between MicroStation V8 DGN files and AutoCAD DWG files. However, translating data from one format to a completely different format inevitably require compromises and substitutions. Simple geometric objects such as lines, arcs, and circles, and properties such as layer assignments correlate directly between the DWG and DGN data formats. Data with built-in features or variations are visually approximated. For example, text and dimensions might have specialized formatting, and color definitions might be customized. Some data cannot be translated completely. For example, product-specific features such as data fields or dynamic blocks can be represented visually but not behaviorally. AutoCAD only supports colors for lines so all entities in the DGN file that have a color property set for a symbol in MicroStation lose the symbol color when imported as a block. When importing DGN files that contain multilines, any linetypes associated with the multilines do not display. The closed property of a DGN polygon or closed polyline is automatically set to No when importing a DGN file into AutoCAD. This is done to ensure that linetypes display properly. AutoCAD Civil 3D 2014 Import to AutoCAD 1. In AutoCAD Civil 3D create a New drawing. 2. From the Application Menu Button select Open > DGN. The Import DGN File dialog will appear. Command: DGNIMPORT 3. Select the file you want to convert and then select Open. The DGN Import Settings dialog will appear. 4. Check ON Import into current drawing and select Ignore duplicate names radio button. 5. In the External DGN references section of the dialog select the radio button Translate references to blocks or xrefs. 6. In the Specify DGN units to convert to DWG units select the Master units radio button. Page 21 of 107 Last updated: 6/18/2015

Note: In the Import DGN Settings dialog box, if you select Import into Current Drawing and select the Translate References to Blocks or Xrefs option in the External DGN references section, all referenced DGN files are converted to block references. If you do not select Import into Current Drawing and select the Translate References to Blocks or Xrefs option, then all referenced DGN files are converted to DWG external references. Note: If you are importing a V7 DGN file that MicroStation V7 DGN file does not have ByLayer setting for color. The user may want to use the Standard DGN mapping rather than the WisDOT one to preserve colors. 7. Click the WisDOT DGN-DWG IMPORT as the setup. 8. Click the OK button. The Import DGN dialog will close and the file will be imported. 9. Zoom extents the drawing and Select All the elements. 10. From the Properties dialog set the Color, Linetype, and Lineweight all to ByLayer. Page 22 of 107 Last updated: 6/18/2015

Verify the Imported drawing 11. In AutoCAD Civil 3D go to the Ribbon and the View tab > Coordinates panel select World icon. Note: World aligns the UCS with the world coordinate system (WCS). You can also click the UCS icon and choose World from the origin grip menu.from the pull down menu View > 3D Views > Plan View > World UCS Command: PLAN [W] Note: Plan view set to World displays an orthographic view of the XY plane of a specified user coordinate system. 12. Locate a known coordinate location in the file and verify the coordinates out to 3 decimal points. 13. Save drawing and then Exit AutoCAD Civil 3D. Translate DWG to DGN Workflow using Civil 3D This workflow document will outline the steps involved to translate an AutoCAD Civil 3D 2014 file formation to MicroStation V8 DGN file format. The workflow will be Civil 3D based and the final deliverable will be the V8 DGN file. AutoCAD Civil 3D 2014 Export to AutoCAD 14. In AutoCAD Civil 3D open DWG drawing file you want to convert to MicroStation DGN. 15. In the command line type EXPORTTOAUTOCAD. The Export drawing name dialog will appear with the file name you are exporting with an ACAD- prefix. Page 23 of 107 Last updated: 6/18/2015

16. Click the Save button. The file will be exported to the folder. Note: Exporting a Civil 3D file to AutoCAD will create a new DWG file with all AEC objects exploded. The default Export Options should work for most files. If any options need to be changed use the command entry: -exporttoautocad or aectoacad Export to MicroStation DGN 17. In AutoCAD Civil 3D open the previously exported ACAD-file. Some of the colors of the elements may have changed now that the Styles are not being used. 18. From the Application Menu Button select Export > DGN File. The Export DGN File dialog will appear. 19. Click the Save button to create the DGN file with the same name as the original dwg file. The Export DGN Settings dialog will appear. 20. In the External DWG references section of the dialog select the radio button Translate all DWG references to DGN files. 21. Check ON Export DGN underlays as DGN references. 22. In the Specify Seed File section of the dialog select the browse icon. The Select Seed File dialog will appear. 23. Select the wisdot-seed3d.dgn file from C:\WisDOT\Stnd\C3D2014\DrawingTemplates then click Open. 24. Make sure the Master units radio button is selected. Page 24 of 107 Last updated: 6/18/2015

25. Click the OK button in the Export DGN settings dialog. The file will be exported to DGN. Page 25 of 107 Last updated: 6/18/2015

Verify DGN results 1. Open the exported DGN file in MicroStation. 2. Locate a known coordinate location in the file and verify the coordinates out to 3 decimal points. 3. From the MicroStation pull down menu Settings > Design File. The Design File Settings dialog will appear. 4. On the left side of the dialog select Working Units. Verify the units are US Survey Feet. DGN Cleanup Color 5. From the MicroStation pull down menu Settings > Color Table. The Color Table dialog will appear. 6. From the Color Table dialog pull down menu File > Default. The WisDOT default color table will be loaded. Page 26 of 107 Last updated: 6/18/2015

ByLevel Symbology 7. Select All elements in the drawing. 8. Select the Change Attributes icon. From the Tool settings dialog check ON Color, Style, and Weight and check F all others. Set the Color, Style, and Weight to ByLevel for all three. Then accept the change in the MicroStation view. 9. Clear the selection set. Page 27 of 107 Last updated: 6/18/2015

Text In the MicroStation file all the AutoCAD text has been converted to TrueType fonts. This causes display issues with some of the characters as shown below. 10. Select All elements in the drawing. Select the Change Text Attributes icon. From the Tool settings dialog check on Font and set it to 5 dot_font5 then accept the change in the MicroStation view. 11. Clear the selection set. 12. Save Settings and Exit MicroStation. Page 28 of 107 Last updated: 6/18/2015

Project data workflow map (added 04/17/2015) A map of a typical, basic Civil 3D project has been posted here: ftp://ftp.dot.wi.gov/dtsd/bpd/methods/c3d-trn/wisdot-c3d14-data-flow.pdf It's purpose is to give a visual example of standard files and objects in a Civil 3D project and the connections between the files. Moving Civil 3D Project Files, Directories, and Data Shortcuts (added 04/17/2015) This process describes the process for transferring Civil 3D Project files, directories and Data Shortcuts. This example shows the transfer of an entire Civil 3D project from a local drive to a network drive. Transfer Files and Directories 1. Create a top level project folder on the network drive. For example N:\PDS\C3D\<network project folder> 2. Browse to the local folder of the project you wish to copy. For example C:\Civil 3D Projects\<local project folder> 3. Copy the entire contents of <local project folder> to <network project folder>. Use the Data Shortcuts Editor The Data Shortcuts Editor is used to re-path Civil 3D data shortcuts from one location to another location. 1. Open Data Shortcuts Editor Start Menu >> All Programs >> Autodesk >> Autodesk AutoCAD Civil 3D 2014 >> Data Shortcuts Editor 2. Browse to N:\PDS\C3D\<network project folder> Note: Select the folder above the _Shortcuts folder Page 29 of 107 Last updated: 6/18/2015

3. View the data shortcuts in the Editor window. You will notice the path is pointing to the original location of the files. Take note of this folder path only up to and including the project number. 4. Select Find and Replace from the Edit menu Page 30 of 107 Last updated: 6/18/2015

5. Enter the <old folder path> in Find: and the <new folder path> in Replace with: Note: Only enter the part of the path up to and including the project number 6. Click Replace All. 7. Verify the New path is correct in the Editor window and click the Save button. Page 31 of 107 Last updated: 6/18/2015

Note: You must click the Save button before exiting the Data Shortcuts Editor or you will lose any changes made. 8. Exit the Data Shortcuts Editor. Reset Shortcut History and Folders 1. Reset shortcut history and folders to allow Civil 3D to recognize the new project location. 2. Browse to: N:\PDS\C3D\<network project folder>\_shortcuts\ 3. Delete the file ShortcutsHistory.xml 4. Browse to: C:\Users\<your username>\appdata\roaming\autodesk\c3d 2014\enu\Project Management\ 5. Delete the files ShortcutFolders.xml and WorkingFolders.xml 6. Open Civil 3D 7. Right-click on Data Shortcuts in the Prospector and select Set Working Folder 8. Browse to: N:\PDS\C3D\ Note: Select the folder above the <network project folder> Page 32 of 107 Last updated: 6/18/2015

9. Right-click on Data Shortcuts in the Prospector and select Set Data Shortcuts Project Folder 10. Select the newly transferred <network project folder>. Continue working in the project or exit Civil 3D. Merging Civil 3D Project Files, Directories, and Data Shortcuts (added 04/17/2015) This process describes the process for merging Civil 3D Project files, directories and Data Shortcuts into an existing project folder. This example shows the merging of a Civil 3D project from an external folder into an existing WisDOT network folder. Rename Existing Directory and Transfer Files 1. Browse to an existing WisDOT project folder. (These folders are typically named with the project number) For example N:\PDS\C3D\12345678 Note: Ensure no one is working with any files in the folder before proceeding. 2. Rename the project folder by appending merge to the project number. For example N:\PDS\C3D\12345678-merge Note: This folder will store the existing files until we are ready to merge. Do not copy files into here yet. 3. Create a new empty project folder using the same name as the original folder. For example N:\PDS\C3D\12345678 Note: We will use this folder to transfer new files into. 4. Browse to the <Civil 3D project folder> you wish to merge. 5. Transfer the entire contents of the <Civil 3D project folder> into the empty <project number> folder you just created. Page 33 of 107 Last updated: 6/18/2015

Use the Data Shortcuts Editor The Data Shortcuts Editor is used to re-path Civil 3D data shortcuts from one location to another location. 1. Open Data Shortcuts Editor Start Menu >> All Programs >> Autodesk >> Autodesk AutoCAD Civil 3D 2014 >> Data Shortcuts Editor 2. Browse to N:\PDS\C3D\<project number> Note: Select the folder above the _Shortcuts folder Page 34 of 107 Last updated: 6/18/2015

3. View the data shortcuts in the Editor window. You will notice the path is pointing to the original location of the files. Take note of this folder path only up to and including the project number. 4. Select Find and Replace from the Edit menu Page 35 of 107 Last updated: 6/18/2015

5. Enter the <old folder path> in Find: and the <new folder path> in Replace with: Note: Only enter the part of the path up to and including the project number 6. Click Replace All. 7. Verify the New path is correct in the Editor window and click the Save button. Note: You must click the Save button before exiting the Data Shortcuts Editor or you will lose any changes made. Page 36 of 107 Last updated: 6/18/2015

8. Exit the Data Shortcuts Editor. Merge Project Files Merge new project files with existing project files. Note: Files may be overwritten during a merge. Make an archive of the project folder if there is any question as to if files should be overwritten or not. 1. Browse to the <project number> folder with the newly transferred files. For example N:\PDS\C3D\12345678 2. Move the entire contents of this folder to the merge folder created at the beginning of this workflow. For example N:\PDS\C3D\12345678 to N:\PDS\C3D\12345678-merge Note: If the Confirm Folder Replace dialog appears, check Do this for all current items and click YES. Page 37 of 107 Last updated: 6/18/2015

Note: If the Move File dialog appears, check Do this for the next XX conflicts and click Move and Replace. 3. There should now be an empty project folder. Verify there is nothing in it, then delete the empty folder. 4. Remove the suffix from the merge folder and rename <project number-merge> to <project number> For example N:\PDS\C3D\12345678-merge to N:\PDS\C3D\12345678 Page 38 of 107 Last updated: 6/18/2015

WisDOT Subassemblies WisDOT Subassemblies and Superelevation (Civil 3D 2012 and beyond) Civil 3D 2012 provides new superelevation controls. This content explains what the new functionality means for users of the WisDOT subassembly library. The new superelevation functionality is described in the What s New help file content, accessed in the top right corner of Civil 3D interface. You can also view the version upgrade videos at ftp://ftp.dot.wi.gov/dtsd/bpd/methods/c3d-trn/wisdot-c3d-train-manual.pdf#190_050_superelevation_changes. The C3D2012 stock subassembly library is built to work in tandem with new superelevation controls in the superelevation wizard to add flexibility in defining how corridors handle superelevation. If you want to explore the new superelevation controls, build an assembly using Autodesk s LaneSuperelevationAOR subassembly, run through different combinations of superelevation configurations, and monitor the changes to the assemblies behavior in a corridor. Controls like the inputs for Potential Pivot, Slope Direction, and specifying SE side different from insertion direction all work to allow flexibility in defining the Axis of Rotation through superelevation transitions. Page 39 of 107 Last updated: 6/18/2015

The WisDOT subassembly library is not built to use this functionality. In fact, with some combinations of Superelevation wizard inputs, WisDOT subassembly corridors will produce a slew of error messages and may not read the intended lane slopes. The WisDOT subassembly library already has the superelevation controls needed for WisDOT design standards built into lane and shoulder subassembly logic. If you choose to use the WisDOT library for your roadway lanes and shoulders, the alignment superelevation should be developed in the superelevation wizard as follows: Page 40 of 107 Last updated: 6/18/2015

Page 41 of 107 Last updated: 6/18/2015

Remember to run the Superelevation Update macro and you now have the baseline superelevation properties needed to use WisDOT subassemblies in your corridors. This same Undivided Crowned superelevation setup will work for all cases of general roadway design with WisDOT subassemblies. For more information on WisDOT s superelevation macro and why it is needed, see Civil 3D New User Training, alignments module. WisDOT Subassembly Inputs So how do you set up your WisDOT subassemblies superelevation controls in this system? For detailed information on subassembly behavior, review the subassembly help files. To help you get started, here s a look at several different roadway typical section types: Page 42 of 107 Last updated: 6/18/2015

Case 1 Single lane ramp, crown at lane edge, planar subgrade (shoulder slopes down at crown but subgrade continues upward) Page 43 of 107 Last updated: 6/18/2015

Page 44 of 107 Last updated: 6/18/2015

Page 45 of 107 Last updated: 6/18/2015

Case 2: Undivided Roadway with crown (Left side same settings as right) Page 46 of 107 Last updated: 6/18/2015

Case 3: Divided Roadway with median, baseline at median edge or center of median, crown between lanes (only showing one of the divided roadways, the other is a mirror image) Page 47 of 107 Last updated: 6/18/2015

Page 48 of 107 Last updated: 6/18/2015

Page 49 of 107 Last updated: 6/18/2015

Page 50 of 107 Last updated: 6/18/2015

Frequently Asked Questions What do you prefer that we do? Use WisDOT lane/shoulder subassemblies, or stock? Should I change my assemblies to use the stock subassemblies? Some possible scenarios: I m starting a new corridor My corridor is built, but there s time to change it I have a PS&E in 4 months The choice is yours. We developed the WisDOT subassemblies to use point, link, and shape codes that are compatible with the stock subassemblies codes, allowing use of WisDOT and Autodesk subassemblies side-byside resulting in consistent surface and corridor output. And, with the new superelevation functionality in C3D2012 the Autodesk lanes and shoulders subassembly offerings have the needed controls to develop superelevation as per our design standards. So you have some flexibility to choose which subassemblies work best for your design intentions. There are limitations to this flexibility however. Each alignment has a single set of superelevation properties, and these superelevation properties may need to be different for WisDOT subassemblies vs. Autodesk subassemblies because of the differences in subassembly logic. The WisDOT subassemblies can t correctly read the Axis of Rotation information created by some input combinations in the Superelevation Wizard, so you shouldn t use both Autodesk and WisDOT lanes/shoulders on the same corridor baseline alignment. For each baseline alignment, use all WisDOT subassemblies on superelevated parts of your assemblies, or use all Autodesk subassemblies on superelevated parts of your assemblies. Don t mix up lanes and shoulders subassemblies, or other superelevated subassemblies, on the same baseline alignment. You can use non-superelevated WisDOT subassemblies in combination with Autodesk lanes and shoulders. Keep in mind there is other functionality in some of the WisDOT lanes and shoulders that isn t currently in the stock subassemblies. So you have to choose what s right for your situation. Are you telling us to never use Use Inside Lane SE? What about an urban roadway with parking lanes where the parking lane slope varies to match adjacent properties? Wouldn t we need to use inside and outside lane superelevation there? You can still use Inside Lane superelevation definition for situations that need it. WisDOT subassemblies will correctly read the Inside Lane SE data. To include the Inside Lane Superelevation containers in an alignment s superelevation properties, use a number value of 2 in the Number of lanes field in the Lanes dialog box of the Superelevation Wizard, other settings are as shown above. Page 51 of 107 Last updated: 6/18/2015

You probably will not get design-ready results from the Superelevation Wizard in this scenario; you may have to do some manual editing of the lane slope values and transition locations in the tabular editor. Another way to do mass changes is to the tabular editor superelevation data is to export to a csv file, edit the csv file in Microsoft Excel, and import the edited csv back into the alignment s tabular editor superelevation data. A csv file is a comma-separated value file that can be opened in Excel and edited with common spreadsheet copypaste functions. Page 52 of 107 Last updated: 6/18/2015

Modeling Roadway Modeling Workflow Tips and Best Practices (added 04/17/2015) 1. Create corridor surfaces as early as you can in the design process. When creating a design corridor, create the corridor surfaces immediately along with it. Maintain the corridor surface feature line list as the design concept evolves. Inspect these surfaces as design modifications are made. A design can look OK in the corridor, but it might not be structured properly to make corridor surface development as easy as it should be. This structural problem in the corridor data can lead to significant design rework if it isn't identified early. Fortunately there is an easy way to see these problems. They show up visibly in the surface models. Significant time will be spent reworking design if corridor surfaces are not created early and the resulting surface models inspected as the design progresses. 2. Why corridor links are not allowed to define, or help define corridor surfaces: Methods hears this question frequently, presumably because the use of corridor links would save time in defining and maintaining the definition of corridor surface models. Making the use of corridor links even more attractive is the "overhang correction" functionality in corridors that helps clean up areas of vertical links in our corridor surfaces. With all these benefits tied to the use of corridor links in surface definition, why does WisDOT require corridor surfaces be defined by corridor feature lines only? Let's discuss the Design Model deliverables before answering this question. Here are a few key aspects of the Design Model deliverables: A. The principle component of Design Model packages are surface models. The surface models communicate design intent clearly, more so than the other deliverables in the Design Model. B. Proposed surface model longitudinal breaklines are also an important deliverable. Some contractors will choose not to use Design Model surface models in construction operations, and will instead develop their own sets of surface models that suit their construction operations and workflows. Contractors who anticipate following this practice have clearly stated that the longitudinal breaklines of proposed surfaces will be most useful to them in their Construction Model development efforts. C. The primary source of longitudinal breaklines in the Design Model surface models is the list of corridor feature lines used to define corridor surfaces. D. It is critical that all the data in Design Models be: 1. Consistent with the plan 2. Consistent with itself 3. Must be complete, with no missing information. Again, why not use corridor links to define surface models? 1. One reason is that using corridor links to define corridor surfaces significantly increases the risk that the designer will not specify all the needed corridor feature lines in the corridor surface definition, leading Page 53 of 107 Last updated: 6/18/2015

to delivery of an incomplete set of breaklines in the Design Model package. By adding corridor links to the definition, the designer will fix problems in the corridor surface related to missing corridor feature lines. This is bad. Those problems should be visible to the designer, not hidden or fixed behind the scenes. If corridor links are not used in surface definition, the absence of needed corridor feature lines will be clearly visible to the designer, especially in corridor section editor. When corridor links are used in the surface definition, the missing corridor feature line problems are hidden from the designer making it very easy to deliver an incomplete set of longitudinal breaklines in the Design Model. The end result: a Design Model package with surface models that are inconsistent with breaklines. This is a deal-breaker as far as the use of corridor links is concerned, WisDOT deliverable requirements will disallow use of corridor links in corridor surface definition until this problem is resolved. 2. Overhang correction functionality cleans up surface model triangulation in areas of vertical links, but it does not correct the problem in the longitudinal breaklines. If overhang correction is used to fix these problems in design, the problems will reappear when contractors use Design Model breaklines to develop Construction Model surfaces. See Roadway Design Workflow Tip #3 for a method to collect these vertical link problems without using "overhang correction". 3. Longitudinal breakline data leads to better, more consistent roadway surface model triangulation than cross sectional patterned data. This is a similar concept as survey collection. Originally WisDOT collected survey data for DTM surfaces in the traditional cross sectional collection pattern. Experience taught us that longitudinal breakline collection of roadway data results in better triangulation overall, and survey collection practices changed to a longitudinal feature based collection pattern for existing ground surface models. The same is true for proposed surface models. Many times that triangulation from cross sectional elements, such as corridor links, is OK. But some situations that commonly appear in roadway terrain areas will triangulate incorrectly with cross sectional based data, use of longitudinal roadway features (corridor feature lines) corrects those triangulation errors. 3. How can I correct vertical link problems in my proposed surface models without using "overhang correction" with corridor links in the corridor surface definition, or without using a surface edit actions on the refinement surface? A vertical link is created when 2 corridor feature lines (CFLs) that are the same offset distance from the baseline, are both used in defining the same surface model. Fix the vertical link problem by inserting LinkWidthAndSlope subassembly to your assembly. Using a generic link subassembly like LinkWidthAndSlope, create a new CFL to replace one of the old CFLs from the vertical link. Offset the new CFL from the old CFL by 0.01'. Use the new CFL in the corridor surface definition, remove the old CFL from the corridor surface definition. Page 54 of 107 Last updated: 6/18/2015

Page 55 of 107 Last updated: 6/18/2015

4. When modifying corridors, turning off all baselines that are outside the area you are working in will improve system performance. When finished working with the corridor turn all baselines back on and rebuild the corridor before saving and closing the DWG file, this will ensure the corridor surfaces are completely constructed through the full extents of the corridor. Page 56 of 107 Last updated: 6/18/2015

5. Avoid using "Parameter Overrides" to make changes to your corridor. Make the needed to changes to the input parameter values in your assemblies instead. Parameter overrides will save time when initially used, but will cost you much lost time overall. Parameter overrides are tied to a station, not a location in coordinate space. If baseline stationing shifts, parameter overrides are all incorrect and must be redone. Design changes are difficult to execute within corridors that are heavy on parameter overrides. Changes made in parameter overrides are much less visible in the design data than are independent assemblies and regions. Note: Parameter overrides can be a useful tool for experimenting with results of different input parameter values. But once the correct input parameter solution is identified, remove the parameter overrides and implement the changes with a copy of the assembly and new corridor region. 6. Explore using conditional subassemblies ConditionalHorizontalTarget and ConditionalCutOrFill in your designs. These can save a lot of time in design by: consolidating multiple typical section scenarios within a single assembly, reducing corridor structure complexity by reducing number of regions. ConditionalHorizontalTarget makes transition locations between typical sections easier to adjust because the locations are defined by a target object that can be moved easily. ConditionalCutOrFill makes it easier to manage multiple daylighting solutions within a single assembly/region. There are many other timesaving uses of conditional subassemblies, they are very flexible tools that open up opportunities for creative corridor design solutions. 7. Use a target oriented philosophy in corridor design. Page 57 of 107 Last updated: 6/18/2015

Don't try to manage all the roadway cross section geometry changes with input parameters, use horizontal and vertical target objects to define geometry when you can. Create target objects for applicable horizontal roadway features. 8. Use single object representation in design data. Don't have multiple objects representing the same thing, use a single object and reference it when needed. Design changes are much easier to manage when this approach is followed. Example: Use the same objects for corridor targeting that are used for plan sheet roadway feature graphics. Doing so will help keep plan sheets and Design Models synchronized. Note: Be careful about making copies. If you copy a dwg, you now have a copy of all the objects that lived in the original dwg. Those objects now need to be renamed in the new dwg. 9. Don t just look at surfaces in the corridor section editor. This only tells part of the story. Orbit around the surface to look for problems early and often. 10. Build as much of your design as you can in the corridor. You can do more than you think there. 11. Refinement surfaces represent the current state of your design. Corridors are one source of refinement surface definition, but feature lines and other 3D linework can also be used as breaklines and/or grading surfaces. 12. Build corridors from intersections outward Designing in Civil 3D is easier if this is done. 13. Use copies of assemblies in different regions rather than reusing the same assembly in multiple regions Unintended changes can occur to a design when there are multiple regions using the same assembly. The assembly could be modified for a specific situation, forgetting the modification will be applied to the other regions. It is better to have multiple identical assemblies of different names than it is to have a single assembly used multiple times. 14. Projects with multiple design corridors can combine multiple corridor surfaces (of the same type) into a single refinement surface by using multiple "Paste" operations. 15. Use both WisDOT subassemblies and Autodesk subassemblies. The 2 subassembly libraries can be used effectively in the same design. The one problem with this in practice is the combining of WisDOT subassemblies with Autodesk subassemblies using Axis of Rotation (AOR) superelevation functionality. Use of AOR requires differences in baseline superelevation definition that are not compatible with WisDOT subassemblies. See Roadway Design Workflow Tip #16. 16. Don't use WisDOT subassemblies in the same baseline (horizontal reference line) as Autodesk subassemblies with Axis of Rotation (AOR) superelevation functionality. Page 58 of 107 Last updated: 6/18/2015

Use of AOR requires differences in the baseline's superelevation definition that are not compatible with WisDOT subassemblies. If you need to use Autodesk AOR subassemblies in your design, don't use the WisDOT subassemblies with slope control by superelevation on the same baselines as the Autodesk AOR subassemblies. 17. It is possible to build your entire roadway assembly with generic link subassemblies. That may not be the best way to construct an assembly, but thinking that way can help solve unique assembly problems for which there is no subassembly. 18. Keep the data flowing down stream. (Follow the Civil 3D Project Data Map) There is a uni-directional flow to the data relationships in the WisDOT roadway design workflow, the Civil 3D Project Data Map depicts this idea. Keeping this concept in mind will help keep your project data structured and operating correctly, and help you avoid data problems such as circular references. 19. For subassemblies that require targeting, name them so you know what the target should be. Example name: TARGET-ETW AliProf and SideRoad AliProf 20. A corridor can easily be broken apart into multiple corridors in separate files, but multiple corridors cannot be combined together easily. 21. Do not create data shortcuts of surface profiles. Instead, data reference the surface and create the surface profile in each drawing it is needed. This practice reduces the total amount of objects in your data shortcut list. This practice will also make it easier to avoid circular references, and it may improve system performance in some situations. 22. Avoid use of surface editing tools. It is better to make changes through corridor tools, or use of feature line and 3D linework as breaklines, and the Civil 3D grading tools. Use of surface edit tools will make changes to the surface model, but those changes will not be in the breakline delivery for those surfaces, leading to Design Model data inconsistency. These design changes can be made in a way that will promote better data consistency. Example: using the "Swap Edge" command can alter triangulation of a refinement surface as desired, but the same can be accomplished by adding a feature line or 3D poly or line as a breakline to the refinement surface. 23. The purpose of the corridor in our design workflow is to create the longitudinal breaklines of our proposed work surface models. 24. Refinement surfaces represent your finished design work, they are the design goal. Refinement surfaces are the surface models for proposed work in Design Model delivery. 25. Surface models are the goal of roadway design, not cross sections. Cross sections have traditionally been the primary goal of roadway design, but not anymore. They have been replaced by surface models as the primary form of roadway design output. Cross sections are now a by-product of the design process. Develop Design Model surface models correctly, and then cut sections on those surface models for plan sheets. 26. It is OK to use corridor link graphics in plan sheet section views. Page 59 of 107 Last updated: 6/18/2015

Some people prefer the look of cross sections achieved by keeping corridor links visible in plan sheet section views, this is acceptable practice. But, in all cases, the correct refinement surface models must be visible in plan sheet section views also. This is a key quality control element in our design workflow that helps ensure plan sheets and Design Models are consistent with each other. 27. Turn off connection of unneeded corridor feature lines to improve system performance. Some subassemblies produce corridor points which are assigned multiple point codes. When a corridor is constructed, by default a corridor feature line is created for each corridor point code. Corridor points with multiple codes produce multiple coincident corridor feature lines. The redundant corridor feature lines can be turned off by un-checking them in the Corridor Properties dialog box as shown below, only 1 corridor feature line per corridor point is needed to define surface models. Roadway Modeling Tip Videos (added 06/18/2015) How to structure the point codes for a shoulder cutout http://165.189.80.136/dot/c3d-trn/080/tips/1-shouldercutout.mp4 How to structure the point codes and curb return subassemblies for an intersection cutout (sideroad pavement depth deeper than mainline) http://165.189.80.136/dot/c3d-trn/080/tips/2-intersectioncutout.mp4 How to add point codes and structure them for an intersection cutout (sideroad pavement depth deeper than mainline) considering that the curb return assembly is not creating crown-based point codes. http://165.189.80.136/dot/c3d-trn/080/tips/3-sideroadcenterline.mp4 How to add point codes to create all needed feature lines behind WisDOT CGGen subassembly. Page 60 of 107 Last updated: 6/18/2015

http://165.189.80.136/dot/c3d-trn/080/tips/4-cg-cutout.mp4 Refinement surface edits that are common for intersections. http://165.189.80.136/dot/c3d-trn/080/tips/5-intrfntedits.mp4 A method for handling a change in pavement depth on a roadway. http://165.189.80.136/dot/c3d-trn/080/tips/6-pavmentchange.mp4 Modeling Crossovers There are multiple ways to design a crossover with Civil 3D and every situation is different. This document discusses one method for modeling crossovers using a combination of tools in Civil 3D. First, here are some best practices and design recommendations to help with the crossover geometry. Make sure the crossover placement allows for adequate room in the construction zone. Place the crossover in a location that is visible to approaching motorists. Look at the longitudinal profile of your roadway and try to place the crossover in a location where the pavement will drain. If the area is flat, consider using Slotted Corrugated Metal Pipe Surface Drains. Good drainage may sometimes be achieved by warping the pavement slopes. Use SDD 15D11 as a guide. Design for no less than 10 mph below posted speed. Use the existing roadway crown to your advantage when selecting curve radii. The crossover model will be dependent on the existing median pavement edges. It is a best practice to survey these pavement edges at a minimum. Ideally, the entire median (pavement edge to pavement edge) should be surveyed. Here is one method to model a median crossover with Civil 3D. The naming shown is based on a North-South roadway. To avoid rework, finalize the location of the crossover prior to constructing the surface models. Crossover Geometry Create a new drawing with the WisDOT template and give it an appropriate name such as "Crossover Edgelines.dwg". Data shortcut reference the following: NB and SB reference line alignments and existing surface profiles NB and SB centerline alignments Existing Surface (ideally with a supplemental median survey included) Xreference the project mapping. Determine the best location for the crossover. Draw the horizontal geometry for the median crossover. Be sure to include the edge of pavement and edge of shoulder line work for the gore areas. This can be done with lines and arcs, the end result needs to be continuous polylines. Use the proper layers. Save and close the drawing Crossover Setup Surfaces Create a new drawing with the WisDOT template and give it an appropriate name such as "Crossover Setup Corridor.dwg". Data shortcut the following: NB and SB reference line alignments and existing surface profiles Existing Surface (ideally with a supplemental median survey included) Create a joint polyline that represents the inverted crown location of the crossover median. The polyline should Page 61 of 107 Last updated: 6/18/2015

extend through the limits of the crossover. Create an assembly consisting of two lanes. Create a corridor called "Crossover Setup". Set the corridor begin and end stations to the crossover extents. Use the NB alignment, Existing Surface profile, and the assembly from step 6. Recommended frequency is 5 ft. Target the first lane to the inverted crown polyline Target the second lane to the SB reference line alignment and existing surface profile. Review the lane cross-slopes in the corridor section editor. The right lane slope will be constant and the other will vary to match the terrain. Check to make sure the variable slopes are reasonable. You may need to adjust the location of the inverted crown line or modify the slope of the constant slope lane in the assembly. Also, superelevation can be established on the NB alignment to vary the right lane slope to aid in pavement drainage or to better match the existing conditions. Turn off all unnecessary feature lines in the corridor properties "Feature Lines" tab. The feature lines that are needed are ETW, Crown, ETW_Sub, and Crown_Sub. In the "Surfaces" tab of the corridor properties, create a Top and a Datum surface. Page 62 of 107 Last updated: 6/18/2015

Save the drawing and create data shortcuts for the Top and Datum surfaces. Crossover Top Surface Create a new drawing with the WisDOT template and give it an appropriate name such as "Crossover Top Surface.dwg". Data shortcut the following: Crossover Setup - Top surface Exist surface Xreference the Crossover Edgelines.dwg file. Create a new Site called "Crossover - Top". Create feature lines for the cross over edge lines using the Create Feature Line from Objects command. Place these feature lines in the Crossover - Top Site. Do not assign a style. Place the feature lines on the appropriate layers. Assign elevations from the Crossover Setup - Top surface. Accept the default weeding factors. Page 63 of 107 Last updated: 6/18/2015

Example naming convention: (EOP = Edge of Pavement, EOS - Edge of Shoulder) South Gore EOP - Top South Gore EOS - Top North Gore EOP - Top North Gore EOS - Top Create feature lines representing the NB and SB edges of pavement and place them in the Crossover - Top site. Give them appropriate names like NB EOP - Top and SB EOP - Top. Assign elevations from the Crossover Setup - Top surface. Create a feature line representing the inverted crown location between the edge of shoulder gore radii and place it in the Crossover - Top site. Give it an appropriate name like Inverted Crown - Top. Assign elevations from the Crossover Setup - Top surface. Page 64 of 107 Last updated: 6/18/2015

Create a feature line at each end of the crossover limits connecting closing off the work area. Name them something appropriate like NB North EOP, NB South EOP, SB South EOP, SB North EOP. From the Modify tab, select the Elevations from Surface command from the Edit Elevations panel. Choose the Crossover Setup - Top surface and check Insert intermediate grade break points. Select all of the feature lines. In the Crossover - Top site, create a grading group called "Crossover - Top". Turn on Automatic Surface Creation. Check "Use the Group Name", give it a style of P Triangles-Top, and set the Tessellation spacing to 5'. Open the Grading Creation tools dialogue. Edit the Grading Criteria to match your project conditions. Make sure Target is set to Surface and Interior Corner Overlap is set to "Hold Slope as Maximum". Page 65 of 107 Last updated: 6/18/2015

Create Gradings off of the Gore EOS - Top feature lines. Set your target surface to Exist. Apply to the entire length. From the Grading Creation Toolbar, select the Create Grading Infill command. Select each of the areas of the crossover to complete the surface creation. These areas include four shoulder areas and two pavement areas. The Crossover Top surface should now be complete. Inspect the surface for abnormalities and make any surface edits as needed. Save the drawing and create a data shortcut for the Crossover - Top surface. Page 66 of 107 Last updated: 6/18/2015

Crossover Datum Surface Create a copy of the Crossover Top Surface.dwg file and rename it as Crossover Datum Surface.dwg Open the Crossover Datum Surface.dwg file. Right click on the Crossover Top Grading Group in the Toolspace - Prospector and select properties. On the Information Tab, uncheck Automatic Surface Creation. Confirm the deletion of the Crossover Top surface. Right click on the Crossover Top Grading Group in the Toolspace - Prospector and select Delete. Confirm the deletion of all Gradings. Create a new Site called SGSP - Setup Select the two Gore EOS feature lines and move them into the SGSP - Setup site. Rename the Crossover - Top Site properties, rename the site to Crossover - Datum Delete the following feature lines from the Crossover - Datum site: South Gore EOP - Top North Gore EOP - Top NB North End - Top NB South End - Top SB South End - Top SB North End - Top Rename the remaining feature lines in the Crossover - Datum site with a Datum designation instead of Top. Create a new Grading Group in the SGSP - Setup site called SGSP Setup. Do not turn on Automatic Surface Creation. Open the Grading Creation Tools. Set the target surface to Crossover Setup - Datum. Use the same Grading Criteria that was used for the Crossover Top gradings. Create gradings on each of the Gore EOS feature lines. From the Toolspace - Settings tab, navigate to Gradings - Styles - Standard. Right click on standard and select Edit. On the Display tab, turn off all Plan view component visibility except for Daylight Line. Type EXPLODE at the command line. Select the two gradings. What will remain are two 3D polylines representing the crossover subgrade shoulder point. Data shortcut reference the Crossover Top surface. Give it a border only style. Select the Crossover Top surface and choose the Extract Objects command from the contextual ribbon. Click Ok. Turn the Crossover Top surface to the No Display style. Using the Trim command, trim the ends of the subgrade shoulder point 3d polyline against the Crossover Top surface boundary 3d polyline. The Crossover Top surface boundary 3d polyline can then be deleted. Use the Create Feature Lines from Objects command to convert the SGSP polylines to feature lines. Give them appropriate names like "SGSP south" and SGSP north". Do not assign a style. Place them on the P_RDWY_Subg_ShldPt layer. Erase existing entities, Assign Elevations from the Crossover Setup Datum surface. Do not weed points. These feature lines belong in the Crossover - Datum site. Create a feature line at each end of the subgrade shoulder point feature lines to a point perpendicular to the NB EOP and SB EOP feature lines. Similar to step 7 in the Create Crossover Top Surface segment. Page 67 of 107 Last updated: 6/18/2015

Grip edit the NB EOP and SB EOP feature lines ends to match the feature lines created in step 19. Grip edit the Inverted Crown feature line to snap to the subgrade shoulder point feature line. From the Modify tab, select the Elevations from Surface command from the Edit Elevations panel. Choose the Crossover Setup - Datum surface and check Insert intermediate grade break points. Select all of the feature lines except the Gore EOS - Top feature lines. Create a new grading group in the Crossover - Datum site called Crossover - Datum - Infills. Turn on Automatic Surface Creation. Check "Use the Group Name", give it a No Display style, and set the Tessellation spacing to 5'. Open the Grading Creation Tools. Place infills for the two areas enclosed by the SGSP feature lines, NB & SB EOP feature lines, and Inverted Crown feature line. From the Modify tab - Edit Geometry Panel, select the Stepped Offset command. Set the offset distance to 0.01'. Select the NB EOP and SB EOP feature lines. The elevation does not matter yet. Rename the feature lines created in step 25 to NB Exist and SB Exist. Use the Elevations from Surface command to assign elevations to the NB Exist and SB Exist feature lines from the Exist surface. Create a new surface called Crossover - Datum. Give it the P Triangles-Datum display style. In Toolspace - Prospector, right click on the Crossover - Datum surface and choose Select. Click Edit Surface from the contextual ribbon and choose paste surface. Paste the Crossover - Top surface. Click Edit Surface again and choose paste surface. Now paste the Crossover - Datum - Infills surface. Right click - Display order - Send to Back Select the NB Exist and SB Exist feature lines and click Add to Surface as Breakline command from the contextual ribbon. Choose the Crossover - Datum surface. Under Supplemental factors, check Distance and change it to 5'. Accept the other defaults in the breakline type dialogue box. Create a closed polyline that will act as a hide boundary to trim out the triangle outside of the NB South EOP, NB North EOP, SB South EOP, and SB North EOP feature lines created in step 19. Create a second closed polyline for the other side of the crossover Expand the Crossover - Datum surface in the Toolspace Prospector. Expand Definition. Right click on Boundaries and select Add Boundaries. Change the type to Hide and make sure Non-destructive Breakline is checked. Click Ok and select the two closed polylines from step 31. Page 68 of 107 Last updated: 6/18/2015

The Crossover Datum surface should now be complete. Inspect the surface for abnormalities and make any surface edits as needed. Save the drawing and create a data shortcut for the Crossover Datum surface. Page 69 of 107 Last updated: 6/18/2015

Pipe Networks Culvert pipes summary (updated 6/12/15) Pipe Rules Pipe Rules Pipe Rules CP CLASS III 12-CH Cover: 2-15 FT CPCSAC 12-CH Cover: 1-40 FT CPCPE 12-CH Cover: 2-11 FT CP CLASS III 15-CH Cover: 2-15 FT CPCSAC 15-CH Cover: 1-40 FT CPCPE 15-CH Cover: 2-11 FT CP CLASS III 18-CH Cover: 2-15 FT CPCSAC 18-CH Cover: 1-40 FT CPCPE 18-CH Cover: 2-11 FT CP CLASS III 21-CH Cover: 2-15 FT CPCSAC 21-CH Cover: 1-40 FT CPCPE 24-CH Cover: 2-11 FT CP CLASS III 24-CH Cover: 2-15 FT CPCSAC 24-CH Cover: 1-40 FT CPCPE 30-CH Cover: 2-11 FT CP CLASS III 30-CH Cover: 2-15 FT CPCSAC 30-CH Cover: 1-40 FT CPCPE 36-CH Cover: 2-11 FT CP CLASS III 36-CH Cover: 2-15 FT CPCSAC 36-CH Cover: 1-40 FT CP CLASS III 42-CH Cover: 2-15 FT CPCSAC 42-CH Cover: 1-40 FT CPCPP 12-CH Cover: 2-15 FT CP CLASS III 48-CH Cover: 2-15 FT CPCSAC 48-CH Cover: 1-40 FT CPCPP 15-CH Cover: 2-15 FT CP CLASS III 54-CH Cover: 2-15 FT CPCSAC 54-CH Cover: 1-40 FT CPCPP 18-CH Cover: 2-15 FT CP CLASS III 60-CH Cover: 2-15 FT CPCSAC 60-CH Cover: 1-58 FT CPCPP 21-CH Cover: 2-15 FT CP CLASS III 72-CH Cover: 2-15 FT CPCSAC 72-CH Cover: 1-49 FT CPCPP 24-CH Cover: 2-15 FT CP CLASS III 84-CH Cover: 2-15 FT CPCSAC 84-CH Cover: 1-42 FT CPCPP 27-CH Cover: 2-15 FT CP CLASS III-A 12-CH Cover: 2-11 FT CPCSAC 96-CH Cover: 1-37 FT CPCPP 30-CH Cover: 2-15 FT CP CLASS III-A 15-CH Cover: 2-11 FT CPCPP 36-CH Cover: 2-15 FT CP CLASS III-A 18-CH Cover: 2-11 FT CPCA 12-CH Cover: 1-40 FT CP CLASS III-A 21-CH Cover: 2-11 FT CPCA 15-CH Cover: 1-40 FT PSP 60-CH Cover: 1-106 FT CP CLASS III-A 24-CH Cover: 2-11 FT CPCA 18-CH Cover: 1-40 FT PSP 72-CH Cover: 1-76 FT CP CLASS III-A 27-CH Cover: 2-11 FT CPCA 21-CH Cover: 1-35 FT PSP 84-CH Cover: 1-56 FT CP CLASS III-A 30-CH Cover: 2-11 FT CPCA 24-CH Cover: 1-35 FT PSP 96-CH Cover: 1-47 FT CP CLASS III-A 36-CH Cover: 2-11 FT CPCA 30-CH Cover: 1-30 FT PSP 108-CH Cover: 1-41 FT CP CLASS III-A NON-METAL 12-CH Cover: 2-11 FT CPCA 36-CH Cover: 1-30 FT PSP 120-CH Cover: 1-37 FT CP CLASS III-A NON-METAL 15-CH Cover: 2-11 FT CPCA 42-CH Cover: 1-30 FT PSP 132-CH Cover: 1-35 FT CP CLASS III-A NON-METAL 18-CH Cover: 2-11 FT CPCA 48-CH Cover: 1-25 FT PSP 144-CH Cover: 1-33 FT CP CLASS III-A NON-METAL 21-CH Cover: 2-11 FT CPCA 54-CH Cover: 1-25 FT PSP 156-CH Cover: 1-32 FT CP CLASS III-A NON-METAL 24-CH Cover: 2-11 FT CPCA 60-CH Cover: 1-32 FT PSP 168-CH Cover: 1-31 FT CP CLASS III-A NON-METAL 27-CH Cover: 2-11 FT CPCA 72-CH Cover: 1-30 FT PSP 180-CH Cover: 1-30 FT CP CLASS III-A NON-METAL 30-CH Cover: 2-11 FT CPCA 84-CH Cover: 1.5-30 FT CP CLASS III-A NON-METAL 36-CH Cover: 2-11 FT PASP 6-FT SPAN Cover: 1.5-15 FT CP CLASS III-B 12-CH Cover: 2-15 FT CPCP 12-CH Cover: 1-15 FT PASP 7-FT SPAN Cover: 1.5-15 FT CP CLASS III-B 15-CH Cover: 2-15 FT CPCP 15-CH Cover: 1-15 FT PASP 8-FT SPAN Cover: 2-12 FT CP CLASS III-B 18-CH Cover: 2-15 FT CPCP 18-CH Cover: 1-15 FT PASP 9-FT SPAN Cover: 2-11 FT CP CLASS III-B 21-CH Cover: 2-15 FT CPCP 24-CH Cover: 1-15 FT PASP 10-FT SPAN Cover: 2-10 FT CP CLASS III-B 24-CH Cover: 2-15 FT CPCP 30-CH Cover: 1-15 FT PASP 11-FT SPAN Cover: 2-8 FT CP CLASS III-B 27-CH Cover: 2-15 FT CPCP 36-CH Cover: 1-15 FT PASP 12-FT SPAN Cover: 2-7 FT CP CLASS III-B 30-CH Cover: 2-15 FT PASP 13-FT SPAN Cover: 2-6 FT CP CLASS III-B 36-CH Cover: 2-15 FT CPRC CLASS III 12-CH Cover: 2-15 FT PASP 14-FT SPAN Cover: 3-12 FT CP CLASS III-B NON-METAL 12-CH Cover: 2-15 FT CPRC CLASS III 15-CH Cover: 2-15 FT PASP 15-FT SPAN Cover: 3-11 FT CP CLASS III-B NON-METAL 15-CH Cover: 2-15 FT CPRC CLASS III 18-CH Cover: 2-15 FT PASP 16-FT SPAN Cover: 3-10 FT CP CLASS III-B NON-METAL 18-CH Cover: 2-15 FT CPRC CLASS III 21-CH Cover: 2-15 FT PASP 16.5-FT SPAN Cover: 3-10 FT CP CLASS III-B NON-METAL 21-CH Cover: 2-15 FT CPRC CLASS III 24-CH Cover: 2-15 FT CP CLASS III-B NON-METAL 24-CH Cover: 2-15 FT CPRC CLASS III 27-CH Cover: 2-15 FT PACS 17x13-CH Cover: 1.5-13 FT CP CLASS III-B NON-METAL 27-CH Cover: 2-15 FT CPRC CLASS III 30-CH Cover: 2-15 FT PACS 21x15-CH Cover: 1.5-12 FT CP CLASS III-B NON-METAL 30-CH Cover: 2-15 FT CPRC CLASS III 36-CH Cover: 2-15 FT PACS 24x18-CH Cover: 1.5-10 FT CP CLASS III-B NON-METAL 36-CH Cover: 2-15 FT CPRC CLASS III 42-CH Cover: 2-15 FT PACS 28x20-CH Cover: 1.5-9 FT CP CLASS IV 12-CH Cover: 1-25 FT CPRC CLASS III 48-CH Cover: 2-15 FT PACS 35x24-CH Cover: 1.5-9 FT CP CLASS IV 15-CH Cover: 1-25 FT CPRC CLASS III 54-CH Cover: 2-15 FT PACS 42x28-CH Cover: 1.5-9 FT CP CLASS IV 18-CH Cover: 1-25 FT CPRC CLASS III 60-CH Cover: 2-15 FT PACS 49x32-CH Cover: 1.5-7 FT CP CLASS IV 21-CH Cover: 1-25 FT CPRC CLASS III 66-CH Cover: 2-15 FT PACS 57x37-CH Cover: 1.5-7 FT CP CLASS IV 24-CH Cover: 1-25 FT CPRC CLASS III 72-CH Cover: 2-15 FT PACS 64x43-CH Cover: 1.5-7 FT CP CLASS IV 30-CH Cover: 1-25 FT CPRC CLASS III 78-CH Cover: 2-15 FT PACS 71x47-CH Cover: 1.5-7 FT CP CLASS IV 36-CH Cover: 1-25 FT CPRC CLASS III 84-CH Cover: 2-15 FT PACS 77x52-CH Cover: 1.5-7 FT CP CLASS IV 42-CH Cover: 1-25 FT CPRC CLASS III 90-CH Cover: 2-15 FT PACS 83x57-CH Cover: 1.5-8 FT CP CLASS IV 48-CH Cover: 1-25 FT CPRC CLASS III 96-CH Cover: 2-15 FT CP CLASS IV 54-CH Cover: 1-25 FT CPRC CLASS III 102-CH Cover: 2-15 FT PAPCCS 17x13-CH Cover: 1.5-13 FT CP CLASS IV 60-CH Cover: 1-25 FT CPRC CLASS III 108-CH Cover: 2-15 FT PAPCCS 21x15-CH Cover: 1.5-12 FT CP CLASS IV 72-CH Cover: 1-25 FT CPRC CLASS IV 12-CH Cover: 1-25 FT PAPCCS 24x18-CH Cover: 1.5-10 FT CP CLASS IV 84-CH Cover: 1-25 FT CPRC CLASS IV 15-CH Cover: 1-25 FT PAPCCS 28x20-CH Cover: 1.5-9 FT CP CLASS V 12-CH Cover: 1-35 FT CPRC CLASS IV 18-CH Cover: 1-25 FT PAPCCS 35x24-CH Cover: 1.5-9 FT CP CLASS V 15-CH Cover: 1-35 FT CPRC CLASS IV 21-CH Cover: 1-25 FT PAPCCS 42x28-CH Cover: 1.5-7 FT CP CLASS V 18-CH Cover: 1-35 FT CPRC CLASS IV 24-CH Cover: 1-25 FT PAPCCS 49x32-CH Cover: 1.5-7 FT CP CLASS V 21-CH Cover: 1-35 FT CPRC CLASS IV 27-CH Cover: 1-25 FT PAPCCS 57x37-CH Cover: 1.5-7 FT CP CLASS V 24-CH Cover: 1-35 FT CPRC CLASS IV 30-CH Cover: 1-25 FT PAPCCS 64x43-CH Cover: 1.5-7 FT CP CLASS V 30-CH Cover: 1-35 FT CPRC CLASS IV 36-CH Cover: 1-25 FT PAPCCS 71x47-CH Cover: 1.5-7 FT CP CLASS V 36-CH Cover: 1-35 FT CPRC CLASS IV 42-CH Cover: 1-25 FT PAPCCS 77x52-CH Cover: 1.5-7 FT CP CLASS V 42-CH Cover: 1-35 FT CPRC CLASS IV 48-CH Cover: 1-25 FT PAPCCS 83x57-CH Cover: 1.5-8 FT CP CLASS V 48-CH Cover: 1-35 FT CPRC CLASS IV 54-CH Cover: 1-25 FT CP CLASS V 54-CH Cover: 1-35 FT CPRC CLASS IV 60-CH Cover: 1-25 FT PACSAC 17x13-CH Cover: 1.5-13 FT CP CLASS V 60-CH Cover: 1-35 FT CPRC CLASS IV 66-CH Cover: 1-25 FT PACSAC 21x15-CH Cover: 1.5-12 FT CP CLASS V 72-CH Cover: 1-35 FT CPRC CLASS IV 72-CH Cover: 1-25 FT PACSAC 24x18-CH Cover: 1.5-10 FT CP CLASS V 84-CH Cover: 1-35 FT CPRC CLASS IV 78-CH Cover: 1-25 FT PACSAC 28x20-CH Cover: 1.5-9 FT CPRC CLASS IV 84-CH Cover: 1-25 FT PACSAC 35x24-CH Cover: 1.5-9 FT CPCS 12-CH Cover: 1-40 FT CPRC CLASS V 12-CH Cover: 1-35 FT PACSAC 42x28-CH Cover: 1.5-7 FT CPCS 15-CH Cover: 1-40 FT CPRC CLASS V 15-CH Cover: 1-35 FT PACSAC 49x32-CH Cover: 1.5-7 FT CPCS 18-CH Cover: 1-40 FT CPRC CLASS V 18-CH Cover: 1-35 FT PACSAC 57x37-CH Cover: 1.5-7 FT CPCS 21-CH Cover: 1-40 FT CPRC CLASS V 21-CH Cover: 1-35 FT PACSAC 64x43-CH Cover: 1.5-7 FT CPCS 24-CH Cover: 1-40 FT CPRC CLASS V 24-CH Cover: 1-35 FT PACSAC 71x47-CH Cover: 1.5-7 FT CPCS 30-CH Cover: 1-40 FT CPRC CLASS V 27-CH Cover: 1-35 FT PACSAC 77x52-CH Cover: 1.5-7 FT CPCS 36-CH Cover: 1-40 FT CPRC CLASS V 30-CH Cover: 1-35 FT PACSAC 83x57-CH Cover: 1.5-8 FT CPCS 42-CH Cover: 1-40 FT CPRC CLASS V 36-CH Cover: 1-35 FT CPCS 48-CH Cover: 1-40 FT CPRC CLASS V 42-CH Cover: 1-35 FT PCP Cover: 2-15 FT CPCS 54-CH Cover: 1-40 FT CPRC CLASS V 48-CH Cover: 1-35 FT PCPCS Cover: 1-49 FT CPCS 60-CH Cover: 1-58 FT CPRC CLASS V 54-CH Cover: 1-35 FT PCPRC Cover: 2-15 FT CPCS 72-CH Cover: 1-49 FT CPRC CLASS V 60-CH Cover: 1-35 FT CPCS 84-CH Cover: 1-42 FT CPRC CLASS V 66-CH Cover: 1-35 FT CPCS 96-CH Cover: 1-37 FT CPRC CLASS V 72-CH Cover: 1-35 FT CPRC CLASS V 84-CH Cover: 1-35 FT CPCSPC 12-CH Cover: 1-40 FT CPCSPC 15-CH Cover: 1-40 FT CPRCHE CLASS HE-III 14x23-CH Cover: 2-15 FT CPCSPC 18-CH Cover: 1-40 FT CPRCHE CLASS HE-III 19x30-CH Cover: 2-15 FT CPCSPC 21-CH Cover: 1-40 FT CPRCHE CLASS HE-III 24x38-CH Cover: 2-15 FT CPCSPC 24-CH Cover: 1-40 FT CPRCHE CLASS HE-III 29x45-CH Cover: 2-15 FT CPCSPC 30-CH Cover: 1-40 FT CPRCHE CLASS HE-III 34x53-CH Cover: 2-15 FT CPCSPC 36-CH Cover: 1-40 FT CPRCHE CLASS HE-III 38x60-CH Cover: 2-15 FT CPCSPC 42-CH Cover: 1-40 FT CPRCHE CLASS HE-III 43x68-CH Cover: 2-15 FT CPCSPC 48-CH Cover: 1-40 FT CPRCHE CLASS HE-III 48x76-CH Cover: 2-15 FT CPCSPC 54-CH Cover: 1-40 FT CPRCHE CLASS HE-III 53x83-CH Cover: 2-15 FT CPCSPC 60-CH Cover: 1-58 FT CPRCHE CLASS HE-III 58x91-CH Cover: 2-15 FT CPCSPC 72-CH Cover: 1-49 FT CPRCHE CLASS HE-III 63x98-CH Cover: 2-15 FT CPCSPC 84-CH Cover: 1-42 FT CPRCHE CLASS HE-III 68x106-CH Cover: 2-15 FT CPCSPC 96-CH Cover: 1-37 FT CPRCHE CLASS HE-IV 14x23-CH Cover: 1-25 FT CPRCHE CLASS HE-IV 19x30-CH Cover: 1-25 FT CPRCHE CLASS HE-IV 24x38-CH Cover: 1-25 FT CPRCHE CLASS HE-IV 29x45-CH Cover: 1-25 FT CPRCHE CLASS HE-IV 34x53-CH Cover: 1-25 FT CP = CULVERT PIPE CPCPE - CULVERT PIPE CORRUGATED POLYETHYLENE CPCPP = CULVERT PIPE CORRUGATED POLYPROPYLENE CPCS = CULVERT PIPE CORRUGATED STEEL CPCSPC = CULVERT PIPE CORRUGATED STEEL POLYMER COATED CPCSAC = CULVERT PIPE CORRUGATED STEEL ALUMUM COATED CPCA = CULVERT PIPE CORRUGATED ALUMUM CPCP = CULVERT PIPE CORRUGATED POLYETHYLENE CPRC = CULVERT PIPE REFORCED CONCRETE CPRCHE = CULVERT PIPE REFORCED CONCRETE HORIZONTAL ELLIPTICAL PSP = PIPE STRUCTURAL PLATE PASP = PIPE ARCH STRUCTURAL PLATE PACS = PIPE ARCH CORRUGATED STEEL PAPCCS = PIPE ARCH POLYMER COATED CORRUGATED STEEL PACSAC = PIPE ARCH CORRUGATED STEEL ALUMUM COATED PCP = PIPE CATTLE PASS PCPCS = PIPE CATTLE PASS CORRUGATED STEEL PCPRC = PIPE CATTLE PASS REFORCED CONCRETE Page 70 of 107 Last updated: 6/18/2015

Storm Sewer Summary (updated 6/12/15) Pipe Rules Structures Rules SSPC 6-CH Cover and Slope: 1-15 FT Slope: 0.3-10% Max Length: 350 FT CATCH BASS 3-FT Max Dia: 1.25 FT Sump: 2 FT SSPC 8-CH Cover and Slope: 1-15 FT Slope: 0.3-10% Max Length: 350 FT CATCH BASS 4-FT Max Dia: 2 FT Sump: 2 FT SSPC 10-CH Cover and Slope: 1-15 FT Slope: 0.3-10% Max Length: 350 FT CATCH BASS 5-FT Max Dia: 3 FT Sump: 2 FT SSPC 12-CH Cover and Slope: 1-15 FT Slope: 0.3-10% Max Length: 350 FT CATCH BASS 6-FT Max Dia: 3.5 FT Sump: 2 FT SSPC 15-CH Cover and Slope: 1-15 FT Slope: 0.3-10% Max Length: 350 FT CATCH BASS 2X3-FT Max Dia: 2 FT Sump: 2 FT SSPRC CLASS II 12-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 350 FT CATCH BASS 2.5X3-FT Max Dia: 2 FT Sump: 2 FT SSPRC CLASS II 15-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 350 FT SSPRC CLASS II 18-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 350 FT MANHOLES 3-FT Max Dia: 1.25 FT SSPRC CLASS II 21-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 350 FT MANHOLES 4-FT Max Dia: 2 FT SSPRC CLASS II 24-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 350 FT MANHOLES 5-FT Max Dia: 3 FT SSPRC CLASS II 27-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 400 FT MANHOLES 6-FT Max Dia: 3.5 FT SSPRC CLASS II 30-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 400 FT MANHOLES 7-FT Max Dia: 4 FT SSPRC CLASS II 36-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 400 FT MANHOLES 8-FT Max Dia: 5 FT SSPRC CLASS II 42-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 500 FT SSPRC CLASS II 48-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 500 FT MANHOLES 3x3-FT Max Dia: 2 FT SSPRC CLASS II 54-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 500 FT MANHOLES 4x4-FT Max Dia: 3.5 FT SSPRC CLASS II 60-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT MANHOLES 5x5-FT Max Dia: 3.5 FT SSPRC CLASS II 66-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT MANHOLES 6x6-FT Max Dia: 4.5 FT SSPRC CLASS II 72-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT SSPRC CLASS II 78-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT LETS 3-FT Max Dia: 1.25 FT SSPRC CLASS II 84-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT LETS 4-FT Max Dia: 2 FT SSPRC CLASS II 90-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT SSPRC CLASS II 96-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT LETS 2X2-FT Max Dia: 1 FT SSPRC CLASS II 102-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT LETS 2X2.5-FT Max Dia: 1.5 FT SSPRC CLASS II 108-CH Cover and Slope: 2-11 FT Slope: 0.3-10% Max Length: 1000 FT LETS 2x3-FT Max Dia: 2 FT SSPRC CLASS III 12-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 350 FT LETS 2.5x3-FT Max Dia: 2 FT SSPRC CLASS III 15-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 350 FT SSPRC CLASS III 18-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 350 FT SSP = STORM SEWER PIPE SSPRC CLASS III 21-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 350 FT SSPC = STORM SEWER PIPE COMPOSITE SSPRC CLASS III 24-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 350 FT SSPRC = STORM SEWER PIPE REFORCED CONCRETE SSPRC CLASS III 27-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 400 FT SSPNRC = STORM SEWER PIPE NONREFORCED CONCRETE SSPRC CLASS III 30-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 400 FT SSPRCHE = STORM SEWER PIPE REFORCED CONCRETE HORIZONTAL ELLIPTICAL SSPRC CLASS III 36-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 400 FT SSPRC CLASS III 42-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 500 FT SSPRC CLASS III 48-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 500 FT Concrete Pipe Wall Thickness (inches) SSPRC CLASS III 54-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 500 FT 12 2 SSPRC CLASS III 60-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 15 2.25 SSPRC CLASS III 66-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 18 2.5 SSPRC CLASS III 72-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 21 2.75 SSPRC CLASS III 78-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 24 3 SSPRC CLASS III 84-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 27 3.25 SSPRC CLASS III 90-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 30 3.5 SSPRC CLASS III 96-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 36 4 SSPRC CLASS III 102-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 42 4.5 SSPRC CLASS III 108-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT 48 5 SSPRC CLASS IV 12-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 350 FT 54 5.5 SSPRC CLASS IV 15-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 350 FT 60 6 SSPRC CLASS IV 18-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 350 FT 66 6.5 SSPRC CLASS IV 21-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 350 FT 72 7 SSPRC CLASS IV 24-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 350 FT 78 7.5 SSPRC CLASS IV 27-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 400 FT 84 8 SSPRC CLASS IV 30-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 400 FT 90 8.5 SSPRC CLASS IV 36-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 400 FT 96 9 SSPRC CLASS IV 42-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 500 FT 102 9.5 SSPRC CLASS IV 48-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 500 FT 108 10 SSPRC CLASS IV 54-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 500 FT 14x23 2.75 SSPRC CLASS IV 60-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 1000 FT 19x30 3.25 SSPRC CLASS IV 66-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 1000 FT 24x38 3.75 SSPRC CLASS IV 72-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 1000 FT 29x45 4.5 SSPRC CLASS IV 78-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 1000 FT 34x53 5 SSPRC CLASS IV 84-CH Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 1000 FT 38x60 5.5 SSPRC CLASS V 12-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 350 FT 43x68 6 SSPRC CLASS V 15-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 350 FT 48x76 6.5 SSPRC CLASS V 18-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 350 FT 53x83 7 SSPRC CLASS V 21-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 350 FT 58x91 7.5 SSPRC CLASS V 24-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 350 FT 63x98 8 SSPRC CLASS V 27-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 400 FT 68x106 8.5 SSPRC CLASS V 30-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 400 FT SSPRC CLASS V 36-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 400 FT Inlet Structure Layout SSPRC CLASS V 42-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 500 FT Structure Centerline o/s from SSPRC CLASS V 48-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 500 FT Cover Back of Curb (ft) Surface Elev. Adj. (FT)* SSPRC CLASS V 54-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 500 FT A 1 0.06 SSPRC CLASS V 60-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 1000 FT B 1 0.06 SSPRC CLASS V 66-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 1000 FT BW 1 0.04** SSPRC CLASS V 72-CH Cover and Slope: 1-35 FT Slope: 0.3-10% Max Length: 1000 FT F 1.5 0.09 H 1 0.06 SSPNRC CLASS 3 6-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT S 0 0 SSPNRC CLASS 3 8-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT T 1.27 0.08 SSPNRC CLASS 3 10-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT V 1.44 0.04 SSPNRC CLASS 3 12-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT WM 1.25 0.08 SSPNRC CLASS 3 15-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT Z 0.75 0.05 SSPNRC CLASS 3 18-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT * Based on 0.0625 ft/ft gutter slope SSPNRC CLASS 3 21-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT ** Based on 0.04 ft/ft shoulder slope SSPNRC CLASS 3 24-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 350 FT SSPNRC CLASS 3 30-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 400 FT SSPNRC CLASS 3 36-CH Cover and Slope: 6-10 FT Slope: 0.3-10% Max Length: 400 FT SSPRCHE CLASS HE-III 14x23-CH SSPRCHE CLASS HE-III 19x30-CH SSPRCHE CLASS HE-III 24x38-CH SSPRCHE CLASS HE-III 29x45-CH SSPRCHE CLASS HE-III 34x53-CH SSPRCHE CLASS HE-III 38x60-CH SSPRCHE CLASS HE-III 43x68-CH SSPRCHE CLASS HE-III 48x76-CH SSPRCHE CLASS HE-III 53x83-CH SSPRCHE CLASS HE-III 58x91-CH SSPRCHE CLASS HE-III 63x98-CH SSPRCHE CLASS HE-III 68x106-CH SSPRCHE CLASS HE-IV 14x23-CH SSPRCHE CLASS HE-IV 19x30-CH SSPRCHE CLASS HE-IV 24x38-CH SSPRCHE CLASS HE-IV 29x45-CH SSPRCHE CLASS HE-IV 34x53-CH Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 350 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 350 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 400 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 500 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 500 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 500 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT Cover and Slope: 2-15 FT Slope: 0.3-10% Max Length: 1000 FT Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 350 FT Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 350 FT Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 400 FT Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 400 FT Cover and Slope: 1-25 FT Slope: 0.3-10% Max Length: 500 FT Page 71 of 107 Last updated: 6/18/2015

Storm and Sanitary Analysis (SSA) Project Options Settings for Storm Sewer Use Hydrodynamic Enable overflow ponding at nodes Hydrology: Rational and/or TR-20 Time of Concentration: SCS TR-55 is okay for Rational or TR-20. If known, you can also use User-Defined. Minimum allowable is 5 min. Analysis Options Settings for Storm Sewer Set reporting time step to 1 min (TR-20) Set routing time step to 1 sec (TR-20) 1 day analysis length Other Storm Sewer Tips/Hints With the WisDOT customization, Civil 3D is set to export pipe network inlets as FHWA HEC-22 generic inlets in SSA. Once in SSA, you have the option to switch the inlets to Neenah, if desired. However, once they are switched, Civil 3D will switch them back to FHWA if you re-export the Pipe Network to SSA. Civil 3D exports inlets to SSA with the correct grate dimensions. However, the grate type may not be correct and needs to be checked and changed if necessary. Civil 3D exports inlets to SSA with the On Grade or On Sag attribute defined in Civil 3D. There are IDF curves for each of the Wisconsin counties available in SSA. They are located here: C:\ProgramData\Autodesk\SSA 2014\Database The SCS Type II is available in SSA. Sheet Layouts and Sheet Sets (added 06/03/2015) Subset Sheet Layouts Subset sheet layouts are to be used with Sheet Sets to set the Title text fields in a layout title with the name of the subset the layout is under. This can now allow for drawings with different titles to be contained in one Sheet Set. Page 72 of 107 Last updated: 6/18/2015

Subset layouts in sheet template files are prefixed with S-. All the WisDOT sheet templates have two sets of layouts that contain title blocks and preset viewports set to various scales. The set without the S- prefix contain automatic text fields that are tied to the sheet set custom properties that begin with Title. Example: Title Plan Profile Using Subset Sheet Layouts with Sheet Sets Subset sheet layouts can be used in place of standard sheet layouts when: Adding individual layouts from template Creating detail sheet layouts Creating view frames to create plan or plan & profile sheets Creating section views to create section sheets To use a subset sheet layout: 1. Open the Sheet Set Manager 2. Create a new sheet set or open an existing sheet set. 3. Create a New Subset 4. Enter a Subset Name. (The Subset Name will be used to populate the sheet title text field in the WisDOT title block for subset sheet layouts added to a subset.) Page 73 of 107 Last updated: 6/18/2015

5. Import subset sheet layouts so they are under the Subset. Page 74 of 107 Last updated: 6/18/2015

All other text fields in the title blocks remain controlled by sheet set custom properties. Page 75 of 107 Last updated: 6/18/2015

Layouts Best Practice The best practice is to use one or the other template layout sets, but do not mix them. Changing existing custom layout fields to Subset fields The Title fields in the layouts that use the custom properties can be switched to fields that are defined by the Sheet Set Subset(s). 1. In the layout of a drawing already attached to a Sheet Set. Double-click the left mouse button while hovering over the Title text field. 2. Double-click the left mouse button while hovering over the highlighted text field in the text box. 3. Select CurrentSheetSubSet in the Field names list. 4. Press OK, to dismiss the dialog. 5. Add Subsets to the Sheet Set, and organize drawings under the proper subsets to reflect the title name required for each drawing. 6. Save the drawing to reflect the field changes. Page 76 of 107 Last updated: 6/18/2015

Exporting GIS Data (added 06/03/2015) Converting Civil 3D Parcels to GIS Shapefiles This section describes the workflow for translating parcels with associated attributes, such as parcel number and parcel area, into shapefiles for use with GIS software such as ArcGIS. Verify the Coordinate System Verify the coordinate system in a parcel drawing by looking in the drawing status bar. If there is no box showing a coordinate system then there is not a coordinate system assigned to the drawing. To set a coordinate system use the Set Coordinate System Multiple DWGs macro found in the Toolbox tab of the Toolspace under WisDOT Macros. This tool can be used for a single drawing or multiple drawings. Note: The macro cannot be used on a drawing that is currently open. 1. Close the target drawing(s) if currently open. 2. Execute the Set Coordinate System Multiple DWGs macro. 3. Browse to the drawing(s) by clicking Add 4. Select a county from the list in the dialog box and select the datum. 5. Click Process All to set the coordinate system. Export Civil 3D Objects to SDF Civil 3D objects, such as parcels, must be exported to Autodesk Spatial Data Format (SDF) before exporting to shapefile. This converts the parcels into data objects (polylines) with attributes associated to the data objects. Parcels can be converted to polylines in other ways to create shapefiles, but no other method includes the parcel attributes except exporting to SDF. Page 77 of 107 Last updated: 6/18/2015

Note: Civil 3D objects with a style of _No Display will not export. Visible linework must be present in the drawing in order to export a Civil 3D object. 1. On the Output tab of the ribbon choose Export Civil Objects to SDF. 2. The Export to SDF dialog box will appear. Set the file name and location, confirm that the coordinate system information is correct, and click OK to export all Civil 3D Objects to SDF. Import SDF File into New Drawing 1. Start a new drawing. 2. Type MAPIMPORT in the command line. 3. Choose Files of type: Autodesk SDF (*.sdf), browse to an SDF file, and click OK. The Import dialog box will appear. 4. Set the coordinate system for the new drawing. 5. Check box next to Import polygons as closed polylines 6. Uncheck all except Parcels in the Input Layer column. 7. Click in the Data column in the Parcels row to set attribute data. Page 78 of 107 Last updated: 6/18/2015

8. Set the radio button for Create object data in the Attribute Data dialog box. 9. Click Select Fields A list of attributes associated with parcels will appear in the Object Data Mapping dialog box. Select or deselect attributes to import. 10. Click OK on all open dialog boxes to import the SDF file. Parcel shapes are inserted into the drawing as polylines with attributes. Export Polylines with Attributes to a Shapefile 1. Type MAPEXPORT in the command line. This will bring up the Export Location dialog box. 2. Choose Files of type: ESRI Shapefile (*.shp), enter a file name, and click OK. The Export dialog box will appear. 3. On the Selection tab, select Line as the Object type. 4. Choose either Select all to include all linework in the drawing, or choose Select manually. To select objects manually click the selection button. Page 79 of 107 Last updated: 6/18/2015

5. On the Data tab, click Select Attributes Page 80 of 107 Last updated: 6/18/2015

6. The Select Attributes dialog will appear. Under Object Data check the attributes to be exported and click OK. 7. Click OK in the Export dialog box and a shapefile will be created, complete with attribute data, for use with GIS applications. WisDOT Civil 3D Linetypes (Updates added 10/05/2014) This document will describe the changes to the WisDOT custom linetypes; the changes in the drawing template settings; and outline the workflows for both true size and annotation scales in the new template. Linetypes that are true size such as pavement markings and barrels will need to be scaled using the objects properties. The rest of the linetypes such as easement lines and utilities will automatically adhere to the annotation scale in the layouts. Linetype scale reference There are three linetype settings to consider when setting up your drawings: LTSCALE, PSLTSCALE, & MSLTSCALE. Linetype Scale LTSCALE controls the dash spacing and symbol size in linetypes. For WisDOT new linetypes the default scale factor will be set 1.00. A value larger than 1 will scale the linetype up and a value less than 1 will scale the linetype down. The Linetype scale is an absolute value and not relative value. MSLTSCALE Model Space Line Type Scaling only has two options ON or F. Setting MSLTSCALE to 1 (ON) is the default setting. Setting MSLTSCALE to 1 (ON) will cause the Line type scale of any geometry in model space to be scaled by the Annotation scale. This allows you to have a preview of how the line type scale might look when seen through a scaled viewport. MSLTSCALE Overrides LTSCALE in Modelspace, but it doesn t effect Paperspace, so it won t change how your geometry looks inside your viewports. Using MSLTSCALE is a really good way of checking that your linetypes are going to look as you expect them to, without having to Flick back and forth between Paperspace and Modelspace. Page 81 of 107 Last updated: 6/18/2015

Setting MSLTSCALE to 0 (F) will cause the Linetypes displayed on the Model tab to be not scaled by the annotation scale. PSLTSCALE This variable controls the linetype scaling of geometry displayed in paper space viewports Paper Space Line Type Scale. This variable only has two settings. Setting PSLTSCALE to 0 (Off) will mean that the linetype scale factor of your modelspace geometry will not be effected by the scale of your viewport. Setting PSLTSCALE to 1 (On) means that the line type scale of your modelspace geometry will be scaled to match the viewport scale. If you use paper space layouts, turning paper space line type scaling on ensures that all your geometry will have the correct line type scale, no matter what the viewport scale is. CELTSCALE Sets the current object linetype scaling factor. The linetype scaling for any new objects placed in the drawing file will be relative to the LTSCALE command setting. A line created with CELTSCALE = 2 in a drawing with LTSCALE set to 0.5 would appear the same as a line created with CELTSCALE = 1 in a drawing with LTSCALE = 1. The default value is set to 1. Working with Existing Files If your drawing is nearing completion and linetypes are working with your project there should be no need to update your drawing from the new template. To determine if your drawing file has the old linetypes, type LTSCALE at the command line. If it is set to 0.005 then you are using the old template with the older linetypes. Settings for previous Templates Prior to August 2013 all WisDOT drawing templates had the following settings. LTSCALE = 0.005 CELTSCALE = 1.0 PSLTSCALE = 1 MSLTSCALE = 1 Importing Older Linetypes into Older Drawings When you need to update your old drawing with compatible linetypes follow these steps. 4. In the command line type linetype. The Linetype Manager dialog will appear. Page 82 of 107 Last updated: 6/18/2015

5. In the Linetype dialog click the Load button. The Load or Reload Linetypes dialog will appear. 6. From the Load or Reload Linetypes dialog click the File button. The Select Linetype File dialog will appear. 7. Path to C:\Program Files\Autodesk\AutoCAD Civil 3D 2012\Support\Linetypes and select the file wisdotlt-pre-aug2013.lin click Open. The linetypes will be loaded into the Load or Reload Linetypes dialog. 8. Select the linetype(s) you wish to add and then click the OK button. The Linetypes Reload Linetypes dialog will appear. Page 83 of 107 Last updated: 6/18/2015

a. You can hold down Ctrl to select several linetypes b. SHIFT to select a range of linetypes c. Right click popup menu Select All 9. From the Linetypes Reload Linetypes dialog select Reload all selected linetypes. The new linetypes will be added to the drawing file. 10. Click the OK button in the Linetype Manager dialog. The dialog will close. 11. Regen your drawing to see the change in scales. Workflow for Updating New Linetypes into Older Drawings If you have an old drawing and you can take advantage of updating your drawing with the new linetypes follow these steps. 1. Prior to importing the linetypes verify the following variables are set. To read and set these, type the variable name at the command line. a. LTSCALE = 1.0 b. CELTSCALE = 1.0 c. PSLTSCALE = 1 d. MSLTSCALE = 1 2. If any object overrides are applied to your line work the following steps will not show the updated linetypes. Select all line work in the drawing file and verify ALL Linetype properties in the drawing file are set to ByLayer and the Linetype scale is set to 1. Page 84 of 107 Last updated: 6/18/2015

3. In the command line type linetype. The Linetype Manager dialog will appear. 4. In the Linetype dialog click the Load button. The Load or Reload Linetypes dialog will appear. 5. From the Load or Reload Linetypes dialog click the File button. The Select Linetype File dialog will appear. 6. Browse to the new linetype file a. For Civil 3D 2012 path to C:\Program Files\Autodesk\AutoCAD Civil 3D 2012\Support\Linetypes and select the file wisdot-lt.lin click Open. The linetypes will be loaded into the Load or Reload Linetypes dialog. b. For Civil 3D 2014 path to C:\WisDOT\Stnd\c3d2014\Support\Linetype and select the file wisdot_2014.lin click Open. The linetypes will be loaded into the Load or Reload Linetypes dialog. Page 85 of 107 Last updated: 6/18/2015

7. Select All the linetypes and then click the OK button. The Linetypes Reload Linetypes dialog will appear. a. You can hold down Ctrl to select several linetypes b. SHIFT to select a range of linetypes c. Right click popup menu Select All. 8. From the Linetypes Reload Linetypes dialog select Reload all selected linetypes. The new linetypes will be added to the drawing file and the old linetype definitions will be changed to match the new definitions. 9. Click the OK button in the Linetype Manager dialog. The dialog will close. 10. Regen your drawing to see the change in scales. Updating Layers with New ByLayer Symbology (added 10-05-14) The linetypes are now in the design file but the layer definitions need to be updated to reflect the new linetype names. 11. From the ribbon Manage tab > CAD Standards panel > Layer Translator. The Layer Translator dialog will appear. Page 86 of 107 Last updated: 6/18/2015

12. Pick the Load button from the Translate To section of the dialog. 13. Change the Files of type to Drawing Template (*.dwt) 14. Path to the WisDOT templates and select wisdot12.dwt or wisdot14.dwt depending on the version you are using, and click Open. The Layers will be loaded in the Translate To section of the dialog. Page 87 of 107 Last updated: 6/18/2015

15. Click the Map Same button. The layers will be added to the Layer Translation Mappings section of the dialog. Page 88 of 107 Last updated: 6/18/2015

16. Click the Translate button. An alert box will appear asking if you want to save the mapping information. Click Translate Only. The layers will be translated to the new layer scheme. 17. Verify the layers are correct by opening the Layer manager and checking a couple P_PM layers. For a complete listing of Layers that changed see Appendix A. Page 89 of 107 Last updated: 6/18/2015

18. In the command line type PURGE. Purge all unused linetypes from the drawing file. 19. Save the drawing file. Workflow to update Xref files with old linetypes If your file has an xref file using the old linetypes you will need to update the linetypes and the properties of the xref-dependent layers. 13. Open each Xref design file that is attached to a host file and follow the workflow above named Workflow for Updating New Linetypes into Older Drawings. 14. After each xref file is updated then open each Host file (the drawing file that is consuming the external referenced drawings). 15. In the command line type VISRETA=0. Note: Setting Visretain to 0 will allow each xref to be reloaded and the layer table, as stored in the reference drawing (xref), will take precedence. 16. Click View tab > Palettes panel > External References Palette Command: xref 17. Select each xref to be reloaded and Right click. From the menu select Reload. The reference will be reloaded and the new layer properties will be updated. 18. In the command line set VISRETA back to 1. 19. Save the host file and Exit. Working with the New Template Settings for New Templates After August 2013 all WisDOT drawing templates have the following settings. LTSCALE = 1.0 CELTSCALE = 1.0 PSLTSCALE = 1 MSLTSCALE = 1 Workflows for True size Linetypes Objects using the True Size linetypes must be scaled by changing the linetype scale of the object. 20. Select the objects whose linetype scale you want to change. 21. Click Home tab > Palettes panel > Properties. 22. On the Properties palette, click the Linetype scale control. 23. Change the linetype scale that you want to assign to the objects. Page 90 of 107 Last updated: 6/18/2015

Layout scales = Linetype scale When LTSCALE is set to 1 use the equation (linetype scale = (1/Desired Scale) to determine the linetype scale. Below is a list of common Linetype scale settings. Viewport Scale Linetype Scale 1:10FT = 0.10 1:20FT = 0.05 1:40FT = 0.025 1:50FT = 0.02 1:100FT = 0.01 1:200FT = 0.005 In a drawing that contains a vast majority of objects using the True size linetypes, it is a good practice to set MSLTSCALE to 0 (zero). MSLTSCALE sets whether the objects linetypes are affect by the annotation scale in the Model tab. 0 = Off and 1 = On. Setting MSLTSCALE off will display the objects linetypes as true size. The same way it will be displayed in the Layout viewport. Annotative Linetypes To change the linetype of an object, to use the layout s annotation scale. 24. Verify that LTSCALE is set to 1, PSLSCALE is set to 1 and MSLTSCALE is set to 1. 25. Select the objects whose linetype scale you want to use annotation scale. 26. Click Home tab > Palettes panel > Properties. 27. On the Properties palette, click the Linetype scale control. 28. Change the linetype scale to 1.0. Page 91 of 107 Last updated: 6/18/2015

Linetypes Best Practices 1. Linetype scaling on or off with XREFs needs to be a wholesale choice. Turning it off in a file only impacts the view in that file. So unless you're going to have linetype scaling turned off in all the files you're going to use, it's not helpful in getting the real world linetypes to display correctly. Leave MSLTSCALE on always. 2. While not necessary, it may be easiest to keep all real world linetypes in files separate from associative linetypes. I wouldn't do this on mapping files, but it may simplify things for pavement marking and construction staging files. 3. Object linetype scaling needs to be identical for all of the real world linetypes that you intend to use together. The reason for this is the global effect of LTSCALE and not being able to differentiate LTSCALE for different XREFs. For simplicity sake, I would recommend having the object linetype scaling being identical across a project. You could have it as something like 1 inch: 1 ft to keep object linetype scale as 1 on all of the objects, but associative linetypes would look awful in modelspace. So I would recommend going with something like 1 inch: 100 ft and then for real-world linetype files, set CELTSCALE to 0.01 so that all objects you create inherent that LTSCALE. 4. It is possible to create sheets with the different scales than the default scale you choose with real world linetypes. To do so, XREF in the real world linetype files that you need and change the LTSCALE of the sheet file you're working in. For example, if you set your default scale to 1 inch:100 ft and you want to create sheets at 1 inch: 50 ft, set the LTSCALE for the 1 inch: 50 ft. file to 0.5. 5. You cannot create a single file with layouts that have different scales and get real world linetypes to look correct in all the layouts. This is an okay workflow if you only have associative linetypes. Migrating blocks between Civil 3D versions (added 04/17/2015) It is good practice when migrating blocks to insert them into a blank out-of-the-box template. This way we avoid saving forward any old settings contained in the drawings within which these older blocks reside. Depending on the scale of migration we can accomplish this a couple of different ways. WORKFLOW 1 Migrating a small number of blocks Start a new block library drawing with 2014 template Start a new drawing using the out-of-the-box acad.dwt template found here: Page 92 of 107 Last updated: 6/18/2015

C:\Users\<user name>\appdata\local\autodesk\c3d 2014\enu\template Insert older blocks using Design Center Open Design Center, and browse to the source drawing containing the blocks to be migrated. The reason this workflow is designed for migrating a small number of blocks is because Design Center only allows one block to be inserted at a time. That is not ideal for migrating hundreds of blocks, but it does work well for smaller numbers. Open the Blocks section in the source drawing in Design Center, and drag each block into model space one at a time. Otherwise, right-click on each block and choose Insert Block. Save the new block library drawing in the appropriate location with the appropriate name, and the newly migrated blocks are now ready to be used. WORKFLOW 2 Migrating many blocks Start a new block library drawing with 2014 template Start a new drawing using the out-of-the-box acad.dwt template found here: C:\Users\<user name>\appdata\local\autodesk\c3d 2014\enu\template Insert and explode existing block library drawing Click on the Insert tab of the Ribbon and then select the Insert button on the Block panel. In the Insert dialog box browse to the existing block library drawing you wish to migrate. Be sure that the Insertion point, Scale, and Rotation options are all unchecked. Be sure the Explode option is checked on. This will insert the entire drawing into the new 2014 drawing template and will explode into its individual objects. Page 93 of 107 Last updated: 6/18/2015

Clean up the new block library drawing Next we will run a few commands in order to clean unwanted items out of the new block library drawing. 1) Type PURGE in the command line. Be sure that the option for Confirm each item to be purged is unchecked and that the option for Purge nested items is checked on. Click on the Purge All button, and close the dialog box when the command is finished. Page 94 of 107 Last updated: 6/18/2015

2) Type PURGE in the command line. Type R to select the option Regapps. Hit enter to select the default asterisk for name of regapps to purge. This will select all regapps. Type N when prompted to verify each name to be purged. This will get rid of any 3 rd party apps running in the background. 3) Type AUDIT in the command line. Type Y when prompted to fix any errors detected in the drawing. Save the new block library drawing in the appropriate location with the appropriate name, and the newly migrated blocks are now ready to be used. Data Shortcut Best Practices (added 04/17/2015) Migrating a Project From Civil 3D 2012 to Civil 3D 2014 When migrating a project from Civil 3D version 2012 to version 2014 it is very important that you DO NOT do anything else with the project files other than migration. DO NOT move files. DO NOT copy files. DO NOT rename files or objects within the files. If there is a problem with data shortcuts while migrating a project we do not want to add variables to complicate troubleshooting. Page 95 of 107 Last updated: 6/18/2015

Follow the How to Re-path all subassemblies within project corridor drawings and Project Drawing Migration sections of the WisDOT User Readme document for the proper process to migrate your project drawings. If this process is followed, the data shortcuts will be migrated properly as well. DO NOT perform a SAVE AS command within the data shortcut editor in an attempt to migrate the data shortcuts to the new version. This will create a copy of all of the XML files for the data shortcuts which can create a problem. This will happen automatically when the above steps are followed. Moving a Project Location When moving a project location on the network drive you should move the ENTIRE project folder. This will ensure that all of the data shortcuts and their references will follow the relative paths of the moved data shortcut XML files. Next, open the data shortcut editor from the start menu, and navigate to the project shortcut folder. Perform a Find and Replace command on the paths in order to re-path them to the new data shortcut folder location. Renaming or Moving Individual Project Files Best practice for renaming or moving project files is not to do it at all, but in the event that it must be done you must first validate your data shortcuts after renaming or moving a file. Once the data shortcut list has been validated you must synchronize the references in any files which are consuming the data shortcuts coming from the file which was renamed or moved. DO NOT wait on validating the data shortcuts when these types of changes are made. It will cause problems downstream such as data shortcut duplications and general confusion among team members. It is also good practice to inform all team members of such a change so they are aware of it. Renaming Individual Drawing Objects The same practices should be applied to this type of project change as outlined in the above section for renaming or moving individual project files. Incorporating External Drawings into a Project When incorporating drawings from an external consultant copy over ONLY the drawings. DO NOT copy over any of the shortcut folders nor any of the XML files contained therein. If these files are replacing existing project files then archive the original files, and replace them in windows explorer with these new external files. Open these new files, and synchronize references. Repair all broken references by navigating to the proper source files from your project folder for each broken reference. If there were data shortcuts which were created from these external files you will need to recreate these data shortcuts in your project. Notable difference between Data Shortcuts in Civil 3D 2012 and in Civil 3D 2014 Data references, other than for surfaces, are now saved (cached) directly in the drawing files. This is a great benefit when sharing files remotely. This eliminates the need to re-route all data shortcuts to the source files in order to view and use the data as references. Page 96 of 107 Last updated: 6/18/2015

Updating settings and styles in production DWG files Most of the settings and styles that control a DWG file are contained within the file. Updates to a template file are not automatically brought into existing files. This topic covers the different methods for updating settings and styles for existing files in Civil 3D. Civil 3D Styles and Drawing Settings Update Use the import styles tool to update a DWG file's Civil 3D standards with those found in the latest WisDOT template. 16. Open the dwg file you wish to update in Civil 3D. 17. Manage ribbon => Styles panel => Import 18. Browse to template file containing standards you'd like to apply to the dwg file. In a standard Windows7 Civil 3D install, WisDOTxx.dwt is found at C:\Users\USERNAME\AppData\Local\Autodesk\C3D 2012\enu\Template\USWI. In a standard WindowsXP Civil 3D install, WisDOTxx.dwt is found at C:\Documents and Settings\USERNAME\Local Settings\Application Data\Autodesk\C3D 2012\enu\Template\USWI. In the Import Civil 3D Styles dialog box, you can review new Civil 3D standards that will be imported. You can also choose to delete standards that are no longer in the WisDOT template - if they aren't in use in the drawing. You can make modifications to the import/delete actions if you wish. You can turn on, or off import drawing settings. Details are available in Civil 3D Help documents. 19. Press OK. Save the dwg file. 20. Consider updating AutoCAD standards also. Page 97 of 107 Last updated: 6/18/2015

AutoCAD Standards Update Use the import styles tool to update a DWG file's AutoCAD standards with those found in the latest WisDOT template. 21. Open a new drawing using the template containing the new standards you want applied to the project dwg file. 22. C3D button => Save As => AutoCAD Drawing Standards. Remember where you save this DWS file. 23. Open the dwg file you wish to update. 24. Manage ribbon => CAD Standards panel => Configure 25. In the Configure Standards dialog box, Standards tab, click the + button and browse to you DWS file. 26. In the Configure Standards dialog box, Plug-Ins tab, select the types of standards you'd like to update. Usually you'd check all. 27. Click the Settings... button. The settings should look as shown. Page 98 of 107 Last updated: 6/18/2015

28. Click Check Standards... button 29. The tool will notify you of DWG layers that are no longer in the DWS standards file. You can cycle through this by clicking Next. The layer will not be deleted from the dwg file. 30. When the update is complete you will receive a notification with update statistics. Page 99 of 107 Last updated: 6/18/2015

31. Close the Check Standards dialog box 32. Manage ribbon => CAD Standards panel => Configure 33. Remove the DWS file from the drawing by clicking the X button. Click OK to close the Configure Standards dialog box. 34. Save the DWG file. Page 100 of 107 Last updated: 6/18/2015

Using Design Center to transfer layouts from one dwg file to another (changed 04/17/2015) (DWGUpdater interim workaround) When a dwg file is updated by the DWG Updater macro, layouts may get lost. DWG Update creates a backup copy of the original dwg file in a backup subfolder. The layouts can be saved by moving them from the backup file to the recently created updated file. Within Civil 3D, open the newly created dwg file in which the layouts are missing, keep it as your active drawing file Open Design Center In the Design Center folder view, browse to the backup dwg file containing layouts, expand the backup file in folder view Select layout category shown within file in Folder list Shift select to select all layouts in the backup file shown on the right side of Design Center. Page 101 of 107 Last updated: 6/18/2015

Right-click on the selected layouts, choose Add Layout(s) from the right-click menu Layouts are now in the updated dwg file, save and close. Appendix A Layers that changed linetypes Name Linetype New Linetype Old E_AREA Wisdot3 DGN Style 3 E_AREA_Primary_Environmental_Corridor Wisdot3 DGN Style 3 E_BLD_Dash Wisdot3 DGN Style 3 E_BLD_Footing Wisdot1 DGN Style 1 E_BLD_Gazebo Wisdot3 DGN Style 3 E_BLD_HvyDash Wisdot3 DGN Style 3 E_BLD_Porch Wisdot1 DGN Style 1 E_BLD_Steps Wisdot1 DGN Style 1 E_BLD_ToiletPublic Wisdot2 DGN Style 2 E_DRN_ConcDitch Wisdot5 DGN Style 5 E_DRN_DrainTile Wisdot5 DGN Style 5 E_DRN_EndWall Wisdot5 DGN Style 5 E_DRN_Pipe Wisdot5 DGN Style 5 E_DRN_PipePlastic Wisdot5 DGN Style 5 E_DRN_PipeRein Wisdot5 DGN Style 5 E_DRN_RipRap_Area Wisdot3 DGN Style 3 E_DTM_Boundary Wisdot3 DGN Style 3 Page 102 of 107 Last updated: 6/18/2015

E_DTM_Building Wisdot5 DGN Style 5 E_DTM_CompDiscontinuity Wisdot2 DGN Style 2 E_DTM_ObscureArea Wisdot7 DGN Style 7 E_DTM_SlopeBottom Wisdot1 DGN Style 1 E_DTM_SlopeTop Wisdot1 DGN Style 1 E_DTM_WeakAreaApprox Wisdot3 DGN Style 3 E_DTM_WorkLine Wisdot4 DGN Style 4 E_DWY Wisdot3 DGN Style 3 E_DWY_BoatLanding Wisdot3 DGN Style 3 E_DWY_CE Wisdot3 DGN Style 3 E_DWY_FE Wisdot3 DGN Style 3 E_DWY_PE Wisdot3 DGN Style 3 E_FTMS_Conduit Wisdot2 DGN Style 2 E_FTMS_Loop Wisdot1 DGN Style 1 E_LTG_CID Wisdot4 DGN Style 4 E_LTG_Conduit Wisdot3 DGN Style 3 E_LTG_Footing Wisdot1 DGN Style 1 E_MAP_ContIndexWk Wisdot3 DGN Style 3 E_MAP_ContoursInterWk Wisdot3 DGN Style 3 E_MAP_Limits Wisdot3 DGN Style 3 E_MISCPROP_AirRunwayGrass Wisdot3 DGN Style 3 E_MISCPROP_AirRunwayPaved Wisdot3 DGN Style 3 E_MISCPROP_Bleacher Wisdot3 DGN Style 3 E_MISCPROP_Dash Wisdot3 DGN Style 3 Name Linetype New Linetype Old E_MISCPROP_HvyDash Wisdot3 DGN Style 3 E_MISCPROP_Monument Wisdot3 DGN Style 3 E_MISCPROP_Septic_Dash Wisdot3 DGN Style 3 E_MISCPROP_ShtDash Wisdot5 DGN Style 5 E_PATH Wisdot3 DGN Style 3 E_PATH_Sidewalk Wisdot5 DGN Style 5 E_PM Wisdot2 DGN Style 2 E_PR_Marsh Wisdot6 DGN Style 6 E_PR_Rock Wisdot2 DGN Style 2 E_PR_Utilities Wisdot7 DGN Style 7 E_RDWY_Edge Wisdot3 DGN Style 3 E_RDWY_Gravel Wisdot3 DGN Style 3 E_RDWY_PavtEdge Wisdot3 DGN Style 3 E_RDWY_ShldPaved Wisdot3 DGN Style 3 E_RR_Abandoned Wisdot3 DGN Style 3 E_RW_Break Wisdot3 DGN Style 3 E_RW_CSM Wisdot2 DGN Style 2 E_SGN_Footing Wisdot5 DGN Style 5 Page 103 of 107 Last updated: 6/18/2015

E_SIG_Conduit Wisdot3 DGN Style 3 E_SIG_IC Wisdot4 DGN Style 4 E_STRUCT_Joint Wisdot3 DGN Style 3 E_STRUCT_Pier Wisdot3 DGN Style 3 E_STRUCT_WingWall Wisdot1 DGN Style 1 E_SURF_Mask Wisdot4 DGN Style 4 E_SURF_Weak Wisdot2 DGN Style 2 E_UTL_AboveGroundPipe Wisdot4 DGN Style 4 E_UTL_Loop_UG Wisdot1 DGN Style 1 E_WAL_Noise_Sound Wisdot5 DGN Style 5 E_WTR Wisdot6 DGN Style 6 E_WTR_Dock_Pier Wisdot3 DGN Style 3 E_WTR_FlowLine Wisdot6 DGN Style 6 E_WTR_Wetland_Boundary Wisdot6 DGN Style 6 E_XS_Approx Wisdot4 DGN Style 4 E_XS_BenchLedge Wisdot2 DGN Style 2 Level 17 Wisdot3 DGN Style 3 Level 23 Wisdot3 DGN Style 3 Level 3 Wisdot3 DGN Style 3 P_AREA Wisdot2 DGN Style 2 P_CRDR_Regions Wisdot2 DGN Style 2 P_DRN_CofferDam Wisdot3 DGN Style 3 P_DRN_Underdrain_Pipe Wisdot6 DGN Style 6 P_E_PR Wisdot3 DGN Style 3 Name Linetype New Linetype Old P_E_XS_BMGRD Wisdot1 DGN Style 1 P_E_XS_DTM Wisdot2 DGN Style 2 P_E_XS_Ground Wisdot3 DGN Style 3 P_E_XS_Pipe Wisdot1 DGN Style 1 P_E_XS_RW Wisdot1 DGN Style 1 P_E_XS_UTL Wisdot1 DGN Style 1 P_E_XS_WWDTM Wisdot2 DGN Style 2 P_FTMSConduit Wisdot2 DGN Style 2 P_GRAD_FeatureLine Wisdot3 DGN Style 3 P_LTG_CID Wisdot4 DGN Style 4 P_LTG_Conduit Wisdot3 DGN Style 3 P_MISC_TYPS_Dashed Wisdot3 DGN Style 3 P_PM_1RMPerm_100_100 R100 50R100 P_PM_1RMPerm_100_40 R100 20R100 P_PM_1RMPerm_25_100 R25 50R25 P_PM_1RMPerm_25_40 R25 20R25 P_PM_1RMTemp_25_100 TR25 50TR25 P_PM_1RMTemp_25_40 TR25 20TR25 Page 104 of 107 Last updated: 6/18/2015

P_PM_1RMTemp_50_100 TR50 50TR50 P_PM_1RMTemp_50_40 TR50 20TR50 P_PM_2RMPerm_100_100 DR100 50DR100 P_PM_2RMPerm_100_40 DR100 20DR100 P_PM_2RMPerm_25_100 DR25 50DR25 P_PM_2RMPerm_25_40 DR25 20DR25 P_PM_2RMPerm_50_100 DR50 50DR50 P_PM_2RMPerm_50_40 DR50 20DR50 P_PM_2RMTemp_100_100 DTR100 50DTR100 P_PM_2RMTemp_100_40 DTR100 20DTR100 P_PM_2RMTemp_50_100 DTR50 50DTR50 P_PM_2RMTemp_50_40 DTR50 20DTR50 P_PM_CenterLine_100 PM1 50PM1 P_PM_CenterLine_40 PM1 20PM1 P_PM_DBLDelineator_100_100 DDL100 50DDL100 P_PM_DBLDelineator_100_40 DDL100 20DDL100 P_PM_DBLDelineator_25_100 DDL25 50DDL25 P_PM_DBLDelineator_25_40 DDL25 20DDL25 P_PM_DBLDelineator_50_100 DDL50 50DDL50 P_PM_DBLDelineator_50_40 DDL50 20DDL50 P_PM_DotEdge_100 PM7 50PM7 P_PM_DotEdge_40 PM7 20PM7 P_PM_DotLane_100 PM2 50PM2 P_PM_DotRaisedMarker_100 PM2R 50PM2R Name Linetype New Linetype Old P_PM_DotTape_100 PM2T 50PM2T P_PM_DotTape_40 PM2T 20PM2T P_PM_HOVDualLeft_100 PM3 50PM3 P_PM_HOVDualLeft_40 PM3 20PM3 P_PM_LaneLine_100 PM1 50PM1 P_PM_LaneLine_20 PM1 20PM1 P_PM_LaneLine_40 PM1 20PM1 P_PM_LaneLine_50 PM1 50PM1 P_PM_LaneRaisedMarker_100 PM1R 50PM1R P_PM_LaneRaisedMarker_40 PM1R 20PM1R P_PM_LaneSpTemp_100 PM4 50PM4 P_PM_LaneSpTemp_40 PM4 20PM4 P_PM_LaneSpTempRaisedM_100 PM4R 50PM4R P_PM_LaneSpTempRaisedM_40 PM4R 20PM4R P_PM_LaneTape_100 PM1T 50PM1T P_PM_LaneTape_40 PM1T 20PM1T P_PM_LaneTemp_100 PM5 50PM5 P_PM_LaneTemp_40 PM5 20PM5 Page 105 of 107 Last updated: 6/18/2015

P_PM_LaneTempRaisedM_100 PM5R 50PM5R P_PM_LaneTempRaisedM_40 PM5R 20PM5R P_PM_RALane_100 PM8 50PM8 P_PM_RALane_40 PM8 20PM8 P_PM_RALaneSp_100 PM6 50PM6 P_PM_RALaneSp_40 PM6 20PM6 P_PM_RALaneSp10_100 PM9 50PM9 P_PM_RALaneSp10_40 PM9 20PM9 P_PM_RALaneSp12_100 PM6 50PM6 P_PM_RALaneSp12_40 PM6 20PM6 P_PM_SGLDelineator_100_100 SDL100 50SDL100 P_PM_SGLDelineator_100_40 SDL100 20SDL100 P_PM_SGLDelineator_200_100 SDL200 50SDL200 P_PM_SGLDelineator_200_40 SDL200 20SDL200 P_PM_SGLDelineator_25_100 SDL25 50SDL25 P_PM_SGLDelineator_25_40 SDL25 20SDL25 P_PM_SGLDelineator_400_100 SDL400 50SDL400 P_PM_SGLDelineator_400_40 SDL400 20SDL400 P_PM_SGLDelineator_50_100 SDL50 50SDL50 P_PM_SGLDelineator_50_40 SDL50 20SDL50 P_PM_Tape_100_100 T100 50T100 P_PM_Tape_100_40 T100 20T100 P_PM_Tape_25_100 T25 50T25 P_PM_Tape_25_40 T25 20T25 Name Linetype New Linetype Old P_PM_Tape_50_100 T50 50T50 P_PM_Tape_50_40 T50 20T50 P_PM_Yield_100 PMYLD 50PMYLD P_PM_Yield_40 PMYLD 20PMYLD P_PR_IntersectingRd Wisdot7 DGN Style 7 P_PR_SpecialDitches Wisdot2 DGN Style 2 P_PR_SpecialDitchesA Wisdot6 DGN Style 6 P_PR_SpecialDitchesB Wisdot2 DGN Style 2 P_RDWY_Joint Wisdot4 DGN Style 4 P_RDWY_ShldAgg Wisdot3 DGN Style 3 P_RW_SlopeIntercepts Wisdot2 DGN Style 2 P_RW_SlopeStake Wisdot7 DGN Style 7 P_RW_Traverse Wisdot1 DGN Style 1 P_SIG_Conduit Wisdot3 DGN Style 3 P_SIG_IC Wisdot4 DGN Style 4 P_TC_Drums_100_20 B100 20B100 P_TC_Drums_100_50 B100 50B100 P_TC_Drums_25_20 B25 20B25 Page 106 of 107 Last updated: 6/18/2015

P_TC_Drums_25_50 B25 50B25 P_TC_Drums_50_20 B50 20B50 P_TC_Drums_50_50 B50 50B50 P_TC_DrumsLight_100_20 B100L 20B100L P_TC_DrumsLight_100_50 B100L 50B100L P_TC_DrumsLight_25_20 B25L 20B25L P_TC_DrumsLight_25_50 B25L 50B25L P_TC_DrumsLight_50_20 B50L 20B50L P_TC_DrumsLight_50_50 B50L 50B50L P_TC_FlexTubMark_25_20 FDL25 20FDL25 P_TC_FlexTubMark_25_50 FDL25 50FDL25 P_TC_FlexTubMark_50_20 FDL50 20FDL50 P_TC_FlexTubMark_50_50 FDL50 50FDL50 P_TC_VP_25_20 VP25 20VP25 P_TC_VP_25_50 VP25 50VP25 P_TC_VP_50_20 VP50 20VP50 P_TC_VP_50_50 VP50 50VP50 P_XS_EAR_EBS Wisdot2 DGN Style 2 Page 107 of 107 Last updated: 6/18/2015