> 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/gryfn-legacy-hardware/gryfn-sonoran/user-manual/data-management.md).

# Data Management

## 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 per 1-3 minutes (depending on configuration)</td><td>~1.5MB per minute</td><td>All file types should be .T04. If there is a .T0C, the sensor was not shut down properly. This file may be corrupt, but users can attempt to rename the extension to .T04 and process.</td></tr><tr><td>LiDAR</td><td>1 per minute</td><td>~117MB 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, pps, and settings files all exist.</td></tr><tr><td>SWIR</td><td>Mission time (s) ÷ Frame Period value ≈ number of data cubes</td><td>SWIR data should capture several GB of data for even short flights</td><td>Check that frameindex, imu_gps, pps, and settings files all exist.</td></tr><tr><td>Thermal*</td><td>1 image per 1.5 seconds</td><td>~200-300kb per image</td><td></td></tr></tbody></table>