Limitations¶
The edges, stated plainly. Each is a chosen boundary, not an undiagnosed bug.
Geometry-derived volume is gross, not net¶
Tier-2 volumes are un-subtracted solids: a wall over-reports by its windows and doors. See quantities and provenance — the tag exists so you can tell tier 1 from tier 2 and treat tier 2 as a bound.
Tessellated geometry is proxy geometry¶
The meshes in the GLB are simplified representations for visualization. They are not a substitute for a B-rep kernel.
Do not clash-detect with them.
Some elements get no mesh at all and come back as a bounding box instead. How many, per model, is measured rather than asserted — see coverage.
Past a work budget, an element is a box or is left out¶
goifc bounds the work of tessellation, extraction and storey plans by the
file's size (see
SECURITY.md, which
also lists what is not bounded yet). When an
element runs past its own tessellation budget, its items are boxed; past twice
the budget they are left out. The whole Build has a budget too: past it, the
remaining elements in element order are each one box; past twice it they get no
geometry. Storey plans that run past their budget leave out the sections they
could not cut.
Each of these says so in the warnings, so a figure is never silently smaller: an element over its own budget is named, and the Build and storey-plan budgets give a count of the elements or sections they boxed or left out. No model in the coverage corpus reaches any of the budgets.
One consequence for drawings: a cut whose rings overlap in very large numbers (more than 2^24 units of nesting work) keeps every ring as an outline, so a hole among them is drawn filled. Disjoint rings, however many, are nested correctly.
No EXPRESS schema¶
The semantic layer reads positional attribute indices that are stable across IFC2X3 and IFC4 for core entities. Exotic or schema-specific attributes are not reachable this way.
The step layer below it is honest about the same boundary: IsA and ByType
are exact-type only, and there is no subtype expansion or attribute-by-name.
A section plane lying exactly along a solid's edges emits nothing¶
A triangle only contributes a crossing segment when it has a vertex strictly above and one strictly below. A face that merely touches the plane cannot close a ring.
This is a known gap with a test pinning it. See sections and floor plans.
Storeys with no contained mesh produce no plan¶
BuildImport omits them from StoreyPlans rather than guessing a cut plane.
See storey plans.
Only T-joins are built¶
A join cuts a partition's end against another wall's face (a T). Two wall
items meeting end to end, an L corner, are refused: off_wall when the
partition stays outside the other wall, not_on_face when its end reaches
into the other wall's body. Build them as a room, which mitres its corners. Walls that cross each other (an X) are not
joined: build the crossing wall as two partitions, each joined to the other
wall. See walls that meet mid-wall.
Scope of hardening¶
The well-trodden path is BuildImport on architectural IFC exports, because
that is what Blox's import pipeline exercises. Off that path — MEP-heavy models,
structural-analysis exports, non-architectural STEP — expect to find edges.
Finding one is a useful bug report. See compatibility for what is and is not promised.