With a mapping of all Revit Categories to IfcBuildingElementProxy (in the Export Options),
there seems to arise a conflict with the hardcoded mapping and the geometry creation.
The Stair Run is translated to 2 entities: IfcRampFlight as well as IfcBuildingElementProxy.
The Stair Stringer is (of course 2 times) also translated to 2 entities: IfcMember and IfcBuildingElementProxy.
A little bit too much geometry I think.
Retested it with R2019.1
with regular 19.1 exporter and with current-Github-IFC4RV-exporter-version
IFC4RV1
A) 19.1 exporter (regular version): same issue as with R2018 and 18.4 (as expected, since the code should be similar)
A.1) IFC export options: Stairs mapped 2 IfcBuildingElementProxy -> doublure of StairFlight and supports: issue
A.2) IFC export options: Stairs mapped 2 IfcStair -> correctly exported with 1 x IfcStairFlight (Run), 2 x IfcMember (Supports/Stringers), 2 x IfcRailing: export OK!
B) 19.1 exporter (current-Github-IFC4RV-version): issue of double geometry solved, but other issue
B.1) IFC export options: Stairs mapped 2 IfcBuildingElementProxy -> no double geometry anymore: the StairFlight and the Supports are exported only as IsBuildingElementProxy (as intented): export OK!
B.2) IFC export options: Stairs mapped 2 IfcStair --> the StairFlight and the Supports are baked together: (new) issue [I suppose the correct result should be similar to A.2]
Just one for almost the start of the new week.
R2018.3
18.4.0
IFC2x3CV2 & IFC4RV
With a mapping of all Revit Categories to IfcBuildingElementProxy (in the Export Options),
there seems to arise a conflict with the hardcoded mapping and the geometry creation.
The Stair Run is translated to 2 entities: IfcRampFlight as well as IfcBuildingElementProxy.
The Stair Stringer is (of course 2 times) also translated to 2 entities: IfcMember and IfcBuildingElementProxy.
A little bit too much geometry I think.
Last edit: Dirk Van Rillaer 2018-07-08
Retested it with R2019.1
with regular 19.1 exporter and with current-Github-IFC4RV-exporter-version
IFC4RV1
A) 19.1 exporter (regular version): same issue as with R2018 and 18.4 (as expected, since the code should be similar)
A.1) IFC export options: Stairs mapped 2 IfcBuildingElementProxy -> doublure of StairFlight and supports: issue
A.2) IFC export options: Stairs mapped 2 IfcStair -> correctly exported with 1 x IfcStairFlight (Run), 2 x IfcMember (Supports/Stringers), 2 x IfcRailing: export OK!
B) 19.1 exporter (current-Github-IFC4RV-version): issue of double geometry solved, but other issue
B.1) IFC export options: Stairs mapped 2 IfcBuildingElementProxy -> no double geometry anymore: the StairFlight and the Supports are exported only as IsBuildingElementProxy (as intented): export OK!
B.2) IFC export options: Stairs mapped 2 IfcStair --> the StairFlight and the Supports are baked together: (new) issue [I suppose the correct result should be similar to A.2]