OpenRoads Designer - Corridor Contours Do not Tie into Existing Contours

Hello. 

I am having issues getting the proposed contours from a corridor to tie into the existing contours. Please see the screenshots and scenario below. 

At STA 736+10, the End condition seeks and ties to the existing surface as desired. *Note How the proposed contours tie into the existing contours prior to STA 736+10 (left of the vertical cyan line)

At STA 736+12.5, the end condition does not tie to existing surface. This results in the proposed contours to the left of the cyan line not tying into the existing surface. This is the case from STA 736+10.01 to STA 736+14.99.

At STA 736+15.00, the end condition ties back into existing surface. 

Ultimately, I need the proposed contours on BOTH sides of the red notch to tie into the existing surface. There appears to be a 5ft section (between STA 710+00 and 715+00) where the end condition does not solve to existing surface. My template interval is 5ft. I have tried changing to the template interval with no luck. I have also tried adding Key Stations with no luck. 

If anybody has any thoughts that could lead to a solution, I would be VERY grateful. 

Parents
  • Hello Aaron,
    If the end condition is not solving, as appears to be the case, then the problem is not the corridor model settings, such as template drop interval, but rather with the template itself.  Use the Testing function of the template editor to identify the situations where the end conditions fail.  That will be your starting place to fix the problem.  Also, check that you don't have other constraints that would result in your end condition seeking a target other than the existing terrain.

    Karl Dauber, PE
    Advance Consulting
    Laurens County, SC
    karldauber@advconsult.net
    www.advconsult.net
    www.linkedin.com/in/karldauber

  • Hey Karl! 

    Thanks for the response. I have tested the end condition using the testing function, and it works fine for all the scenarios I could throw at it. I have also made sure that the only target it seeks is the existing terrain. 

    Please note that this end condition is only failing to solve in that one 5ft area between where the end condition solves at the top of existing fill slope (Section 736+10, see screenshot) and where it solves at the bottom of the existing fill (STA 736+15, see screenshot)

    It's like the end condition is caught in a transition between those two stations and does not solve. 

Reply
  • Hey Karl! 

    Thanks for the response. I have tested the end condition using the testing function, and it works fine for all the scenarios I could throw at it. I have also made sure that the only target it seeks is the existing terrain. 

    Please note that this end condition is only failing to solve in that one 5ft area between where the end condition solves at the top of existing fill slope (Section 736+10, see screenshot) and where it solves at the bottom of the existing fill (STA 736+15, see screenshot)

    It's like the end condition is caught in a transition between those two stations and does not solve. 

Children
No Data