buildingSMART / buildingSMART/IFC4.x-development

Geometry Use Definitions in IfcRelSpaceBoundary2ndLevel

Open
#631 0 comments 0 reactions 0 assignees View on GitHub
after-NWI iso-Ed
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

Hello,
Is there a mistake in the picture Geometry Use Definitions from https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcRelSpaceBoundary2ndLevel.htm or do I understand it wrong?
The CorrespondingBoundary and inverse relation Corresponds should always be faces positioned one on each side of an element. Correct?
In the picture the above 2ndLevel Boundaries are #212 and #211. So in the text of #212=IfcRelSpaceBoundary2ndLevel the attribute CorrespondingBoundary -> #201 is not correct. It should be #211.

I hope you understand what I mean.
Greetings from Rosenheim

Contributor guide

Open the contributing guide

Research direction

Start with the Geometry Use Definitions page for IfcRelSpaceBoundary2ndLevel linked in the issue, then compare the diagram with the #211, #212, and #201 attribute references described in the report. Done means determining whether CorrespondingBoundary and Corresponds are represented correctly and documenting or correcting the identified reference if it is wrong.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.