SAC Typical Road Structure

[Anonymous]

Good morning, all...

I would like to make a typical Road Structure for Divided planer with medium in SAC.  I got some pkt files (Attached) and I try to modified based on my road structure, unfortunately I cannot complete my road structure.  if anyone is helping, it will be highly appreciated.

The original Structure CAD file attached. In this Structures criteria mentioned Below : 

Slope -2.5 (Both Side)

The super elevation is  Left is  e 3.5      Right side  e -3.5

Road Width 3.65*4 = 14.6 for 4 tracks

Road Type - Divided planer with medium

Is it possible to make typical structure SAC for the divided planer with medium  -   The required /modified Contents in SAC are below mentioned:

Road Structure Width

Slop  

Daylight Slope

Road Structure Depth  (Eg.Base, Subbase, etc)

Super Elevation. 

Each Structure  Point Code   Eg, Inside Code,.EPS    (after creating the corridor, in future for extracting points from the corridor)  

[KMercier_C3D]

I would suggest starting with your ShoulderRounding28-08-19.pkt and making the following changes. 

• After L1 is defined, I would change all references to Shoulder_Slope to instead be L1.slope so that all of your layers remain parallel with one another when an elevation target is used. 
• Change all of your points P3, P5, P8, and P9 to be auxiliary points defining the depths and then use them to slope the opposite direction to mimic your desired structure shape.
• Regarding the tracks/lanes would you want each of those defined as a different shape or would just a point with a point code placed on top of L1 at the different distances meet your needs?

[Anonymous]

Hi Madam

As per u r instruction I made the line I changed all references to Shoulder_Slope, 

If I select P2&L1 , I changed the elevation Target as None,  the EPS point individually changed the direction,  the other area not changing.

Later I try to make left side daylight using Auxiliary Points, unfortunately it is not coming properly,  I would like to make  left daylight slope, same as right 1:1  and depth based on each Sub Structures Eg. Wearing, Base, Sub base etc.

Required the tracks/lanes is different shape,

Required L1 is different distance

Top Inside & outside points need Individual point codes of each horizontal Lines or road structure.

[KMercier_C3D]

1. Are all 4 lanes always equal width?
2. Will it ever be more or less than 4 lanes? 
3. Can you explain "Required L1 is different distance" do you mean that the outer edge of road needs a horizontal target to vary? If it does vary do the lanes equally vary with it or only the outside lane?
4. Do you need to define a shape for the fill below the subbase above the existing surface?
5. Are you defining the 3500 center median as a stock C3D subassembly (LinkWidthAndSlope) or would you want that as part of this subassembly?
6. If the road is in cut instead of fill is it still 2:1 side slopes to daylight? 

[KMercier_C3D · Accepted solution]

Could you use the attached PKT file that I previously created and posted here on the forums in a different post? 

you would use one of the subassembly for each lane.

On the inside lane you would change the input parameter SideOfDaylight to Inside. On the middle lanes you would change the input parameter SideOfDaylight to None. On the outside lane you would change the input parameter SideofDaylight to Outside. You can set any extra layers to =0 depth

To define the slope of the full roadwidth you would use a stock Civil 3D subassembly for LinkWidthAndSlope and target the outside elevation and width as required and set the OmitLink to Yes. This subassembly will not show and just be for information. This subassembly would need to be defined prior to your first lane but can share the same point as your inside lane. Then on your Civil 3D Assembly Properties Construction tab you will go to each lane check the checkbox for UseParameterReference and then use the dropdown to select the LinkWidthAndSlope.slope to use the calculated slope for each of the lanes. 

You would then just use a generic LinkSlopeToSurface for your daylight. 

[Anonymous · Accepted solution]

Hi Madam, Thank you for your reply and spending time me your valuable time.

This structure for two roads, Different place, there is no connection with both road, but the assembly almost same. only change the track width

1. The first road 4 lanes are equal width 3.65M, Total 4 lines
2. The second road 3 lanes 3.65M and last line 3.2M Total 4 Lines
3. Required L1 is always based on the track width
3A. If our track length is different (instead of 3.65) is it possible make automatically vary of length of L1 Distance only using L1 is offset target (Outer edge). But other all Horizontal line always based on the daylight slope,
4.Do you need to define a shape for the fill below the sub-base above the existing surface? Yes
5.Medium is not part of the sub Assembly, (Median from (both sides 3.5M, 12% Slope) stock C3D sub assembly its taking from (LinkWidthAndSlope) this SAC for the (divided planer with medium)
6.If the road is in cut instead of fill the daylight slope not fixed 2:1, it will be vary.

The attached pkt file is very good and useful, but I don't know how to fix the daylights, from outer edge of L1. (Right) Origin from Left.

Now just I am learning to study making sub assembly,  then I will try other Eg. Super elevation etc.
Madam, My English is very poor, if any word or sentence is not correct, pls forgive me.

First of

[KMercier_C3D · Accepted solution]

The attached PKT file (a combination and modification of the ExtendAll6Layers pkt that I previously shared) should get you close to what you want. It is set up to handle targeted lane offsets for up to four lanes, an outside target elevation (that maintains the calculated constant slope for all of the lanes), and superelevation (applied consistently for all of the lanes). If you wanted the lanes to behave more independently for elevation/slope then there would need to be some changes. For any dimensions that you don't want just enter a 0. You also do not need to use the target offsets if the lane is constant (for example if you just wanted to vary the width on lane 4 then you can just use that one target and all of the others will maintain their appropriate input parameter width)

The daylight to existing surface in the cut scenario may also need some modifications depending on how that would be handled. 

Feel free to use and make your own changes or if you need assistance with changes I can talk you through it. 

And no need to apologize about your English. You write it better than I can write any other language and I am pretty sure that I understood most of what you wrote. 

[Anonymous · Accepted solution]

Hi Maadam

Thank you for response and solving the issue,  Almost done the work,  If I need any assistance with this assembly, I will send you madam. 

Regards

Jijinajabbar

[Anonymous]

Hi, Maadam

I imported pkt file in customized tool palates, as sub assembly and create the assembly.  but exact shape color is coming only first 3 layer, the other two shape color coming as fully white.  After I try to mirror the assembly, the mirrored assembly total shapes coming irregular.  Also I made the corridor and   create the sample line creation.  in the section view full assembly structure is white. (Attached). please solve  the issue. Your early response will be highly appreciated.

Regards

Jijinajabbar

[Anonymous]

Hi,

I imported pkt file in customized tool palates, as sub assembly and create the assembly.  but exact shape color is come only first 3 layer, the other two shape color come as fully white.  After I try to mirror the assembly, the mirrored assembly total shapes coming irregular.  Also I made the corridor and   create the sample line creation.  in the section view full assembly structure is white. (Attached). please solve  the issue. Your early response will be highly appreciated.

Regards

Jijinajabbar

[KMercier_C3D]

The two bottom shapes coming in as white are due to your Code Set Style and the Layer5ShapeCode input parameter and Layer6ShapeCode. 

The twisted shapes on the left are a SAC quirk that I can not fix easily without a lot of time to troubleshoot it and I just don't have that time right now. Sorry.