Let’s say you have a Generic Annotation family with about 60 different view states controlled by visibility Yes/No checkboxes. These visibility states are linked to Sheets, and the Generic Annotation families themselves are placed in the Sheet views in Revit. I’m sure you are thinking “why??” at this point, but let’s skip past that part…
Can we drive the Annotation family visibility states based on its ‘host Sheet’ in Revit? Not really.
Can we create a mapping table in Excel, Dynamo-push a single integer value into the Annotation instances based on the host Sheet, and drive the visibility by formula that way? Yep.
Here’s the basic steps:
I used dir and Notepad++ to make the list, one column in Excel for the lookup value (I used Sheet Number), and one for the parameter I want to get and use
This relied on having the Family parameter list sorted Ascending in the Family Editor
The Excel sheet looked a bit like this – notice how the driving parameter is an Integer?
This is the work in progress in Dynamo – getting the Generic Annotation families, matching them up and getting the related Excel integer value
This is the completed dyn, with the push back into the Element Parameter to drive the visibility – see how the string has to get converted ToNumber before pushing into the Integer parameter?
And here is one instance in the project
After running this once, all visibility states are set properly throughout the project
Yet another example of @dynamobim making the Revit-impossible, possible 🙂
Very cool and advanced workaround by Jose Fandos over at Andekan: We will route around this limitation by first inserting the annotation family into another face-based family, and using this intermediary face-based family to place the annotation the way we want into the final Lighting Fixture. via Symbols for Lighting Fixtures Showing in Plan – Andekan � Blog
He also demonstrates that some Lighting Fixtures will display the Maintain Annotation Orientation checkbox, but some will not, and how to work around this.
So if you want to copy annotation and detail elements from one Plan View to another (without having to fiddle around with filtering of selections etc), just go to:
Then, browse to the currently opened file, select it, and then select the source view. Click to place. Done.
Also very cool:
● this command has intelligence with regard to Detail lines vs Model lines! Even though the Filter command cannot tell you if a line is Detail or Model, this Insert 2D Elements command will only bring detail lines
● running this command places the items onto the Clipboard as well. In certain situations, you can use the Paste Aligned command (such as between aligned Plan Views) AFTER you have finished placing the first instance of the 2D elements …
Pre-2013 sketch based stairs have the Stair Path bound to the actual Stair element. In Revit 2013 when using Component Stairs, the Stair Path becomes a separate element. Think of it as a special Tag for Stairs. The Stair Path tool is located on the Annotate ribbon:
You can safely delete the path from views where you don’t want to see it. It seems that these are automatically created in certain Plan views – I’m unsure what the ‘rule’ governing the automatic creation of Stair Paths is, yet.
The Stair Path is a System Family. You can Duplicate existing Path types to create and customize the Stair Path to your liking:
Also, the Categories related to Stair UP and DOWN text have all been moved to the Annotation Categories in Visibility / Graphics! You won’t find them under Model – Stairs anymore:
No doubt you issue many PDF files to consultants, Clients, Builders and the like. Why not add a URL link to your titleblock, so that anyone receiving your PDF files can jump directly to your webpage?
Its as simple as adding a parameter of type:URL into your titleblock.
To make it even easier for you, I have created a Generic Annotation family with a URL parameter inside it. Simply load this family into your titleblock, then link the parameter from it to a parameter in your titleblock (see image).