buildingSMART / buildingSMART/NextGen-IFC
References, Insertion blocks, typical floors
- Dominant language
- TeX
- Stars
- 64
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
99% of floors in the condo design are the same.
Duplicating them
- increase file size with factor 99
- make impossible modification after Design Transfer View
STEP ed 3 is one way, but maybe we will have better solution knowing business logic... At least typical floors.
Move IfcMappedItem one level up.
(Remaining 1% of floors is made from the same typical floor parts)

Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the STEP ed 3 approach and the IfcMappedItem placement described in the issue, along with how the Design Transfer View handles duplicated floors. The work is done when typical floors and their repeated parts can be represented without duplicating nearly identical floor data while preserving the remaining unique parts.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100