It sounds like you might be better off using a custom SA. You can set one up that will accept a min and max WIDTH then if you can hit the surface within that range using a specified slope, then do so --otherwise use the alternate slope.
You can still use the ConditionalCutFill subassembly to test whether you are in cut or fill at the 25' offset mark, then proceed accordingly:
Use generic link subassemblies to shift the conditional test location 25 feet. Test to see ff the depth is greater than 1.25 (25' x 5%). Then on the end of each condition, use generic links to return back 25'.
One scenario that simply testing for cut or fill at 25' @ 5% like I suggested with a ConditionalCutFill SA would fail at, would be if you had a hump in between that you did not want to grade out through, and you were in fill at the 25' offset test point.
Reading the original post I want to be sure that I understand the intent. Starting from the shoulder the section extends outward at -5% until it daylights or reaches 25' from EOP. If it reaches the 25' without daylighting, then it continues at -3% until it daylights, or falls of the edge of the surface.
This is DaylightGeneral. With the Fill1 link is set to -20:1 for 25' and the Flat fill slope set to -33.333/1 it should perform as shown below.
Please use the Accept as Solution or Kudo buttons when appropriate
I can confirm.
I didn't realize DaylightGeneral had this initial Fill Width funtionality for this problem (Kudos given). This will solve that hump scenario where the cut/fill test at 25' would fail.
I did not try this last scenario and will need to give it a try. I ended up creating a new baseline along the EOP and running out the -5% to determine where it went past the 25' offset. In the areas that went past it I just created a different assembly that went to the 25', then matched from there at the -3%. For the most part, the areas that went past were confined to 2 long areas and so it was pretty easy to designate the regions. This also allows me to basically let the pavement on the runway to be independent so-to-speak from the infield area as they usually need some additional contour tweeking. Thanks for all of the help guys......
Boon's suggestion automates all of this and is easy to set up.
I never use DaylightGeneral because it doesn't have capability to target horizontal and elevation targets which we always need to tie ditches into culverts and bridges.
However it works perfectly for your Fill problem, and I will consider using it for more Fill scenarios now.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.