"Elevation override" Parameter to replace Elevation parameter

[danezeq]

Hey.

I have a special case in which i need "Elevation override" Parameter which i created, to replace the regular Elevation parameter in schedules. **Only when Elevation override parameter entered**.

That should be done with a formula on schedule properties window, right?

[Ilic.Andrej]

If I understood you well, you want to use "elevation override" as a condition (if elevation override is checked, use the custom value, otherwise use the actual value)

Create a calculated parameter and use this formula:

if(elevation override, overriden elevation, elevation)

...where "elevation override" is a yes/no project parameter and "overridden elevation" is a length project parameter.

After your work is done, just hide the schedule fields.

[danezeq]

Thanks. will it be possible to do it without the yes/no parameter? i mean if the Elevation override parameter has some value in it - that means "yes". if it's empty - it'll be "no".

[barthbradley]

---

@danezeq wrote:

That should be done with a formula on schedule properties window, right?

---

There may be another approach. Tell us the particulars about this "special case".  Also, post the family.  

[Ilic.Andrej]

---

@danezeq wrote:

Thanks. will it be possible to do it without the yes/no parameter? i mean if the Elevation override parameter has some value in it - that means "yes". if it's empty - it'll be "no".

---

you could try and use some other condition like:

if(overriden elevation>0,overriden elevation,elevation)

but I agree with @barthbradley . Tell us about the specific issue cause you might wanna avoid this nasty workaround.

[danezeq]

That could be a bit difficult to phrase but i'll do my best 🙂

There are some areas on this project which are "off-levels". that is a half floor above the rest of the floor.

i need to place signs and state their elevation from floor. the constructor should install them according to my schedule.

The elevation number should express the distance from the floor, not from the level.

My first thought was to draw new levels which are in between the normal levels. (like "-3.5").

But then i found that there more special cases when the floor can be 10cm above the level. so i must find a more durable solution.

[barthbradley · Accepted solution]

I think I mentioned this to you in your other thread.  The gist of it is to Nest your Face-Based Sign Family into a "unhosted" Family Template, place instance of Sign in  an Elevation View,  pull a dimension from the Sign to the Ref. Level and label the dimension with a SHARED Parameter. Then check "Work Plane Based" and uncheck "Always Vertical", load it into Project and place on a Host Work Plane in Plan View and use the Parameter to drive its elevation/offset above the Host Work Plane.  

See 2019 RVT attachment. 

[danezeq]

Thanks @barthbradley 

From your post i can learn that using this method i can skip that trick of using an elevation override parameter.

So i tried the family you've posted (thank you again!) and for some reason it placed wrongly: the elevation show as plan and plan symbol shows on elevation. Do i need to change any setting inside the family ?

[barthbradley]

That's is by-design. I wrote above to "load it into Project and place on a Host Work Plane in Plan View". 

[danezeq]

@Ilic.Andreji'm trying your suggested formula and i get this inconsistent units error:

https://www.youtube.com/watch?v=ZYuz6LcYgSg

i hope im adding it to the right place.

@barthbradleyi'm getting some difficulties to use this method, i will try to explain the new problems it creates.

[barthbradley]

Regarding your formula issue; try a neutralizer. Divide by one (/1) or Multiply by one (*1). 

Regarding the issue with the family I provided; can you share what that issue is?  

[barthbradley]

https://revitforum.org/showthread.php/1138-Revit-Inconsistent-Units-and-how-to-neutralize-them

[martijn_pater]

I was thinking to nest it in a two level based family template (apparently you can't schedule those top/bottom levels ootb though). But you can create a shared parameter for the elevation to bottom, dimension the upper ref level/bottom ref level and associate the shared parameter as instance reporting parameter.

edit: more or less the same as given by @barthbradley in post #7 actually.

[Ilic.Andrej]

---

---

@danezeq wrote:

@Ilic.Andreji'm trying your suggested formula and i get this inconsistent units error:

https://www.youtube.com/watch?v=ZYuz6LcYgSg

i hope im adding it to the right place.

---

its because every overridden elevation must have some default value added (like 0)

[danezeq]

but the whole purpose of this parameter is to override the "elevation" only if there is a value inserted.

thus, in all other cases the override elevation parameter should be empty.

[martijn_pater]

You can't check for an empty value (you would need an on/off parameter)... but it's still not really clear to me what you are trying to do...

[danezeq]

@barthbradleyabout the "family inside family" solution:

it opens a lot of new issues to resolve like:

i cannot choose between all my types that i created, Then i've found that i can define the type as a parameter inside the family, so i AM able to choose type but i should create a new type in the "father" for each type in the "son"

and then - schedules wont recognize all the "sons" types.

When i place these "family inside family" types on plan, they baheve differently from the original types, they dont stick strictly with walls, like - they're not wall-mounted or something.

...and lot's of more changes. if i were to use this trick you've provided, i will attack you with tons of new questions about how to adjust this new family to my project needs and my way of work.

i think i should let it go this time and keep working with what i have.

Maybe i just need to build this family from scratch and somehow make it associate to the level correctly (the current family dont recognize the level - EVER) and then the Elevation parameter will work right.

[martijn_pater]

Then you would have to add a parameter for the nested types. Select the nested sign geometry, go to label (top left) and add a type parameter. But a downside is that it populates the dropdown with all Generic model types ie. or in your case specialty equipment if I remember correctly. Or you'd have to nest it twice and work with visibility, but from what I remember you also have quite a lot of different signs/types... not really a good option then.

[danezeq]

That's exactly what i did but then, schedules wont see them.

[martijn_pater]

Did you make it a shared family? See link.