> For the complete documentation index, see [llms.txt](https://docs.theiamarkerless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theiamarkerless.com/axiom-v2025/theia3d-documentation/data-formats/video-data.md).
# Video Data
### Video Data
Example structure of video data.
{% hint style="danger" %}
Video names must not contain accents, as these can cause errors during the Organize Videos process. Use only alphanumeric characters with space, hyphen (-), underscore (\_), or period (.) as delimiters. Avoid using commas (,) or semicolons (;).
{% endhint %}
The video data for a single trial must be contained in its own folder, and each video file must be in its own subfolder. The name of each subfolder must be the ID of the corresponding camera. There are no requirements on the structure of the names of the video files, but the names must be unique and videos must be .avi or .mp4 format. For example, the figure above shows video data for a walking trial collected using four cameras with IDs 21375, 21379, 21380, and 21381.
Organizing your videos in this format can be achieved using the [Organize Videos](/axiom-v2025/theia3d-documentation/theia3d-dropdown-menus/tools-menu/organize-videos.md) tool.
It is also best practice to keep the associated extrinsic calibration file nested within the trial folder and beside the camera ID folders. This can be achieved using the [Assign Calibration Files](/axiom-v2025/theia3d-documentation/theia3d-dropdown-menus/tools-menu/assign-calibration-files.md) tool.
---
# 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.theiamarkerless.com/axiom-v2025/theia3d-documentation/data-formats/video-data.md?ask=&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.
