Methodology & Checks

Elements without geometry, shape reuse and copy-pasted geometry

Summary

An element in an IFC file is a record with data, and usually a shape. Without the shape it does not show in a viewer, it is missing from clash detection and from anything measured in 3D, and nobody can check its quantities by looking at it. With a shape that software cannot process, the result is the same, only harder to spot.

How the shapes are written also matters. Repeated objects, such as windows, bolts or noise barrier panels, can share one shape definition, or each copy can carry its own. Shared definitions keep the file small and make changes in one place; copies make the file heavier and every change a repeat.

The report covers this in five checks: Elements with geometry, Geometry that can be processed, Shape reuse (mapped geometry) and Copy-pasted geometry on the Geometry page, and Quantities on objects without geometry on the Consistency page. How heavy the shapes are is a separate topic, explained in Geometric weight and the density heatmap, and which kinds of shapes fail on import is in The risks of complex IFC geometry types.

Where you see it in the report

PlaceWhat it shows
Geometry page, checks Elements with geometry (marked key), Geometry that can be processed, Shape reuse (mapped geometry) and Copy-pasted geometryFor example 97.5% (412 without), 99.3% · estimate, 38% mapped · 1,204 unique shapes and 310 placements (4.2%).
Geometry page, card Repetition: modelled or pastedHow repeated shapes are written: reused through a mapped item, typed repeats without a mapped item, and unmanaged copies. Below it, Detail vs. quantity plots each class by number of objects and triangles per object.
Consistency page, check Quantities on objects without geometryThe number of elements that carry quantities but have no shape, for example 12 unlinked quantities.
In short pageUnder Can we use this model as the legal document (MALD)?, a blocker when more than 2% of the elements have no geometry. Under Is anything broken in the file? and in the interoperability risk, a note with the number of elements without geometry. Both leave element assemblies out of that count.
Capabilities pageThe condition Geometry on ≥ 98% of elements for Coordination ready.
Potential pageThe action of each check that scores below 80, with the points it would add to Overall quality.

The Geometry page and its checks only appear when the file has 3D geometry at all.

Elements with geometry

The share of elements that have a shape of their own (a representation in IFC terms). Openings are not counted, and virtual elements, which are meant to have no body, never count as missing one. The score is the share itself.

The check has a weight of 2, which is why it is marked key, and it is one of the hygiene checks described in Scoring versions and what changed: a pass (95 or more) counts for a quarter of its weight, a failure for its full weight. A file just under 95% therefore loses noticeably more than one just over it.

An element made entirely of parts, such as an element assembly, or a roof, stair or curtain wall whose shape sits in its slabs, flights or panels, has no shape of its own and shows up in this count. The In short page and the interoperability risk leave element assemblies out of their count, because their parts carry the shape.

Other common causes are elements exported for their data only (a system, a zone or a sensor without a body), elements whose geometry was lost in a conversion, and exports that leave out a category. The action in the report is Check the elements exported without a representation.

Geometry that can be processed

The share of objects with a representation whose shape is a 3D shape (a solid or a set of surfaces) of a kind that viewers and clash tools normally process. It covers every object with a representation (openings and annotations excepted), not only elements. The score is the share; the check has a weight of 1 and is a hygiene check like Elements with geometry.

The current audit does not build every shape. It estimates from the shape data, and the value then ends in · estimate. An object counts when its representation holds a 3D shape; an object whose only representation is a line, a footprint or an axis does not, and neither does an object whose shape is empty. The explanation on the check card says so: whether every shape builds without error is not verified. When the geometry engine cannot process a file at all, the audit is completed without building geometry, and this check is estimated in the same way.

Objects that only have a line by nature, such as alignments and alignment segments, grids, structural analysis members and virtual elements drawn as a boundary line, are part of this count. The share can therefore be a little below 100% even when every physical element has a proper 3D shape.

The action in the report is Simplify or repair the object types that fail to mesh.

Shape reuse (mapped geometry)

IFC can store a shape once and place it many times, through a mapped item (IfcMappedItem), usually the shape of a type. This check measures the share of elements whose shape is placed that way, out of the elements with a shape the audit could read.

Share placed through a mapped itemScore
0%50
20%80
One third or more100

