Have you ever ran into a problem when you needed to display some additional information in your Revit level tags such as NGVD elevations in Revit for instance? One thing for sure – please do not try to edit the level name by setting it to something like “Level 1 (+ 3′-6” NGVD)”. This is messy and might get you in all sorts of troubles with your plan/RCP views down the road. Also, taking care of it by adding Text notes is very AutoCAD’ish and and you will have to keep the track of all your elevation/section views and keep copying that note to every new view that you create. Instead solve this issue in a Revit-friendly manner with a few shared parameters and by modifying/creating a new Level Head family with a couple of additional Shared Parameters for the NGVD values – solve it once and for all and make it your office standard.
Here is my proposed solution – if you like it you are welcome to adopt it (I have to warn you that this workflow involves API but all the files can be downloaded so you will need just a little-bit of set-up on your side to get things going)!
So in our office I did the following-I added two Project Shared Instance Parameters :
-first one called “NGVD”, which stores Level elevation taking in consideration the NGVD value (Length parameter type)
-second one called “NGVD Sign”, which stores the sign (either “+” or nothing if the elevation value is negative) (Text parameter type)
Then I also added a non-shared Project Parameter to Project Info called “NGVD Elevation”. This parameter will appear in Project Information and will define the NGVD elevation for “zero-zero” project level. The value of this parameter will drive the values for all the levels. I think it makes a lot of sense to keep the NGVD data at the same place where the rest of project specific information resides – in Project Information.
Ok, so now all the levels in our document have 2 new parameters and are capable of displaying this NGVD data if needed. Now all I needed to do is to modify the Level Head family where I imported the same 2 shared parameters that I assigned to levels in the project document. I won’t go in details – you can take a look at the family itself to figure how the labels work. The family has two types – one that displays NGVD and the other type that doesn’t.
Then in the project I created 2 level types – one that has the Level Head type with NGVD and another one that has Level Head type without NGVD.
Now the API plugin – a very simple one – all it does once you run it is that it goes and looks up the value of NGVD in the Project Information and then goes level by level and fills up/overrides the NGVD values and their signs in each level in the project so they display the correct NGVD value. (You can of course go level by level and fill up the values manually – but that is what the API is for – software should be doing the mundane repetitive tasks – that stuff will only shrink your brain!)
That’s about it.
If you download the files there are instructions on how to install the plugin. The important part is that if you want this workflow to work – make sure you import the shared parameters that I was using:
-open my sample project and open the Project Parameters window
-then select the NGVD parameter and click Modify
-then click Export so it exports this parameter into your SP file
-do the same with the NGVD Sign parameters
-now they are stored in your SP file for your future use with this Level Head family
When you set up your project you will have to recreate all the Project Parameters exactly the way I described it above.