> 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/key-features/jump-to.md).

# Jump To

Navigate instantly to a specific location in the point cloud using the JumpTo feature. Enter the coordinates provided in validation messages to jump directly to cuboid errors or relevant areas.

{% hint style="info" icon="lightbulb-on" %}
Coordinate sharing ensures everyone lands on the exact same spot for consistent reviews.
{% endhint %}

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FIfqP0i2AHNiUTGoLqXyH%2FJumpTo.gif?alt=media&amp;token=86d21403-7f28-4791-9fa0-b54b186e9985" alt=""><figcaption></figcaption></figure>

***

## Benefits

* Saves time searching for specific objects or areas.
* Ideal for QA workflows, supervisor review, or debugging alongside the Validation Report.
* Makes collaboration easier—share coordinate values to guide teammates to the same spot.

***

## Steps to use Jump

{% stepper %}
{% step %}

#### Open the Jump To panel

Press CTRL + J to open the coordinate input panel.
{% endstep %}

{% step %}

#### Enter coordinates

Enter the X, Y, and Z coordinates. Use the Tab key to move between fields.
{% endstep %}

{% step %}

#### Jump to location

Press Enter to jump to the location.
{% endstep %}
{% endstepper %}

A green dot will mark the exact point in the point cloud.

### Using Jump To with Validation Reports

When a validation report is generated and includes warnings or errors tied to specific coordinates, users can instantly navigate to those exact locations using the Jump To feature. This allows for quick review and resolution of issues identified during validation.


---

# 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/key-features/jump-to.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.