ENH: Support for Quantity Parameters
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
### Enhancement Description
Good day,
Would it be possible to expose [IfcQuantityLength](https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/TC1/HTML/ifcquantityresource/lexical/ifcquantitylength.htm), [IfcQuantityArea](https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/TC1/HTML/ifcquantityresource/lexical/ifcquantityarea.htm) and [IfcQuantityVolume](https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/TC1/HTML/ifcquantityresource/lexical/ifcquantityvolume.htm) to the custom Pset mapping?
Seems like the support already exists and it only needs to be tied back to the pset parsing?
https://github.com/Autodesk/revit-ifc/blob/master/Source/Revit.IFC.Export/Exporter/PropertySet/QuantityEntryMap.cs#L143
This is sorely needed because a lot of automated checkers assume an IfcLength/Area/VolumeMeasure property as an invalid input.
Kind Regards,
Dimitar
### Revit Version
2024.0.x
### IFC for Revit Addon Version
24.x.x
### Windows Version
10 22H2
Contributor guide
Research direction
Start by reading Source/Revit.IFC.Export/Exporter/PropertySet/QuantityEntryMap.cs around line 143, then trace the custom Pset parsing path that consumes this mapping. Confirm how IfcQuantityLength, IfcQuantityArea, and IfcQuantityVolume are represented in the generated IFC output, and verify that automated checkers accept the resulting quantity properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100