buildingSMART / buildingSMART/IFC4.x-development

IfcDoor and IfcWindow : add "ClearHeight" and "ClearWidth" parameters

Open
#88 9 comments 0 reactions 0 assignees View on GitHub
allocated-building decided ifc-update-out
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

Hi all, @TLiebich and @aothms ,

In some country regulations, there are specific technical rules about minimum free pass dimension for Doors and Windows (for example: fire exit regulations, ventilation regulations, habitability regulation, and so on). By now, the current parameters of IfcDoor and IfcWindow of IFC 4.2, are not enought to evaluate these regulations:
- There aren’t direct parameters for ifcdoor or ifcwindow
- To try to calculate these “free pass dimensions” with the current parameters of the IFC 4.2 standard, is really impossible, caused by the variability of the design of doors and windows.

I propose 2 current parameters of the IFC, to implement to IfcDoor and IfcWindow:
- ClearHeight (currently only is for IfcSpace): the ClearHeigt for IfcDoor and IfcWindow, represents the maximum clear height or free height dimension, of an opened door or window (with the main panels/leaf opened).
- ClearWidth (currently only is for IfcRamp): the ClearWidth for IfcDoor and IfcWindow, represents the maximum clear width or free width dimension, of an opened door or window (with the main panels/leaf opened).

These proposed parameters can be stored as direct parameters for IfcDoor/IfcWindow (not inside Lining or Panel level), or maybe as parametes in Pset_DoorCommon / PsetWindowCommon.

Thanks and kind regards,
Xavier Coll
EiPM

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the IFC 4.2 definitions for IfcDoor, IfcWindow, IfcSpace, IfcRamp, Pset_DoorCommon, and Pset_WindowCommon referenced in the issue. Compare the proposed ClearHeight and ClearWidth meanings and decide whether they belong as direct parameters or in the common property sets. Done requires an agreed specification change that supports the stated free-pass-dimension use cases.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.