Bernold Kraft

Hi Steve, the current Xbim uses hybrid tessellation approach which has an issue in the Xbim-only code with incorrect orientation of the final mesh. I tried also to switch to...

Hi, the IFC placement relies on RHS logic. Given two axis the 3rd is derived by the cross product. In your case the final Y axis is (0,1,0). Converting from...

Hi @florius0, it's a little bit more complex than just compiling on another platform (I'm also using macOS now). There's an open issue #248 already covering a portion of your...

No, the native cpp code of XbimGeometry (OpenCascade wrapper) is not portable due to the usage of CLR and interop calls.

I wasn't sure if this approach is the best way to handle this. There are multiple IFC placement / aligment entities which provide geometrical data without having a specific context...

Still existing in 5.1.288. Any fixes here? @SteveLockley It's related to a fix in https://github.com/xBimTeam/XbimGeometry/commit/aa7e88f15f9133438b8ba761c884c49164bacfa4#diff-0709a275ed09d3306fb4a5caf5a04aa7. Means that this wall isn't properly closed by some tolerance issue somewhere ... It's an...

The IFC isn't IFC2x3 compliant (as the embedded validation states): `Entity #17 (IfcShapeRepresentation) has validation failures. IfcShapeRepresentation.ContextOfItems is not optional. Issue of type EntityWhereClauses on IfcShapeRepresentation.WR21. Entity #31 (IfcShapeRepresentation) has...

I thought that the ```IfcProject```'s GlobalId (inherited from ```IfcRoot```) would do the trick to match two IFC models against a single project? Revision is more a kind of marking not...

Precision in IFC is really a good point of enhancement. But it doesn‘t depend on the unit type. It more a problem of the topological type (i.e. IfcLengthMeasure). Precision should...

Precision and error are definitions from two different worlds. Error is a term in statistics. The original definition of precision in the IFC is meant as epsilon value or tolerance...