You have to watch out and do it with care when using the room data for extracting a specific dimension to report in the room tag. I highly recommend not to use those and seek a different solution.
Using the Unbound Height and/or Calculated Height based on Volume and Area, may result inaccurate information in your case, especially when multiple disciplines are working with the same model. For the simple reason that the reported values of both the area and the volume are dependent on a set of variables which you may not have ownership of solely. Area and Volume calculation reported in the room tag are linked to Room Computation Setting (it can be center of wall/to face/to core …etc), the Computational height set in the level datum and the upper/base limit offsets of the rooms/spaces used by others for energy analysis, sizing of building systems…etc . You might sleep on some values wake up on different ones.
Hence the area calculated and reported in the room tag is not always the right area you are looking for...example:
- In attics, pitched roofs or rooms with slanted walls (similar to Room 1 in the image below) if the computational height is adjusted, the area calculated would be at the computational height or where that plane interests the walls => not the largest footprint of the room...Using that to denominate the Volume which is already based on 2 other inputs will give you basically a dimension which is not really usable for anything
- If the walls are all straight, the Area reported when the Area computation is set to wall core is not the same net room area calculated to wall face. Add to that the computation of the volume reported in the tag and which is mostly up False ceiling...you will get a height which is related to anything.
There are more examples to give; however, if you read the above and compare the different values reported in image 1 and image 2 (volume/area/calculated and unbound height), and experiment with it a bit in Revit, you will get the point …
.