> 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/english-v14/documentation/karte-und-stockwerk.md).

# Map and floor

The options Map and Floor allow you to place assets geographically.

Companies with a large real estate portfolio or facility management providers usually only have building information available in tabular form.

Keeping a complete overview of data, conditions, and locations is very challenging. With Eliona, the entire real estate portfolio can be displayed on a map. In addition, 2D and 3D floor plans can be integrated into the map and linked with specific building data. This ensures complete control of all infrastructures.

In addition to the quick overview of all building-specific data, room conditions can also be monitored and controlled via the map or floor plans.

Example: You own various systems in different buildings. You place the assets of your system on the map and link different floor plans in your buildings. You now have an overview of the locations in which your system components are located. Using the floor plans, you can localize the assets in even greater detail and view their data.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/H7t12UWd6B1E1Kf7Gv0z/0B238A53-F7E8-482B-9541-82F34388AE14.png" alt=""><figcaption><p>Fig. 1 – The map</p></figcaption></figure></div>

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/UtlOyIIPxB0kRGwsHWco/218AA8A7-2FF8-4772-9698-85E018106741.png" alt=""><figcaption><p>Fig. 2 – The floor</p></figcaption></figure></div>


---

# 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/english-v14/documentation/karte-und-stockwerk.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.
