PR: IfcBuildingStorey and IfcSpace attributes
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
### Problem Description
When exporting from Revit to IFC, the IFC Exporter plugin automatically maps BaseQuantities (when selected in 3D) to specific properties. One item that I've noticed is that the property isn't as per the Schema for specific properties. For example IfcBuildingStorey should have an property "NominalHeight" however when IFC is exported from Revit it is converted into "Height". Below are some screenshots:
**IfcBuildingStorey**


**BuildingStorey reported in Solibri:**
NominalHeight->Height
**IfcSpace**


**Space reported in Solibri:**
NominalHeight->Height
ClearHeight->n/a
GrossPerimeter->Perimeter
NetPerimeter->n/a
GrossFloorArea->Area
NetFloorArea->n/a
GrossCeilingArea->n/a
NetCeilingArea->n/a
GrossWallArea->n/a
NetWallArea->n/a
GrossVolume->Volume
NetVolume->n/a

In the IFC-SPF the data aligns with what viewers are showing so it isn't a viewer issue.
It appears the BaseQuantities are hardcoded and cannot be modified on export i.e., changed from Height back to NominalHeight.
### Revit Version
2025.4.x
### IFC for Revit Addon Version
25.4.0
### Windows Version
11 24H2
Contributor guide
Research direction
No source file or test is named. Start by locating the BaseQuantities export mapping and the IFC schema definitions, then reproduce the Revit 2025.4 export and inspect the IFC-SPF output; done means IfcBuildingStorey and IfcSpace quantities use the schema names and values reported in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- data, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100