> For the complete documentation index, see [llms.txt](https://docs.mapsindoors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapsindoors.com/sdks-and-frameworks/web/directions-and-routing.md). # Wayfinding Wayfinding is a critical component of your indoor map solution enabling efficient route calculations and optimal navigation within indoor spaces.\\ MapsIndoors’ wayfinding functionality is a comprehensive solution that seamlessly integrates local and global maps, considers various travel modes, utilizes entry points for smooth transitions, and breaks down routes into logical legs and steps, ultimately enhancing navigation and user satisfaction.\\ Key elements to dig into when enabling wayfinding in your MapsIndoors solution are: **Outdoor to indoor navigation**\ Turn-by-turn directions visualized on the map with estimated travel time and detailed descriptions. **Venue to Venue wayfinding** When you're getting routes between two of your own MapsIndoors venues and may require using public routes from Google Maps or Mapbox to get there. **Dynamic routes**\ Automated route updates based on obstacles like furniture and changing floor plan layout. **Personalized routes**\ User profiles allow for personalized guidance, based on what the user is allowed to see and where they are allowed to navigate. Getting the right people to the right destinations. **Accessible wayfinding**\ Allow users with disabilities to effortlessly navigate your building by avoiding stairs and using elevators and ramps for navigation. \\ All the guidance is here for you. Happy wayfinding! --- # 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://docs.mapsindoors.com/sdks-and-frameworks/web/directions-and-routing.md?ask=&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.