Inspired by the Advanced Daylighting post on the Being Civil blog I thought I would share a situation that come up at my company that made me put my thinking cap on. In this particular case the designer wanted to control the RIGHT lane slope with two alignments – and of course profiles. In addition, he wanted the LEFT lane to match the variable right lane slope. Last but not least, both lanes would need to have the ability to have variable widths and the cross sections for the Corridor needed to center on the centerline of the road (in this example “Align 2”).
I’ve been thinking about this post for some time. I see most user using the Basic Subassemblies when trying to their corridors do things that the Generic Subassemblies are made to do. It may be the fact that the basic subassemblies look so much easier to understand in the palette. So I will look at these Generic Subassemblies a little more and hope you can find out a new way of doing something. There are 15 Subassemblies so this will take 5 post to cover them all. My disclaimer is this. I did not use complex application with these examples. Just an alignment, profile, surface and corridor. I used the default QNEW setting which used the _AutoCAD Civil 3D (Imperial) NCS.dwt template. Make the jump and let’s get started!
Do your Subassembly names disappear whenever you use the subassembly commands “Copy to”, “Move to”, or “Mirror”?
After the jump learn how to resolve this issue.
Offset Assemblies are a function of Civil 3D that is commonly overlooked. Offset Assemblies can be used to attach Subassemblies to different alignments other then the corridor baseline alignment. This is extremely important when working on projects that have:
1) a construction baseline,
2) are adding a shoulder(s) to an existing road, and
3) much more…
In speaking with clients, friends, and discussion group members about corridors, I have discovered that generic links are often not being used to their full potential.
Read on to get more out of them.



Talk Back