I am attempting to profile the gutter line for an intersection return. One one end of the return I want the profile to match the existing gutter line, and on the other end of the return I want the profile to match the proposed gutter line from my corridor model. To snap to the existing gutter line I created a surface profile along the return. To snap to the proposed gutter line I used the Profile Intersection Point command. I want my profile to connect the existing ground surface on one end of the profile to the point on the other.
The problem is that the point generated from the Profile Intersection Point command is apparently grabbing the elevation from the wrong location along my corridor. I have a template drop on each side of the intersection, and the command appears to be grabbing the elevation from the end point of the gutter line at the wrong template drop.
The issue appears related to the tiniest of gaps between the arc and my corridor:
And if I extend my template drop well past the arc, the elevation self-corrects:
But if I snap the template drop back to the endpoint of the arc, the issue returns:
Does anyone know a good fix for this?
Thanks in advance!
It's strange it would pull any elevation at all with that template not crossing. Is there a chance another corridor object (slope parametric,etc) stops at that same location? It's hard to say without understanding your design intent for that intersection. I've seen the software not marry up despite exact stations. There may be known reasons for this... e.g. location of curve tangent at the EOP (are those EOP intervals from a constant EOP line?) It will not hurt to overlap by a small amount (.005 or less) in the case you're planning to grade that intersection using the create terrain from elements. I'm curious if your design needs to maintain a constant cross slope through those lanes. If so, carrying the template through the intersection may work best and solve these issues.
Bentley Accredited Road Designer | Bentley Accredited Road Modeler
colliersengineering.com
I ended up just adding a little overlap to make it work. You are correct, I am creating a terrain from elements. My plan is to smoothly transition the cross-slope in both directions, so the cross-slope will vary through the intersection which is namely why I wanted to leave a void in the area.
Glad that helped! It's so easy to get lost in the methods and minutia details of the software. Sometimes a real world perspective does the trick...( e.g. relationship between digital space elements and machinery used to construct said elements). In many cases like this, will they (contractors) really going to stop/start at exactly ##+00.000? Kudos to those who do! Haha! Obviously, more structural applications require finer detail and cross discipline coordination, however picking your battles in each case will be the key to efficient use of this software.