> For the complete documentation index, see [llms.txt](https://docs.milientsoftware.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.milientsoftware.com/help/projects/overview/map.md).

# On map

For architects and engineers, the default map provider for **project map** is Ambita. This option is open for everyone. If you want to change project map provider, you can change this here: [Setup > Settings > General](https://app.moment.team/settings/preferences/general) (scroll down to Map). For **customer map** and **project overview map**, Moment always uses Google maps.

### What is project map from Ambita?

The map provided by Ambita gives you the opportunity to:

* Search for a property by looking up address, city, place, matrikkel id, name (person).
* Navigate in fullscreen map with your chosen layers
* See borders between properties
* See details for each property, such as unique id, topography, owners, type (building, road, park and more)
* Save the correct address and cadastre id (matrikkel id) directly to your project in Moment. This unique id gives more opportunities when it comes to usage of other services provided by Ambita or the Norwegian government, such as building application, plan, products and more.

You can find more information on the Ambita integration itself by going [here](https://docs.moment.team/help/integrations/other-systems/ambita).

The map is only available if the project address is in **Norway**. For projects outside Norway, Moment automatically switch to Google maps.

![Look up Rådhusplassen 1, Oslo with the Ambita map component](/files/-M3WijKyWd73o0W2yCs1)

 

![Look up Rådhusplassen 1, Oslo with Google maps](/files/-M3WjBb_QgTIu7Vt7AlN)


---

# 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.milientsoftware.com/help/projects/overview/map.md?ask=<question>&goal=<endgoal>
```

`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.