V8i SS2 - Interchange infield modeling

RE: V8i SS2 - Interchange infield modeling

Joseph Rusiewicz — Wed, 22 Jul 2015 11:39:57 GMT

Okay caddcop, I took several of your comments and combined together for my answer and the fix. I only updated one of the templates to exclude from triangulation and it didn't fix that area. I remembered what you had said about if it was in one place, then it would do it everywhere. So I went through the rest of the templates and made sure to make them all exclude from triangulation. Viola! Thanks for the help!

RE: V8i SS2 - Interchange infield modeling

Joseph Rusiewicz — Tue, 21 Jul 2015 13:36:02 GMT

RE: V8i SS2 - Interchange infield modeling

caddcop — Tue, 21 Jul 2015 13:24:59 GMT

No Feature Name override applied?
Component definitely defined as Do not contour?
We may need a Bentley Colleague to step in, if not.

RE: V8i SS2 - Interchange infield modeling

Joseph Rusiewicz — Tue, 21 Jul 2015 13:09:59 GMT

I tried looking into this and it doesn't seem to be the problem. The same template is used on other ramps without this issue happening. The point it is connecting to is named LOS4 and it does not have any surface feature style assigned. It does not have a surface feature style assigned in any other template in the corridor. The error happens as well when just generating the surface for the single corridor without merging to the main surface. Any other suggestions of things to look for?

RE: V8i SS2 - Interchange infield modeling

caddcop — Mon, 20 Jul 2015 13:58:00 GMT

When I saw things like that, it was due to Point names not being consistent from one template to the next. If somewhere in the corridor, a point name was used in a surface component at the top of grade, that point was then a surface breakline even in areas where it was part of a Do Not Triangulate component.

RE: V8i SS2 - Interchange infield modeling

Joseph Rusiewicz — Mon, 20 Jul 2015 13:51:31 GMT

I have it working now for the most part. Making a main corridor surface out to the hinge point and having the end condition of the ramp come up to find it may have been an easier solution, but I still got it to work. I will keep that in mind for the future.

Another issue that has been popping up is some odd behavior at just one of the ramp infields. Instead of coming off the shoulder to the ditch bottom as in the template, the surface is going to the edge of the bottom pavement layer, and then going to the ditch bottom. See attached. The red is what it should be doing and the white is what is coming out of the modeler as a combined surface. Any thoughts?

RE: V8i SS2 - Interchange infield modeling

caddcop — Fri, 17 Jul 2015 17:17:37 GMT

I was working on a 3+ mile corridor with many point controls for sidestreets and found that using corridor controls was slowing down processing as each time I when to a sidestreet, it had to reprocess the main corridor.

The solution was to create an interim surface that was the main corridor all by itself. Then, all sidestreets were ties to the DTM features instead of the corridor points.

When I had to change the main corridor, I had to recreate the interim surface before I could run the whole project as a single surface.

One important part was that the DTM name for the interim surface had to be unique - it could not be the default main corridor name, as when processing the whole project, the default main corridor name would replace the interim surface and break all of the side street ties.

RE: V8i SS2 - Interchange infield modeling

Joseph Rusiewicz — Fri, 17 Jul 2015 14:30:52 GMT

I guess I should have done some more reading of the help box first. I have target aliasing on to help in the gore areas. I see that I cannot use the point controls then on those corridors. I guess I will have to do a work around and create that surface on its own and make an alignment out of the feature line for that point from the ramp surface and then have the mainline fill look for that. Any other thoughts or suggestions are still welcome.