> 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/upload-anything/urls/google-my-maps.md).

# Google My Maps

Import Google My Maps layers into Felt with a share link. Refresh the layers when the original map changes.

Add a Google My Maps map to Felt with its share link. Felt adds every layer and groups them when there are several. No KML export is needed.

## Add a My Maps map

1. In Google My Maps, click **Share**, and turn on **Anyone with this link can view**.
2. Copy the map's link. It contains `google.com/maps/d/` and `mid=`.
3. In the Felt toolbar, click **Upload Anything** ![](https://217108486-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmRfGitkyjOEMvVsEyGWN%2Fuploads%2FnwKMjNT6E1km4CtnHkqf%2F24.svg?alt=media\&token=9e98d9c4-35a3-416a-8802-b4e366c722cb) > **From URL**, and paste the link.
4. Click **Add to map**. The My Maps layers appear in the legend.

Felt doesn't keep the My Maps colors or icons, so style the layers after you add them.

Felt keeps the link with each layer, so you can refresh the layers when the My Maps map changes. See [Refresh data](/upload-anything/refresh-data.md).

Felt reads My Maps links, not regular Google Maps links. To bring in places or routes from Google Maps, add them to a My Maps map first, or upload them as a KML or CSV file.

{% embed url="<https://www.youtube.com/watch?t=8s&v=EzXBi8XP0B0>" %}


---

# 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/upload-anything/urls/google-my-maps.md?ask=<question>&goal=<user_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.