android tv

It is one of the few tags that can directly access the Level parameter - quite useful, even to the point where I created secondary Design Option called Level Tagger with a bit of Ceiling on it, and then use a Ceiling "Level" Tag to give me the Level in given views.

Using Copy - Paste Aligned to Selected Levels for the bit of Ceiling, and

Copy - Paste Aligned to Selected Views for the Ceiling "Level" tag.

The secondary Design Option is only turned on when I want to use this particular tag, meaning that the Ceilings are typically hidden.


Oh, you can also tag normal Ceilings with Ceiling Tags :-)

Another method of tagging the Level parameter is using the Case Param to Param tool:

1. Add a Text SP in the Project (shared parameter) to the Category for which you want to tag the Level property (ie. Floors)
2. Use Param to Param to copy the Level parameter of Floors to the SP you added in step 1
3. Add that SP to a Floor tag to tag the "Level"

You can't simply use a Floor Tag to tag the thickness of a Floor in Revit...

However, you can:
Convert the Floor to a Part, and use a Parts Tag

Parts tags can natively report thickness of the Part.

EDIT There is another method that comes via Kym Vdz on Facebook, it refers to this post on RFO (you will need to login to download).  I haven't looked into this deeply yet, but it seems to basically use a Floor-based family with a shared Reporting parameter to pass the Floor Thickness into a nested Generic Annotation... there is always many ways to solve a problem in Revit!

Julien writes "you should try this family....hope you like it. it reports the slab thickness. just place it on a floor.

credits to: Revitez!: Utiliser les paramètres de rapport pour coter l'épaisseur d'une dalle dans un plan d'étage

EDIT: This seems to be broken in 2014 at this point.  Even if you have it working in 2013, when you open in 2014 it will "break".  I'm unsure if there is a good workaround yet...

---

Absolutely awesome workaround from Dave Light!  He shows how to use an instance Shared Parameter to pass Keynote value via a Family formula to allow the tagging of Window Mark and Keynote in the same tag.  Read the whole post here.

On a wider level, this method shows that you can formulaically reference System parameters (built in family parameters) and pass their value to a Shared Parameter to allowing tagging.

Easy - just check the Properties for that Keynote:

Ever wanted to get a Tag to pick up the hardcoded Elevation value given to a nested Family?  Then check out this great little thread and cool answer by Julien!

Answer:
You need to set a SP in the nested family.
Make the plate geometry attached to ref planes that are not the 2 from the template. Assign a SP to the distance between the RP at center of geometry and the RP that defines origin. SP will be by instance. Beware of directions for correct behavior when loaded in the host.
In the host family, add the same SP, select the plate, and in properties palette, look for the tiny button on the left. Click and choose the SP you've added. The insert point of the plate must be set to the ref level of the host.
Now you have the elevation of the plate driven by a SP in the host. Create a tag for this SP. You're done. 

By Julien Benoit at
How can I get this parameter into a tag?

Some of you probably already realise that Case Apps have released a suite of Subscription tools (in other words, these are not free).

One in particular caught my eye - Super Tag.  It provides a "simple means for tagging specific family types by category using a specified tag on as many views as you choose."

Video:

Offsite link:
http://apps.case-inc.com/content/subscription-super-tag

Steve posted a few interesting things about Tags recently, including:
These categories are immune to Rotate with Component:
Foundations, Floors, Ceilings, Roofs, Furniture, Furniture Systems, Casework, Generic Models, Structural Columns, Detail Components, Massing, Mass Floors, Curtain Panels, and Specialty Equipment.
and
Architectural Columns, Shaft Openings remain immune to tagging at all.

Now, in the first instance, this proves again why some holistic Category Definition document is urgently needed.  I have called for this a few times before, but I haven't seen one yet.  In relation to Steve's post, the Category Definition document would have to further describe how the Tags of each Category operate...

Secondly, I'm assuming that Steve means you can't Tag by Category on Architectural Columns.  Because you can use a Multi-Category Tag on Architectural Columns without any issue.  Obviously, this is an annoyance.  A couple of ideas on how to get around this:

1. Don't use Architectural Columns, use Structural Columns instead (these can be tagged by category).  In a BIM silo, you shouldn't have a problem...
2. Nest a shared Architectural Column into a Generic Model family and constrain to suit.  Link some parameters through if you want.  Now you can tag the Generic Model, while the Architectural Column will still Schedule and it will even automatically join with adjacent / touching walls.  You will obviously lose some abilities native to Architectural Columns, like Attach / Detach.
3. Use Multi-Category Tags on your Architectural Columns
4. Use Structural Columns instead :-)

Read more:
Revit OpEd: Rotate with Component