I have a null point GR-F-TRUNC-L that is locked to follow the typical cut ditch. Eventually, a point control will move this point.

I have a display rule called DoNotCutL which compares the locations of GR-F-TRUNC-L and the typical cut ditch flow line. When checking Horizontal Absolute distance between the two points is greater than 0, DoNotCutL should resolve to True. When the difference is equal to 0, DoNotCutL should resolve to False.

I have an end-condition component that uses--for testing purposes--a starkly different feature definition. It runs from the edge of the shoulder to the typical cut ditch flow line. The null point GR-F-TRUNC-L is (as mentioned) locked to the same spot as the typical cut ditch, so DoNotCutL should be False. Looking at the display condition, and I click the = button, it resolves to False. Good.

I have no active point controls on this corridor other than superelevation, so there is no reason for this new end-condition component to show up. When I synchronize the template drop, I see this new end-condition component which I absolutely do not expect to see. (Edit: When testing the end conditions within the template editor, when I set up the active terrain model to be within the new end-condition component, the new EC component shows up, whether DoNotCutL is True or False.)

Any thoughts on this?

Geopak SS4 .872.