c3d Best Practices
c3d Best Practices
c3d Best Practices
Best Practices
237A1-050000-PM03A
April 2008
2008 Autodesk, Inc. All Rights Reserved. Except as otherwise permitted by Autodesk, Inc., this publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose. Certain materials included in this publication are reprinted with the permission of the copyright holder.
Trademarks The following are registered trademarks or trademarks of Autodesk, Inc., in the USA and other countries: 3DEC (design/logo), 3December, 3December.com, 3ds Max, ActiveShapes, Actrix, ADI, Alias, Alias (swirl design/logo), AliasStudio, Alias|Wavefront (design/logo), ATC, AUGI, AutoCAD, AutoCAD Learning Assistance, AutoCAD LT, AutoCAD Simulator, AutoCAD SQL Extension, AutoCAD SQL Interface, Autodesk, Autodesk Envision, Autodesk Insight, Autodesk Intent, Autodesk Inventor, Autodesk Map, Autodesk MapGuide, Autodesk Streamline, AutoLISP, AutoSnap, AutoSketch, AutoTrack, Backdraft, Built with ObjectARX (logo), Burn, Buzzsaw, CAiCE, Can You Imagine, Character Studio, Cinestream, Civil 3D, Cleaner, Cleaner Central, ClearScale, Colour Warper, Combustion, Communication Specification, Constructware, Content Explorer, Create>what's>Next> (design/logo), Dancing Baby (image), DesignCenter, Design Doctor, Designer's Toolkit, DesignKids, DesignProf, DesignServer, DesignStudio, Design|Studio (design/logo), Design Your World, Design Your World (design/logo), DWF, DWG, DWG (logo), DWG TrueConvert, DWG TrueView, DXF, EditDV, Education by Design, Exposure, Extending the Design Team, FBX, Filmbox, FMDesktop, Freewheel, GDX Driver, Gmax, Heads-up Design, Heidi, HOOPS, HumanIK, i-drop, iMOUT, Incinerator, IntroDV, Inventor, Inventor LT, Kaydara, Kaydara (design/logo), LocationLogic, Lustre, Maya, Mechanical Desktop, MotionBuilder, Mudbox, NavisWorks, ObjectARX, ObjectDBX, Open Reality, Opticore, Opticore Opus, PolarSnap, PortfolioWall, Powered with Autodesk Technology, Productstream, ProjectPoint, ProMaterials, Reactor, RealDWG, Real-time Roto, Recognize, Render Queue, Reveal, Revit, Showcase, ShowMotion, SketchBook, SteeringWheels, StudioTools, Topobase, Toxik, ViewCube, Visual, Visual Bridge, Visual Construction, Visual Drainage, Visual Hydro, Visual Landscape, Visual Roads, Visual Survey, Visual Syllabus, Visual Toolbox, Visual Tugboat, Visual LISP, Voice Reality, Volo, Wiretap, and WiretapCentral The following are registered trademarks or trademarks of Autodesk Canada Co. in the USA and/or Canada and other countries: Backburner, Discreet, Fire, Flame, Flint, Frost, Inferno, Multi-Master Editing, River, Smoke, Sparks, Stone, and Wire All other brand names, product names or trademarks belong to their respective holders. Disclaimer THIS PUBLICATION AND THE INFORMATION CONTAINED HEREIN IS MADE AVAILABLE BY AUTODESK, INC. "AS IS." AUTODESK, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE REGARDING THESE MATERIALS. Published By: Autodesk, Inc. 111 Mclnnis Parkway San Rafael, CA 94903, USA
Contents
Chapter 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Customer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Legal Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 2
iii
Optimizing System Values, Variables, and Commands . AutoCAD System Variables . . . . . . . . . . . . Use Appropriate Data Resolution . . . . . . . . . Accessing More Windows RAM . . . . . . . . . . Simplify Profile and Section View Styles . . . . . . . . Section View Production . . . . . . . . . . . . . Maintaining Clean Drawings . . . . . . . . . . . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. 25 . 26 . 30 . 31 . 31 . 31 . 32
Chapter 3
Project Management . . . . . . . . . . . . . . . . . . . . . . . 35
Data Storage: Vault or Not . . . . . . . . . . . . . . . . . Data Referencing . . . . . . . . . . . . . . . . . . . . . . Vault References . . . . . . . . . . . . . . . . . . . . Data Shortcuts . . . . . . . . . . . . . . . . . . . . . AutoCAD Xrefs . . . . . . . . . . . . . . . . . . . . Drawing and Object Relationships . . . . . . . . . . . . . Level 1: Individual Design Objects . . . . . . . . . . Level 2: Base, Linework, and Engineering Drawings . Level 3: Production Sheets . . . . . . . . . . . . . . Digging It: Three-Level Project Structure . . . . . . . Sample Project Structure . . . . . . . . . . . . . . . User Access Controls . . . . . . . . . . . . . . . . . . . . Project Folder Structure . . . . . . . . . . . . . . . . . . . Working Folder Location . . . . . . . . . . . . . . . Sharing and Transferring Files . . . . . . . . . . . . . . . . Autodesk Vault Best Practices . . . . . . . . . . . . . . . . Single or Multiple Sites . . . . . . . . . . . . . . . . Creating Additional Vaults . . . . . . . . . . . . . . Single Vault . . . . . . . . . . . . . . . . . . . Multiple Vaults . . . . . . . . . . . . . . . . . Project Folders . . . . . . . . . . . . . . . . . . . . . Working Folders . . . . . . . . . . . . . . . . . . . . Working Folder Configurations . . . . . . . . . Autodesk Vault Project User Interfaces . . . . . . . . Prospector Tab . . . . . . . . . . . . . . . . . . Autodesk Vault Administration Tool . . . . . . Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 . 36 . 37 . 37 . 38 . 38 . 39 . 40 . 41 . 43 . 44 . 45 . 46 . 46 . 47 . 48 . 48 . 50 . 50 . 51 . 51 . 51 . 52 . 54 . 55 . 55 . 57
Chapter 4
Surface Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Working with Large Surfaces . . . . . . . . Controlling Surface Data Resolution . Reducing the Displayed Surface Area . Working with Surface Points . . . . . . . . Filtering Point Files . . . . . . . . . . COGO Point Label Visibility . . . . . Working with LandXML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 . 59 . 60 . 61 . 61 . 62 . 63
iv | Contents
Working with DEM Files . . . . . . . . . . . . . . . . . . . . . . . . . 63 Working with Contour Data . . . . . . . . . . . . . . . . . . . . . . . 65 Minimizing Flat Areas . . . . . . . . . . . . . . . . . . . . . . . . 66
Chapter 5
Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Site Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Multiple Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 6
Corridor Design . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Alignments . . . . . . . . . . . . . Alignment Design Strategies . Superelevation . . . . . . . . . Assemblies . . . . . . . . . . . . . . Baseline Location . . . . . . . Assembly Offsets . . . . . . . Drawing Management . . . . . . . . Corridor Code Set Styles . . . . . . . Corridor Regions . . . . . . . . . . Intersection Design . . . . . . . . . Overlapping Slope Projection Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 . 72 . 73 . 73 . 73 . 74 . 75 . 76 . 76 . 76 . 77
Chapter 7
Parcels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Creating Parcels . . . . . . . . . . . . . . . . . . . . . . . How Parcels are Defined . . . . . . . . . . . . . . . Cleaning Up Drawing Errors . . . . . . . . . . . . . Creating an Enclosed Parcel . . . . . . . . . . . . . . Right of Way (ROW) Creation . . . . . . . . . . . . Parcel Topology and Sites . . . . . . . . . . . . . . . Parcel Interaction with Alignments . . . . . . . . . . Parcel Interaction with Feature Lines . . . . . . . . . Automatic Parcel Creation . . . . . . . . . . . . . . Semi-Automatic Parcel Creation . . . . . . . . . . . Editing Parcels . . . . . . . . . . . . . . . . . . . . . . . . Adding a Boundary . . . . . . . . . . . . . . . . . . Deleting Parcels . . . . . . . . . . . . . . . . . . . . Offsetting Parcels . . . . . . . . . . . . . . . . . . . Updating ROW Parcels . . . . . . . . . . . . . . . . Labeling Parcels . . . . . . . . . . . . . . . . . . . . . . . When to Add Labels . . . . . . . . . . . . . . . . . Parcel Area Selection Label . . . . . . . . . . . . . . Quickly Editing with the Style Selection Dialog Box . Editing Parcel Line Segment Labels . . . . . . . . . . Labeling Parcel External References (Xrefs) . . . . . . Parcel Spanning Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 . 79 . 79 . 80 . 81 . 81 . 82 . 83 . 83 . 84 . 86 . 87 . 87 . 88 . 88 . 89 . 89 . 89 . 90 . 91 . 93 . 96
Contents | v
Chapter 8
Grading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Feature Line Grading . . . . . . . . . . . . . . . . . . . . . . Site Interactions . . . . . . . . . . . . . . . . . . . . . Feature Lines . . . . . . . . . . . . . . . . . . . . Lot Lines . . . . . . . . . . . . . . . . . . . . . . Alignments . . . . . . . . . . . . . . . . . . . . . Point Types and Elevation Control . . . . . . . . . . . Split Point Elevation Control . . . . . . . . . . . Feature Line Break/Trim/Extend . . . . . . . . . . . . . Feature Line Move . . . . . . . . . . . . . . . . . . . . Feature Line Smoothing . . . . . . . . . . . . . . . . . Duplicate and Crossing Feature Lines . . . . . . . . . . Feature Line Labels . . . . . . . . . . . . . . . . . . . . Projection Grading . . . . . . . . . . . . . . . . . . . . . . . How Projection Grading Works . . . . . . . . . . . . . Boundary Representation . . . . . . . . . . . . . Case Study: Two Intersecting Gradings . . . . . . Case Study: Three Intersecting Gradings . . . . . Preparing the Footprint . . . . . . . . . . . . . . . . . Grading to Targets . . . . . . . . . . . . . . . . . . . . Grading Group Surfaces . . . . . . . . . . . . . . . . . Using Explode With Grading Objects . . . . . . . . . . Using Feature Lines and Projection Grading Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 . 102 . 102 . 102 . 103 . 104 . 105 . 105 . 106 . 106 . 108 . 109 . 110 . 111 . 112 . 113 . 115 . 117 . 119 . 119 . 120 . 120
Chapter 9
vi | Contents
Managing Pipe Data . . . . . . . . . . . . . . . . . . . . . . Locating Pipe Network Parts . . . . . . . . . . . . . . . Pipe Networks that Traverse Multiple Surfaces . . . . . Renaming Pipe Network Parts . . . . . . . . . . . . . . Network Labeling Strategies . . . . . . . . . . . . . . . . . . Spanning Pipes . . . . . . . . . . . . . . . . . . . . . . Labeling Pipe External References . . . . . . . . . . . . Digging It: Display Flow Capacity with Manning Equation . Manning Equation . . . . . . . . . . . . . . . . . . . . Writing the Flow Capacity Expression . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. 143 . 143 . 143 . 144 . 145 . 145 . 146 . 147 . 147 . 149
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Contents | vii
viii
Introduction
The Best Practices guide provides an overview of best practices for implementing AutoCAD Civil 3D and using it efficiently in design operations. In addition to what this guide contains, you will find best practices in the Autodesk Civil 3D Users Guide and Moving from Land Desktop to Civil 3D. Another great source of best practices is the Autodesk Civil Engineering Community website (http://civilcommunity.autodesk.com), where you can find many usage tips, sample files, and links to other information sources.
Customer Information
Several parts of this guide include a Digging It section that describes best practices developed by AutoCAD Civil 3D users. Their personal comments and related information are provided to demonstrate how AutoCAD Civil 3D is used on real engineering projects.
Legal Notice
Certain information described in this Best Practices guide was provided by third party contributors and/or customers of Autodesk. Autodesk provides this information as is, without warranty of any kind, either express or implied.
Manage templates, styles, and drawings so you can work most efficiently with AutoCAD Civil 3D software.
_AutoCAD Civil 3D (Imperial) NCS Extended.dwt _AutoCAD Civil 3D (Metric) NCS Extended.dwt
For example, see the surface styles _No Display and Border Only, and the profile view style First View. These are useful as is, and as a basis for developing minimal styles for other objects.
template. Rather than using this template (acad.dwt) to create your drawings, use customized AutoCAD Civil 3D templates.
NCS Templates
If your company is using the National CAD Standard (NCS), then use a template that is set up with NCS standards.
For metric data sets, use the AutoCAD Civil 3D (Metric) NCS Extended template. For imperial data sets, use the AutoCAD Civil 3D (Imperial) NCS Extended template.
Drawing Tips
The following sections describe good practices and will help avoid mistakes when getting started with drawings.
Prevent Scaling
If you are using a 3D drawing, insert your 3D survey drawing into this file. You must ensure that the units of measure are not accidentally scaled to another unit. For example, if your drawing uses imperial units, it may accidentally be scaled to metric. To prevent scaling, set the INSUNITS value to 0.
Drawing Tips | 5
If you want to create a label design that has just the essential data and can be drawn quickly, simplify all text and graphic elements, including the use of rotation, borders, and plan readability. Another useful tactic is to leave a style in place, but temporarily edit the style with the Label Style Composer to turn off the label visibility, as shown in figure 4.
Drawing Tips | 7
Using Styles
Every object has default styles and settings that you should become familiar with, and learn to configure for best results in your projects. However, it is not practical to try and master these for all objects as you learn to design with
AutoCAD Civil 3D. Instead, become familiar with the default styles for objects and labels in your template and over time modify them to suit your needs.
Sample Styles
The Sample_ styles.dwg, provided with AutoCAD Civil 3D, can be used to preview Standard AutoCAD Civil 3D styles and note the differences between them. This drawing will help demonstrate how styles can be managed and the various ways in which styles can be transferred to other drawings. Review Sample_ styles.dwg and see which styles you might want to change at the outset. Compare this drawing with other supplied drawings and assess the styles you would like to incorporate.
Style Comparison
We will compare some basic styles with more complicated styles within a single drawing and also compare a drawing template (.dwt) with a sample drawing. This exercise will help illustrate how some of the basic styles compare to a drawing that has undergone style additions and revisions. When starting out with AutoCAD Civil 3D, focus on the layout and use of the Toolspace Settings and Prospector tabs as they are critical components for style creation, control, and identification.
Sample Styles | 9
The following exercise demonstrates how to change the Existing Ground Contours style so that it reflects the Final Grade style. Editing the contour style will demonstrate how to experiment with styles to suit your requirements. To change the Existing Ground Contour style 1 On the Toolspace Settings tab, expand the Surface styles collection and double-click the Existing Ground Contours style. 2 On the Display tab, click the light bulb icons to turn off the Major Contour and Minor Contour components. 3 Click the light bulb icons to turn on the visibility for the Elevations and Slope Arrows components as shown in figure 7. Keep the Border contour set to Visible.
Now the drawing displays borders, elevation differences indicated by color, and slope direction arrows and appears as shown in figure 8. The contour lines are no longer visible. These changes now reflect the components that are enabled for the supplied Finish Grade surface style.
The Finish Grade style is set up to display the drawing for presentation purposes or for the latter stages of a project. Before setting up your styles you should explore the existing styles to determine what would work best for you. Remember that seemingly small style property edits can have dramatic effects in your drawings.
Style Comparison | 11
NOTE Take a conservative approach when creating styles and make additional changes only as warranted.
Style Suggestions
While learning to use AutoCAD Civil 3D styles, consider the following:
Start out with as few styles as possible until you become more comfortable with the product. Track your new styles so that you can keep them straight until you can remember the visible indications for each one. Take time to explore the wide range of style components and options. You may discover useful aspects of the tools that are not readily apparent.
Only create new styles as you need them. Remember that styles should serve your designs, and are tools to help improve your drawings and facilitate the process. They should not make your job more difficult. Once you become accustomed to their use and how they are created, copied, and edited, the application of styles will greatly enhance your drawings and make your job easier.
Copying Styles
There are various ways to duplicate or copy styles between drawings and templates. This practice saves the time it would take to re-create styles.
Copying Styles | 13
2 Click the Marker tab. Select the Use AutoCAD BLOCK Symbol For Marker option. Right-click in the Block list. Click Browse as shown in figure 10.
3 In the Block Reference Selection dialog box, select *.dwt from the Files of Type drop-down menu, and browse to your template file. 4 Select the template file. Click Open and then click OK. Any style that is not contained in the current drawing will be copied from the template.
2 Select the drawing objects on the layers that you want to delete, or use the Name option to select the layers from the Delete Layers dialog box as shown in figure 11. 3 Press the Shift or Ctrl key to select multiple layers from the list.
NOTE When deleting layers from a template (DWT) file, verify that required/active styles or settings do not reference the layers.
OR 1 On the Toolspace Settings tab, right-click any object collection. Click Edit Feature Settings. 2 Click the Ambient Settings tab, and expand the General property. Set the Save Command Changes To Settings property to Yes. OR 1 On the Toolspace Settings tab, right-click a specific command item in an objects Commands collection. Click Edit Command Settings. 2 Click the Ambient Settings tab, and expand the General property. Set the Save Command Changes To Settings property to Yes.
This render style is scale dependent, so you may have to set an appropriate zoom level before you start the adjustment. NOTE These styles are similar to the NAPKIN command options that create sketch effects, but these adjustments do not add additional entities to the drawing, they just display the styles differently.
Label Styles
This section describes best practices for working with label styles.
Figure 13: Dialog box for accessing label style editing tools
You can drag and drop styles between drawings using the Settings tab Master View. You should not copy labels themselves from drawing to drawing. If you drag a label style into the current drawing along with a label that refers to that label style and you overwrite it, you will lose the style. NOTE You can use a crossing selection to change multiple labels. Draw a crossing selection window over labels that you want to edit, and then select Label Properties. Then use the Properties palette to edit the properties of the selected labels.
Label Appearance
In your final production drawings use as few labels as possible for best performance.
Label Styles | 19
3 Create a Surface Spot Elevation label style named Cut Fill. In the Label Style Composer dialog box, on the Layout tab, change the Name property of the label component to fill. Change its color to Green. Edit the text component and change the Sign Modifier to Hide Negative Value. 4 Make a new component for the Cut value by copying the Fill text component and renaming it to Cut. Change the color to red. Edit the text component, and replace with the Negative Value expression. Change the Sign Modifier to Hide Negative Value. 5 Use the Spot Elevations On Grid command to add labels to the volume surface, using the Cut Fill style. All the spot elevations in a cut area (where the volume surface is negative) will be labeled with the red label, and all the spot elevations with a fill area (where the volume surface is positive) will be labeled with the green text. Since the negative values are hidden, and the expression is used to convert a negative into a positive (the cut), the labels automatically display the appropriate spot elevation.
7 Click on the value column for Contents and open the Text Component Editor dialog box. 8 In the Properties drop-down list, select Low Point Elevation. Click the arrow icon to add it to the label.
9 In the Text Component Editor, click at the beginning of the Low Point Elevation text properties. Press ENTER. In the Properties drop-down list, select Low Point Station. Click the arrow icon to add it to the label. The properties appear as follows: <[Low Point Station(Uft|FS|P2|RN|AP|Sn|TP|B2|EN|W0|OF)]<[Low Point Elevation(Uft|P3|RN|AP|Sn|OF)]>. Click OK to close the Text Component Editor. 10 Click the General tab and set the visibility to True. 11 Click OK to close the Label Style Composer dialog box. 12 Click a curve in a Profile View and right-click. 13 Click Edit Labels to display the Profile Labels dialog box. 14 Locate Sag Curves in Type and set Profile Sag Curve Label Style to Low Point. 15 Repeat steps 4 to 14 to create a High Point label style and assign it to a crest curve.
Parcel Xrefs
The recommendation to add labels after inserting xrefs into your current drawing applies when working with parcel xrefs. Use the source drawing as a canvas for your object data and avoid the clutter of annotation. For more
information about labeling parcel xrefs, see Labeling Parcel External References (Xrefs) (page 93) in the Parcels chapter. NOTE All xrefs transfer into the new drawing whether they are used or not. Components always reference layers, and all layers are transferred into the new drawing.
Xref drawings are read-only, so the only thing that you can change are the layer states.
You cannot change the xref object style or label style. You can change properties of layers. You can use the xref edit command to make edits to the source drawing. Subsequent changes to the source drawing dynamically change the xref data.
To change the color of an object, you can change the xrefs layer as long as you know what it is. Some users prefer to control ByLayer, while others prefer to use color explicitly to display an object no matter what layer it resides on. Use the method that works best for you.
A surface with more than a million points A subdivision with more than 200 lots A corridor longer than 15 km (9.3 miles)
If your projects use smaller data sets, you can still benefit from the advice in this document to improve your work processes and your computer system performance. Implementing some of these recommendations will also enable your team to take on larger projects if the opportunity arises.
Groom the data so it can be processed faster. For input data such as points and surfaces, groom the data at the time of input, or before you start using it in the design process. Use data references to distribute the engineering model across multiple drawings, and to separate the production drawings from the engineering model. Minimize the display and update of objects not required in current design tasks. Reduce the frequency of automated operations such as surface rebuild, drawing save, and virus scanning, or turn off these operations.
These principles are applied at several levels of an engineering project, including the drawing settings, object styles, project management, and working with objects. Because some of the best practices involve decisions to make at the beginning of a project, it is important to read this entire section and consider how to apply the recommendations to your projects.
Data Tiling
Tiling refers to segregating a model into manageable work zones. This process facilitates working with large amounts of data, and enables better data collaboration of the design team.
Large Subdivisions
The concept of tiling a model is effective in dealing with large subdivisions. The lots and corridor models can be tiled so that designers can work simultaneously on multiple tiles, or phases of the project.
If your corridor includes some regions with few changes in the surface or the assembly, consider reducing the frequency of the corridor modeling in these regions to improve processing speed.
If you have a large work group, you can create a script to run on each computer and standardize the AutoCAD settings. To do this, configure the variables on one computer, then click Save All in the System Variables dialog box. The settings are saved in an SVF file or an SCR file, each of which can be run on another computer to update settings. For more information, click Help on the System Variables dialog box.
3D Display Configuration
The display of a complex surface in 3D is memory intensive, especially if the surface includes graphic detail such as material rendering or a draped image. You can improve performance of 3D display at the expense of graphic detail, a trade-off that may be acceptable during the design process. In the final project phase, you can revise these settings to get more detailed images for presentation purposes. The main settings for 3D display are accessible when you enter the AutoCAD command 3DCONFIG. Doing this displays the Adaptive Degradation and Performance Tuning dialog box, as shown in figure 16.
The adaptive degradation settings shown in figure 16 indicate that if the display speed drops below five frames per second, the system starts to degrade the display quality of fast silhouettes, view-dependent objects, and other items selected in the Degradation Order list. Depending on the data you are displaying and the graphics card in your computer, you may get better performance by turning off adaptive degradation.
Variable Settings
The following variables are useful for optimizing system performance.
GRIPOBJLIMIT
Function: Specifies the maximum number of selected objects that can display editing grips. Default setting is 100. Recommended setting: 2
HIGHLIGHT
Function: Specifies whether objects you select in the drawing are redrawn with dashed lines for easier visibility. Default setting is 1 (on), but you can set it to 0 (off) for faster selection of large, detailed objects. The 0 setting is especially effective for working with surfaces that include many contours or other lines. Recommended setting: 0
ISAVEPERCENT
Function: Controls the amount of unused space in a drawing, measured in percent. Default setting is 50. With a setting of 0 the drawing size is minimized, but every save operation is a full save. Recommended setting: 0
SAVETIME
Function: Specifies the time interval in minutes between automatic save (Autosave) operations. Default setting is 10 minutes. Recommended setting: 30 or more
Drawing Settings
Configure the following settings in your drawing templates so that they apply consistently for all drawings created from the templates.
PROXYGRAPHIC
Function: Specifies whether to save proxy graphic images in the drawing. Proxy graphics require space in the drawing file and are required only for display in applications other than AutoCAD Civil 3D. If you do not need to share drawings with users of AutoCAD or other AutoCAD-based applications, you can save space by turning off proxy graphics. If you do need to share drawings with AutoCAD users, consider using the Export to AutoCAD option, which explodes Civil 3D objects to AutoCAD primitives. Recommended setting: 0 (off).
REGENMODE
Function: Specifies whether the REGEN (regenerate) command runs automatically (1) or manually (0). REGEN can be time consuming on a large drawing, so it is advisable to run it manually, when required. Recommended setting: 0
VIEWRES
Function: Specifies the circle zoom percent value, which determines the smoothness of displayed curves. Valid values are integers from 1 to 20000; default is 1000. Setting a lower number causes faster system performance in REGEN operations. Recommended setting: try 50, then adjust up or down to suit requirements
The project may span a wide geographic area, but the design activity is focused along a few narrow corridors. The project contains undeveloped regions, which can use surface data of a lower resolution. The project area may include large flat areas with little topographic relief. These areas too could be represented with data of lower resolution.
Turn off the minor grid lines and ticks Expand the scale of the major grid Avoid using clipped grid options Keep label text very short
Where necessary, apply more detailed styles to any of these elements for final production, but use minimal display styles in the design phase.
The main command removes nested, unused features. To run the command, click File menu Drawing Utilities Purge. A secondary command removes unused registered applications (regapps) from a drawing. To run this command, enter -purge on the command line, then enter the command option r to remove regapps.
Repair Drawings
The Recover command locates, and repairs damaged data in a drawing. The command is intended to be run when you open a drawing. Click File menu Drawing Utilities Recover, select the drawing, then click Open.
Map 3D Cleanup
A powerful utility developed for AutoCAD Map 3D is also included with AutoCAD Civil 3D. It enables you to delete duplicate objects, weed polylines, and do many other cleanup actions. You can set several parameters to control each action. To access the tools, click Map menu Tools Drawing Cleanup, or enter _mapclean on the command line to access the dialog box as shown in figure 18.
NOTE While you can run several actions together, it is recommended that you do them one at a time for better monitoring and control.
Do not specify an insertion point, as doing that would change all the coordinate positions. If the drawing contains many Civil 3D object or large objects, you may need to use alternative methods: export the data to LandXML, and then import it into a new drawing, or Export to AutoCAD, which explodes the Civil 3D objects. If the objects are exploded and you want to re-create them, you may be able to use the exploded polylines or other simple entities as a starting point, or you may need to start from scratch.
If you also want to copy sheet layouts from the drawing, use the AutoCAD DesignCenter tool to drag-and-drop them to the new drawing.
Project Management
This section describes how to organize your drawings, design objects, and work procedures to support a project team. Project management is a big picture issue that affects everyone on the team. Decisions about your project management system can have extensive, long-term consequences. The first challenge is to gain a clear understanding of the planning decisions required and the information you need to make these decisions. Visualize how a particular project management system will work when it is fully loaded with design objects, drawings, and staff members sharing files. How do you keep the system flexible and efficient while still protecting the data? A strategy that works fine with a set of 20 drawings in a month-long project can break down in a long-term project with 400 drawings. Fortunately, with AutoCAD Civil 3D you can start with a simple system and build it up or trim it down as project requirements change.
35
understand your data referencing strategy and object relationships within a typical project. To get acquainted with Vault, you can install it on a networked server or your own computer, experiment with using it, and review the documentation. You probably want to use Vault if you are interested in any of these features:
Secure document locks and version control Assignment of user roles and file access permissions down to the level of folders within projects Automated data backup and restore operations Project labeling and archiving mechanism Management of data at multiple geographic sites within a single database structure
Data Referencing
For all but the smallest projects, it is a best practice to maintain master drawings of common objects such as existing ground surfaces and alignments. These objects can be referenced into other drawings as lightweight copies of the original, requiring very little space. The practice of referencing also protects the source data from unintentional changes, because the referenced objects are read-only copies. The source data cannot be changed in the host drawing. The use of references is another way to leverage the dynamic relationships between objects. When a source object is edited, these changes automatically flow through all referenced copies in other drawings. AutoCAD Civil 3D supports three reference types:
Vault references and data shortcuts can be used for project surfaces, alignments, pipe networks, and view frame groups. Vault references can be used for these same objects, but also for profiles.
Vault References
Vault references are used only within Vault projects, and they are restricted to use within a single project. To use these references across multiple project phases or across different engineering projects, you can create folders for separate engineering projects within a single Vault project folder.
As shown in figure 1, your projects NE and NW are within a single Vault project called North. Vault references can link to anywhere within the North project folder. If you need to extend these references to other projects, create new folders for these projects inside your North project working folder. Replicate the same structure in Vault, using the Autodesk Vault administration tool. Subfolders of this type can be used to group the folders for drawings and documents, but not other project objects, such as the reference links in Prospector or the Vault database files (project.xml, PointsStatus.mdb, PointsGeometry.mdb, Survey.sdb and Survey.sdx).
Data Shortcuts
Data shortcuts are intended for project management systems that do not use Autodesk Vault. This type of reference involves links from drawings to objects in other drawings, without the use of a database. Data shortcuts can be repaired if the links to the source objects are broken.
Vault References | 37
If you are unsure about your need for Autodesk Vault, start with data shortcuts. If you later decide to introduce Vault, you can import your data shortcut projects into Vault. In the process, data shortcuts are automatically converted to Vault references.
Reference Format
When you create data shortcuts from a drawing, you can choose to share all or some of the surfaces, alignments, profiles, pipe networks, and view frame groups in that drawing. The reference to each object is stored in a separate XML file. If you use the default template for data shortcut projects, all of these XML files are stored in the _Shortcuts folder for the project, separated into subfolders by object type.
AutoCAD Xrefs
AutoCAD external references (xrefs) are useful for displaying an entire drawing within another drawing as an overlay, without overly expanding the size of the host drawing. One common use of xrefs is for displaying parcels, because Vault references and data shortcuts cannot handle parcels. You can change the labels of the xref objects. However, the engineering data of the xref objects does not interact with other objects in the host drawing. For example, an alignment in an xref does not split any parcels that it crosses in the host drawing. Xrefs are compatible with all project management systems, whether they use Vault references or data shortcuts. To create an xref, click Insert menu DWG Reference and browse to the drawing that contains the objects you want to see. The objects in the xref drawing are displayed in the host drawing.
Figure 2 shows a sample project structure. This three-level structure can be used with Vault or with data shortcut projects. The following sections describe how to set up the different levels.
Data Referencing
Use data references between your level 1 drawings to share read-only copies of objects such as the existing ground surface. These references can be either Vault references or data shortcuts, depending on your structure.
Explicit Naming
For each drawing, create a unique file name and save it to the designated project working folder. We recommend that you name each drawing with a clear reference to the object it contains (for example, Maple_Street_Centerline.dwg). As the number of project drawings increases, the wisdom of using explicit references in the file names becomes more apparent.
Base Drawings
Base drawings, such as a utility base or grading base, are created by combining data references from level 1 drawings. You can use base drawings to show the existing conditions on a site, and then xref this drawing into a site features plan or a plan set.
Linework Drawings
Creating linework drawings is sometimes an intermediate step between developing engineering plans and base drawings. Linework drawings contain the linework and AutoCAD objects (such as lines, text, and blocks) that are used to build or represent existing conditions. Although linework drawings do not include AutoCAD Civil 3D objects, you can still add linework drawings to the project so that you can manage and reference them later on in the workflow.
Engineering Plans
Engineering planssuch as corridor designs, grading plans, or site plansresult from combining design objects to create other design objects for your project. For example, in a corridor model drawing, you can keep the drawing at a manageable size by using data references to bring in the alignment and profile from their source drawing, and the existing ground surface from its source drawing.
In Toolspace, on the Prospector tab, right-click the project name Get Latest Version.
This operation pulls the most recent versions of all project drawings and design objects into your working folder. Once you have these latest versions, you are ready to create level 3 production sheets.
Addressing Interference
When drawings from level 1 and level 2 are externally referenced into level 3, you may find that there are annotation overlaps, duplication, or other interferences. You can use Layer Manager to turn off interfering text, or you can create a data reference of the design object in the level 3 drawing and control its annotation there. Using this approach, the level 3 drawings can be synchronized to reflect changes that take place in lower levels. While creating references in level 3 requires some duplicate work, it is negligible compared to the benefit of the level 3 sheets being synchronized with the original design.
Bypassing Level 2
You may be able to complete some projects without using all three levels of the workflow. In particular, you may not need the intermediate drawings in level 2. Instead, you may be able to create level 3 sheets by data referencing individual objects from drawings created in level 1. The benefit of bypassing level 2 drawings is that you can create labels directly in the level 3 drawings, avoiding the possibility of generating interference. The downside of bypassing level 2 is that you cannot combine objects from level 1 to design objects such as corridors or utility networks in separate drawings.
Data References
External References
Parcel.dwg Corridor.dwg
Sheet Set.dst
Sheet Compilation.dwg
Figure 3 uses bidirectional arrows to signify read-write access, and unidirectional arrows to signify read-only access:
Surveyors are the only ones with write access to the folder that contains land surfaces. The Surveyors have read-only access to the folder that contains drawings of alignments, parcels, and other civil design objects. Civil Engineers have read-only access to the land surfaces and production drawings, but write access to the civil design objects. CAD Technicians have read-only access to the engineering design folder, but write access to the production drawing folder.
Access controls of this type are a standard administrative function in Autodesk Vault, and can be configured using the Autodesk Vault administration tool. If you are not using Vault, you can set permissions within the Microsoft New
Technology File System (NTFS), using the Sharing and Security settings at the folder level. Consult with your system administrator to set up an effective strategy. For any such strategy, it is a best practice to create several user groups or roles and configure the folder access for these groups. Individual users can be added to a group to acquire the appropriate permissions, and moved to another group if required.
Autodesk Vault, the working folder contains replicas of original documents from the database. The default working folder location for both types of projects is C:\Civil 3D Projects. This location is fine if you use either Vault or data shortcuts for all your projects. However, if you work with both types of projects, you should keep the project types separate for ease of administration. One simple solution is to set your Autodesk Vault working folder to C:\Civil 3D Vault Projects and set your data shortcut working folder to C:\Civil 3D Shortcut Projects.
eTransmit
This standard AutoCAD function can be used to send AutoCAD Civil 3D drawings and referenced objects to a client or remote team member. eTransmit is also useful for transferring drawings from one project to another. All drawings required to support the data references are automatically included in the package. The receiving computer must have the AutoCAD Civil 3D Object Enabler installed, or a full version of AutoCAD Civil 3D. TIP eTransmit is ideal for submitting finished drawings or conducting technical reviews with markups. It can also capture edits to the main drawing, and update the central version, but edits to the referenced drawings are less reliable.
Autodesk Vault can also manage project data for users at multiple geographic locations as if they were all working in the same office. This capability is provided by a multi-site option, available with Autodesk Vault at extra cost.
As shown in figure 5, a multi-site Vault installation involves a single instance of SQL Server managing files for two or more sites. Each databasealso referred to as a vault is typically replicated at each site to facilitate file sharing, but not all files are copied. Individual files are distributed to users as needed. SQL Server keeps track of where copies of files exist and ensures that these are updated or that users are notified of changes. Database administration tasks can be managed from any location, but occur once for the entire network. If your business is distributed across several office locations, the data management and security benefits of multi-site Autodesk Vault may be very useful. For more information, see the Autodesk Data Management Server 2009 Implementation Guide.
When your existing vault is getting so large that administrative tasks are very time-consuming When you start a new set of projects that do not require data from the older projects
If necessary, at any time you can export a project from one vault and import it into another.
Single Vault
The simplest way to organize your projects with Autodesk Vault is to use a single vault to store all projects and their information. All team members have access to this one location, and you set up access control and user names only once. A single vault keeps project data centralized and easier to manage. Using a single vault for all projects makes sense for a small single office or teams that are connected via a local area network (LAN). With a single vault, you reduce both your IT and project management overhead. If your organization has multiple offices connected via a wide area network (WAN), you can still employ a single vault, but with multiple sites. For more information, see Single or Multiple Sites (page 48). A single vault can become unwieldy over time. As the amount of project data increases, so do the time and space required for backup and restore operations.
As your vault grows, you may need to archive some older projects, or create a new vault for new projects.
Multiple Vaults
Using multiple vaults right from the beginning is recommended for large organizations with several departments that use AutoCAD Civil 3D independently. Each departmentsuch as the survey, site, or highway departmentsgets its own vault. This structure makes it easier to separately manage departmental permissions and project access. Each vault can have a separate system administrator, and users can be granted access to only one vault, if necessary. If some users need access to multiple vaults, their permissions must be configured separately for each vault. Another restriction of note is that users cannot log into more than one vault at a time. Organizations with very large, multi-phased projects may want to assign a separate vault for each project for ease of project management. If you elect to partition your data into multiple vaults on a server, your project teams will see shorter project lists and have tighter control over data access. However, there are some disadvantages. Projects reside in different locations and your users have to remember multiple vault names and locations. Also, backing up and maintaining multiple vaults is more work for your IT department.
Project Folders
Create folders to organize your data and to support referencing. Within each vault, you can create any number of project folders, each using a project template, which is a standard hierarchy of folders. These Vault projects do not necessarily correspond to separate engineering projects. The key point here, as noted in Vault References (page 37), is that each drawing can be associated with only one project, and data references must remain within a project folder. Each Vault project should include all of the engineering projects that need to share data. You can always move documents between projects by clicking File menu eTransmit.
Working Folders
Understand how to use your storage location for work in progress.
Project Folders | 51
When working folders are kept on local computers, as shown in figure 6, it minimizes network traffic and accommodates team members who may work offline from the field or a home office. Users create network traffic only when they check files in or out from the vault. The disadvantage of this option is that the project files are stored on the local machine, which makes them unavailable for the backup system. In addition, using external references (xrefs) and Sheet Set Manager (SSM) to share files is a more manual process. This set-up also requires storage capacity on each local machine to accommodate the working folder.
By maintaining private working folders on the server, as shown in figure 7, you protect each users work-in-progress from changes by other users. Locating these folders on the server allows for nightly backup of the data. The drawback to having individual working folders on the server is the increase in network traffic. Additionally, if you do a nightly backup of the folders, you may have a lot more data than you really need, as you may back up multiple copies of the same files in each folder.
Working Folders | 53
Multiple users can share a single working folder, as shown in figure 8. This configuration may be more familiar, because many organizations already use a centralized data or projects folder for their drawings. Similar to individual working folders located on the server, a shared working folder can be backed up nightly, ensuring project data security. However, since it is a common location, the backups will be smaller in size than with the backups of individual working folders. The benefit of this configuration is that drawings with data references or external references are notified and updated every time they are saved, rather then only when they are checked back into the vault, as with the other two options. The disadvantage of the common working folder is that accidental changes can occur more easily when users work with files in the same set of folders. This approach is recommended only for small teams with members who are in close communication with each other and unlikely to be working in the same drawings.
administration tool. In some situations there are distinct advantages to using one of these methods over the other. You can also check Vault files in and out from some Microsoft Office applications.
Prospector Tab
Project files and records are managed most reliably when you use the Toolspace Prospector tab to create all projects. After you create a new project, it is displayed in the Projects collection in AutoCAD Civil 3D. You can also view, edit, and manage drawings and AutoCAD Civil 3D object data stored in a vault from the Prospector tab. You should use a project template to create a standard folder structure for all of your projects. The template _Sample Project is provided with AutoCAD Civil 3D and stored by default in C:\Civil 3D Project Templates. If this template does not meet your needs, simply copy it, revise the folder names and structure, then save it with a different name in the Civil 3D Project Templates folder. Then when you create a project, your custom template will be available to select. It is easy to make multiple templates for different project types.
In the tool window, you can see all project files, including system files such as project.xml. The window also lists all drawings where the selected file is used as a reference and displays DWF versions of the drawing files, so you can quickly find the version you need. You can use the Autodesk Vault tool to conduct many administrative activities. An Autodesk Vault administrator can delete unwanted files, set up working folders, and manage file access for individual users or groups, as described in User Access Controls (page 45). Using the Vault tool, you can restore a previous version of a file without restoring the entire project. If you need to start a new drawing using an existing drawing as the basis, you can use the Copy Design option in the Vault tool to do this without opening the source drawing.
Project Labeling
The Autodesk Vault tool also lets you label project milestones for easy identification. Firms often need to submit deliverables to a client at certain levels of completion, such as 30%, 50%, and 75% completion intervals. For a 30% complete submittal, you can label all drawings in a project 30%. When you create this new label, the most recently checked-in version of every file in the project and all reference files are assigned the label. If, at a later time, you need to restore the 30% completion project files, you can easily restore the project to this milestone by simply restoring the 30% label, instead of doing it drawing by drawing.
Pack and Go
Another helpful administrative task with the Vault tool is Pack and Go, in which a label and all of its referenced files are combined into a single package and sent to either a folder outside the vault or to an e-mail recipient. All files referenced by a selected label are automatically included in the package unless otherwise specified. Use Pack and Go functionality to
Archive a file structure Copy a complete set of files, retaining links to referenced files Isolate a group of files for design experimentation Send a data set to e-mail recipients, such as subcontractors or clients
Because Autodesk Vault allows you to store every file related to your project, such as Word documents, e-mails, and spreadsheets, you should also use the Vault tool to manage files that are not AutoCAD Civil 3D drawings. We do not recommend using the Vault tool on a regular basis to check in or check out drawings with AutoCAD Civil 3D data. In rare cases when these drawings do need to be managedfor instance, if files are lost when checked out of a projectan administrator can force a check-in of the files through the Autodesk Vault tool.
Microsoft Office
When Microsoft Office is installed on the same computer as AutoCAD Civil 3D and an Autodesk Vault client, the file menu for these three Microsoft applications is automatically customized for Vault access. An Open From Vault command and an Autodesk Vault submenu are both added to the Office button, as shown in Figure 10.
Using these commands, you can log in to Autodesk Vault and work securely with documents without leaving the Microsoft application window.
58
Surface Data
Surfaces are essential to most design tasks in AutoCAD Civil 3D, and because of their size, it is important to structure them for efficient processing.
Avoid Snapshots
With large surfaces, avoid creating surface snapshots; instead, retain the active links to point files, XML files, or other input data. The drawback of a snapshot is that it uses system memory, so it can double the amount of memory required for the surface. Snapshots are more useful with small surfaces. The presence of a snapshot results in faster surface rebuilds because AutoCAD Civil 3D references the snapshot rather than redoing the operations that created it.
59
Simplifying a Surface
This surface editing process reduces the number of points on a triangulated irregular network (TIN) surface, making the surface file smaller and easier to process. You can choose from two editing methods, and you can apply the process to the entire surface or limit it to a smaller region. The two editing methods are as follows:
Point removal partitions the surface into small regions, each containing roughly the same number of points. The user-specified percentage of points is deleted from each region. To minimize the possibility of changing the surface during this operation, set a smaller value for the maximum allowed elevation change. No point will be removed if its removal would result in an elevation change larger than your set value. Edge contraction replaces the two endpoints of a triangle edge with a single point, and then redraws the triangles. This method is usually more accurate than point removal, but it takes longer to complete.
With both editing methods, points are not removed if they are on a surface breakline or border. For more information, see Simplifying Surfaces in the AutoCAD Civil 3D Users Guide.
Apply a Mask
Use a mask to display a subset of a surface. The mask boundary can be of any polygonal shape, and you can edit the shape or move the mask around like a
viewing window. Surface redrawing is faster because areas outside the mask are not displayed. The entire surface remains in the drawing for reference in surface volume calculations, and operations such as surface rebuilds continue to process the entire surface.
Create a Boundary
To reduce the processed surface area, create a smaller outer boundary around the region of your design. Areas outside the boundary are not drawn or included in calculations, but they remain in the file, available for future use. If you later need to enlarge the boundary and restore deleted portions, simply rebuild the surface. This operation requires a valid reference to the surface definition data, so you should ensure that this link remains intact.
the point file on import, limiting the number of points imported, or sampling a fraction of the points. To filter a point file on import 1 In Toolspace, on the Settings tab, expand the Point Point File Formats collection. 2 Right-click the file type you want to import Properties. 3 In the Point File Format dialog box (figure 1), set the options on the lower right to limit the total number of points and set a sampling rate.
This type of filtering often makes sense when using LIDAR data, which contains points in a dense grid.
The option to create the source data (breaklines and contours) in the drawing adds 3D polylines. By turning off this option, you can make the surface file much smaller if the source data includes a lot of contours. This data is often not required for your design work with the surface.
The Export Surface To DEM dialog box, shown in figure 4, is where you can set the grid spacing in the exported DEM file. A grid spacing of 2 covers a given area with one quarter the number of points required by a grid spacing of 1. Use a higher numeric setting here to create a DEM file that is smaller in size, and less detailed.
If you add all your contour data in a single operation, use the three default settings shown in figure 6 to edit the contours and create a more accurate surface. AutoCAD Civil 3D uses these options to correct flat areas by checking the surrounding elevations, interpolating new points, and subdividing triangles. If you add contour data in two or more batches, clear the check boxes for the initial batches, so that contours are not edited based on incomplete data. When you add the final batch of contour data, select the three check boxes to correct the contours based on the full data set.
68
Sites
5
The key points about a site in AutoCAD Civil 3D are as follows:
This section explains how to use sites in AutoCAD Civil 3D to manage the dynamic interaction of design objects within a project.
Site Characteristics
Objects in each site collection interact topologically with each other. A site can contain alignments, feature lines, grading groups, and parcels. An object can occupy only one site at a time. Sites can overlap or occupy the same geographic region. You can move or copy objects from one site to another Where two lines in the same site cross, they both acquire the same elevation. The line last drawn controls the elevation. This behavior affects feature lines, alignments, and parcel lot lines.
Multiple Sites
Using multiple sites provides a way to control object interactions within a single drawing. You can move or copy objects into the same site when you want them to interact, and move or copy them into separate sites when you want to isolate them.
69
Site Transparency
The fact that sites are transparent and always visible can be helpful in some situations, such as when you have soil-type parcels overlaid on a grading plan. In other situations, you might want to visibly mark the objects to indicate their site. For example, if you have two phases of a residential project in different sites, you can use the Site Properties dialog box to set the starting parcel number to 101 in one site, and 201 in the other. You can also use different object styles in each site.
Alignment Interaction
When you create alignments, you have the option of not assigning them to a site. Therefore you can keep your alignments from interacting with other site objects during the design period. After the alignment design is finished, you can move the alignments into the parcels site and work with the interactions between both object types. If you use alignments in the design of utility networks, you may want to keep these alignments in a separate site from the parcels and the road alignments. Similarly, you may want to keep your overall grading plan in a separate site from the alignments and parcels. For more information, see Site Interactions (page 102)in the Grading chapter of this guide.
70 | Chapter 5 Sites
Corridor Design
This section describes best practices for corridor design, including suggestions for the related alignment, assembly, profile, and section objects. Corridors can be the most complex, data-rich objects in an AutoCAD Civil 3D engineering design. As you develop the design, structure the data for efficient processing by AutoCAD Civil 3D so that your work is not slowed down by events such as unnecessary rebuilding operations. The large amount of data in a corridor design must also be managed carefully so that it is most useful for those who review the design and construct it on the ground.
Alignments
When creating alignments, use a naming format that identifies the real-world reference for the alignment, such as MapleSt - Edge_of_Pavement. The default names such as Alignment - 1 can get confusing as the design progresses and the number of alignments multiplies. Either type in the name of each alignment as you create it, or modify the alignment naming template to add any standard text to the name, such as project phase. Some corridors can be designed entirely from a single centerline alignment, but most require additional alignments, such as the centerlines of intersecting roads. Create these other alignments before generating the corridor if you have the design information available. Other alignments such as gutter flow lines and curb returns, can be generated from the corridor design or added later in the process.
71
If you select the Add Curves Between Tangents check box, you get an alignment with free curves inserted where two straight segments joined. These free curves are easy to edit, as they retain tangency at all times. If your input polyline includes arcs, these become fixed curves in the alignment, which do not retain tangency in editing. Leaving these as fixed curves is fine if you do not need to edit them. An alternative is to delete these fixed curve subentities and insert a free curve between the adjacent entities. Then if you need to edit the alignment, the free curve retains tangency.
Entity Types
If you are laying out alignments using the drafting tools, it can be overwhelming to see the wide range of line, curve, and spiral tools. To make the correct choice, it helps to understand the difference between fixed, floating, and free entities:
Fixed entities are defined by specific points, with no topological relation to adjacent entities. In editing operations, fixed entities remain connected to adjacent entities, but can be moved out of tangency. This is the type of entity you get when you convert a polyline to an alignment. Floating entities are attached to an existing entity and remain tangent to it. Their endpoint, however is defined by other criteria, such as radius, length, a through point, or finding the best-fit path through a number of specified points. Free entities are always created between two existing entities, and always maintain tangency to them. Free entities are the most flexible in editing operations.
Once you determine which entity type best suits your design context, you can select the appropriate line, curve, spiral, or combination based on your available design data, such as whether you have a known through point, length, or radius.
Superelevation
If you are adding superelevation to any alignments, do so before creating the corridor. Also, the superelevation data is not dynamic, so it does not update if you grip-edit the alignment. Therefore, add the superelevation after the alignment design is stable, or be prepared to redo the superelevation if the alignment is modified.
Assemblies
Assemblies are a versatile component of corridor design, with many subassemblies and structural options to choose from. Understanding these options makes it easier to design corridors for a wide range of uses.
Baseline Location
An assembly baseline is typically located in one of two places, as shown in the following figures.
Central Baseline
The assembly in figure 2 has a baseline in the center of a ditch between two roadways. This assembly can be used for a corridor designed symmetrically along a single central baseline. However, if you are designing a corridor section
Superelevation | 73
from the gutter flow line or another outside line, it usually makes more sense to place your baseline at that location. The best practice is to set your baseline along the primary alignment that controls the corridors location.
Outside Baseline
Figure 3 shows a typical assembly for the design of a curb return in an intersection. The curb return is the curved region that joins the outside edges of two intersecting alignments. The assembly shows a single road lane with a gutter, curb, sidewalk, and standard daylight. The baseline is located where the edge of pavement meets the curb, as this is the alignment that controls the design. Another common location for a curb return baseline is the back edge of the curb.
Assembly Offsets
Use an assembly offset to associate a point on a subassembly with a secondary alignment. This is especially useful in a corridor region such as a knuckle or lane widening.
Figure 4 shows an assembly with an offset on the curb subassembly on one side of the roadway. This offset can be associated with an alignment that defines the outside road edge as it widens to accommodate a turn lane or off-ramp.
Drawing Management
Corridor Model
In a corridor model drawing, keep the drawing at a manageable size by using data references to bring in the alignment and profile from their source drawing, and the existing ground surface from its source drawing.
Section Views
Once the corridor is designed, create a separate drawing for the section views. In this drawing, use a data reference to bring in the alignment, and use an external reference (xref) to bring in the corridor drawing. The sections can extract the required corridor data from the xref.
Profile Views
If a drawing contains several profile views, these can add significant time to the file size and processing time. Several strategies are available to minimize these effects. Especially in the initial design phase of a project, keep each profile view as simple as possible, with minimal labels and data bands, and no clipped grids. As the design progresses, you can add more construction data to the display. If you have profile views in the same drawing as a corridor, you can delete the views after you finish designing the layout profiles. The profile objects remain in the drawing for reference by the corridor, but the rebuilding operations are faster, and the drawing is a little smaller without the profile views. You can re-create the profile views as required in a production drawing, separate from the corridor. For more information, see Simplify Profile and Section View Styles (page 31).
Drawing Management | 75
Corridor Regions
In the initial design stages, divide each corridor into multiple regions. Create a separate region wherever the assembly changes, such as for lane widening or intersections. As the design gets more detailed, you can turn off regions you are not working in and experience faster rebuilds. In each region, set the assembly frequency and the section swath width to avoid loading the design with unnecessary data. For example, assemblies can be widely spaced along a straight roadway across flat terrain, and spaced more closely in regions with a lot of change.
Intersection Design
The Advanced Corridor Design Tutorials distributed with AutoCAD Civil 3D demonstrate an effective process for designing intersections or junctions. The basic sequence is as follows: 1 Modify the layout profile for the side road to match the elevations of the through road and create vertical curves where required for smooth transition in elevation across the intersection. 2 Add the side road baselines and profiles to the corridor design.
3 Remove geometry from the side road regions that cross the intersection. 4 Define curb return alignments and add these baselines to the corridor. Create assemblies for use on the curb return alignments. 5 Evaluate the drainage characteristics of the intersection surface 6 Add a boundary to the intersection surface. This process was developed by Eric Chappell and engineers at Engineered Efficiency, Inc., Itasca, Illinois, U.S.A. (www.eng-eff.com).
Insert a new subassembly in the region where the daylight lines are intersecting and increase the slope in that region. The daylight lines will intersect the surface before intersecting with each other. Create an offset alignment and profile in the region of the tight interior curve and choose a subassembly that grades to the offset feature line in this region. This design forces the connection from the hinge point to the feature line on the inside of the curve.
78
Parcels
This section describes best practices for parcel creation, editing, and annotation, particularly in the context of subdivision design.
Creating Parcels
This section describes parcel creation best practices.
79
80 | Chapter 7 Parcels
One ROW parcel is created for each selected parcel adjacent to the alignment. For example, if you choose two parcels during ROW creation, one on each side of an alignment, two separate ROW parcels will be created, not one complete parcel. These can be combined using the Parcel Union tool on the Parcel Layout Tools toolbar. You do not have to choose parcels on both sides of the alignment to generate ROW parcels. However, if you only pick a parcel on one side, only the ROW parcel on that side of the alignment will be created. If you select a parcel that is adjacent to more than one alignment, the offset value set in the dialog box will be used on all adjacent alignments. The alignment must be in the site for ROW parcels to be generated.
Each site has a site parcel that represents the extents of all objects within the site. All parcels within a site are dynamically related to each other. However, parcels in one site are not related to parcels in a different site. While parcels within a site cannot overlap, sites can overlap, which in turn enables you to work with overlapping parcels. For example, property parcels overlapping soil mapping parcels.
Parcels can be moved to a different site, but the original relationship to the other parcels in the original site is lost. Objects within a site do not have to touch each other. You can see a complete list of sites and the parcels within them on the Prospector tab of Toolspace. Use the Copy to Site and Move to Site commands to easily rearrange where objects are located and to prevent unwanted interaction. Certain site properties such as the site parcel style are specific to the Parcels collection within a site. To edit these properties, right-click the Parcels collection under the named site collection.
This setting is recommended so that your alignments do not interact with parcels when they are created. If at a later time you would like them to interact with parcels, feature lines, or other alignments, you can move or copy the alignment to a site.
82 | Chapter 7 Parcels
When you have a large irregularly shaped parcel to subdivide, it may create varying parcel sizes depending on the creation method used (by angle, by direction, by line). After setting the minimum area and minimum frontage, create back lot lines, and divide an area into bands or pieces where the tool will work well. The parcel automatic mode works best with symmetrical areas and regions with uniform shapes. For areas with irregular shapes or tight inside corners, use the manual layout mode.
84 | Chapter 7 Parcels
7 Either press Enter to accept the default area, or drag your cursor along the parcel. A line is shown and a tooltip appears next to the cursor that shows the area and frontage of the current parcel line position.
NOTE If you turned on the snap increment, the cursor automatically jumps to the area increments that you set. However, if you try to move your cursor below the minimum frontage, the line no longer moves with it. This prevents you from creating parcels that do not match your criteria. To subdivide the parcel, click once to accept the current position of the lot line.
Marissa Jenkinson, a Sales Applications Engineer for CADD Microsystems, Inc., (http://www.caddmicro.com) based in Alexandria, Virginia, U.S.A., has contributed content to this parcel creation section as well as to the parcel editing best practice information.
Editing Parcels
This section describes best practices when editing or altering parcel data.
86 | Chapter 7 Parcels
cannot slide or swing edit regular lot lines, these commands only work with attached lot lines. When you grip an attached lot line, you will see it has a single triangle grip at one end and can be grip edited to slide it along the lot line it is attached to. When working with attached lot lines, edit single lines one at a time. The feature line editing commands that insert or edit elevation points work with attached lot lines. Feature line commands that edit the geometry such as Reverse, Insert PI, and so on do not work with attached lot lines. For more information, see the Grading Feature Line commands topic in the Help System.
Grip Editing
If you grip edit a parcel line and drag it past the Area Selection Label centroid, the parcel regenerates and may be assigned a new number and a different style. Keep track of where the centroid is while grip editing. It is recommended that you complete grip editing and configuration of parcel geometry as much as possible before you add labels.
Adding a Boundary
You can add a boundary around a selected number of parcels. The boundary is represented by a 2D polyline. To create a boundary around a selected number of parcels 1 Enter LineworkShrinkwrap at the command line. 2 Select the parcels that you want to use as a boundary and press Enter. This command draws a polyline around touching objects. If your selection includes parcels that are not touching, the boundary is drawn around each individual parcel.
Deleting Parcels
To delete a parcel, you must delete the individual parcel segments. You cannot delete a parcel by selecting its area selection label and pressing the Delete key. Also note that if you delete a segment line, the parcel as a whole no longer exists even though three of the perimeter lines still exist.
Adding a Boundary | 87
NOTE If a parcel segment is on a locked layer, you are not able to delete the segment. You must unlock the layer, and then you can delete the segment.
Offsetting Parcels
Parcels and parcel segments can be offset using the standard AutoCAD Offset command. To offset an entire parcel, select the area label when asked to pick objects. To offset just one segment of a parcel, select the segment entity when asked to pick objects. You can also offset your site parcel to see its extents and the objects it contains. To offset a site parcel 1 At the command line, enter offset. 2 Enter a small distance (for example, 2 feet). 3 Choose the Site Parcel Area Label as the object to offset. The outline of the site parcel is displayed.
88 | Chapter 7 Parcels
Labeling Parcels
This section describes best practices when labeling parcels.
Labeling Parcels | 89
Create a new style Copy the existing style Create a child style from the existing style Edit the current style properties with the Label Style Composer
90 | Chapter 7 Parcels
The General Line Label Style can be used with parcels as well as feature lines and alignments, and can be selected from the Lines/Curves, Grading, and Alignments menus. The Properties palette also provides access to the Label Style Composer through the Edit Current Style option. This allows for more uninterrupted style property editing because you do not have to navigate to the Toolspace Settings tab. From the styles pull-down menu in the Properties palette, select Create/Edit (as shown in figure 7) to access the Object (Parcel Line Label) Style dialog box as shown in figure 8.
92 | Chapter 7 Parcels
Insert an xref of the parcel drawing into a drawing that contains AutoCAD objects. Label the lot lines. Edit the resulting labels.
Open the files: C:\Program Files\AutoCAD Civil 3D <version>\Best Practices Guide\source.dwg and C:\Program Files\AutoCAD Civil 3D <version>\Best Practices Guide\current.dwg 1 Maximize current.dwg, and select Insert DWG Reference. In the Select Reference File dialog box, navigate to source.dwg, select it and click Open. 2 In the External Reference dialog box, set Insertion Point to 0,0,0, Scale to 1,1,1, and Rotation Angle to 0. It is recommended that you set the Path Type to Relative Path.
3 Click OK. 4 Add labels as you would for regular data. Click Lines/Curves Add Line/Curve Labels Multiple Segment. Label all of the lines and curves that comprise LOT7 and LOT16, which are xref data. The labeling commands work as they do for regular objects. 5 Select and right-click the xref parcels and observe the xref commands that are available.
94 | Chapter 7 Parcels
NOTE The xref data is highlighted with dashed lines when selected. The xref commands affect the corresponding labels in various ways. If you detach or bind the xref, the label is deleted and must be recreated. 6 Right-click a parcel that exists in the current drawing and note the context menu as shown in figure 10.
NOTE When you label xrefs, designate them as such to avoid confusion. With the Text Component Editor, add a convention to the label text for identification. This is an easy way to visually differentiate xref and native object data.
96 | Chapter 7 Parcels
When creating tags, duplicates are not created by default, even if the starting number for creation is set to a duplicate number. You can create duplicates by using the renumber tag command.
98 | Chapter 7 Parcels
100
Grading
The surface modeling tools in AutoCAD Civil 3D software include generic ones such as points and breaklines, as well as purpose-built site grading tools for grading with feature lines and projected slopes. Understanding the strengths and limitations of each tooland learning how to use them togetheris a major part of learning best practices in grading.
101
They support true geometric arcs. They interact with each other. Where two feature lines intersect at a point, editing the elevation of the point edits the elevation of both feature lines. They have much better editing support than 3D polylines.
Site Interactions
A site is a collection of objects that are topologically related. The object types that can be included in a site are feature lines, parcel lot lines, and alignments. A key point to remember is that when objects in the same site intersect, they acquire the same elevation at the crossing point, similar to crossing breaklines in a surface. If you want to create overlapping objects that do not interact this way, simply assign them to different sites. Lets look at some of the interaction of objects within a site.
Feature Lines
You can use multiple sites to manage grading feature lines in distinct groups. The Move to Site and Copy to Site commands are helpful in this process. For example, you can copy feature lines to another site, then lower their elevation to create a subsurface.
Lot Lines
Traditionally, lot lines are thought of as 2D representations of parcels. However, in AutoCAD Civil 3D, lot lines can also have elevations and can be used in building a grading model. Feature line editing commands are used to assign elevations, including at intermediate elevation points. Lot lines interact with feature lines, sharing elevations at common points. They can also be added to surfaces as breaklines. When you display the lot lines, you can choose to use the elevations of the objects or you can flatten the elevations to a specific elevation. This option is available in Site Properties.
It is not always desirable to use lot lines directly for grading work. Inserting elevation points, or intersecting feature lines with lot lines creates break points in the lot line geometry, which affects labels. A lot line crossed by a feature line is split into two segments with separate labels. On a small site, it may be acceptable to use a mix of lot lines and feature lines in your grading site, ignoring the parcels that are created.
If you created the lot lines from AutoCAD entities, use the same entities to create feature lines in the grading site. Copy the lot lines to the grading site, then explode these lot lines, turning them into AutoCAD entities. Then use grading tools to convert some or all of the lot lines into feature lines For a small site, trace the lot lines with AutoCAD entities to convert to feature lines, or use the Draw Feature Line command.
Alignments
Alignments do not have elevations assigned to them directly, but obtain elevations from a profile model. As with lot lines, alignments interact with feature lines in the same site. The most common problem is a split point created where a feature line crosses an alignment, and both objects acquire the same elevation at that point. Split points are more fully explained in the next section, Point Types. The recommended procedure when creating alignments is to not assign them to a site. This prevents interaction between alignments, feature lines, and parcels. In AutoCAD Civil 3D, the default alignment creation options provide this behavior.
In Figure 1, the Elevation Editor shows the elevations for the square feature lines, including two split points where these lines cross feature lines BC and CD. In the Elevation Editor, the point symbol in the first column includes a plus sign (+) at any point that intersects with another feature line.
These commands give you precise control over feature line editing operations.
Polyline 1 on the left is smoothed in two different ways in the arcs on the right, using feature line editing commands as shown in figure 2. Line 2 was created with the Smooth command. When selected, it retains the four grips of a polyline. This type of line always retains tangency to the adjoining lines, and it can be adjusted to form a complex set of arcs, such as when you need to create an aesthetically pleasing landscape design. If you label this line, you can obtain the precise arc parameters for layout on the ground. Line 3 was created using the Fit Curve command. In this case, the three segments have been converted to a single arc. If you grip edit this arc, it does not always retain tangency with the adjoining lines. The single arc can be easier to lay out and usually results in a simpler grading design. When creating gradings from corridor feature lines, the Corridor command CreateGradingFeatureLine is very useful. As shown in figure 4, you can configure the Feature Line Creation Options to smooth the feature line when it is exported, and to create a dynamic link between the corridor and the feature line. Smoothing the feature line replaces tessellated line segments with arcs, and creating a dynamic link ensures that the feature line is updated with any changes to the corridor.
Using an expression, you can configure the direction arrows in this label style to point in the downhill grade direction, which may be more useful. To do this, edit the Arrow component of the Grade Only style, as shown in figure 6.
To set downhill grade arrows 1 In Toolspace, on the Settings tab, expand the General Label Styles Line collection. 2 Right-click Grade Only Edit. 3 In the Label Style Composer dialog box, on the Layout tab, select the Arrow component. 4 In the Direction Arrow section, click the value for Rotation Angle and select Grade Check. 5 Click OK to apply the change.
Projection Grading
A grading projection is constructed from feature lines. As shown in figure 7, the controlling feature line to which a grading is attached is called the footprint. This feature can be edited using the feature line commands. The grading projection creates another line at the outer edge, known as a daylight
line. Depending on the grading criteria, the daylight can be at a specified elevation, distance, or where the grading meets the existing surface. The daylight line is controlled by the grading object and cannot be edited directly.
Projection lines connect the footprint to the daylight line at key design points, such as the start and end of transitions. These projection lines are created with non-editable feature lines. Grading styles have a 3D solid display component that shades the surface and appears automatically in a 3D view. This can be used to view the grading without creating a terrain model.
Figure 8 shows a case in which the footprint has a rounded corner with a radius of 50 feet. Gradings are projected out 100 feet to the surface, and the gradings along two adjacent sides intersect far from the corner. The region of intersection can be quite complicated if the two segments have different footprint elevations or slope projections, resulting in ambiguous elevations where they meet.
Boundary Representation
AutoCAD Civil 3D slope grading uses a technique known as boundary representation, or b-Rep modeling. For each segment of the footprint, a bounded cone, plane, or spline region is created to match the grading criteria for that segment. These pieces are intersected against each other, and the resulting pieces are joined together in order to create a grading with real 3D intelligence.
Figure 9 shows exactly how the cone on the outside corner of a pond intersects with the surface. Notice that you cannot draw a straight projection line from the footprint to the part of the grading that flows along the valley in the lower left. A simple ray projection algorithm would not generate this part of the solution, because it would find only the first ray intersection with the surface, at a higher elevation. By showing accurate results of the grading criteria, AutoCAD Civil 3D makes it easier for engineers to see important details and explore realistic design options. For example, in this case we can see that a retaining wall could prevent the grading from flowing along the valley, and we could revise the design to include such a wall. Finding a good solution becomes more difficult if the grading segments do not intersect each other fully. AutoCAD Civil 3D uses straightening and averaging algorithms to handle these and other problem spots in a second computing pass. While the 2D daylight is reasonably clear in most cases, finding the complete 3D edited solution can be much more complicated. Another complicating factor is the limited precision with which computers can calculate intersections. For these reasons, short segments and shallow angles can also be problematic.
Figure 11 shows a side view of the gradings, which reveals that they have only a single point of intersection. This results in a chasing grade situation between the two segments, without a mathematical intersection line between the two patches, except for the degenerate intersection at the corner point.
The slopes and grades were exaggerated for this example in order to show the problem more clearly, but a similar problem can easily happen any time the slope along the footprint exceeds the cross slope. If two gradings do not
intersect, AutoCAD Civil 3D can handle the problem by averaging the slopes and elevations in the intersection zone. This effectively transitions the cross slope in most cases, as shown in figure 12.
This situation is very common in real-world grading scenarios. In particular, it occurs when grading to the inside of a footprint where elevations of the footprint vary. Similar grading intersection problems can also occur when transitioning around inside corners.
If you look closely from the side, you can see that two of the patches do not intersect at all, and the other intersections are incomplete.
In this case, AutoCAD Civil 3D is able to resolve the conflict through a process of elevation averaging, but as the ambiguous region becomes more complex,
the resolution gets more difficult. Figure 15 shows the cleaned up 3D view of the three intersecting gradings.
Use the Elevation Editor to verify the elevations along feature lines. Look for locations where an elevation may unintentionally drop to zero, such as at a split point. Use the Weed command (WeedFeatures) to remove unnecessary points and simplify grading geometry where possible. This operation can significantly improve the results where two or more gradings intersect. Use the Fit curve command (FitCurveFeature) to replace tessellated segments with an arc. This operation creates a smoothly curved grading face, rather than many short straight segments. Tessellated segments are common with feature lines created from 3D polylines that do not have arc support, such as those created with the Land Desktop grading commands.
Figure 16 shows the dialog box for configuring the weeding operation. You can specify which weeding factors to apply, adjust the numeric values, and preview the results before committing. In the example shown in figure 16, note the report near the bottom of the dialog box that 3 of 20 vertices will
be weeded. When all four check boxes were selected, only one vertex would have been removed. Click the Help button on this dialog box to see the Help topic for weeding and learn how to use these controls for best results.
The grading in figure 17 on the left is graded to the inside of a curve that has been tessellated by line segments. The grading on the right is graded from a true arc. The edited shape of the true arc is a more realistic grading.
You can use the Smooth command to convert a tessellated feature line to a true arc, similar to the polyline fit curve.
Grading to Targets
This section presents some best practices for different target types.
Grading to a distance or to a relative elevation creates a dependent parallel line linked to the footprint. In this case, editing the footprint also updates the offset line. Using the Stepped Offset command creates an independent parallel line that can be edited separately from the footprint.
grading group, so it will not update with changes to the gradings. When surfaces are created from grading groups, boundaries are created around the gradings so that the surface represents the exact definition of the gradings. If the grading closes around on itself, this creates a hole in the surface. To fill in the hole, create grading infill. A grading infill can be created in any region that is entirely enclosed by feature lines.
TIP The exercises described in this section are also available in the form of two detailed Grading tutorials: Grading from a Complex Building Footprint and Using Feature Lines to Modify a Grading. We start with a building pad that already has the basic elevations assigned. In this case, the top portion of the pad is at an elevation of 402 feet and the bottom portion is at 400 feet.
In this case, lets assume that we want to create a 1.5-foot shoulder around the pad, and then grade into the existing ground surface at 1%. At first, it might seem like slope grading is the ideal choice for both of these tasks; however, the area around the ramp needs more control than slope grading alone can provide. Lets look at what happens when we try to apply the first criteria to this footprint, grading to a distance of 1.5 feet.
The 2D view in figure 19 looks fine, but notice in the 3D view of figure 20 how the grade twists in near the ramp:
Because the ramp is steeper than the specified 1% cross-slope, there is not a good way for slope grading to resolve this condition within the given constraints. More importantly, the inner portion of the shoulder is now substantially steeper than 2:1, so the problem will be exaggerated when we try to grade to the surface.
What we need is more detailed control of this region than slope grading allows. Because the daylight of a slope grading is controlled entirely by the criteria, it cannot be edited other than by changing the criteria of the grading. Instead, we can use the Stepped Offset command to generate a daylight line that we can edit manually to resolve the area around the ramp. First, we run the stepped offset command with the same parameters that were given to the slope grading (1.5' at 1%). This initial step yields essentially the same daylight solution as the slope graded version. However, because this is a stepped offset, we can use the full set of feature line editing tools to refine the solution. Next, we use the feature line Fillet command with a radius of 15' to create a smooth fillet between the corners of the two pads, as shown in figure 21.
Notice that the feature line fillet uses the elevations from the existing feature line, and smoothly interpolates them across the length of the fillet, as shown in figure 22.
Several other feature line editing tools could also have been used to trim out this portion of the grading and set the desired elevations for the shoulder edge. Now that we have a smoother feature line to grade from, we apply a 2:1 grade-to-surface criteria and create infill grading objects to handle the interior parts. Each infill grading must be completely bounded by feature lines. Figure 23 clearly shows the diamond markers for the two infill grading objects: one for the building pads and the ramp between them, another for the perimeter of both pads and the area between the fillets and the ramp.
Figure 24 shows the same grading in a 3D shaded view. The gray area (1) is the infill grading that represents the shoulder, the gold area (2) is the pad infill grading, and the green (3) is the slope grading to the surface.
The arc portion of our ramp (area 1 in figure 25) is not triangulated very well One of the triangles adjacent to the ramp (area 2) is steeper than we would like
To fix the arc triangulation, we need to set a finer value for tessellation spacing in the grading group. As shown in figure 26, this can be difficult to find in the Grading Group Properties dialog box, because it can be set only when Automatic Surface Creation is enabled. However, this setting is also used for the Create Detached Surface command and infill grading triangulation. The best solution at this point is to turn on Automatic Surface Creation, change the tessellation spacing from the default value of 10 feet to 1 foot, then turn off Automatic Surface Creation again. You must click Apply after turning on Automatic Surface Creation in order to apply the changed settings.
With the tessellation spacing set correctly, you need to update the infill grading. The easiest way to do this is by selecting the interior feature line (the building pad), and using MOVE with a displacement of (0.0, 0.0, 0.0). The results are shown in figure 27.
The arcs in the ramp (area 1) are now triangulated better, but the triangles on the right side (2) are not well distributed. To handle this last issue, we will add another feature line to the infill to control the elevations in the same way that a breakline is used in a surface. First, create a polyline in the area that needs to be fine-tuned.
Then use the Create Feature Lines From Objects command. In this case, we want to assign elevations from grading objects so that the new feature line
starts at reasonable elevations. There is no need to insert intermediate grade break points. The triangulation of the infill adjusts to accommodate the new feature line, as shown in figure 29. Any of the feature line editing tools can now be used to precisely control this portion of the infill grading.
By using feature lines and projection grading skills together, we have demonstrated how to work through a typical design process, creating an initial grading, and then optimizing it for the specific project terrain. As demonstrated in this process, once you understand the grading design concepts, and master the basic procedures, you can combine projections with
feature lines, and use a range of operations to resolve the design challenges of a particular project.
130
Pipe Networks
This section describes best practices for working with pipe networks parts catalogs, as well as for creating, editing and labeling pipe networks.
If you use Part Builder to modify a part, you will probably change the XML file, as it contains the detailed dimensions and calculations. Changes to the DWG and BMP files are possible, but not essential in every case. AutoCAD Civil 3D installs the default pipe network parts catalog at C:\Documents and Settings\All Users\Application Data\Autodesk\C3D <version>\enu\Pipes Catalog.
131
You can point your drawing to a different catalog by clicking Pipes menu Set Pipes Network Catalog, and then changing the settings in the dialog box shown in figure 2.
Multi-User Environment
In a multi-user work environment with multiple parts catalogs, it is easy to create unwanted changes in drawings if your parts catalogs do not have consistent contents and standard locations. Unwanted changes can occur because each drawing references the parts catalog at the location specified on the computer on which it was created. If the drawing is opened on a different computer, where it cannot find a catalog at the same location, it points to the default location, or whatever is defined on the second computer. Unwanted changes can occur to parts in the drawing if the following conditions are met:
The user of the second computer edits the pipe network with an operation that references the parts catalog. The referenced part has specifications in the current catalog that differ from those in the original catalog.
Under these conditions, the part specifications from the current catalog are applied to the part in the drawing.
Operations that reference the catalogand can introduce unwanted changesinclude adding a part to the network or moving a part. Other operations, such as editing a label, do not reference the catalog.
When changes to a parts catalog are expected, designate a single person (the catalog manager) to be responsible for making changes and maintaining the master parts catalog. When the master catalog changes, the catalog manager distributes the updated catalog to all users or offices. Users send all new or modified parts to the catalog manager for addition to the master catalog. Among the team, agree on a standard process for doing this. For example, users could send to the catalog manager an entire catalog folder, or just the affected files (DWG, XML, and BMP) for a single part. If all users store their parts catalogs locally on their computers, the catalogs should be in the same location, preferably the default C: drive path used by AutoCAD Civil 3D. If a number of users are on the same network, a single pipes catalog can be stored in a central network location. In this case, it is important for users to avoid changing the shared catalog, as they could interfere with the work of other users. Instead, the catalog manager should be responsible for making all changes and notifying the users. When a new or modified part is required, always use Part Builder to make the edits. Manual edits to an .xml file can produce unwanted results. When modifying a default part, save it with a new name so that it can be easily distinguished from the original part. When sharing a drawing with another user, prevent unwanted part changes by setting the pipe network catalog to the same location, such as a shared network drive, or the default C: drive. If two separate catalogs are involved, verify that their contents are identical. AutoCAD Civil 3D uses the US Imperial Pipe Catalog and US Imperial Structure Catalog, by default. When creating a pipe network, if you are
working with metric drawings, change the Pipe Catalog to metric. Click Pipes menu Set Pipe Network Catalog. In the Pipe Network Catalog Settings dialog box, select US Metric Pipes and US Metric Structures for the Pipe Catalog and Structure Catalog fields, respectively.
Problematic Scenarios
The following sections describe scenarios that can cause unexpected changes in pipe network drawings. Solutions are provided that can prevent or recover from the problem outlined in each scenario.
Solution: User A sends the new part to the catalog manager, who distributes it to User B and others, maintaining standard catalogs that contain identical parts.
for their parts catalogs. If this is done, drawings can be shared reliably and it is easier to maintain standard catalogs.
To assign optional properties to a part size 1 Navigate to the Part Parameter Configuration xml file (AeccPartParamCfg.xml). The default location is C:\Documents and Settings\All Users\Application Data\Autodesk\AutoCAD <version>\enu\Pipes Catalog\Aecc Shared Content 2 Open the file and click View Source to modify the file. 3 Navigate to the <AeccParamDeclaration> section. A sample optional property is the Hazen Williams Coefficient flow analysis. The entry for this is as follows: <AeccDfParameter name="ACHW" desc="Hazen Williams Coefficient" context="FlowAnalysis_HazenWilliams" index="0" datatype="Float" usage="Double_General" unit="" visible="True" internal="True"/>. 4 Copy an existing optional property and make changes as appropriate to create a new property. 5 In the <AeccParamUsage> section, the corresponding entry for the sample in step 3 is <AeccOptParam context="FlowAnalysis_HazenWilliams"/>. Copy and modify an entry as appropriate to create a new entry for your property. 6 Save and close the xml file.
Parts Lists
The following sections describe best practices for using Parts Lists.
If you edit network parts, rules are never re-run automatically, in order to avoid inadvertent or unwanted changes to pipe or structure elevations. To re-run rules, use the ApplyRules command.
Specifying Styles
Right-click a collection on the Prospector tab to batch change properties such as style, rule, or render material.
You can quickly edit the styles of many pipes or structures in the Prospector tab for that pipe network as shown in figure 3. To bulk edit pipes or structures 1 Right-click the Pipes collection on the Toolspace Prospector tab. 2 Press the shift key and select the desired pipes, then in the item view, right-click the Style column header and select Edit. 3 You are prompted to choose a different style. Make your selection and the selected pipes are updated in the drawing.
Rerouting Pipes
You cannot connect pipe network elements from different networks. Therefore, create a single network that includes all parts that might eventually need to be connected. For example, include all storm drainage structures and pipes in a single pipe network. During the course of your design, you may find that a particular section of pipe should be connected to a different structure.
Convert 3D Polylines
A good method for creating water and gas line pipe profiles is to create a 3D polyline and then convert it to a pipe network.
To convert a 3D polyline 1 Use the Survey feature to convert survey data to a 3D polyline object. 2 Use the CreateNetworkFromObject command to convert the 3D polyline into a pipe network. Based on the vertices of the 3D polyline, AutoCAD Civil 3D will place structures on the network. For more information, see
Spanning Pipes
You can add spanning labels to pipes in profile view in the same way you can add them in plan view. Just as for pipes in plan view, you can move profile span labels to any connected pipe or structure in the span. NOTE The AutoCAD LIST command is a good method to list the connected pipes in the span.
Breaking Pipes
As it is not always feasible to complete layout before creating labels, you can use spanning labels to annotate pipe spans. Spanning labels are useful in places where you have connected a lateral to a pipe. When a lateral is connected to a pipe, the original pipe is broken at the connection point. A spanning label annotates the two broken pipe segments as if they were still one continuous pipe.
Manning Equation
With the use of a mathematical expression for Mannings equation, you can label pipes in plan or profile to display their flow capacity as a basis for analyzing the overall capacity of your network. AutoCAD Civil 3D seemingly does not have the ability to design pipes based on a flow value, which is usually expressed in cubic feet per second. However, with the expression, you can design hydraulically. This is a good example of how the creative use of expressions with label styles can greatly improve your network designs. Mannings equation is considered the engineering default for calculating gravity flow in a pipe. This equation is an expression using four components of a pipe. The four components are:
Cross-sectional area of flow expressed in square feet Slope expressed in feet of fall over feet of run Hydraulic radius expressed in feet and calculated as flow cross-sectional area divided by the wetted perimeter A roughness coefficient known as Mannings n value which has no units.
Q = (1.49/n) * Area * (hydraulic radius)^(2/3) * (slope)^(1/2), where Q is flow in cubic feet per second.
By assuming that a pipes theoretical maximum capacity occurs when flowing 100% full, the hydraulic radius for a circular pipe can be reduced to a simple term:
Hydraulic radius = area / perimeter Hydraulic radius = pi*r^2 / 2*pi*r Hydraulic radius = r / 2, where r is radius in feet.
Using this simplification, Mannings equation for circular pipe flowing full can be reduced to a function of pipe radius, slope, and roughness:
In Toolspace, on the Settings tab, expand a pipe label style collection. Right-click Expressions and click New. In the New Expression dialog box, enter the name as FLOW. Enter the following expression: 1.49*pi*((({Start Crown Elevation}-{Start Invert Elevation})/2)^2)*(1/0.013)*((({Start Crown Elevation}-{Start Invert Elevation})/4)^(0.6667))*(SQRT({Pipe Slope}))
Click OK.
NOTE The term ((Start Crown Elevation Start Invert Elevation)/2) has been substituted for Pipe Radius. The use of Pipe Radius, which is a named component of the pipe, does not work correctly in this case. Similarly, do not use the {Inner Pipe Diameter} component. This expression assumes a Mannings n value of 0.013, which is the standard for concrete pipe. In fact, pipes have a named component for Mannings n value which you can set. However, adding that component to your expression yields an undesired result so you should not use it for this procedure.
Displaying the flow capacity is useful for design purposes. When it is time to produce your construction plans, assign a style more suitable for production drawings. As pipes are created and labeled, the label style DESIGN FLOW will display the pipes flow capacity (Q).
The flow capacity label is especially effective in profile view where the invert grips of each pipe can be adjusted until the desired pipe capacity is reached.
You may have to follow each iteration of invert raising or lowering with a REGEN command to regenerate the drawing, but it is still effective. You can create pipe and structure tables in AutoCAD Civil 3D. Now with the added expression for flow, it becomes easy to add the capacity of a pipe to a table. These expressions demonstrate the importance of fully exploring the capability of mathematical expressions with AutoCAD Civil 3D. Making a couple of assumptions, it is easy to see that any user with a simple understanding of Mannings equation can create an expression for flow capacity and compare that value to the expected flow calculated by the design storm. This comparison can then be used to help set the diameter and slope of a pipe. For more AutoCAD Civil 3D tips and tricks, see Jeffrey Olds technology bulletin postings at the Hagerman & Company, Inc. website: http://newsletters.hagerman.com/newsletters.
Index
3DCONFIG setting 27
A
adaptive degradation setting 27 alignments 71, 103 for corridors 71 site interaction 103 assemblies 73 for corridors 73 assembly offsets 74 AutoCAD system variables, setting 26 Autodesk Vault 4849, 5152, 55, 57 administration tool 55 and Microsoft Office 57 configuration 48 multi-site 49 multiple vaults 51 project interfaces 55 working folder options 52
C
code set styles 76 contour data, flat areas 66 corridors 71, 76 best practices 71 intersection design 76 regions 76 corrupt data, purging 33 country kits 5 cut and fill labels for surface
19
D
data 24, 30, 3637 management 24 referencing 36 resolution 30 shortcuts 37 data clip boundary 60 data shortcuts, XML files 38 default template, specify 4 DEM export 63 Digging It 1, 43, 147 drag and drop styles 13 drawing 3, 29, 31 settings 29 structure, section views 31 templates 3
B
best practices 1, 3, 8, 18, 24, 35, 48, 59, 71, 79, 101, 131, 133 Autodesk Vault 48 corridors 71 drawing templates 3 grading 101 label styles 18 large data sets 24 other sources 1 parcels 79 parts catalogs 133 pipe networks 131 points and surfaces 59 project management 35 styles 8 boundary for surface 61 boundary representation (grading) 112 breaklines, adding 61
E
editing 105, 109 feature line labels 109 feature lines 105 elevation points 104 eTransmit and project files 47 explode grading object 120 external references (xrefs) 38
Index | 153
F
feature line 101, 119 grading 101 offset 119 folder permissions 45 footprint preparation 117
surface cut and fill 19 LandXML files 63 layers 8, 15 deleting unused 15 for display management 8 lot lines 102103 and grading 102 interaction with feature lines
103
G
grading 101, 110, 112113, 117, 119 120 best practices 101 boundary representation 112 detached surface 119 example 120 feature line method 101 footprint preparation 117 infill 120 intersection of planes 113 object parts 110 offset feature lines 119 slope projection method 101 use of explode 120 grading group surfaces 119 grid surface 63 GRIPOBJLIMIT setting 28
M
Mannings equation 147 mask for surface 60
O
object styles 6 minimal 6 offset feature lines
119
P
parcel creation 79, 8384 automatic 83 from AutoCAD geometry 79 semi-automatic 84 parcels 79, 81, 86, 8889, 93, 96, 9899 best practices 79 editing 86 labeling 89 labeling xrefs 93 offsetting 88 site topology 81 spanning labels 96 table creation 99 tag renumbering 98 parts catalog management 133 performance optimization 25 pipe networks 131, 136, 138139, 143 145, 147 best practices 131 design 139 display flow capacity 147 labeling 145 locating parts 143
H
HIGHLIGHT setting 29
I
infill grading example 126 ISAVEPERCENT setting 29
L
label styles 7, 18 editing 18 minimal 7 labeling xrefs 21 labels 1920 profile high/low points
20
154 | Index
Mannings equation 147 multiple surfaces 143 parts catalog 131 parts lists 138 renaming parts 139, 144 resizing parts 138 user-defined optional properties 136 point files 61 and surfaces 61 filtering 61 points 62, 104 elevation 104 performance enhancement tips 62 profile high/low point labeling 20 profiles, for corridors 75 project management 36, 38, 4548 data referencing 36 eTransmit 47 links between drawings 38 project import and export 47 project templates 46 user permissions 45 using Autodesk Vault 48 working folder 46 project structure, three levels 38 project template 46, 55 PROXYGRAPHICS setting 29 purging redundant data 32
section view drawing structure 31 simplify surface 60 site object interactions 69, 102 sites 81 parcel interactions 81 slope projection grading 101 styles 1314, 1618 drag and drop 13 for sketches, concept drawings 17 setting default 16 surface transparency 18 transfer from template 14 surface 19, 59 cut and fill labels 19 snapshot 59 surfaces 60, 63, 6566 contour data 65 export DEM 63 LandXML import 63 masks and boundaries 60 minimizing flat areas 66 system settings for better performance 25
T
table tag renumbering template settings 29 98
Q
QNEW command 4
V
Vault references 37 VIEWRES setting 30
R
RAM increase 31 REGENMODE setting 30 right-of-way parcels 81, 88
W
WBlock, removing corrupt data working folder location 46 33
S
Sample_Styles drawing 9 SAVETIME setting 29 section swath width 76
X
XML data shortcut files xref labeling 21 xrefs 38 38
Index | 155
156