# Page Not Found

The URL `files/OVr49porEak0zliV0Lq1` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Introducing Point Cloud and Elevation Map Overlays](https://releases.flytbase.com/april-2025/introducing-point-cloud-and-elevation-map-overlays.md)
- [Webhooks for Media & Mission Events](https://releases.flytbase.com/september-2025/webhooks-for-media-and-mission-events.md)
- [Feature Updates: Zones and Unit Conversion](https://releases.flytbase.com/august-2024/feature-updates-zones-and-unit-conversion.md)
- [AirData Integration: Automatic Flight Log Sync](https://releases.flytbase.com/april-2026/airdata-integration-automatic-flight-log-sync.md)
- [Improvements to Drone Deploy Flink](https://releases.flytbase.com/january-2025/improvements-to-drone-deploy-flink.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://releases.flytbase.com/april-2025/introducing-point-cloud-and-elevation-map-overlays.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.

### Option 2 — Browse the documentation index

Full index: https://releases.flytbase.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://releases.flytbase.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/april-2025/introducing-point-cloud-and-elevation-map-overlays.md`).

You may also use `Accept: text/markdown` header for content negotiation.