This is probably blasphemous to the IFC gods, but it seems like it would be very helpful to have techniques like the following in IFC.
-
<span style="color:red">#148</span>= IFCBUILDINGSTOREY('2Xg7c1A415nR_KbA9qpXi$',#42,'Level 1',$,'Level:Story Level',#146,$,'Level 1',.ELEMENT.,<span style="color:red">0.</span>);
-
<span style="color:red">#154</span>= IFCBUILDINGSTOREY('2Xg7c1A415nR_KbA9qp4ns',#42,'Level 2',$,'Level:Story Level',#153,$,'Level 2',.ELEMENT.,<span style="color:red">12.</span>);
-
219= IFCWALLSTANDARDCASE('3aOFpwRCn36Pv_D8U$GBBQ',#42,'Basic Wall:Testy Wall Type:153022',$,'Basic Wall:Testy Wall Type',#183,#213,'153022');
-
213= IFCPRODUCTDEFINITIONSHAPE($,$,(#188,#210));
-
210= IFCSHAPEREPRESENTATION(#125,'Body','SweptSolid',(#200));
-
200= IFCEXTRUDEDAREASOLID(#198,#199,#20,<span style="color:red">#154.elevation - #148.elevation</span>);
-
198= IFCRECTANGLEPROFILEDEF(.AREA.,$,#197,5.25,0.5);
-
-
-
-
-
In this instance, the importing application could retain the height of the wall as a function of the difference between the 2nd and 1st floor elevations, which in this case equals 12ft (or meters, if that's the unit in the IFC file)
A small step to parameterizing IFC?