The score is 50 plus one and a half times the share, up to 100. The check has a weight of 0.75. Low reuse is normal for models in which most objects are unique, such as a bridge or an earthwork; the score never goes below 50. The value also gives the number of unique shapes in the file.

Copy-pasted geometry

The audit compares the shapes of all elements of the same IFC class, wherever they are placed, at a precision of 10 micrometres. Identical shapes that are each written out in full, without a mapped item, are repeats. When every element with that shape is linked to one type object, the repeats are typed repeats: a properly typed model whose exporter did not share the geometry. Otherwise every copy after the first counts as copy-pasted.

The score is 100 minus 3 points for every 1% of copies among the elements with a shape the audit could read, down to 0: copies equal to 10% of those elements give 70, a third or more give 0. The check has a weight of 0.75. The card Repetition: modelled or pasted shows all three kinds side by side: reused through a mapped item, typed repeats and unmanaged copies.

Copies are not wrong in themselves. Ten identical dwellings or a row of identical piers can be modelled that way on purpose. They cost file size and consistency: a change to one copy does not reach the others, and nothing in the file says they belong together. The action in the report is Convert repeated copies into typed or mapped objects.

Quantities on objects without geometry

The number of elements that carry a quantity set (Qto_ sets and other quantities) but have no shape of their own. Such a quantity can’t be checked against anything: there is no body to measure, and the quantity check has nothing to compare it with. It may be correct, or it may come from a template, a type or a deleted object.

The score is 100 when there are none and 40 when there are any. The check has a weight of 0.5, belongs to the Consistency dimension and is a hygiene check. An assembly that carries a total weight or length but has no shape of its own, because its parts carry the shapes, is counted too. The action in the report is Check where these quantities come from.

The checks at a glance

CheckScoreWeight
Elements with geometry (Geometry)The share of elements with a shape of their own. Hygiene check.2 (key)
Geometry that can be processed (Geometry)The share of objects with a representation that hold a processable 3D body. Hygiene check.1
Shape reuse (mapped geometry) (Geometry)50 plus 1.5 × the share placed through a mapped item, up to 100.0.75
Copy-pasted geometry (Geometry)100 minus 3 × the share of copies, down to 0.0.75
Quantities on objects without geometry (Consistency)100 with none, 40 with any. Hygiene check.0.5

Geometry and Consistency checks count for three quarters in the Overall quality score. The full list of checks is in What we check.

Why it matters

  • What isn’t shown isn’t checked. An element without a shape is skipped by clash detection, by anyone reviewing the model visually, and by every quantity taken from the geometry. An asset register built from the model may hold records nobody can find on screen.
  • Unprocessable shapes fail late. They often surface only when the next party imports the file, which can be years after delivery.
  • Copies drift apart. When one copy of a repeated object is changed and the others are not, the model no longer tells you which version is right. Shared definitions and types prevent that.
  • File size is a running cost. Every copy is stored, transferred, opened and rendered for the life of the asset. Reuse keeps the file lighter without losing anything.

How to fix it

  • Ask the author to check the elements exported without a representation: were they meant to have a shape, or should they not be in the file?
  • For objects that fail to process, re-export them as simpler solids or as triangulated geometry; The risks of complex IFC geometry types lists the constructs that cause most trouble.
  • Model repeated objects as types and, where the authoring tool offers it, export the type’s geometry once and place it for every occurrence (mapped geometry).
  • Replace copy-pasted objects with instances of one type, so a change reaches every occurrence.
  • Remove quantities from objects that have no shape, or give the objects their shape.

Upload the corrected file with Examine a model to see the effect.

Frequently asked questions

My model is fully modelled, yet Elements with geometry is below 100%. Why?

Usually because of elements made of parts, such as assemblies, roofs, stairs or curtain walls, that have no shape of their own. Their parts carry the shape.

Why does Geometry that can be processed say “estimate”?

Because the audit estimates it from the shape data instead of building every shape. It tells you which objects carry a 3D body; it does not prove that every body builds without error.

Is copy-pasted geometry an error?

Not in the IFC sense: the file is valid. It is a sign of how the model was made, and it costs file size and consistency. Typed repeats are not counted as copies.