<\/p>\n
This subassembly was written in a few minutes pretty much as a learning tool for myself to get into the SC. It does, however, provide amazing depth and flexibility when you start to consider not only the predefined tools in the toolbox but the ability to use API functionality within the SC and also from the .NET math class.<\/p>\n
The key to transitioning a value across the range of a region comes through the expression<\/p>\n
((Baseline.Station – Baseline.RegionStart) \/(baseline.RegionEnd – Baseline.RegionStart)) * slopei<\/strong><\/p>\n Where \u2018slopei\u2019 is the delta slope value calculated from \u2018Value at End\u2019 \u2013 \u2018Value at Start\u2019<\/p>\n In order to apply the batter subassembly, and not end up with a roadway corridor full of excessive non-necessary regions, I took an approach of firstly building a roadway corridor out to the edge of hinge.<\/p>\n From this point I extract the hinge string using the \u2018Create Feature Lines From Corridor\u2019 command from the Home tab on the ribbon, making sure the hinge line extracted maintains a dynamic link to the corridor (and making sure the Smoothing option is turned off as this creates extra vertices around any alignment curves)<\/p>\n Now that the feature string is linked to the mainline corridor, we can go about setting up an additional corridor to handle just the earthworks. To do this we setup a new assembly with a generic \u2018LinkWidthAndSlope\u2019 subassembly and set the parameters like below<\/p>\n Link Codes \u2013 none<\/p>\n <\/p>\n <\/p>\n <\/p>\n We then attach the \u2018BatterTransition\u2019 subassembly to the previous link. We can then change the values to suit our requirements (I\u2019ve used 2:1 to 5:1)<\/p>\n <\/p>\n <\/p>\n <\/p>\n Looking at the whole assembly now, we see our hidden link (which I have relabelled to \u2018SubString\u2019) and the batter slope.<\/p>\n We can now create our earthworks corridor and assign some targets as follows (I\u2019ve called the corridor \u2018<Corridor> \u2013 Batters\u2019 just to keep the roadway and batter corridors close in the prospector).<\/p>\n We just need to ensure that the Width and Elevation targets are set to the hinge string that we created dynamic to the corridor. In the image below, I have set the first range between Stn 700-750. This forces the batter to transition from 2:1 to 5:1 between these stations<\/p>\n As you can see, a smoothly transitioned slope!<\/p>\n To finish off the batter slopes, we simply need to copy the batter transition assembly to create our various types, including constant slopes. In this example I have simply setup a 2:1 constant, a 5:1 constant and a 2:1-5:1 transition.<\/p>\n We now use Civil 3D\u2019s corridor context-sensitive menu to \u2018Add Regions\u2019, Copy Regions\u2019, \u2018Match Parameters\u2019 and \u2018Region Properties\u2019 to add in the rest of the earthworks adjacent to the roadway.<\/p>\n Personally, I have found that copying the initial region using the \u2018Copy Region\u2019 command and the changing the region\u2019s assembly using the \u2018Region Properties\u2019 to be a much faster way of applying multiple batter slope regions throughout a corridor. This is only due to the new Civil 3D 2015 feature of automatically reassigning similar targets (i.e. I don\u2019t have to go through and assign the hinge feature line targets repeatedly)<\/p>\n Copy Region (2:1 to 5:1 batter slope)<\/em> <\/p>\n<\/a><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/a>Point Code \u2013 none<\/p>\n
\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n
<\/a><\/p>\n