# Prioritized Capture

A key challenge facing the LayerDrone Network is that not all of earth needs capture. Areas vary immensely in the benefits of high-quality aerial imagery captured at a higher frequency or even on-demand. Some critical factors include:

* Human activity, active presence, and footprint
* Built environment complexity, density, and value
* Rate of change in the environment&#x20;
* Restrictions on collection (legal or environmental)
* Active markets for data, which is a way of saying that any human activity collecting data should prioritize collection where other humans want that data and can fund its capture

<figure><img src="/files/c9oDWleEXCTad44YLbZM" alt=""><figcaption></figcaption></figure>

The supply-led missions are intended to approximate these target spexigons to let new markets flourish, while the demand-led missions ultimately best reflect where humans are willing to pay for standardized aerial imagery.

<figure><img src="/files/dtg2oroRxk8vhQ9ANWpo" alt=""><figcaption></figcaption></figure>

The LayerDrone Network, via a governance process, will ultimately be developing missions and establishing rewards, with the primary goal of monetizing the underlying data. The process for this will likely vary over time and as the network expands.

<br>


---

# Agent Instructions: 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:

```
GET https://layerdrone.gitbook.io/layerdrone/the-layerdrone-protocol/prioritized-capture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
