In my original life I was a motor mechanic, USA. auto mechanic. I work in NZ UK and Australia, then in architecture in Australia and NZ. I love the way language changes within specific industries across countries and across the world. Hence my question about 'nosings' that's just English I can only imagine how this happens in the other major languages of the world
I don't know when the nosing setting was added, but a BIG Thank You for that to the dev team, nice Xmas present :) Our local 'Aotearoa NZ' compliance requires stair pitch angle to be stated, would love to see that included if possible, something like image below
The pitch is being calculated as the ratio between height and length, the patch is just this one line actually: calculated_params["Pitch"] = round(height/length, 5)). If multiplied by 100 gives the slope in %.
As a ratio of two dimensions, the ratio is unitless and equal to the tangent of the angle between the ground and the stair so the angle (in degrees) = arctan(Rise / Run). I am not familiar as how IFC handles slope units, but should be easy to add new ways to display this value in the desired format on the Blender UI.
@elschilling For me, that is very helpful. Nice work! Others may have local requirements of their own to add. As you may have noticed I am a little obsessed about stairs, I will put together some other thoughts on how BBIM Parametric Stairs can 'best in class'
Hi fellow stair enthusiasts ;) I made a little stair calculator addon (actually, ChatGPT did the scripting bit) for local NZ Building Code. This highlighted why I struggled with the Parametric Geometry-Stair parameters in BBIM. The example in the image shows the addon in the N-panel and the BBIM parameters which are at odds, like 'number of treads' and 'height' must be 'floor to floor minus one riser'. This may very well be interpretations of differences? I am keen to hear the thoughts of others
I do like your tool @Nigel ! it looks cool
It looks like BBim staircase modifier is not measuring to the top of the landing for the height but the 15th tread?
Yes the treads on the BBim stair modifier look at risers - 1 for the treads for some reason, the staircase modifier definitely needs some work and love. I definitely think this is a difference of 'interpretation' with your tool giving the correct interpretation here
@nigel Agreed the floor to floor height is more significant, the default height parameter (on the right in your image) only seems relevant for a stair flight (component of a stair). Oddly though the height is not listed in the Pset.
Comments
Is a feature request
https://github.com/IfcOpenShell/IfcOpenShell/issues/3422
Thanks for letting me know, BTW is 'nosing' a common term in other countries? I know it from work in Australia and New Zealand
That's what it's called in the states, as well.
it appears as NosingLength in the docs:
https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/Pset_StairFlightCommon.htm
We call it Nosing in South Africa too!
In my original life I was a motor mechanic, USA. auto mechanic. I work in NZ UK and Australia, then in architecture in Australia and NZ. I love the way language changes within specific industries across countries and across the world. Hence my question about 'nosings' that's just English I can only imagine how this happens in the other major languages of the world
I don't know when the nosing setting was added, but a BIG Thank You for that to the dev team, nice Xmas present :) Our local 'Aotearoa NZ' compliance requires stair pitch angle to be stated, would love to see that included if possible, something like image below
@Nigel can you please create an issue on github about stair pitch angle?
Pull request: https://github.com/IfcOpenShell/IfcOpenShell/pull/4151
This is my first BB pull request, please tell if I am doing something wrong!
Thanks for your contribution. What units is the pitch? radians, degrees, decimal degrees?
The pitch is being calculated as the ratio between height and length, the patch is just this one line actually: calculated_params["Pitch"] = round(height/length, 5)). If multiplied by 100 gives the slope in %.
As a ratio of two dimensions, the ratio is unitless and equal to the tangent of the angle between the ground and the stair so the angle (in degrees) = arctan(Rise / Run). I am not familiar as how IFC handles slope units, but should be easy to add new ways to display this value in the desired format on the Blender UI.
@elschilling that was quick, thank you. Is it possible to add pitch in degrees as well? e.g. 32.4 deg
Sure! Here is the update proposal. If ok I will update the commit. Happy to collaborate :)
@elschilling For me, that is very helpful. Nice work! Others may have local requirements of their own to add. As you may have noticed I am a little obsessed about stairs, I will put together some other thoughts on how BBIM Parametric Stairs can 'best in class'
Hi fellow stair enthusiasts ;) I made a little stair calculator addon (actually, ChatGPT did the scripting bit) for local NZ Building Code. This highlighted why I struggled with the Parametric Geometry-Stair parameters in BBIM. The example in the image shows the addon in the N-panel and the BBIM parameters which are at odds, like 'number of treads' and 'height' must be 'floor to floor minus one riser'. This may very well be interpretations of differences? I am keen to hear the thoughts of others
I do like your tool @Nigel ! it looks cool
It looks like BBim staircase modifier is not measuring to the top of the landing for the height but the 15th tread?
Yes the treads on the BBim stair modifier look at risers - 1 for the treads for some reason, the staircase modifier definitely needs some work and love. I definitely think this is a difference of 'interpretation' with your tool giving the correct interpretation here
@nigel Agreed the floor to floor height is more significant, the default height parameter (on the right in your image) only seems relevant for a stair flight (component of a stair). Oddly though the height is not listed in the Pset.