> 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/65r-sensor-user-guide/65r-sensor/data-offload/file-structure.md).
# File Structure
## Introduction
The 65R uses an internal SSD to store the captured data. This article will describe the file storage structure.
***
## File Structure
The 65R file structure is as follows:
**data > snapshots > session folders > rgb > 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 65R 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 is a sub folder labeled rgb. This folder contains the the imagery.
---
# 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://support.senterasensors.com/home/65r-sensor-user-guide/65r-sensor/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 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.
