Commands  ›  Architecture / Floors  ›  Architecture Add Floor Above Selected Level From Existing Floor Footprint

Architecture Add Floor Above Selected Level From Existing Floor Footprint

Architecture / Floors writes to model Public API · not yet exposed

Coming soon

Before you run this

One level selected. A floor exists on the level immediately below. Project default floor type defined for the new level (or fallback type configured).

After it runs

One new Floor element placed on the selected level following the boundary of the floor below; type set to the project default; offset zero.

When to use this

Don't use this when

Schemes with set-backs / variable footprints, levels that need mass-modelling, or projects where structural floors are managed in the structural model.

Decision flow

1. Read the selected level and find the floor on the level immediately below.
2. Read the lower floor's boundary curve loop.
3. Pick the floor type from the project default for this level, falling back to the lower floor's type.
4. Create a new Floor on the selected level following the same boundary in one Transaction.
5. Report the new floor's id, level and area.

What you'll see in the chat

on start
I'll copy the floor below onto that level now.
thinking
Reading the lower floor's boundary and the project floor type for the selected level.
on success
Done — floor placed on {level} ({area} m²) using {floor_type}.
on failure
Couldn't copy the floor up: {error}.

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/architecture_add_floor_above_selected_level_from_existing_floor_footprint
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

copy floor up · stack floors · repeat floor · level setup · multi-storey footprint

PillarArchitecture / Floors