1. © 2011 Autodesk CI6401-P - Corridor Deconstruction Peter Funk Autodesk, Inc.

2. © 2011 Autodesk Class Summary  The corridor model in AutoCAD® Civil 3D® has many interconnected parts that work together to produce roadway models. In this class, we will dig into the different parts of the model to see how they all fit and work together. We will discuss alignment, profiles, offsets, targets, surfaces, assemblies, subassemblies, regions, the ATC file, the subassembly code, code sets, labels, cross sections, corridor surfaces, and feature lines. Attendees should have a good working knowledge of the corridor model in Civil 3D. We're going down to bedrock in this class.

3. © 2011 Autodesk Learning Objectives  Learning Objectives  At the end of this class, you will be able to:  List the different parts of the corridor model  Explain how the program processes the model using the geometry in Civil 3D and the subassembly code  Create a great corridor model and design cross sections  Describe new trends in cross-sectional design that go beyond traditional subassembly programming

4. © 2011 Autodesk Corridor Modeling Basics  Point, Links and Shapes

5. © 2011 Autodesk Set the Plane

6. © 2011 Autodesk Establish the Points

7. © 2011 Autodesk Play “Dot to Dot” for the Links

8. © 2011 Autodesk Color the Links to make the Shape

9. © 2011 Autodesk Rinse and Repeat  The process is repeated for each subassembly at the station  Moving from  Center to Right  Center to Left  After all the subassemblies are processed for the station, the process repeats for the next station

10. © 2011 Autodesk Finish the corridor  Adding  Feature Lines  Corridor Surfaces

11. © 2011 Autodesk Corridor Rules  Process from the start of the alignment to the end  Can’t go backwards  Each section is processed in isolation from the one before and the one that follows  Each Subassembly is processed in isolation from the one before (but values can be passed)  Process order  Center to right  Center to left  Marked points need to be established before they are used

12. © 2011 Autodesk Point, Line and Shape Codes  The codes used by the subasemblies are hard coded (in most cases)  To modify  Modify the shipping source code, recompile  Recreate the subassemblies using Subassembly Composer  Modify the “Codes” file

13. © 2011 Autodesk Codes File  Used to “translate” codes used by the subassemblies  Only one file on the system with a fixed name  Multiple files can be used, but a rename is needed  Most Country Kits have a codes file built into them

14. © 2011 Autodesk C3DStockSubassemblyScripts.codes  //Attention; do not use commas in description  //  //Index No.,Localized code,Original Code,Description  //  1,Crown,Crown,Crown point between travel lanes on finish grade  2,Crown_Pave1,Crown_Pave1,Crown point on the Pave1 layer  3,Crown_Pave2,Crown_Pave2,Crown point on the Pave2 layer  4,Crown_Base,Crown_Base,Crown point between travel lanes on the base layer  5,Crown_Sub,Crown_Sub,Crown point between travel lanes on the subBase layer  6,ETW,ETW,Edge of traveled way; inside or outside edges of travel lanes on finish grade  6,EOP,ETW,Edgo of pavement; inside or outside edges of travel lanes on finish grade

15. © 2011 Autodesk Code Set  Used with the Codes file to stylize Point, Links and Shapes  Controls the Labels of Point, Links and Shapes  Multiple code sets can be used  Corridor Model  Cross Sections

16. © 2011 Autodesk Conditional Subassemblies  Surface  Can branch based on Cut or Fill  Can also branch based on depth of  Offset  Can branch based on if the offset if found  Can branch based on distance to offset  Layout Graphics leave much to be desired

17. © 2011 Autodesk Issues  Bow Ties  Water Falls  Shooting Daylights  Missed Daylights

18. © 2011 Autodesk Bow ties  Bow ties happen because the corridor is processing in a cross section mode  Happen on the inside corners of intersections if the cut/fill is too great  Can be solved by using grading instead of cross section design

19. © 2011 Autodesk Waterfalls  Waterfalls happen with the profile is too short for the alignment

20. © 2011 Autodesk Daylights  Shooting Daylights  Typically happen when the profile is too far above or below the surface  Can also happen when the daylight chases up or down an slope that has a similar slope to the daylight line  Can be solved by  Adjusting the slope  Modify the profile/alignment  Missed Daylight  Typically happen at the edge of a surface where the daylight can’t intersect the surface within the limits of the site  Can be solved  Change the slope  Get a bigger site  Modify the profile/alignment

21. © 2011 Autodesk New Trends  Subassembly Composer  Corridor Solids

22. © 2011 Autodesk Subassembly Composer  Download the Subassembly Composer from the Subscription Center

23. © 2011 Autodesk Corridor Solids  Down load the Corridor Solids project from Autodesk Labs

24. © 2011 Autodesk Wrap Up  Can You?  List the different parts of the corridor model  Explain how the program processes the model using the geometry in Civil 3D and the subassembly code  Create a great corridor model and design cross sections  Describe new trends in cross-sectional design that go beyond traditional subassembly programming

25. © 2011 Autodesk Questions  peter.funk@autodesk.com

26. © 2011 Autodesk Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2011 Autodesk, Inc. All rights reserved.