Finding the boundary lines of an element is something that I have been trying to do in Dynamo for a little while now. There are several different tasks that you can automate in Revit once you have the boundaries of an element. First, you can automatically draw Area Boundary Lines for your planting plans. And particularly for Floors, you can use boundary lines to create duplicate Floors.
So I was quite pleased to discover Collector.ElementSketch in Spring Nodes. Continue reading
One of the pitfalls of using Areas as planting areas is that Areas do not have any 3d representation. This can become an even bigger issue if you want to create a rendering that shows the plants in those Areas.
But with Dynamo, you can automatically place individual Planting components in their respective Areas based on their spacing and types.
One of the simplest and most useful applications of Dynamo is driving Shared Parameters with formulas. This allows you to have a Shared Parameter as a “Calculated Value,” which is something that you cannot do in Revit without access to the API. But to do this in Dynamo, you just need a few nodes.
As mentioned in Part 3, creating planting plans using Areas has certain drawbacks. The most substantial is that Areas do not have types, so their parameters are all instance parameters. This can be mostly overcome by using Styles. While Styles have their own rules, they make it easier to tie Area parameters together, which can also make it easier to define perennial plant mixes within a single Area.
Styles can be used across all scheduleable families/ categories and are accessed by creating a schedule key instead of scheduling building components (when creating a new schedule).
After creating an Area Style schedule Continue reading