Spaces: closed volumes, room areas and virtual boundaries
Summary
Spaces (IfcSpace) are the rooms and zones of a building: the offices, corridors, plant rooms and car parks that floor areas, room schedules, lettable area, cleaning contracts, energy calculations and facility management are built on. A space has a volume, a floor area and a name or number, and the systems you run the building with often use it as the address of everything in it.
Spaces are easy to get almost right. The room looks fine in the viewer while its volume is open, its area is stored in the wrong unit, or a virtual line between two open-plan zones has turned into something that looks like a wall. The report checks three of these: Watertight space geometry on the Geometry page, and Qset room area plausibility and Virtual boundary consistency on the Consistency page.
Not every model needs spaces. Bridges, roads, tunnels, structural and installation models usually have none, and are not marked down for that. Whether an architectural building model has spaces at all is the Spaces check on the Structure page, explained in Spatial structure and containment.
Where you see it in the report
| Place | What it shows |
|---|---|
| Geometry page, check Watertight space geometry | How many spaces have a closed volume, for example 212/230. Buildings only. |
| Consistency page, check Qset room area plausibility | The average room area from the space quantity sets, in your units, for example 18.4 m² average per room. Shown when the file has spaces. |
| Consistency page, check Virtual boundary consistency and the cards Virtual boundaries | The number of virtual elements and what is wrong with them, broken down by kind of problem. |
| In short page, Is anything broken in the file? | A warning when the total floor area in the space quantities is less than half, or more than 1.1 times, the floor area measured from the geometry. |
| Capabilities page | Spaces present for Operations / FM, and Spaces present and Space boundaries present for Energy analysis. Both are draft rules. |
| Potential page | The action of each check that scores below 80, with the points it would add to Overall quality. |
Watertight space geometry
The audit builds the shape of every space and checks whether it is closed: a watertight volume, in which every edge is shared by exactly two faces and nothing is missing. A space with a gap, a missing ceiling face or loose surfaces is not watertight, and neither is a space whose shape cannot be built.
The score is the share of spaces with a shape that are watertight: 212 of 230 gives 92. The check has a weight of 0.5 and belongs to the Geometry dimension. It is scored for buildings, and only when at least one space could be built; files without spaces, or whose spaces have no shape, are not marked down here.
Why it matters: the volume of an open shape is undefined. Software that calculates room volumes, heated volume or air changes either refuses the space or calculates something meaningless, and an energy simulation built on it is wrong without saying so. The action in the report is Close space boundaries so volumes are watertight.
Qset room area plausibility
Floor areas of spaces are often taken straight from the file, from the quantity set Qto_SpaceBaseQuantities or a vendor equivalent. This check is a sanity check on those numbers: is the average room size anything like a room?
The audit reads one area per space from its quantity sets: GrossFloorArea, NetFloorArea, GrossArea or NetArea, or otherwise a quantity with “area” in its name, converted with the file’s units. Areas held only in property sets or authoring-tool parameters are not read. The total is divided by the number of spaces.
| Average area per space | Score | Usually means |
|---|---|---|
| Less than 2 m² | 15 | Areas in the wrong unit or scale, or most spaces without an area quantity |
| 2 to 2,000 m² | 100 | Plausible |
| More than 2,000 m² | 40 | Areas in the wrong unit, for example square millimetres declared as square metres |
| No space has an area quantity | not scored | The check advises exporting Qto_SpaceBaseQuantities |
The check has a weight of 0.75 and belongs to the Consistency dimension. Spaces without an area quantity still count in the number of spaces, so they pull the average down: export an area for every space, not only some. The check looks at the average, not at each room, so one wrong room among many correct ones will not show here; the quantity check compares quantities with the geometry object by object.
Virtual boundary consistency
Where two spaces meet without a wall, for example a kitchen open to a living room or two zones in an open-plan office, the boundary between them is drawn as a virtual element (IfcVirtualElement). It is a line or a surface that separates spaces, not a physical object. Software that recognises it as virtual leaves it out of quantities, structural and energy calculations; software that sees material or a body may treat it as a real partition.
The audit checks every virtual element for things it should not have:
- a solid 3D body;
- a material;
- a volume, weight or mass quantity with a value;
- physical properties: load-bearing set to true, or a value for fire rating, acoustic rating, thermal transmittance or combustible;
- space boundaries that use it but are not marked as virtual;
- no space boundary at all (an orphaned virtual element);
- openings cut into it or filling one;
- a type object.
Each problem counts once per virtual element, so one element with a material and a solid body counts twice; a space boundary that is not marked as virtual counts once for every such boundary. The score is 100 minus the number of problems as a percentage of the number of virtual elements, down to a minimum of 20. The check has a weight of 0.75, belongs to the Consistency dimension, and is not scored when the file has no virtual elements. The action in the report is Remove materials, solid geometry, or physical properties from virtual separators and ensure space boundaries are set to VIRTUAL.
The checks at a glance
| Check | Score | Weight |
|---|---|---|
| Spaces (Structure) | 100 with spaces, 0 without, for architectural building models; information only for other buildings. See Spatial structure and containment. | 1 |
| Watertight space geometry (Geometry) | The share of spaces with a closed volume. Buildings only. | 0.5 |
| Qset room area plausibility (Consistency) | 100 for an average of 2 to 2,000 m² per space, 15 below, 40 above. | 0.75 |
| Virtual boundary consistency (Consistency) | 100 minus problems as a share of virtual elements, at least 20. | 0.75 |
Why it matters to an owner
- Floor areas carry money. Rent, service charges, cleaning contracts and space planning are priced per square metre. An area in the wrong unit is not a rounding error; it is a factor of a million.
- Energy and comfort start from spaces. Energy calculations need closed volumes and proper space boundaries; an open shape or a virtual line with a material gives a model that runs and a result that is wrong.
- Facility management uses spaces as addresses. Assets, work orders and inspections are linked to rooms. Spaces without areas or with broken shapes make the room list unreliable from day one.
Frequently asked questions
My bridge has no spaces. Is that a problem?
No. Spaces are only expected in architectural building models: only such a model is marked down for having none, by the Spaces check. The checks on the spaces themselves are not scored for a file without spaces.
My room areas are in a property set, not a quantity set. Why does the check say there are none?
The check reads areas from quantity sets only, because those are the standard place for measured quantities. Exporting Qto_SpaceBaseQuantities makes the areas readable for every tool, not only this check.
Does a space have to be watertight to be useful?
For a room list and a floor area, not always. For volumes, energy analysis and anything that needs to know what is inside the room, yes.