> For the complete documentation index, see [llms.txt](https://docs.segments.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.segments.ai/how-to-annotate/label-3d-point-clouds/merged-point-cloud-view-for-static-objects.md).

# Merged point cloud view (for static objects)

When labeling a static object in 3D point cloud sequences, a single frame might not show the object in full detail. It can thus be difficult to assess the full dimensions of an object.

To solve this issue, you can toggle a merged point cloud view.

{% embed url="<https://youtu.be/om5w69OErVs?t=17>" %}
This video shows how you can use the merged point cloud view to draw a perfect cuboid around a static object.
{% endembed %}

## Toggle the merged point cloud view

Click on the merged point cloud icon (![](https://1553794111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHczBG7NHgAtEe4ql1rXH%2Fuploads%2Fdp0tJ6lLqCHrCswfRQYR%2Fimage.png?alt=media\&token=d9757adc-9e1b-45da-9be1-531f4b910cad)) in the right toolbar to toggle the merged point cloud view on/off.

{% hint style="info" %}
Tip: [use your GPU in Chrome](https://segmentsai.notion.site/How-to-use-your-GPU-in-Chrome-2b95e19fb77c456c87f798013769a98a) to make sure the 3D point cloud interface runs smoothly.
{% endhint %}


---

# 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.segments.ai/how-to-annotate/label-3d-point-clouds/merged-point-cloud-view-for-static-objects.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.