> For the complete documentation index, see [llms.txt](https://annotationdocs.telusinternational.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annotationdocs.telusinternational.com/3d-point-cloud-annotation.md).

# 3D Point Cloud Annotation

In this section, We have added some examples to understand how to create an 3D point cloud annotation job and export the results once the job has been labeled.

There are two types of point cloud annotation tasks supported in GT Studio:

1. **3D Bounding Box:** 3D bounding boxes on point clouds + projected cuboids on image
2. **2D-3D Linking:** 3D bounding boxes on point clouds + linked 2D bounding boxes on images

GT Studio supports multi-sensor setups, i.e. where you have a point cloud along with images from multiple cameras. If you provide calibration information (poses of each sensor and camera intrinsic), the tool will automatically project annotations from the 3D space to the cameras.

{% hint style="warning" %}
We support 3D point cloud annotations in our enterprise plan as a fully managed service offering. Please [contact us](https://playment.io/sign-up) if you are interested in 3D point cloud annotations.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://annotationdocs.telusinternational.com/3d-point-cloud-annotation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.