Horizontal Feature Constraint stops part way along the feature

The 50' range is relative to the location of the point during processing... with that said, you do not have a horizontal constraint (#2) to make it as relative as the controlling of the template.  Once you pick a point to guide that, it should solve as long as 50' right of the control is correct.  

Hi Shawn, thanks for responding!I believe I found the error, I shared it with someone else and the text of that response is posted below. I'm curious about your answer though, what do you mean by "to make it as relative as the controlling of the template?"

Update: sillish mistake?

Make when you're using null points with horizontal feature constraints that what the rest of your template is doing is matching your line work and/or plan graphics file. I copied my back of curb line work into my plan graphics file to use as a reference for the horizontal feature constraint in my template, what I forgot to take into consideration was that my shoulder was transitioning here as well. So my horizontal feature constraint wasn't finding my curb because my curb line work was "too close" to the edge of shoulder in my model (which did not match the edge of shoulder the curb line work was based off of).

Easy fix (which should've been done initially), bring my shoulder transition line work into plan graphics as well and create a point control to tag the edge of shoulder in my model to that line so that my horizontal feature constraint can find my back of curb reference line work as well.

​

3-d model showing curb point control edge of shoulder transition

plan graphics file with edge of shoulder transition and new width line and back of curb line work

Glad I could help... or did I?.  Anyway, here's what you wanted.... "Relative" ,  (since you didn't have a Horizontal constraint defined--the point was yellow) meaning the template origin control point  moves with the corridor control, then the point control moves with it until it finds the "Horizontal Feature Constraint" within 50 feet of that "relative" location.   Pretty much what you just discovered.  It's either within the 50' left (negative value) or right (positive value).  So, yes, "too close" meaning wrong side of constraint defined value of positive 50. Again relative to the point assigned to it horizontally.  Not having that point assigned and "floating" in the template... it never followed the horizontal shifts of the alignment and other offsets being changed or controlled.  If you were to put a negative (-50) instead it may have solved unless "too close" refers to the fact the point control in the template and the desired 2D linework crossed left and right of the searching point of the template.   To clarify with an example,  edge of shoulder is 48' at the beginning of the transition and tappers to 60' offset (adding a 12' lane), your 50' search would only solve past the 50' offset.  Setting the search to something smaller than 48' would solve the entire distance.

Glad I could help... or did I?.  Anyway, here's what you wanted.... "Relative" ,  (since you didn't have a Horizontal constraint defined--the point was yellow) meaning the template origin control point  moves with the corridor control, then the point control moves with it until it finds the "Horizontal Feature Constraint" within 50 feet of that "relative" location.   Pretty much what you just discovered.  It's either within the 50' left (negative value) or right (positive value).  So, yes, "too close" meaning wrong side of constraint defined value of positive 50. Again relative to the point assigned to it horizontally.  Not having that point assigned and "floating" in the template... it never followed the horizontal shifts of the alignment and other offsets being changed or controlled.  If you were to put a negative (-50) instead it may have solved unless "too close" refers to the fact the point control in the template and the desired 2D linework crossed left and right of the searching point of the template.   To clarify with an example,  edge of shoulder is 48' at the beginning of the transition and tappers to 60' offset (adding a 12' lane), your 50' search would only solve past the 50' offset.  Setting the search to something smaller than 48' would solve the entire distance.

Not really on this issue, but you did help with a different horizontal feature constraint issue I had! I was setting my constraint limits to be where I wanted the point to be rather than providing a broader ranger like you had said. Thanks so much!