Corridor Surface problem - feature lines connecting across intersection

Anonymous

Corridor Surface problem - feature lines connecting across intersection

Anonymous
Not applicable

I've always used the top links to create surfaces from corridors.  Recently I found out the benefits of adding feature lines to the surface as well, to improve the contours at curb returns and lane tapers.  Now I always add the following:

 

1 link and 5 FL definitions in corridor surface1 link and 5 FL definitions in corridor surface

I've attached a screenshot of how some curb returns look before I did this - the surface doesn't always follow the face of curb as it goes around an arc.  Overhang correction was set to top links and I was still getting problems.  Adding the FL to the corridor surface definition helped.

 

This worked great for me on my last project.  I'm using it on a new residential project with many intersections.  Most of the intersections do fine, but there are two where the surface is trying to model the curb returns AND also connecting the curb "across" the travelway.  A screenshot of the problem is attached.  The bottom intersection is displaying the problem?

 

Any ideas?

 

 

0 Likes
Reply
Accepted solutions (1)
1,408 Views
2 Replies
Replies (2)

Mike.M.Carlson
Advisor
Advisor

Hello,  

 

Try switching the over hang correction to “Bottom Links” and rebuild.

 

If not, try to edit the corridor surface in those problem areas by “flipping faces” .

 

I hope one of these helps.  




Michael M. Carlson
Senior Civil Designer
CADD Manager
AutoCAD Civil 3D Professional
AutoCAD Professional

0 Likes

Anonymous
Not applicable
Accepted solution

I tried using the bottom links for overhang, but that didn't work.

 

I isolated the problem to one region in my corridor, that went along the primary alignment.  I noticed the stationing of it was overlapping with the stationing of the intersection regions.  I figured just pulling back the stationing to remove the overlap would fix the problem.  But it didn't.  I tried several other changes, and it still wouldn't change.

 

Finally I created a new baseline, and a new region within that baseline.  That is what worked.  

 

Weird bug, but also simple bug to fix in the end.

 

 

0 Likes