Monday, January 09, 2012

Revit MEP Space Tag Shows Unoccupied Now

The alternate title I was going to use is, "More Floors Than Revit Wants".

A thread popped up at AUGI recently discussing space tags that were working but aren't now. In this case, the tags being used were made to report the linked file's room name and number instead of showing the space's own name and number. That's a common work around to avoid worrying about what a space's name and number really is.

One reply mentions that they've seen a situation where they have more than one linked file and there are floors in each of them. It's my observation that the multiple floors issue isn't just that there just are multiple floors, it's that usually there are floors that are "inside" the Space. When an architect places "finish" floors on top the structural slab (often in a separate model) they typically place the floor using an offset equal to the material thickness. This puts the floor up/inside the Space.

This seems to reduce the space to a quivering mess.

One thing that fixes it, adjust your level(s) computation height (Instance Property of a Level) so it is equal to the top or slightly above their finish floors. To avoid that, ask them (the team that gave you the file) to set their finish floors so they are not Room Bounding instead. You'll have to wait for the new file though.

Then again, another way is to just use the regular space tag (using space name/number) and the Space Naming Utility extension (free to subscription members) to sync Room names/numbers with Space names/numbers. I'm still amazed that it isn't just built into RME by now.


Luke Johnson said...

Hey Steve, I always love it when people mention what Revit Wants :-) Nice post.

Steve said...

Okay I'll let your spam by this time. :)

Brian Mackey said...

I find finish floors that are room bounding cause many issues. I posted a little tip on turning them off globally on my blog. Glad to see others posting about this.