buildingSMART / buildingSMART/IFC4.x-development

Ambiguity on whether or not clipping and CSG geometry is deprecated in documentation

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

Description

[Original post](https://forums.buildingsmart.org/t/clipping-csg-geometry-concepts/3100)

I recently discovered two confusing notes in ifc4 html documentation. Is that supposed to mean that IfcBooleanClippingResult, IfcBooleanResult & IfcPrimitive3D are essentially deprecated (i.e. can be imported but should not be exported)? Isn’t that a bit conflicting with DTV idea? :thinking:

[https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC1/HTML/schema/templates/body-clipping-geometry.htm 1](https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC1/HTML/schema/templates/body-clipping-geometry.htm)

NOTE This representation type is predominately used for compatibility with previous releases of the standard.

[https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC1/HTML/schema/templates/body-csg-geometry.htm 2](https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC1/HTML/schema/templates/body-csg-geometry.htm)

NOTE The Items__IfcBooleanResult and IfcPrimitive3D shall also be allowed for compatibility with previous releases of the standard.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.