> 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-cloud-portal/user-guide-for-jmap-cloud-portal/configuring-project-data/organizing-project-layers/setting-the-layer-display-order-on-the-map.md).
# Setting the Layer Display Order on the Map
The order of layers on the map determines how they are drawn on top of one another. The layer at the bottom of the stack is rendered first, followed by the one just above it, and so on up to the topmost layer, which is drawn last.
This order is important because it affects layer visibility based on their transparency or type. For example:
* A raster layer at the top of the stack may hide layers below it.
* A polygon layer may occlude point or line layers if it is drawn after them.
**To change the layer order on the map:**
1. Activate the tool by clicking 
**Layer Order**.
2. In the **Layer Order** window, select the layer to move by clicking its name or 
.
3. Drag the layer to the desired position and drop it.
The map automatically updates to reflect the new order.
---
# 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-cloud-portal/user-guide-for-jmap-cloud-portal/configuring-project-data/organizing-project-layers/setting-the-layer-display-order-on-the-map.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.