> For the complete documentation index, see [llms.txt](https://multiset.gitbook.io/multiset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multiset.gitbook.io/multiset/basics/georeferencing-maps.md).
# Georeferencing Maps
The MultiSet Visual Positioning System (VPS) now supports the use of geolocation data as an external prior to enhance localization performance. This feature, called **GeoHint**, allows you to provide approximate GPS readings to the localization query, which helps narrow down the search space and improves the speed and accuracy of pose estimation.
By geo-referencing your 3D scans with WGS84 coordinates, you can leverage device GPS and other sensors to provide initial position estimates that significantly reduce the computational load during localization.
### Benefits of Using HintPosition
* **Improved Performance**: Reduces search space and computational requirements
* **Faster Localization**: Achieves quicker initial positioning by focusing on relevant areas
* **Higher Accuracy**: Resolves potential ambiguities in visually similar environments
* **Seamless Transitions**: Enables smooth transitions between different mapped areas
* **Reduced Resource Usage**: Lower memory and processing requirements on devices
### Setting Up Geo-Referenced Maps
To use the GeoHint field in Localization API's effectively, you need to establish a proper geo-reference for your MultiSet maps. This involves:
1. Recording the exact WGS84 coordinates (latitude, longitude, altitude) of your map's origin point
2. Documenting the compass heading to establish the orientation relative to true north
3. Configuring these values in your MultiSet Developer Portal
{% hint style="success" %}
To achieve accurate conversions at the centimetre level, ensure that you enter at least 6 decimal places for latitude and longitude.
{% 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://multiset.gitbook.io/multiset/basics/georeferencing-maps.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.