> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor.md).

# 3D Multi-Sensor Fusion Labeling Editor

3D Multi-Sensor Fusion Tool allows labeling of point clouds. The Tool supports multiple features and interactions to support precise labelling.

View [key features](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features.md).

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2F2Wy7Qjk03Hw8sifR7rwF%2Fimage.png?alt=media&amp;token=c3042067-9477-4f6f-9752-bfb652785a98" alt=""><figcaption></figcaption></figure>

* Datasets of multiple sensors: Images, LiDAR, RaDar
* Sensor fusion: Labelling across sensors simultaneously
* Feature to label sequential datasets
* Multiple [Drawing Tools](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools.md) to label points in 3D & 2D datasets:
  * [Cuboid](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools/cuboid.md)
  * [3D Polygon](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools/3d-polygon.md)
  * [Brush Sphere](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools/brush.md)
  * [3D Polyline](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools/3d-polyline.md)
  * [2D Polygon](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools/2d-polygon.md)
  * [2D Bbox or Rectangle](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools/2d-bbox-or-rectangle.md)
  * [2D Polyline](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools/2d-polyline.md)

## **Recommended System Configuration** <a href="#system-configuration" id="system-configuration"></a>

* CPU: intel i7 13th gen or higher
* 16GB of RAM is the amount of memory for speed and smooth functioning
* 8 GB GPU Card for rendering
  * GPU: Nvidia (8gb memory or higher)
* Operating System - Mac/ Windows
* Supported Browser - Chrome

## Annotation Tool Guide Direct link:

* [Tool Layout](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/tool-layout.md)
* [Drawing Tools](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/drawing-tools.md)
* [Tool Shortcuts](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/tool-shortcuts.md)
* [Key Features](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features.md)


---

# 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.imerit.net/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor.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.