> 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.md). # Floor

Fig. 1 – The floor overview with various assets.
Assets in the form of points and polygons are visible on the floor.

## Overview The "Floors" function is closely related to the [-> "Map"](/collection/platform/map-and-floor/map.md) function. In the "Map" function, assets were placed on an interactive map. In the "Floors" function, on the other hand, assets are placed on a static floor plan. ## Open a Floor To open a floor, proceed as follows:

1. Click on **Map \[A]** 2. In the **sidebar \[B]**, navigate to the floor you want to open.\ ◈ Floors are marked with the symbol **\[C]**. Assets without this symbol are not floors. 3. Click on the symbol **\[C]**\ ▷ The floor overview (see Fig. 1) opens ## Floor Plans Floor plans are static images. In contrast to the interactive map, floor plans cannot be rotated, zoomed, etc. Instead, you upload an image from your computer and place your assets on this image. Theoretically, you can use any image as a floor plan. Floor plans or renderings of 3D models are particularly suitable (see Fig. 1). ### Polygons vs. Points On floors, you can display assets in 2 different forms: * Points * Polygons

Fig. 2 – Left: Assets as points, Right: Assets as polygons
A two-dimensional floor plan serves as the floor plan

#### Points Points correspond to the icons on the map. They are particularly suitable for displaying assets such as sensors, controls, etc. #### Polygons With the "Polygon" option, assets are not displayed as points but as colored areas. Polygons are particularly well suited for displaying rooms. Polygons are only available in the "Floors" function. In Figure 2, on the left side, assets are displayed as points. On the right side, assets are displayed as polygons. The shape and color of the polygons can be customized. You can set for each individual asset on a floor whether this asset should be displayed as a point or as a polygon. Both points and polygons can be present on a floor at the same time. --- # 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.md?ask=&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.