Order of Processing Template Points, Components, Rules, and End Conditions

Holly Herring — Tue, 21 May 2019 14:19:43 GMT

Current Revision posted to OpenRoads | OpenSite Wiki by Holly Herring on 5/21/2019 2:19:43 PM

Product(s):	OpenRoads Designer, InRoads, MX, GEOPAK
Version(s):	10.00.01.15+ 08.11.09+
Area:	Templates

Question:

What is the order in which template data is processed at each template drop?

Answer:

This is generally the order in which OpenRoads solves the location of points and components at each template drop...

Template is dropped, and points are placed according to the point constraints stored in the template.
Parametric constraints are applied as defined in the template, and in the corridor.
Horizontal Feature constraints are applied to move points if the feature is found in the specified range.
Point controls are applied to the assigned points, overriding the corresponding constraint, and all points that are constrained back to the point controlled point will be recalculated.
Component display rules are solved based on the current position of all points.
End conditions are solved by extending designated segments along the specified slope to seek their targets.

Kevin McDonald — Fri, 04 May 2018 15:36:12 GMT

Revision 4 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 5/4/2018 3:36:12 PM

Product(s):	OpenRoads Designer, InRoads, MX, GEOPAK
Version(s):	10.00.01.15+ 08.11.09+
Area:	Templates

Question:

What is the order in which template data is processed at each template drop?

Answer:

This is generally the order in which OpenRoads solves the location of points and components at each template drop...

Template is dropped, and points are placed according to the point constraints stored in the template.
Parametric constraints are applied as defined in the template, and in the corridor.
Horizontal Feature constraints are applied to move points if the feature is found in the specified range.
Point controls are applied to the assigned points, overriding the corresponding constraint, and all points that are constrained back to the point controlled point will be recalculated.
Component display rules are solved based on the current position of all points.
End conditions are solved by extending designated segments along the specified slope to seek their targets.

Holly Herring — Thu, 02 Nov 2017 22:16:03 GMT

Revision 3 posted to OpenRoads | OpenSite Wiki by Holly Herring on 11/2/2017 10:16:03 PM

Product(s):	OpenRoads Designer, InRoads, MX, GEOPAK
Version(s):	10.00.01.15+ 08.11.09+
Area:	Templates

Question:

What is the order in which template data is processed at each template drop?

Answer:

This is generally the order in which OpenRoads solves the location of points and components at each template drop...

Template is dropped, and points are placed according to the point constraints stored in the template.
Parametric constraints are applied as defined in the template, and in the corridor.
Horizontal Feature constraints are applied to move points if the feature is found in the specified range.
Point controls are applied to the assigned points, overriding the corresponding constraint, and all points that are constrained back to the point controlled point will be recalculated.
Component display rules are solved based on the current position of all points.
End conditions are solved by extending designated segments along the specified slope to seek their targets.

Kevin McDonald — Wed, 18 Nov 2015 20:36:21 GMT

Revision 2 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 11/18/2015 8:36:21 PM

Question:

What is the order in which template data is processed at each template drop?

Answer:

This is generally the order in which OpenRoads solves the location of points and components at each template drop...

Template is dropped, and points are placed according to the point constraints stored in the template.
Parametric constraints are applied as defined in the template, and in the corridor.
Horizontal Feature constraints are applied to move points if the feature is found in the specified range.
Point controls are applied to the assigned points, overriding the corresponding constraint, and all points that are constrained back to the point controlled point will be recalculated.
Component display rules are solved based on the current position of all points.
End conditions are solved by extending designated segments along the specified slope to seek their targets.

Kevin McDonald — Mon, 16 Nov 2015 20:14:56 GMT

Revision 1 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 11/16/2015 8:14:56 PM

Question:

What is the order in which template data is processed at each template drop?

Answer:

This is generally the order in which OpenRoads solves the location of points and components at each template drop...

Template is dropped, and points are placed according to the point constraints stored in the template.
Parametric constraints are applied as defined in the template, and in the corridor.
Point controls are applied to the assigned points, overriding the corresponding constraint, and all points that are constrained back to the point controlled point will be recalculated.
Component display rules are solved based on the current position of all points.
End conditions are solved by extending designated segments along the specified slope to seek their targets