As follow-up to a previous post, Plant Connector Detail Lines via Dynamo, a reader suggested that the plantings could be sorted a few different ways, including by x and y coordinate values and by distance from another point. I thought these were both good ideas, so I went ahead and made a few nodes that can do just that.
Today’s Landform update has a few new nodes, including Points.SortByDistance and Continue reading
Of the few Site tools that exist, Property Line is one of the most fundamental. Almost any site, regardless of size, will have property lines. These can be a significant coordination issue with Architecture, especially on an urban site.
Creating the Segments
There are 2 ways to create a property boundary: by entering distances and bearings or by sketching. It is usually easier to sketch the boundary first, especially if it is already drawn on the survey. A sketched property line can then be converted into a table, though you will always get the following warning: Continue reading
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
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
One of the most versatile families in Revit is the Generic 
Annotation (this is the same as the Symbol, on the Annotation ribbon). It is commonly used to create symbol-like families, such as keynotes, north arrows, graphic scales, and stamps. But it can also be used to generically annotate a drawing/ view.
In typical Revit standards and best-practices, it is almost always preferable to use a Tag, since a Tag pulls actual information from the object. Generic Annotations are better than just “dumb” Text, but unlike Tags, they will not update if any information about the annotated object changes.
Grading plans are one of the few exceptions to using Tags. Continue reading
landarchBIM 