> For the complete documentation index, see [llms.txt](https://docs.hamina.com/hamina/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hamina.com/hamina/survey/survey-explorer.md).
# Survey Explorer
Learn about the Survey Explorer in Hamina Network Planner.
The **Survey Explorer** tool works like a microscope, allowing you to zoom in on a specific spot on the survey path.
## Basic Usage
1. Activate the Survey explorer tool.
2. The Survey Explorer popover will appear along the bottom.
3. Click and drag along a survey path (or survey point) to see precise measurements at that location.
4. Use the tabs to switch between the **Spectrum** view, **Networks** view, and **Access points** view in the Survey Explorer popover.
### Spectrum View
If a spectrum analyzer was connected during a survey, a spectrum density view is displayed here. Otherwise, spectrum density is derived from the QBSS Load IE from nearby access points.
### Networks View
Groups nearby access points by SSID. Channel width represents the maximum heard within the SSID, and signal strength is averaged over the last 5 seconds of the survey trailing the survey inspector ("roaming man").
### Access Points View
Shows per-radio details. Signal strength is averaged over the last 5 seconds.
#### Pinning an AP
If you'd like to track a particular access point, you can use the **Pin row** option to pin it to the top of the list. This will allow you to monitor a particular access point as you drag the survey explorer ("roaming man") along the survey path.
{% hint style="info" %}
You might need to scroll to the top of the list after you pin an access point.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.hamina.com/hamina/survey/survey-explorer.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
