> For the complete documentation index, see [llms.txt](https://docs.jmapcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jmapcloud.io/en/jmap-ng/jmap-ng-user-guide/data/data-layers.md). # Data Layers The card for each layer contains information such as the name, the presence of styles, etc. To access the available tools, hover over the layer card.


	Layer icon Reproduces the layer style (appearance of features). A number on the icon indicates that at least one style is configured. See the Styles section for details.
Ecological Interest	Layer name Identifies the layer.
	If metadata is configured, a tooltip displays it on hover.
	Selection Makes the layer features selectable for editing or interactive selection. See the Making Layer Features Selectable section for more details.
	Display Enables or disables the display of the layer on the map. See the Displaying Layers section for more details.
	Menu Depending on the data type, contains: More information (see the Information section for details) Styles (see the Styles section for details) Show layer extent (see Geographic Extent section for details) Filter features on the map (see Filtering Features section for 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.jmapcloud.io/en/jmap-ng/jmap-ng-user-guide/data/data-layers.md?ask=&goal= ``` `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.