The following paragraph and the attached illustration come from one of my old posts in Augi about this:
"Another solution for this issue of swapping notes with different contents is this: One host annotation family with one family type parameter for generic annotations, and a set of generic annotation families nested into. For example, the file "Notes.rfa" hosts the following files: "Note 1.rfa", "Note 2.rfa", "Note 3.rfa", etc. These files shall have descriptive names, according to their content. By doing this, the family maker can create the notes independently, without any visual clutter. In addition, the host file needs very few parameters, maybe just one: the family type parameter. No need to use visibility parameters nor any formulas. On the other side, the end user just inserts "Notes" and then simply chooses, for example: "Note for Acme", "Note for Abc", etc."
But is this possible in a Multi Category tag? I'm trying to accomplish this with the attached tag. I recreated all the different labels in seperate families. But I can't nest these in the MC family to refer to.
What I want to accomplish is similar to Alex' OP: I want to be able to swap the different labels.
The current tag is composed of 11 lines of text labels:
Mark (system value)
Omschr0 to Omschr9 (which would add up to Description 1 to 9)
Each Omschr-parameter is a type parameter, which holds a text description of the item tagged.
Say I would want to tag a wall made of different layers.
Layer 1: Exterior brickwork
Layer 2: Air cavity
Layer 3: Insulation
Layer 4: Interior brick wall.
Or a floor, roof, or any other component made out of different parts which I want to name in the tag.
Using this tag I can fill in all the text labels to create one single tag.
Why not use Material Keynotes? Well, because these layers often have multiple lines. For instance, a standard tag for this wall would contain the next lines:
Omschr 0: Exterior brickwork, size axb
Omschr 1: Color
Omschr2: Mortar to be used
Omschr3: Air cavity 30mm
Omschr 4: 100mm insulation, manufacturer and type
Omschr 5: fixation by....
Omschr6: 100mm interior brickwork
Omschr7: mortar to be used
omschr8: finish (if not modelled seperately)
This tag is normally used in a detail view. In a section view I would use the same tag, but only some lines (omschr 0,1,3,4,6,8). Because I can set the visibility for each line but I can't change the order in which the lines are displayed I have to use multiple tags and align them manually (tag1 for lines 0+1, tag2 for lines 3 and 4, etc)
I posted an example of this workflow earlier in this thread
If I could select the shared parameter which each label is referring to, I would be able to do this in 1 tag. But I never got this to work properly... Any ideas?
Last edited by mdradvies; January 30th, 2011 at 11:41 PM. Reason: clarification
So far, I dont' see a way to do this. These are two roads which both go to a dead end:
1) A multi-category tag can receive generic annotation families as nested, but generic annotation families don't accept shared parameters. Therefore, we can't have a multi-category tag that works with shared parameters and at the same time has labels that swap generic annotation families with a family type parameter.
2) Generic model tag families can accept shared parameters but cannot be nested into the Multi-category tag. Therefore, again, we can't have a multi-category tag that works with shared parameters and at the same time has labels that swap model tag families with a family type parameter.
This is as far as I could take it myself... Too bad, but thanks for checking. Always a b***h when you find out you missed on checkbox in order for it to work. Still have the feeling I am missing out on something though. Can't put my finger on it. So I'll be working on it some more when I have the time.
One question though: If I were to go for option 1, would the nested GA's still reflect on the item tagged? Or is the GA only referencing "itself" My current tag has the nice feature that the parameters "omschrijving 0-9" are dependent of the type of element. So, if I were to tag Wall type 1 and reuse this somewhere else in the project, it will have the same (consistent) text notes automatically.
I think this isn't the case when using GA's is it?
There are pros and cons to all of the systems, but that one with Shared Parameters has massive holes in it too. We use all of the different systems, for different levels of detail, which is a decent compromise.
We use Material keynotes for Large Sections and Details, where we call out the individual elements.
We use Item Keynotes or Tag-Type Comments/Description Tags by Element, at the Building Section / Elevation views where we want more general notes.
You can circumvent the Keynotes with your own system, but Revit has enough holes that none of them will work perfectly. That system would scare the heck out of me, since the objects materials arent driving the note, the notes are all at the element level for something very detailed. If someone swaps out GYP for PLYWD, they also need to remember to go change the notes?
I do agree though: this one is not usefull for large firms with a lot of people using the notes.