Layer Stacks

‍Layer Stacks

This guide explains what a layer stack is, how it is structured, what each component does, and how to build one correctly in spaciv. Use it alongside the video and slides as a step-by-step reference.

1. What Is a Layer Stack?

A layer stack is two or more layers combined in a specific order. When you stack them, spaciv creates a composite layer: a single merged view that brings together all the data from every layer in the stack.

The composite layer is what you use in your project. It reflects your data as configured by all the layers in the stack, without changing any of the original sources.

How the composite layer works

When two object layers are stacked, every object from both layers appears in the composite layer. All property columns from both layers are included. If an object does not have a value for a property that belongs to the other layer, that field simply stays empty.

Nothing is changed or lost. The composite layer is purely additive.

Note: In practice, a layer stack contains more than just object layers. The full structure is covered in Section 2.

2. The Full Layer Stack Structure

A complete layer stack in spaciv has five components, always arranged in the same order from bottom to top.

1. Object Layers (bottom)

 Your imported data files always sit at the very bottom. These are your employee list, room list, or any other data you have uploaded. Everything else in the stack references these layers.

A typical stack includes two object layers: your employee data and your room data.

2. Space Modules

 Above your object layers sits the Space Modules layer. This is a system preset that comes built into spaciv. You do not need to create it yourself.

Space modules are the standard workplace building blocks: focus desks, collaboration areas, meeting rooms, social spaces, and so on. Each module has a defined size and function. This layer gives spaciv a shared vocabulary for what different workspace types look like.

3. Modification Layer

 Above the space modules sits your modification layer. This is where your scenario lives. It selects specific objects and changes their properties, so the composite layer reflects a planned or hypothetical change rather than the current state.

In our project, this is the Move 2030 layer created in Lesson 2.

4. Baseline Needs

 Above the modification layer is the Baseline Needs layer. This is another system preset. It contains benchmark data for how much space different types of employees typically require, based on how they work and what activities they do.

It provides the reference values that spaciv uses when calculating space requirements.

5. Space Rules (top)

 The Space Rules layer always sits at the very top. It is the calculation model that drives the entire stack.

A space rule defines how space should be allocated based on a specific workplace concept. spaciv includes four preset concepts:

• Classic — traditional assigned desking. One desk per person, enclosed offices, structured meeting rooms.
• Open Space — open plan layouts with shared desks and fewer enclosed spaces.
• Hybrid — flexible working model. Desk count is reduced because not everyone is in the office every day.
• Activity Based Working (ABW) — no assigned desks. Employees choose from a variety of space types depending on their task.

Each concept uses different ratios of workplace modules. Swapping the space rule immediately changes the calculated space output, without touching any of the data below it.

 Note: You can also customise a space rule to match your organisation's specific setup, or create a new one from scratch.

3. Why Layer Order Matters

The order of layers in a stack is not flexible. Layers higher in the stack reference the layers below them. If a layer is in the wrong position, it will either reference data that is not yet available or produce incorrect calculations.

The rule is simple: base data at the bottom, calculation logic at the top.

• Bottom → Object layers (your files)
• Above that → Space Modules (system preset)
• Above that → Modification layer (your scenario)
• Above that → Baseline Needs (system preset)
• Top → Space Rules (workplace concept and calculation model)

Note: Always check the layer order before saving. If the stack produces unexpected results, the order is the first thing to verify.

4. Building Your Layer Stack

Here is how to build the Move 2030 layer stack from this lesson.

Create the stack

1. In the sidebar, navigate to Layer Stacks under your account.
2. Click Add New. Name it Move 2030 and confirm.

Add layers in order, bottom to top

1. Click Add Layer. Select Object Layer and choose your Employee List.
2. Add a second layer. Select Object Layer and choose your Room List.
3. Add the Space Modules preset layer. You will find this in the system presets list.
4. Add your Move 2030 modification layer.
5. Add the Baseline Needs preset layer.
6. Add the Space Rules layer. Select the workplace concept that matches your project.

Check the order and save

1. Review the layer order from bottom to top. It should follow the sequence above exactly.
2. If any layer is in the wrong position, drag and drop it into the correct place.
3. Add a short description so your team knows what this stack is modelling, then click Save.

Note: Preset layer stacks are also available in spaciv. These include the Baseline Needs stack and others built on spaciv benchmark data. You can explore them, use them as a starting point, and edit them to fit your own data.

5. Summary

• A layer stack combines multiple layers into a composite layer that merges all data from each source
• The correct order from bottom to top is: object layers, space modules, modification layer, baseline needs, space rules
• Space rules are the calculation model at the top of the stack. They define the workplace concept and drive all space calculations
• Layer order matters. Layers at the top reference layers below them. Base data must always sit at the bottom