> For the complete documentation index, see [llms.txt](https://gryfn.gitbook.io/gryfn-hardware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gryfn.gitbook.io/gryfn-hardware/support/gobi-user-manual/data-management.md).

# Data Management

{% hint style="warning" %}
When GOBI is powered indoors, GRYFN recommends pointing a small fan at the main exhaust vents to help keep thermals in check. GOBI maintains good temperatures in flight with sufficient airflow across the chassis, but can become quite hot when sitting powered in stagnant air for extended periods of time.
{% endhint %}

## Data Storage

A 500GB internal mSata Solid State Drive (SSD) is installed in the chassis. This internal device collects and stores VNIR Hyperspectral, LiDAR, and GNSS data. A 256GB SD Card is installed in the optional RGB frame camera for storing RGB images.

## Offloading Data

### Via GRYFN Processing Tool

<table><thead><tr><th width="113">STEP</th><th>ACTION</th></tr></thead><tbody><tr><td>1</td><td>Connect to chassis via Ethernet or WiFi</td></tr><tr><td>2</td><td>Open GRYFN Processing Tool</td></tr><tr><td>3</td><td>Open the <strong>Bundle Data</strong> tab</td></tr><tr><td>4</td><td>Under <strong>Download from Sensor</strong> click <strong>Query Sensor</strong></td></tr><tr><td>5</td><td>After a few seconds your GOBI chassis will appear, click on it</td></tr><tr><td>6</td><td>Click <strong>Create GRAW</strong></td></tr><tr><td>7</td><td>All available missions will appear</td></tr><tr><td>8</td><td>Select the mission you wish to download &#x26; bundle</td></tr><tr><td>9</td><td>Choose a save path</td></tr></tbody></table>

### Via FTP Service

First, connect to the GRYFN GOBI chassis via Ethernet. Then, in your FTP application of choice (WinSCP, Filezilla, etc.), to access LiDAR data, VNIR Hyperspectral data, and system logs, use the following session settings:

#### GRYFN Storage

| PARAMETER     | VALUE      |
| ------------- | ---------- |
| File Protocol | FTP        |
| Host Name     | 10.0.65.50 |
| Port Number   | 21         |
| User Name     | gryfn      |
| Password      | gryfn      |

#### SBG Internal Storage

| PARAMETER     | VALUE         |
| ------------- | ------------- |
| File Protocol | FTP           |
| Host Name     | 10.0.65.100   |
| Port Number   | 21            |
| User Name     | supervisor    |
| Password      | *no password* |

Files can be found in the following directories:

<table data-full-width="true"><thead><tr><th>DATA TYPE</th><th>DIRECTORY</th><th>FILE TYPES</th></tr></thead><tbody><tr><td>GNSS</td><td>/data/{mission_name}/gnss</td><td><strong>.00#</strong><br>     • Raw data file (where # is the session file, new session is made per UTC hour)<br><strong>.json</strong><br>     • System configuration file</td></tr><tr><td>LiDAR</td><td>/data/{mission_name}</td><td><strong>.pcap</strong><br>     • Raw LiDAR data packets<br><strong>.json</strong><br>     • System configuration fiel</td></tr><tr><td>VNIR</td><td>/data/{mission_name}/{collection_name}</td><td><p><strong>.hdr</strong><br>     • Hyperspectral data header file<br><strong>.bin</strong></p><p>     • Hyperspectral raw data file<br><strong>.txt</strong><br>     • Various frameIndex, settings, and other data files</p></td></tr><tr><td>System Log</td><td>/data/gryfn.log.{date}</td><td><strong>.log</strong></td></tr><tr><td>Frame Camera</td><td>Images are stored to the camera's SD Card</td><td><strong>.jpg</strong><br>     • Image files</td></tr><tr><td>GNSS Internal Data Logger</td><td>/dataLogger</td><td><strong>.00#</strong><br>     • Raw data file (where # is the session file, new session is made per UTC hour)<br><strong>.json</strong><br>     • System configuration file</td></tr></tbody></table>

### Data Confirmation

After the flight, or after data has been downloaded to your local device, check file counts and sizes against the nominal collection rates in the table below to ensure data has been captured properly.

<table data-full-width="true"><thead><tr><th width="157">SENSOR TYPE</th><th>FILE COUNT</th><th>FILE SIZE</th><th>NOTES</th></tr></thead><tbody><tr><td>GNSS-INS</td><td>1 file</td><td>~1.5MB per minute</td><td>A new file will be created if time rolls over the hour (clock time, not capture time).</td></tr><tr><td>LiDAR</td><td>1 per minute</td><td>~175MB per file</td><td>First &#x26; last file may be smaller<br>May be smaller if over low reflection object.</td></tr><tr><td>VNIR</td><td>Mission time (s) ÷ Frame Period value ≈ number of data cubes</td><td>VNIR data should capture several GB of data for even short flights</td><td>Check that frameindex, imu_gps, settings files all exist.</td></tr><tr><td>RGB</td><td>Image every 2s</td><td>~30 - 70MB per image</td><td>Check event log vs number of images</td></tr></tbody></table>

## Clearing Storage

### GNSS-INS, LiDAR, and VNIR

<table><thead><tr><th width="113">STEP</th><th>ACTION</th></tr></thead><tbody><tr><td>1</td><td>Connect to chassis via Ethernet or WiFi</td></tr><tr><td>2</td><td>Navigate to GOBI WebUI Data page</td></tr><tr><td>3</td><td>Locate mission for deletion and press Delete</td></tr></tbody></table>

{% hint style="warning" %}
Clear Mission button will delete GNSS data, LiDAR data, and VNIR data from 500GB internal storage. RGB data must be deleted from the SD card separately. Only remove data *inside* the DCIM folder.
{% endhint %}

### GNSS-INS Deletion from SBG Data Logger

SBG has its own internal data logger. Data is copied from SBG's data logger to GRYFN's internal storage upon mission completion.

<table><thead><tr><th width="113">STEP</th><th>ACTION</th></tr></thead><tbody><tr><td>1</td><td>Connect to chassis via Ethernet or WiFi</td></tr><tr><td>2</td><td>Navigate to GOBI WebUI Data page</td></tr><tr><td>3</td><td>Locate mission for deletion and press Delete</td></tr></tbody></table>


---

# 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://gryfn.gitbook.io/gryfn-hardware/support/gobi-user-manual/data-management.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.