OpenRoads roundabout profile (or workflow)

I'm working on a roundabout. I'm new to OpenRoads and would love some advice on how to work this better, so if you have a workflow-related workaround, I'm all ears. Prior to installing Microstation SS3 (8.11.09.608) with Geopak, I was using Microstation SS2 with Geopak.

I've already established alignments along the baseline which is the centerline analog--for each approach and departure lane, it is the left side (as traffic would see). I have profiles for each alignment and they have matched quite well. The circulatory roadway has been prevailing within the typical 16' width. Outside that, I'm considering it a tossup at the moment.

Now I'm trying to smoothly blend all the alignments together. Comparing the template drops, I'm seeing an approximately 2-inch discrepancy between the approach lane pavement and the circulatory roadway. This should not be. To adjust the profile in order to match it, I've created a new surface along the approach alignment using only the surface of the circulatory roadway's pavement. What I'm seeing is that the drop is 0.0016 ft = 0.0192 in, which is palatable. But again, this isn't what I see when I compare the approach lane's template drop compared with my circulatory roadway's template drop.

Any thoughts on why this might be? Or might there be a bug here?

Please don't ask me to upload my file. I know it's the default answer like "did you try turning off your computer and turning it on again?" but can you please try to give me some guidance before just falling on that? 

  • Have you used any point control in creating your corridors? I've only tried doing this in MXROAD and I had to create a series of point control strings using native workflows, then use those to create horizontal point controls leaving the levels from the strings I'd created. It's a bit rough and ready but seems to work reasonably well. I'm not familiar with Geopak so I'm not sure how this would work there.
  • I suppose it's worth noting that I have little to no experience with point controls. I know that with point controls you can specify that a given point in the template to follow a certain line--especially (or perhaps only) if that line is in a 3D space. But unless I'm missing something, this application of point controls is not all that different from specifying the component to seek that line as a linear target using aliasing, etc. The use may be slightly different and perhaps slightly more or less flexible (either of which could be considered a better under certain circumstances) than Linear Both targeting.

    Just now, I'm gathering an idea to use a Linear Both target to find the edge of the circulatory roadway's lane, and then work from there.