> For the complete documentation index, see [llms.txt](https://docs.hamina.com/hamina/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hamina.com/hamina/guides/maps-floors.md).
# Managing Maps and Floors
Learn how to switch, rename, and manipulate maps in Hamina Network Planner.
## Adding Maps
Maps can be added to Hamina in the **Floor** drop-down menu at the top. Click the **Floor** drop-down menu, and click the **Add a floor** button to add additional maps.
{% hint style="info" %}
Until floors are added to a building, maps don't have any relationship with each other. Instead, they simply exist in the same project.
{% endhint %}
## Renaming Maps
To rename a map, click on the **Floor** drop-down, point to the floor, and click **Rename**.
### Map Sorting
In the Floor dropdown menu, maps are sorted numerically/alphabetically in *descending* (largest to smallest) order, which causes the floors to be sorted logically in how they would stack up in a building, for example:
* Floor 4
* Floor 3
* Floor 2
* Floor 1
It is possible to further organize maps with additional names, such as the names of buildings.
{% hint style="info" %}
Note: Only one multi-floor building is supported per project. If you need to design for more than one multi-floor building, then we recommend creating a unique project for each building.
{% endhint %}
#### Map Sorting for Buildings
When floors are added to a building, they are sorted in the map dropdown based on their order in the building, which can override the default map sorting. To learn more, see [Align Floors](/hamina/simulation/align-floors.md).
Floor 1 is erroneously placed above Floor 2, to illustrate how buildings override default map sorting.
## Cropping Maps
Hamina Network Planner supports non-destructive map cropping, so you can change the cropping of the map without modifying the original floor plan image. When a crop is applied, it can be changed back at any time.
Cropping a vector-based map image (such as a PDF or CAD file) will also automatically resample the map. For example, if the background map is a very large warehouse with lots of white space, Hamina Network Planner might accidentally crush the resolution to fit the image within the maximum map resolution (16000x16000 pixels for PDFs, or 8000x8000 pixels for CAD files, which don't yet support the higher resolution). Applying a crop to remove whitespace will cause the image to resample, which can dramatically improve or completely fix the resolution of the map.
1. In the **Maps/Floors** menu, point to the desired map and select **Adjust**.
2. The **Adjust floor plan image** pane will appear on the right. Click the **Crop** button.
3. On the map, either click and drag to create a rectangle, or use the handles on the corners of the crop area to select the desired area to crop.
4. At the top center of the select crop area, click the **Apply crop area** button.
## Ceiling Heights
For each map or floor, there is a ceiling height that is set automatically depending on the circumstances of the project. Walls and attenuating objects set to `Ceiling Height` will use this value.
The ceiling height is set by:
1. The minimum ceiling height, which is determined by the project's **Environment Type**:
1. **Warehouse**: 10 meters (\~33 feet)
2. **Retail**: 4 meters (\~13 feet)
3. **Data Center**: 4.5 meters (\~14 feet)
4. **Airport**: 6 meters (\~20 feet)
5. **Convention Center**: 8 meters (\~26 feet)
6. **Factory**: 6 meters (\~20 feet)
7. **Shopping Mall:** 5 meters (\~16 feet)
8. **All other environments**: 2.5 meters (8 feet)
2. Pushed upwards by the highest access point, wall, or attenuating object on the map.
Alternatively, the ceiling height can be defined by adding the map to a building, at which point it becomes a floor, and receives the ceiling height setting from the [Align Floors](/hamina/simulation/align-floors.md) tool.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hamina.com/hamina/guides/maps-floors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
