One of the very first Dynamo blog posts I read demonstrated how to place an adaptive fence component so that it would follow Topo. At the time, I thought it was an interesting concept, but not overly useful since I typically use non-adaptive fence components and fences will frequently step (instead of slope) with grade change.
However, not all fences are stepped, and I recently decided to take a look at trying the same concept on a non-adaptive fence. It is quite a bit more complicated than the adaptive version, but there are several reasons why you might not use an adaptive fence component and the concept can also be used to place a stepped fence.
I came across this video that Aaron Maller posted a few days ago and I thought it was worth sharing. In it, Aaron is simply laying out some Parking families in Revit, but it is interesting to see the various ways in which people build and use their own content. There are almost always things that you can learn from other people to improve your own methods and content.
Anyone who has spent much time in Revit is almost undoubtedly aware of the hierarchical structure of Revit model families. All model families are assigned to a Category, and each Family usually has both multiple Types and Instances (though not always).
This hierarchy can be used when selecting Revit elements in Dynamo. And while the Dynamo primer does include a nice diagram of this hierarchy, it does not thoroughly demonstrate how each level of the hierarchy can be used to select elements.
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.