While Revit has adequate tools for individual plants, planting areas (for perennials and the like) are not as easily done. There are many system families that calculate areas: filled regions, floors, rooms, and areas. Though you could use filled regions, it is never advisable to use an annotation for a physical (model) element. Instead, I recommend areas.
Areas are funny little families. Like rooms, they overlay over everything and only appear in plan view. Since they are designed for floor plans, they are not ideal for planting plans, but they work well enough. Just like most things in Revit, this process requires a bit of investment initially, but the payoffs are there immediately when you start tagging.
Step 1: Load Shared Parameters
(If using Area Styles, skip this step. This is covered in Part 4)
As a system family, their shared parameters must be loaded directly though Project Parameters (under Manage tab). I’ve shown below which shared parameters I load in for Areas; I don’t load Scientific Name (explained below).
Step 2: Make an Area Plan and Draw Area Boundaries
Areas only show up in special plan views: Area Plans (I use Rentable). So after making an area plan you then need to draw area boundaries. This is one of my least favorite parts of this workflow because it gets a bit redundant drawing boundaries multiple times (but you can lock these boundaries to your existing edges).
Step 3: Place Areas
I use the Name parameter as a replacement for Scientific Name. Revit remembers all of these that you’ve tied into Color Schemes. So you can easily grab them as you place Areas.
Step 4: Calculate those Values and Tag ‘Em
Once you get your Area schedule set up you’re going to need a few extra fields: Spacing is a length and Count Calc(ulated) is a number. The formula for triangulated planting is: (Area / 1) / (Spacing * Spacing * 0.866)
Just like I discussed previously (in Part 2), the calculated count can’t be pulled directly into the tag. But you can keep the accurate number in your final schedule. So your final result can look something like this:
Now, there are a few downsides to this workflow. Unless you lock your area boundaries, they will need to be updated when your hardscape/softscape edges shift. Also, Areas are not intended to be used as plant types, so their parameters are all instances and do not lock across type. This can be addressed by using Area Styles (Part 4), or it can be monitored manually and updated in your final schedule (where you are not itemizing every instance).
I also did not fully explain Color Schemes, but here’s a bit of what mine looks like: