> For the complete documentation index, see [llms.txt](https://inscada.gitbook.io/ins/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inscada.gitbook.io/ins/en-1/user-interface/project-map.md).
# Project Map
Using Project Map, you can show the data you want on the map in the GPS coordinates entered in the project definition. In the filter menu on the right side, you will see a list of all the variables selected for the project. Next to each variable is a checkbox where you can activate its representation on the map. On the corresponding coordinate, you can change the order of the data in the tooltip with the order parameter.
You can enter the API key of the GIS system to be connected with using the 
settings button on the filter menu. inSCADA is set to Google Maps by default. When you click on the settings button, you can change the update time interval of the data displayed on the map by using the interval parameter. The default is 3000 ms
{% hint style="info" %}
In order to display the data on the map, you should consider your applications in different locations as different projects in inSCADA. Thus, you can visualize the summary information of your distributed systems on the map.
{% endhint %}
---
# 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://inscada.gitbook.io/ins/en-1/user-interface/project-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.