> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/create-a-floor.md).

# Create a Floor

## Create a Floor

A floor is created as an asset in **Assets Hub** and configured in **Map & storey**.

However, several special features must be considered:

1. Select **Building Storey** as the asset type.
2. Assign the floor to its building through **Parent location**.
3. Configure its geographic position, floor-plan image, and floor number.

Before you begin, make sure the building asset already exists. The following sections explain the floor setup.

### Create a "Floor" Asset

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-e7bbbc09cee25704ea42a4ebf30a7009b84f349a%2Fstorey-create-asset.png?alt=media" alt="Add Asset dialog populated with the Building Storey type, GAI, asset name, and description."><figcaption></figcaption></figure></div>

1. Open **Assets Hub** **\[A]**.
2. Click **Asset** **\[B]**.\
   ▷ The **Add Asset** dialog opens.
3. Select **Building Storey** under **Asset Type** **\[C]**.
4. Enter a unique **GAI** **\[D]**.
5. Enter the **Asset name** **\[E]**.
6. Enter a **Description** **\[F]**.
7. Optional: Enter **Associated ID(s)**.
8. Optional: Select **Tags**.
9. Click **Add** **\[G]**.\
   ▷ The floor asset is created.

### Assign a Floor to a Building

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-3e9b7d3e45e8cd1bc763f011997ddb928c05d084%2Fstorey-parent-location.png?alt=media" alt="Floor asset information with the building selected as Parent location and the Show/edit location control below it."><figcaption></figcaption></figure></div>

1. Open the floor asset in **Assets Hub**.
2. Open its information for editing.
3. Select the building under **Parent location** **\[H]**.
4. Click **Save**.\
   ◈ Scroll down in the information form if the button is outside the visible area.

### Add a Floor Plan

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-55f5851971d5675868a31538940a26e7f03493a2%2Fstorey-settings.png?alt=media" alt="Map placement form with Asset is a storey enabled, an uploaded floor-plan image, and Storey floor set to 2."><figcaption></figcaption></figure></div>

1. Open the floor asset's information for editing.
2. Click **Show/edit location** **\[I]**.\
   ▷ **Map** **\[J]** opens the asset's location configuration.
3. Enable **Assign Placement** **\[K]**.
4. Click the floor's geographic position on the map.
5. Enable **Asset is a storey** **\[L]**.
6. Upload the floor plan under **Storey scheme** **\[M]**.
7. Enter the floor number under **Storey floor** **\[N]**.
8. Click **Save** **\[O]**.\
   ▷ The floor configuration is saved and its storey icon appears in the asset tree.

{% hint style="info" %}
The upload accepts JPG, JPEG, PNG, and SVG images up to 50 MB.
{% endhint %}

You can now [open the floor](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor.md#open-a-floor) and [place assets on its plan](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/placing-assets-on-a-floor.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/create-a-floor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
