> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/dashboard-builder/components/image.md).

# Image

Building Digital Twins with Raster Images and SVGs

### Raster Image mode

In raster image mode, individual POIs can be mapped onto an image.

### SVG mode

In SVG mapping mode, you can map device data directly to specific file layers in addition to custom Points of Interest (POIs). This mode is ideal if you already have a pre-processed SVG file (such as a floor plan or building layout).

#### File Structure Requirements

To ensure akenza correctly identifies your interactive layers, your SVG file must be structured using specific group (`<g>`) IDs. Use the following template as a guide:

```
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
    ...
    <g id="viewer">
    <g id="assets" fill="none">
      <path id="Floor2.Room1" d="" />
     ...
    </g>
  </g>
</svg>
```

#### How Device Mapping Works

* akenza automatically parses the distinct layers defined within the SVG.
* You can map devices to SVG layers based on static information, such as custom fields or device identifiers (e.g., matching the asset `id` in the SVG to a device name).
* Once mapped, devices can be filtered by tags to create partial views based on specific use cases (e.g., displaying only *desks* or only *meeting rooms*).


---

# 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.akenza.io/dashboard-builder/components/image.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.