# Value mapping in Eliona
Value mapping makes it possible to translate raw data (e.g. numeric or boolean values) into meaningful colors, texts, or categories. This function is used to present information more clearly visually—for example in widgets, floors, or attributes.
## Value mapping for attributes
Value mapping for attributes automatically translates numeric values into descriptive texts. These texts can be displayed in many places in Eliona—for example in Smartview, in widgets, or in the detail view of an asset—and help present technical measurements in an understandable way.
### Purpose
Value mapping in *Eliona* translates numeric values of an attribute automatically into descriptive texts. This representation makes technical measurements easier to understand and simplifies interpretation in everyday use. The texts appear, for example:
* in the *Smartview*,
* in widgets,
* in the detail view of an asset.
The configuration is done either directly in the attribute or centrally via the[ -> Asset Modeling](https://docs.buildings.ability.abb/collection/english-v14/documentation/assets/asset-modeling-create-templates/create-a-new-template).
### Configuration
In **\[A]** several mapping fields can be added.
A mapping consists of pairs of **threshold value → result text**:
* **\[B]** Left field: The threshold value that serves as the upper limit for a value range
* **\[C]** Right field: The text that should be displayed when the measured value is below the associated threshold value
The rule is:
> All values that are **smaller** than the defined threshold value are assigned to the respective text.
**Note on order**\
The entries do not have to be sorted manually— *Eliona* interprets the mapping list correctly internally, from **highest to lowest threshold value** . The order of the input rows is therefore **not decisive** for the logic, but it does help with clarity during configuration.
### Example evaluation
Given the following configuration:
| Threshold | Result |
| --------- | ---------------- |
| 100 | Critical |
| 50 | Warning |
| 10 | Normal operation |
**Evaluation:**
* A value of **7** → Normal operation
* A value of **30** → *Warning*
* A value of **75** →Critical
* A value of **99.9** → Critical
* A value of **101 or more** → *No mapping*, the original value is displayed (if no higher threshold value is defined)
#### Notes
* The entries should be defined without gaps if every value is to be assigned a text.
* If no mapping applies, the original value is displayed.
***
## Value mapping in widgets
In widgets, a **Value mapping** can be used to interpret numeric data both **visually (color)** and **in terms of content (text)** . This assignment improves the readability of values and supports faster assessment of the state.
### Purpose
The mapping enables a clear classification of numerical values into categories—for example “Normal operation,” “Warning,” or “Critical.” In addition, each status can be given its own color, which is immediately visible in the display (e.g. progress bar or number field).
### Use case
#### Visualizing door status with value mapping
This mapping assigns the text *Locked* to all values ≤ 0, in brown display, while values up to 1000 are shown with *Unlocked* and green color. In practice, this means that:
* Sensor values such as `0` → *Locked*
* Sensor values `1` to `100` → *Unlocked*
{% hint style="info" %}
The mapping can be extended as needed by clicking **“Add mapping”** . Make sure that the value ranges are covered without gaps if every possible value is to be assigned.
{% endhint %}
### Display in the widget
In a widget, e.g. in the overview of a building, the following then appears directly visible for each door (front or back entrance):
* **Text**: *Locked* or *Unlocked*
* **Color**: Visual highlighting appropriate to the state
***
## **Value mapping in the floor (POIs and polygons)**
In the module *floor* areas of a digital plan—such as **Polygons** or **POIs** —can be automatically color-coded depending on the current attribute value. This is done via a **Value mapping**in which numeric values are assigned to specific **Colors** . The color visualization supports quick recognition of states directly in the spatial context.
### **Purpose**
With this function, states or measurements can be displayed directly in the context of a floor plan or building area. The color coding helps to recognize critical situations more quickly or to visually confirm normal operating states.
Examples:
* Mark temperature ranges in production facilities with colors
* Highlight power consumption of individual devices
* Clearly display door or window status
### **Configuration**
The configuration is done directly in the POI or polygon editor in the floor. Under the section *Value mapping* you can define value thresholds, each assigned a color:
* **Threshold value:** Defines the upper limit of a value range
* **Color:** Color applied when the measured value is less than or equal to the threshold value
### **Example configuration**
This configuration means:
* Values less than or equal to 90 → **Green**
* Values less than or equal to 93 → **Yellow**
* Values less than or equal to 10000 → **Red**
#### **Notes**
* Color mappings apply exclusively to numeric data.
* The color display does not replace numeric values, but complements them visually.
* If no suitable threshold value is found, the selected **default color** displayed
.png)
