> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/layers.md). # Layers - [Legend](https://help.felt.com/layers/legend.md): Choose which layers appear in a Felt map's legend, rename categories, and add captions and layer metadata so people understand your map. - [Organize layers](https://help.felt.com/layers/organize-layers.md): Arrange the layers in a map's legend, and group related layers so people can switch between them with a slider or dropdown. - [Filter layers](https://help.felt.com/layers/filter-layers.md): Show only the features in a layer that match a condition, such as Status is Open. A filter hides features without changing the layer's data. - [Create layers](https://help.felt.com/layers/create-layers.md): Create a point, line, or polygon layer with your own attributes, then draw its first feature on the map. - [Edit features](https://help.felt.com/layers/edit-features.md): Draw new features in a layer, reshape them, and keep their values up to date on the web. Your edits are saved as you go. - [Forms](https://help.felt.com/layers/forms.md): Design the form people fill in when they add or edit a feature, on the web or in the Field App, so the data you capture stays consistent. - [Copy and duplicate layers](https://help.felt.com/layers/copy-and-duplicate-layers.md): Reuse a layer on another map, or duplicate it to try a new style. Copies keep their styling and settings. --- # 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.felt.com/layers.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.