I would say that the one from Kivanc allows quick analysis, but at the end user will decide how to manage it because, as you said, it not only a test on a cross section location. You certainly have to place a minimum length of same barrier type. another way is to get both in the template and use display rule + parametric constraint or point control. Possible workflow - Using plan sketch of barrier types: do an analysis with Kivanc method to get theoretical barrier type. You don't need all components and features but at least one feature / barrier type you can easily identified in the drawing. Based on this analysis, in the 2D drawing, create a linear geometry with an Horizontal offset per barrier type. You can use any value but using barrier type height could make sense. In the template create a null point at 0 offset from centerline, like BarrierTypePicker create a display rules horizontal distance from centerline to BarrierTypePicker 0<=1.5 1.5<2 ... On each barrier type component, apply the corresponding display rule Don't apply the display rule on an end condition but on a component that is parent of the end condition, if you need end condition. The advantage is to have a plan view of barrier types you can easily change to have dynamic update (OpenRail Designer) of the modelling. The alternative is to use parametric constraints. Maybe even easier, but less graphic/dynamic, and more suitable for Rail Track. Same principle, but instead of drawing a feature with different offsets to define the barrier type, you set a parametric constraint on the BarrierTypePicker (just add a label for the horizontal offset) and set the value along the track from station to station. The advantage here is to have an easy to read/understand table of what you are applying: the table of parametric constraints you can import/export.
↧