It would be wonderful if I could provide an example using Autodesk® Revit® MEP's Elevation parameter, but alas, that built-in parameter is

*still*not available for tagging or schedules.

However, here is the approach I used with a shared parameter used to report elevation. I am using three calculated values. I could get by with just one, but I like the idea of having one value to convert the elevation to a real number and one value to calculate the whole number, for QC purposes, and the third value to provide the actual filtering.

- Sparling Mounting Height: Shared parameter, Length, that reports the elevation of the element. How I wish I could use Elevation here!
- Elevation As Number (can be hidden): Calculated value, Number, using this formula: (Sparling Mounting Height / 0' 1")
- Whole Value (can be hidden): Calculated value, Number, using this formula: round(Elevation As Number)
- Is Whole (can be hidden): Calculated value, Yes/No, using this formula: Elevation As Number = Whole Value

Note that the Round function does not work with lengths so it is neccessary to normalize the value from Sparling Mounting Height: (Sparling Mounting Height / 0' 1")

*Update: Bruce Johnson pointed out that I could normalize using inches rather than feet and Revit converts the value correctly.*

I round the calculated value of the elevation, in inches, normalized to a number to be used to test if the original value was a whole number.

Finally, we do the actual test to provide a Yes/No result that can be used to filter the schedule.

I also wish that I could resize the Calculated Value dialog so that it would be easier to document my schedules. However, I have no fix for that, other than adding it to the AUGI wishlist.

Autodesk, the Autodesk logo, AutoCAD, Navisworks, and Revit are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries.

## No comments:

## Post a Comment