Daylighting by a function in C3D

[gbravo]

Hi All! I have came across a problem. I have a road given with the alignment and profile, i have built up a base assembly for it, made the corridor, but i need to place a ditch in cut condition far from the daylight point cause of the geotechnical instructions. The distance from the daylight point where the ditch should be placed differs as the cut height changes along the alignment. My question is how can i drive a subassembly based upon the cut heigth(depht)? ( I need to calculate the cut depth across my corridor then make this as an input data for calculating the ditch center alignment far from the daylight point. Expl.: When we have 6 meters in cut condition, the ditch center alignment should be at least 6/2+3 meters far from the daylight point in that sampled section. So, as the cut depth changes across the alignment, so changes the distance of the ditch center alignment from daylight point!)

Thx all.

G.

[rustysilo]

It may be good to post how your current assembly is composed.

[gbravo]

The assembly:

 

The problem:

 

 

Where the magenta width is derived from the green cut height, Green/2+3meters, but always at least 5 meters from daylight, when hillslope >5 percent, because of downcoming water!

Of course the magenta ditch not yet part of the assembly. But should it be a part somehow?

Thx a lot..

[Prime]

You will most likely have a need to do this as a three step process.

 

First run slope analysis of the surface to find where your hill side slopes are within the range requiring the ditch to be offset on the upslope side.

 

First run your assembly without the ditch, in other words you probably can not use the stadard daylight assembly that contains the ditch to do this.

Set up your first run so that you know where the daylighting is going to fall as this is the other control

 

Now add an offset to your assembly, a link width and slope sub assembly , and then the rest of the ditch section.

This will give you the ability to attach the ditch to it's own offset alignment and profile later if you ant, or manually override the standard ditch offset from the daylight line using the view edit sections tool and entering widths as desired

[Prime]

also a couple other tricks could be played here:

 

use corridor utilities, create profile from feature line of that daylight limit

place the daylight profile in the profile view, and then

 

copy the FGPGL profile, and move it up, give it a unique style

repeat as required to create as many vertical deflection zones as required to analyze and design within those constraints

 

when done one would then have the FG PGL, and a profile for the 0-2.5 meter cut, then one for 2.5-4 meter cuts, etc this will get you your station ranges for entering the override values as mentioned above

[gbravo]

Yeah. I have already did the rest of you wrote ex. slope analisys which is a good idea. So you mean that placing an assembly offset in the base assembly to the ditched-side to the daylighting point, then just put there a link to the desired surface by a given width, and adjust these widths manualy section by section? I was thinking about this, not a big work in this project . The main goal is how can drive those assemblies at the offset by getting out some other data , make calculus and get the results in connection with the fixed width link to the desired surface to achieve the correct ditch location.

 

I was also wondering what if I list points along the road alignment from the low point of the side ditch, and the daylight point, making the difference between them after an excell export, calculating the right ditch center width and placing the points back to the drawing, orthogonaly to the road aligment, building a pline, making a grading feature of it, draping it on the desired surface, and that is. Or not?

[gbravo]

I have now listed the COGO points for my corridor, but I discovered all coordinates listed are in Easting and northing, previously i changed the UCS orthogonal to my alignment ( which is straight ) but the coords are still E&N in output. Orthogonal coords should better suit my needs now . Do you know some trick?