Model family reads room number and puts it into model text

[MiWolff]

Would be brilliant if we could setup a modelled annotation that displays info about the modelled environment. That model annotation would know and display which room it is located in. That way we could have visible alphanumeric info while virtually visiting our designs without setting up extra parameters that need to be maintained manually or by some dynamo script that users need to know about to routinely run it.

[Mike.FORM]

It would be nice to be able to assign rooms, spaces, areas to signage families, or have it as a subcategory for signage families similar to how railings have subcategories. This would then give access to all the built-in parameters.

[mhiserZFHXS]

@Mike.FORM 

I think manually assigning a room to a given family would be a much more consistent result than trying to have Revit figure that out on its own. It makes more work on any given sign, but it'd probably cause less headaches overall.

The way we do signage now is we have an empty family nested and shared in our door families that can be picked up by our signage schedule. That way we can pull some info from the doors, but even that is a bit clunky, and its not something some of our less savvy Revit users can wrap their heads around.

This would be a much more straight forward system that I think most people could use and understand, and could probably even have utility beyond signage.

[Mike.FORM]

@mhiserZFHXS I agree, what I was saying would be to have sub-categories for signage such as room, area, and spaces.

If the family is set to the room sub-category then you would get all the built-in room parameters so you could associate it with model text and other parameters within the family for formulas and what not.

Then when you load it into the project you can assign the room to that family using a drop down that lists all the rooms in your model.

It could also be set up in the family the same way profiles have a usage.

[MiWolff]

While elements like structural columns do know their positions if a grid is in place, their families do not have access to that info inside the family editor. If they had, you still could not put that info into a model text, because that would require the text parameter to become a multi-line text parameter.

[Mike.FORM]

Agreed, that's a whole other model text issue.

Model text should work the same way as a label where you assign parameters to the model text instead of just linking them.

Then it would be able to use any parameter type.