[PIR SS2] Can I change a component into an end condition? Or should I use display rules?

I am trying to clean up a project to get it out the door. Of course, the person who worked on it previously is no longer here...Yes, I am watching videos, but I haven't found the one I need, or they just haven't answered all my questions.

I have a handful of templates that all have a paved shoulder with end conditions attached to find existing ground. As I work along, I've realized that I could accomplish what I want much more easily if the shoulder were actually an end condition as well. That way, I could apply end condition exceptions and a few other controls. Is there any way to 'back" my shoulder into being an end condition? Or do I have to create all that from scratch all over again?

Or could the bulk of my issues be solved with display rules instead?

The biggest (by far) exception I will need is for there to just be "no shoulder" at all drives and road approaches. For this stage of what I am doing, I need to just show the pavement lanes, and stop when I encounter drives or roadways. I have design features in plan view for those areas, and I thought I could just do it with a style constraint. Can I do that, even if the shoulder isn't an end condition?

if I drive those style constraints with null "seek" points, do I need separate points for left and right? Sometimes I do have approaches right across the street from each other, and I'm not sure how a single seek point would trigger both sides.

And I wish, I wish, I wish I could just copy components between templates. On my own project I could have set this up with template "pieces" that I could drag into any template I want, but I didn't set this up - I'm just trying to get it working.
Thank you.

Parents Reply Children