> 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/mapset-multiple-maps.md).
# MapSet : Multiple Maps
### Overview
A MapSet is a container structure that enables the unified management and interaction with multiple individual maps, primarily used for handling large-scale venues and areas where Visual Positioning System (VPS) capabilities are required. It acts as a coherent unit, allowing multiple map fragments to function as a single, seamless mapping solution.
### Key Concepts
#### Map Consolidation
* MapSets solve the challenge of managing extensive areas by combining multiple smaller, more manageable maps into a unified structure
* Each constituent map maintains its individual characteristics while contributing to the larger whole
* The system preserves the integrity and detail of individual maps while enabling seamless navigation across their boundaries
#### Spatial Relationships
* Maps within a MapSet are positioned with high-precision relative coordinates and rotations
* The accurate spatial relationships between maps ensure:
* Seamless transitions between adjacent areas
* Consistent positioning across the entire venue
* Accurate distance calculations spanning multiple maps
* When a MapSet is created, the relative coordinate is assigned with respect to the origin of the **first map** of the MapSet, so every map's coordinate is defined with respect to the first map
{% hint style="success" %}
When you add a new Map in a MapSet, its transform is calculated with respect to the existing maps, but existing maps are not impacted.
{% endhint %}
#### User Experience
Despite the underlying complexity of multiple maps, end-users interact with a MapSet as if it were a single map:
* Continuous navigation across map boundaries
* Unified coordinate system across the entire venue
* Consistent positioning and orientation references
* Seamless VPS functionality throughout the covered area
### Best Practices
1. Divide large venues into logical, manageable sections
2. Ensure sufficient overlap between adjacent maps
3. Maintain consistent mapping quality across all constituent maps
####
---
# 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/mapset-multiple-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.