Tips and Tricks for Roadway Designer
description
Transcript of Tips and Tricks for Roadway Designer
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
Denis Schaffer
Tips and Tricks for Roadway Designer
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
2 | WWW.BENTLEY.COM
• Templates are the real power behind the Roadway Designer, so we are going to start with Template Tips.
• The “smarter” a template, the less work that needs to be done in Roadway Designer.
• Even complex templates can be elegant and simple to use.
But BEWARE of the….
FRANKEN-TEMPLATE!!!
Template Tips
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
3 | WWW.BENTLEY.COM
-noun
/ Spelled Pronunciation [Frank-in tem-plit]
A typical roadway section consisting of an unheard of number of components, null points and end conditions as well as unnecessary display rules including double negative display rules and rules that exist only because the template was copied multiple times. Be aware of this type of template as opening such a template will oftentimes either cause the system to crash, or literally eat the individual alive.
Sentence: Bob sent me this Franken-template to look at, but I can’t understand what exactly he was trying to do so I just rebuilt it for him from scratch.
Franken-tem⋅plate
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
4 | WWW.BENTLEY.COM
• Having a robust Point list will make creating templates much easier
• Parameterize everything to reduce the need for many templates
• When building templates, think about how it is going to be used in a project, and constrain it appropriately
• Before setting up a Display Rule, make sure an End Condition wouldn’t be more appropriate– End Conditions are easier to manage and test– Display Rules should be limited to backbone changes
due to external controls
Good Template creation practices
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
5 | WWW.BENTLEY.COM
• Be VERY CAREFUL when using Display Rules with End Conditions– An End Condition will attempt to solve even if it is
not displayed.• Use meaningful names for Display Rules.
Don’t just accept “Rule1”, “Rule2”, etc.• When creating End Conditions…
Test… Test… TEST!!
Good Template creation practices
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
6 | WWW.BENTLEY.COM
• Document your templates– Create Documentation for your templates using a
company standard and associate that documentation to each template using the “Documentation Link”
Good Template creation practices
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
7 | WWW.BENTLEY.COM
• Value Equation– Adds the ability to vary a constraint number value
based on the differences between two additional points.
– Reduces the need for Null Construction Points• “-” at the beginning of a constraint label
– Got rid of the annoying “Mirrored” label when templates are built using the mirror/reflect options.
– Reduces the need for redundant “Mirrored” constraint labels.
• End Condition tree view in Active Template tree.– Allows for easy review of end condition branches in
priority order.
New Enhancements to improve workflow
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
8 | WWW.BENTLEY.COM
• End Condition Priorities and End Condition start points– In prior releases, there was no way to determine the
order of solution of end conditions that started from multiple start points
– Now the start points are processed in order of the lowest priority End Condition that originates at that start point
• Sometimes it’s easier to just place a point approximately where they are suppose to go, and then “pushing” them into the right place by editing/adding constraints
Did you know?
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
9 | WWW.BENTLEY.COM
• When placing a constrained, overlay/stripping, or end condition component, using precision keyins DL=, HS=, or VS= will result in constraints that match the keyed in values
Did you know?
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
10 | WWW.BENTLEY.COM
• You can change the drag point for a template by left clicking over the point you want to be the new drag point in the preview window
• While zooming in/out with the mouse wheel, holding down CTRL will zoom only in the X-direction, and holding down SHIFT will only zoom in the Y-direction
• You can pan by clicking and holding down the mouse wheel.
• Dragging and dropping a template onto itself will duplicate what it there– Useful for manual benching or quick mirroring
Did you know? – oldies, but goodies
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
11 | WWW.BENTLEY.COM
• Surface Symbology has been added as a property of a Corridor– Allows differentiation of corridors in multi corridor
interactions in cross section view• You can now completely mange backbone
transitions– delete/add transitions between any two template
drops (to add right click second transition)
Roadway Designer Tips
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
12 | WWW.BENTLEY.COM
Roadway Designer Tips• Don’t over clutter your views with display
references.– While display references are very useful, displaying
too many can affect performance– Display them when you need them to make sure
things work okay, but once you are done, turn them off
• A point’s coordinates are determined in this order (Highest first)1. Highest priority Point Control2. Style Constraint3. Point Constraint4. Coordinates where placed in template
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
13 | WWW.BENTLEY.COM
Roadway Designer Tips• Point controls work by replacing the constraint
that most closely matches the point control.Eg. If a point has a horizontal and slope constraint, a
vertical control will replace the slope constraint, but if the point had a vertical constraint and a slope constraint, the vertical control would replace the vertical constraint. In the event that the constraints are the same (slope-slope for instance), the second constraint will be replaced.
© 2
009
Bent
ley
Syst
ems,
Inco
rpor
ated
14 | WWW.BENTLEY.COM
Roadway Designer Tricks• When trying to find another corridor point to
determine where to start/end a point control or add a template drop, try using an arrow component with a point control to locate the desired point.
• If an End Condition transition is not working the way you expect, it is probably because the transition performs a linear transition from the end condition state at the start of the transition to the state at the end.