Starting point: a tall building and a cramped screen
The InnerWeb map editor lets you describe a site as a set of buildings and their floors. In a building with two or three levels, the floor selector bar fits on screen without any trouble. The problem starts with buildings that have a dozen or several dozen levels: a tall automated warehouse, a multi-storey car park next to the plant, a technology tower.
This is a test scenario run on the staging environment, not a description of a deployment at a customer. The map administrator adds a building with 32 floors and checks whether an ordinary user, for example a shift supervisor or a dispatcher, can reach any level without scrolling the whole page and without layout errors.
The test also matters to the integrator who prices a project before the site visit. If the selector behaves predictably at 32 levels, the offer does not need to reserve interface limits for tall buildings.
How the floor selector works
The selector shows buttons only for a building with at least two floors. A single-level building does not get an unnecessary bar. The labels in the Polish version are P for the ground floor, then 1, 2 and the following numbers, so the user immediately recognises the level they are on.
Above 12 floors the selector switches to window mode: 12 buttons are visible at once, with arrows above and below them for moving up and down. The window can also be moved with the mouse wheel. As a result the bar has a constant height whether the building has 13 or 32 levels.
How many window positions for 32 levels
With 32 floors and a 12-button window, you need to look at least three window positions to see every level: 32 divided by 12 gives 2.67, which means three screens of buttons. In practice the user moves the window one level at a time or several levels at once with the wheel, so the number of clicks depends on how far the target is from the starting level.
Visible buttons vs. building levels
- Building levels
- Visible buttons
Step-by-step test on staging
It is worth planning the test as a short 15 to 20 minute session with one person on the map administrator side and one on the end user side. The steps below give a repeatable result that can be attached to the acceptance protocol.
- Add a building in the map editor and give it an outline and a height, because only an area with an outline and a height is treated as a building with volume.
- Set the number of floors to 32 and name the levels according to the agreed convention.
- Open the building with a double click and check whether the floor bar fits in the browser window at a typical laptop resolution.
- Scroll the window with the arrows from P to 32, then back down, and record whether every button responds.
- Repeat the scrolling with the mouse wheel and check that the page underneath the bar does not scroll with it.
- Select level 20 and add a zone or a risk on it, to confirm that the data is assigned to the correct floor.
- Return to the site view and check that the building name is visible from zoom level 16.
What was observed and how to read it
The most important result: the bar does not grow with the number of levels. Whether the building has 13, 20 or 32 floors, the user sees the same 12 buttons, so the page layout stays stable and the buttons do not run off the screen.
The second conclusion concerns navigation: choosing a level far from the starting point takes several window moves. For an administrator who works every day on levels 25 to 32, it is more convenient to move the window once and stay in its lower range. For a dispatcher who responds to an event in an unfamiliar place, it helps to have the level description from the local naming convention at hand.
The third conclusion: a test on staging does not replace a trial with the target data. Only with the real number of zones, lines and risks on each level can you see whether the labels blend into one another.
Conclusions for designers of tall-building maps
The 12-button window solves the layout problem but not the problem of clarity. If the building has 32 levels and employees call them by names different from the numbers in the selector, the map will need translation. Agree with the shift supervisor whether you use numbers or technological names before anyone starts entering data.
When planning beacon coverage for such a building, remember the InnerWeb guideline: one beacon per 100 to 200 m2 inside a building. For a multi-level building the area of each level counts separately, so the number of devices grows with the number of floors, not with the footprint of the building.
The described trial concerns only the map interface. It does not prove location accuracy in a specific facility. That is assessed only after the beacons are installed and a walk-through with a phone has been done.
Checklist
Video
Frequently asked questions
From how many floors does the selector switch to window mode?
Above 12 floors. Up to 12, all buttons are visible at the same time; above that you see a window of 12 buttons with arrows.
Does the selector appear for a single-level building?
No. Buttons appear only for a building with at least two floors, so a simple facility does not get an unnecessary bar.
What labels does the user see in the Polish version?
P for the ground floor, then 1, 2 and the following numbers. The naming convention can be agreed with the users before data is entered.
Let's check your facility on the map
Book a short call: we will show the map editor on the example of a tall facility and discuss how to describe your levels.
Let's talk