Folks, I am in need of a template expert to assist me.
I am working on the end condition and subgrade components of my template, trying to eliminate the need for end condition exceptions and hand editing of the subgrade in the cross sections.
Problem #1:
Problem #2:
I have been spinning my wheels on this all day and starting to think maybe I have overcomplicated it or maybe what I am trying to do is not possible. I prefer to use a single template for the project, as end conditions are not uniform throughout.
If anyone has any insight I would be indebted and if anyone could fit in some time, I would love to hop on a Teams meeting to explain further. I have also attached the template below.
TIA for any help!
test library.itl
Are your ditches standard, or do they have a ditch profile? You might be able to control the change from ditch to slope by the existence of the ditch profile if there's no profile for that station range, the ditch end condition would fail and give you the slope by default.
A Flat-bottom ditch and a V-ditch might actually be the same ditch, using a variable for "bottom width".
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Mary, I appreciate you taking the time to respond.
The ditches are all controlled by vertical point controls. How would the lack of profile make the ditch not model? I figured if there is no vertical control present the ditch will still model at whatever vertical constraint it is set to in the template?
I could make the flat bottom and v ditch one in the same, controlling the bottom width with a parametric constraint. The issue I see with that is I could only use one feature definition. Since the V ditches always point upstation, I end up drawing them in by hand anyway so maybe it wouldn't be a huge issue if all of the ditches had the flat bottom feature definition.
I feel like I shouldn't need to create some elaborate template with complex display rules and tests, like why can't I just have these end conditions in the template and say from xx+xx to yy+yy I want to use this end condition, etc. I guess I just have trouble wrapping my head around templates.
I don't like master templates. I mean they are powerful, but as you see, they are also complex and difficult to troubleshoot. I prefer to run my pavement as one corridor, my left sideslope as another (referencing the pavement) with my right sideslope as a third. That way, my pavement does what it does, and my end conditions are on separate corridors as their own template drops. That way, it really can be "from xx+xx to yy+yy use this end condition". My end condition templates can get a little complex if I want to play with testing and rules, but I don't have to think of all the conditions for a giant template that would do everything. I'm sure there are projects where that approach might not work, but for what I've been up to it works fine.
I'll have to get back to you on the vertical point controls, and how to make the ditch end condition fail. It's been a minute since I've done a template, so I could be misremembering or getting confused.
Matt,
It's possible to say from xx+xx to yy+yy I want to use this end condition.
To do this, you need to use two null points as a switch condition connected to display rules. Depending on the distance between the two points a display rule is triggered and displays one of the end conditions.
Example:
The distance is set using a parametric constraint on the two null points making it a fully manual process.
This is what I have done but I think I am having issues with priority. Only the end condition that is priority 1 will display.
The template I made uses several end conditions, and each end condition uses priority 1. This works because each end conditions has it's own independent point of origin.
The image shows the control points that govern the display rules at the bottom, and the separate end conditions above the road surface.(In the corridor they move to the same level using another parametric constraint, but are placed at different levels for easy editing.)
Answer Verified By: Matt Murphy
Thanks Jan!
It does seem my issue was that all 3 end conditions shared the same point of origin. I fixed that and the parametric constraint display trigger is now working properly. Problem #1 solved!