> For the complete documentation index, see [llms.txt](https://gryfn.gitbook.io/gryfn-operations/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-operations/operations/flight-planning/flight-planning-calculator.md).

# Flight Planning Calculator

{% file src="/files/WUdAddGkbl7KTLW1wGiZ" %}

GRYFN's Flight Planning Calculator allows users to calculate data characteristics from flight parameters. By inputting a flight altitude, speed, and spacing in the user-defined boxes, our calculator will display the corresponding ground sampling distance (GSD), overlap percentage, and other relevant characteristics. While the resulting values in the spreadsheet are color coded based on processing and product viability, the better resolution and overlap percentages, the better your products will be.

<figure><img src="/files/ifuSVH9pHEUD9YWQGfTv" alt=""><figcaption><p>Example Flight Calculator Setup (GRYFN)</p></figcaption></figure>

## Standard Parameters

### Line-Scan Hyperspectral

Line-scan hyperpsectral sensors typically do not require much overlap between adjacent flight lines (sidelap). Due to the nature of these sensors, data is layered on top of each other in the orthomosaic process. GRYFN recommends a minimum of 30% sidelap, this percentage should account for instability in aircraft roll.

### LiDAR Sensors

LiDAR sensors can create point clouds with very little overlapping information between adjacent flight lines. Due to the restrictions from other sensors, LiDAR is typically well above acceptable ranges of sidelap. GRYFN recommends a minimum of 30% sidelap for LiDAR sensors.&#x20;

Point density for LiDAR sensors will vary based on flight speed, distance to object, and sidelap percentage. To increase point density:

* Fly slower
* Shorten the distance between adjacent flight lines
* Fly lower (proceed with caution)

### RGB Frame Cameras

RGB frame cameras are typically the limiting factor around flight planning characteristics. They have the highest requirements for overlapping data and typically the lowest frame rate. GRYFN recommends an absolute minimum of 70% overlap and 70% sidelap in order to process an orthomosaic, although aiming for higher (80% for both) is likely to provide better feature matching results and therefore higher quality data products.


---

# 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-operations/operations/flight-planning/flight-planning-calculator.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.
