> For the complete documentation index, see [llms.txt](https://docs.growthfactor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growthfactor.ai/faqs.md).

# FAQs

<details>

<summary>Where can I learn more about Retail Expansion?</summary>

Try visiting our [Retail Expansion Knowledge Base!](https://www.growthfactor.ai/resources/retail-location-analysis-guide-2025-trade-area-analysis-best-practices)

</details>

## Layers

<details>

<summary>Why can't I see certain layers on my map?</summary>

If a layer isn't appearing in your Map Layers panel, it may be disabled in your settings. Click the **Manage Layers** button at the bottom of the Map Layers panel to open the Manage Layers dialog, where you can enable any hidden layers.

</details>

<details>

<summary>How do I customize which layers appear in my legend?</summary>

Click the **Add or Edit Layers** button at the bottom of the Map Layers panel to open Manage Available Layers dialog. From there, you can enable or disable any layer. Disabled layers won't clutter your panel but remain available to re-enable anytime.

</details>


---

# 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://docs.growthfactor.ai/faqs.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.