> For the complete documentation index, see [llms.txt](https://carare.gitbook.io/share-3d-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carare.gitbook.io/share-3d-guidelines/3d-process/modelling.md).

# Post-processing

Post-processing is required after data capture to transform the raw datasets into 3D models. The work involves a sequence of processing steps that can include:

* Scaling data to reference points&#x20;
* Aligning datasets to bring them together in the same 3D coordinate system&#x20;
* Meshing (to transform data into a 3D mesh model)&#x20;
* Editing holes or topological errors in the mesh&#x20;
* Texturing (for example by projecting images on the 3D geometry)

Post-processing also allows the creation of multiple 3D models from the same data for different applications with different levels of detail or other criteria. The results include:

* Formats suitable for publishing on the web&#x20;
* Formats for 3D printing&#x20;
* Formats suitable for import into Virtual or Augmented reality applications&#x20;
* Preservation formats


---

# 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://carare.gitbook.io/share-3d-guidelines/3d-process/modelling.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.
