I recently watched a SIG presentation where the presenter was using a parent /child relationship to turn off/on the proposed median. I have always used display rules to do this. I was curious if anyone knew if there was advantage to doing it with the parent/child relationship as opposed to doing it with display rules. Maybe one uses more memory than the other? Thanks Brian
I use both. Display rule to turn off say a curb and the parent/child to turn off the grass verge and earthworks.
But verge and earthworks have their own display rules allowing me to leave the curb but turn off the verge and earthworks or just remove the earthworks.
Parent/child arrangements in median with regards to Barrier would allow you to set a series of Barrier foundations that only apply when you have a barrier and a different pavement solution with no barrier.
Regards
Chris
AECOM Roads UK&I Digital Engineering, Design & Solutions Lead | Sector Information Management Lead
Associate Director – Digital
OpenRoads Designer 10.12 | MicroStation 2023 | ProjectWise CE 10.3.4 | ContextCapture | ProjectWise PowerShell 2023 | ProjectWise WSG API | Generative Components | OpenBridge Designer 10.12
Civil 3D 2023 | Dynamo | Navisworks Manage
PowerShell | Visual Studio | Office 365 | Power Platform | Teams | SharePoint | Visio
Speckle | BIMVision | Revizto | Solibri
Chris, thanks for the response. I did not do a good job of explaining what was presented in the SIG. Say I have a curb with a sidewalk behind it. The sidewalk was only going to be there if the curb was built. Display rule to turn on the curb with the sidewalk a child to the curb. What he was doing on the SIG was he built a DNC end condition seeking the curb. Then had the curb and sidewalk as children to the DNC end condition. DNC end condition does not find curb and then the curb and sidewalk not shown. I was just curious if there was an advantage to doing this way.
OK yes, same principal as i described but instead of manually controlling if Curb and sidewalk is on with Parametric Constraints and Point Controls. The demo in the SIG sounds like they are using Horizontal Feature seeking to determine if a curb & sidewalk is needed.
Some people refer to this as a "FrankenTemplate" where one template fits every design instance by using a variety of point controls and/or, horizontal feature seeking. This is somewhat like GEOPAK criteria where plan view graphics controlled what the cross section drew, except this controls the 3D model that is built. This technique is often used to drop in driveways, leave gaps at intersections and apparently to draw curb and gutter or some other roadside grading.
Even in this instance, the parent/child relations simplify maintenance.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Thanks Chris