> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/admin/settings/maps/overcoming-gis-limits.md).

# Overcoming GIS limits

Avoid GIS API rate limits by using Premium GIS, enabling paid Google services, or self-hosting Nominatim

{% hint style="info" %}
In this article, GIS services (or Geographic Information Systems services) refer to combination of services like geocoding, routing, distance calculations, street view, and similar.
{% endhint %}

When relying on free or public GIS services, such as Google API keys or OpenStreetMaps servers, you may encounter usage limits. This can lead to services like geocoding, routing, or street maps becoming unavailable or functioning very slowly. To avoid these issues, Navixy recommends using Navixy's **Premium GIS** package or a similar paid GIS service.

There are several solutions to solve the issue of API limits:

* **Enable the Navixy GIS package (recommended)**\
  This is the most convenient and inexpensive method. See [Navixy GIS packages](/docs/admin/settings/maps/navixy-gis-packages-compare.md) for more information.
* **Enable paid services in your Google Maps account**\
  Activating paid subscriptions for Google Maps APIs or similar paid services increases your usage limits. For information on prices and conditions, see Google's website. In this case, Navixy recommends creating two separate Google API keys and restrict them accordingly. The first key should only allow access to the Google Maps JavaScript API and Google Street View Image API, while the second key should only allow access to the Google Maps Geocoding API, Google Maps Geolocation API, and Google Maps Directions API. You can monitor usage statistics in your Google Developer Console.
* **Install your own Nominatim server**\
  For more information about Nominatim server, see [Nominatim](/docs/on-premise/on-premise/how-to-guide/installation/optional-software/nominatim.md).

If you have any questions regarding these solutions, don't hesitate to contact the Navixy customer success team.


---

# 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://navixy.com/docs/admin/settings/maps/overcoming-gis-limits.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.