> For the complete documentation index, see [llms.txt](https://docs-en.kivicube.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.kivicube.com/manual-old/resources-specification/image-tracking/3d-tracking.md).

# 3D Tracking

When a user wants to recognize a 3D object, there are generally two schemes, which are to perform alignment and conversion through 2D recognition. Or make it through real 3D recognition. However, the cost of 3D recognition projects is relatively high and can only be done through APP.

## 3D algorithm tracking

### AR access method

3D detection and  tracking is generally based on 3 modes: CAD recognition tracking, point cloud recognition tracking, SLAM and AI hybrid recognition tracking.

![](/files/-MF4eunPZfq0b1X_iw3s)

Please note here that identification and tracking are two different stages, please contact Miren Kiviman for specific details.

![](/files/-MF4f4A8M2jxYzXUSl8Y)

## 2D algorithm tracking

### AR access method

WebAR, WeChat link, WeChat applet, APP-AR

### Authoring identification map

In the WebAR scene, multiple recognition pictures can be added to the cloud tracking scene. After any recognition picture is successfully recognized, the current scene can be opened.

![](/files/-MF4f_bCuG9zBTQHZtkA)

This recognition method requires multiple identification maps to be taken for the scene to be recognized. According to the characteristics of the location, angle changes, day and night changes, and light changes must be taken. Therefore, if it is an outdoor scene, a large number of photos should be taken.

![](/files/-MF4fz-BsJ6vXQJ5ZKaC)

## Scope of application 

Stone steles, billboards, reliefs, some sculptures, some exhibits This method can only identify and cannot track real-time images. If you need the ability to track, you still have to use APP to make it.


---

# 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://docs-en.kivicube.com/manual-old/resources-specification/image-tracking/3d-tracking.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.