Coverage and sites
What a registered site is, what its pod can reach, and how a new location gets added.
SupaDrone flies from fixed locations. What you can request depends on whether the thing you want looked at falls within reach of a deployed pod.
Registered sites
A registered site is a location with a deployed pod, its approvals in place and its operating constraints established. Requests at a registered site are ordinary: choose the asset, choose the mission type, submit.
Flight radius
A pod serves an area around itself, not only the ground it stands on. The approvals held for a location apply across that radius, which is why a Host pod can serve nearby Fly demand at all.
The radius is a property of the site, established when the site was approved. It is not something a single request can extend. See Regulatory and airspace.
Assets within a site
A site usually contains several things worth inspecting: buildings, elevations, yards, stockpiles, perimeters, plant. Registering these as named assets is what makes repeat requests short and makes results from different dates line up against each other.
Locations with no pod
If what you need is outside the reach of any deployed pod, there is no mission to request there yet. Two routes forward:
- A Station at your site. A dedicated deployment, bought outright, which also earns from nearby demand if you choose to share it. See Host.
- Existing capture. If the need is for footage or imagery of a place rather than a new flight, check SupaVault first.
New locations take time. Approval for a site is obtained before deployment and is measured in months rather than days, which is the reason pods are fixed and the reason coverage is a map rather than a promise. See Requesting a new site for what a location needs.