Should target aliasing find my target corridor precisely?

I should add that I am using Power GEOPAK SS3 08.11.09.722.

When I later clip my corridors together, the horizontal clip location is correct, but the vertical offset remains.

I should add that I am using Power GEOPAK SS3 08.11.09.722.

When I later clip my corridors together, the horizontal clip location is correct, but the vertical offset remains.

Is it safe to assume that the component that should be truncated is targeting a terrain? Also, do you have an example of a cross section that was constructed as you expect it to? If so, my first guess is that you have a non-end-condition component coming off the curb, and this cross section occurs before the two alignments have enough separation.

Another guess is that in the end conditions for that component, you have a vertical offset from the target.

The component that should be truncated is set to target a terrain in the template, but then target aliasing is set up within the corridor to target the adjacent corridor.

In my template the fill end condition comes right off of the back of curb, and it is a single end condition, set to "search for interception", "place point at interception", and the "end condition is infinite". So I would expect the end condition search to be workable unless the curbs overlap.

There is no vertical offset in my end condition component in the template.

In other corridors, we have noticed that the end condition does not solve precisely if the station in question is targeting a corridor slope that is undergoing a transition (via a parametric constraint).
In my case, there are no parametric constraint, and I even removed the horizontal feature constraints.

I thought that if Corridor A is targeting Corridor B, then the Corridor A cross sections should resolve precisely, while the Corridor B cross sections might not due to interpolation effect of where exactly the model gets evaluated when the stationing does not line up between the corridors.

This scenario reminds me of www.youtube.com/watch. Have you watched that? Instead of using a new terrain model target alias, the demonstrator uses <Active Surface>. I'm not sure whether that's what you've already done. And I'm not sure that after having done this it will work as intended anyway.

HTH