> For the complete documentation index, see [llms.txt](https://help.datamidsouth.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.datamidsouth.org/memphis-property-hub/features/layers.md).

# Layers

A **map layer** is a set of related information displayed on the map—like transparent sheets stacked on top of each other. Each layer shows a specific [theme](https://help.datamidsouth.org/memphis-property-hub/features/themes.md), or dataset about properties, at a specific [view](https://help.datamidsouth.org/memphis-property-hub/features/views.md).&#x20;

The Memphis Property Hub was designed to help you navigate these layers seamlessly, with each [theme ](https://help.datamidsouth.org/memphis-property-hub/features/themes.md)tab showing a default layer that shows up automatically. However, you can turn layers **on** or **off** to customize what you see, helping you explore specific questions.

### Adding and Removing Layers

On the [left panel,](https://help.datamidsouth.org/memphis-property-hub/getting-started/tour-the-interface.md#left-panel) you can hide or show different layers by clicking on the eye icon on the right side of each layer.&#x20;

<figure><img src="https://2346146017-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBsYufvkow7meMorVBVMT%2Fuploads%2FXMVmOpu89wRc9DZfntXW%2Flayer%20eyes%20both.jpg?alt=media&amp;token=f352ace2-10ac-48b5-8975-14012d63b630" alt=""><figcaption></figcaption></figure>

An **open eye** icon means the layer is currently showing, while a **closed eye** icon means the layer is currently hidden.

{% hint style="info" %}
*We recommend showing just one layer at a time and keeping the others hidden to make visualizations easier to understand.*
{% endhint %}

When [**VIEW TRENDS**](https://help.datamidsouth.org/pages/Hlk2Yb2U7tGcSdN9zK50#id-2.-trends-geographic-area-views) is selected, you can also use the eye icon to show or hide different groupings in the legend.&#x20;

<figure><img src="https://2346146017-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBsYufvkow7meMorVBVMT%2Fuploads%2F3sfguo7gMJldU0m3sSVM%2Fshow%20only%20this.jpg?alt=media&amp;token=11854115-566f-4023-b51b-f9e71afa06c6" alt=""><figcaption></figcaption></figure>

Click “Show only this” to focus on one group at a time.


---

# 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://help.datamidsouth.org/memphis-property-hub/features/layers.md?ask=<question>&goal=<user_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.
