ENH: Support for IfcLogical datatype
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
### Enhancement Description
Any ```YesNo``` parameters that are mapped to IFC attributes with the ```IfcLogical``` datatype are exported with an ```UNKNOWN``` value (no matter what the parameter value is). Could you please add support for ```IfcLogical``` in a future version?
Examples:
- Pset_BuildingStoreyCommon.AboveGround
- Pset_BuildingCommon.IsLandmarked
Tested with IFC4 RVArch
### Revit Version
2023.1.x
### IFC for Revit Addon Version
23.3.1
### Windows Version
10 22H2
Contributor guide
Research direction
Start by locating the IFC export code that maps YesNo parameters to IFC attributes, then inspect how the IfcLogical datatype is handled. Reproduce the issue with Pset_BuildingStoreyCommon.AboveGround or Pset_BuildingCommon.IsLandmarked; done means supported YesNo values are exported without always becoming UNKNOWN.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100