> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/6x-series-sensors-user-guide/6x-series-sensors/data-offload/file-structure.md).
# File Structure
6X Series Sensors File Structure
## Introduction
The 6X uses an internal SSD to store the captured data. This article will describe the file storage structure.
***
## File Structure
The 6X file structure is as follows:
**data > snapshots > session folders > data sub-folders (rgb, NIR, Red Edge, etc) > image files**
The session folders are labeled as YYYY-MM-DD\_HH-MM-SS. Where YYYY-MM-DD is the date that the imagery was collected on, and HH-MM-SS is the UTC time that the session folder created at (when the 6X status lights turned green).
{% hint style="info" %}
If the 6X is power cycled between flights over a single area, there will be a session folder for each power up and session start of the camera. i.e. the imagery will be split between each folder.
{% endhint %}
Inside of each session folder there are 6 sub-folders. These sub-folders contain the imagery from each individual lens/channel of the 6X.
The folders are labeled based on the lens filter (Blue, Green, Red, Red Edge, NIR, RGB, etc). The center wavelength and filter width are also displayed.
Inside of each sub-folder the imagery that corresponds to the folder will be found.
***
---
# 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://support.senterasensors.com/home/6x-series-sensors-user-guide/6x-series-sensors/data-offload/file-structure.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.
