## enterprise-apps
### Mappedin Directory
# Mappedin Directory
The Mappedin Directory is a comprehensive indoor wayfinding experience built to be deployed on kiosk screens in an on-site environment. The directory application is a web app that can be hosted in a number of different ways.
!Mappedin Directory in a Mall
## Requirements
### Working with a Hardware Integrator
:::tip
In order to provide the smoothest installation experience, we strongly encourage partnering with an experienced hardware integrator.
:::
A hardware integrator should be able to fulfill all the following responsibilities:
- Provisioning machines with the correct device settings and Mappedin configurations.
- Deploying a browser and keeping it up to date.
- Handling security measures (e.g. locking down the OS).
- Responding to any crashed or frozen machines.
- Maintaining remote access for debugging and maintenance.
- Ensuring machines are rebooted periodically.
### Resolution
The Mappedin Directories are built to run on the following screen resolutions. Using a different screen resolution is not supported and will likely result in unexpected graphical issues and/or loss of functionality.
- 1080p Portrait (1080px wide by 1920px tall)
- 1080p Landscape (1920px wide by 1080px tall)
- 4k Portrait (2160px wide by 3840px tall)
- 4k Landscape (3840px wide by 2160px tall)
### CPU
In general, any CPU manufactured in the last 5 years paired with a dedicated GPU should be sufficient. For example, any of the following processors are acceptable:
- Intel i5 or i7
- Ryzen 5 or 7
The following link can be used to compare hardware to the minimum CPU requirements. These comparisons should be used as a guide and testing should be performed on all hardware. To use the comparison, select your CPU from the right hand side of the page.
- UserBenchmark CPU Comparison
### GPU
The performance demands of the directories primary result from rendering the 3D map on screen, thus the GPU requirements vary depending on the desired screen resolution.
Mappedin recommends hardware equivalent to or better than the following GPUs:
- **1080p:** Intel HD Graphics 520
- **4k:** NVIDIA GeForce GTX960
The following links can be used to compare hardware to the minimum GPU requirements. These comparisons should be used as a guide and testing should be performed on all hardware. To use the comparisons, select your GPU from the right hand side of the page.
- 1080 HD UserBencmark GPU Comparison
- 4K UserBencmark GPU Comparison
### Operating System
The Mappedin Directory is optimized for devices running the following versions of Windows. Other operating systems are not supported.
- Windows 10 Pro
- Windows 11 Pro
### Network
The Mappedin Directory requires an internet connection to function with access to `*.mappedin.com` domains. Any network whitelist must allow access to these domains.
### Browser
:::tip
In order provide the best possible directory experience, Mappedin may experiment with new technologies. It is recommended to always keep your browser up-to-date to take advantage of the latest features.
:::
The Mappedin Directory is optimized to run within a Chrome or Chromium browser environment. The minimum supported Chromium version for the Premium Directory experience is version 106.
## Configuration
The following configuration properties are required for deployment. Obtain these from a Mappedin employee before deploying a Mappedin Directory.
| Property | Description |
|----------|-------------|
| venue | A unique identifier for the desired venue or map. |
| kisokId | A unique identifier for a specific directory machine at the venue. This can either be a name or UUID. |
| clientId | An API key. This acts like credentials required to load map data. |
| clientSecret | An API key. This acts like credentials required to load map data. |
| baseUrl | A URL indicating a specific directory load out. For a normal directory, this will be `https://solutions.mappedin.com/directory/gen7/index.html`. If a different directory experience (e.g. Premium Directories) is desired, a different URL will be provided by Mappedin. |
| apiGateway | A specific endpoint to load map data from. This most often `https://api-gateway.mappedin.com`. Clients with data in EU data centers should use `https://api-gateway.eu.mappedin.com/`. |
## Installation
Mappedin provides an executable that can be used to install a kiosk if some steps are performed beforehand. Follow these steps to perform Environment File Installation:
1. Create a `mappedin-directory` folder in the %appdata% directory of the target device. This will usually live at `C:\Users\\AppData\Roaming\mappedin-directory`.
2. Either create an environment.json file using the information in Directories Configuration or obtain an existing environment.json provided by Mappedin. The `environment.json` will look something like the following:
```json
{
"baseUrl": "https://solutions.mappedin.com/directory/gen7/index.html",
"venue": "mappedin-demo-mall",
"kiosk": "kiosk-1",
"clientId": "some-client-id",
"clientSecret": "some-client-secret",
"apiGateway": "https://api-gateway.mappedin.com"
}
```
3. Place the `environment.json` within the newly created `mappedin-directory` folder.
4. Download the installer from this link: Mappedin Directory Installer
5. Run the installer.
Mappedin Directory should automatically startup with a functioning directory when the installation completes. If a login screen appears, then the `environment.json` file was not configured correctly. In this case, the file needs to be corrected and the directory needs to be rebooted.
The app will be configured to start automatically every time the device restarts. As a security measure, Mappedin Directory will terminate the `explorer.exe` process to remove the Windows UI elements and prevent guests from interacting with the OS.
## Uninstallation
To uninstall a Mappedin Directory after using the Environment File Installation, open “Add/Remove Programs” in Windows settings and search for “Mappedin Directory”. Uninstall the application through from the available menu.
To fully clear all cached data and configuration files, locate and delete the following folders as well as all of their contents:
- `%localappdata%/mappedin_directory`
- `%appdata%/mappedin-directory`
## No installer
The directories can also be loaded directly in a browser without needing to download and run the installer. To load the directories in a browser, use the following URL template:
```
{baseurl}?venue={venue}&kiosk={kiosk}&clientId={clientId}&clientSecret={clientSecret}
```
Replace the `{variables}` (including the braces) with values from Directories Configuration and paste the entire link into the URL. This will load the directory application directly into a web page, which can be opened on a kiosk device in full-screened to hide the default browser UI.
When deploying the directory this way, it is recommended to lock down the device's OS to prevent users from accidentally closing the directory application. It may also be convenient to configure the device to automatically restart the directory application when rebooted.
## Large-Scale Deployments
Mappedin supports special procedures for deployments involving hundreds or thousands of directories. To learn more about large-scale directory deployments, contact Mappedin support.
## Updates
If updates are unavailable (e.g. due to lack of internet access), then a previously cached version will be used instead.
### Data Updates
Map data is fetched every 10 minutes by default. This value is configurable.
### Software Updates
#### Environment File Installation
The Mappedin Directory installer includes a robust auto-update mechanism that automatically checks for new versions and installs them without requiring manual intervention.
The system is configured to check for updates every hour, but new updates are not installed immediately. Although the update process is designed to be quick and minimally disruptive, it is scheduled to occur once a day during periods of minimal activity to eliminate any possible business disruptions. Updates usually occur between 03:00 and 03:30 local time.
#### No Installer
The Mappedin Directory will automatically load the latest software release when loaded in a browser.
## Monitoring
The directory exposes a health endpoint which will return either `{ clientStatus: "waiting" }` if the health check is waiting to connect to an offline directory or `{ clientStatus: "connected" }` when the kiosk is online. As the directory runs on port 19254, the health endpoint is available at `:19254/health`. For example, a script running locally on the same machine could query `localhost:19254/health`.
## Integrations
### Broadsign
The directory application includes integration capabilities with Broadsign digital signage systems. This integration operates as a one-way communication system where the directory notifies Broadsign when it's switching contexts, but Broadsign doesn't actively communicate back to the directory about state changes.
When the directory takes control, Broadsign automatically minimizes itself to allow the directory to display full-screen. When the directory session ends, it signals Broadsign to return to the foreground and resume its normal operation.
## Troubleshooting
### Application Logs
The directory generates comprehensive logs that are stored at the path `appdata%/mappedin-directory/logs`. These logs capture startup information, operational details, and any errors that occur during runtime. Providing logs alongside your incident report provides critical information to Mappedin and can help facilitate a speedy resolution.
## Frequently Asked Questions
### How do I access the OS when the directory is running?
Sometimes it is necessary to access Windows on a running kiosk, either for debugging or to update system settings. To use Task Manager to restart and access the Windows UI, go to **File > Run New Task** and run `explorer.exe`.
### Why does the directory UI look strange or broken?
The most common cause of UI issues is device resolution. First, make sure the device is one of the supported resolutions (refer to Directory Resolution).
If the hardware resolution is supported, ensure that the Windows display scale is exactly 100%.
### Why are my data changes not showing up?
Data and software updates happen at predefined intervals (refer to Directory Updates). Updates require an internet connection to complete successfully, otherwise the directory will fall back to the latest loaded data.
### I see an empty black screen when the directory starts. What do I do?
An empty black screen usually indicates that the device's OS was successfully locked down, but the directory app failed to launch. This could be the result of an error during installation. Reinstall the kiosk, and if the issue persists, contact Mappedin support with your application logs (refer to Directory Application Logs).
### My directories are showing “We'll be right back”. What do I do?
The “We'll be right back” message on a black screen usually indicates that the directory encountered an unexpected error during its use and was unable to recover automatically. Restart the machine, and if the issue persists, contact Mappedin support with your application logs (refer to Directory Application Logs).
### My directory is missing an app I expect (e.g. weather, transit). What do I do?
This is most likely due to missing permissions on the directory's API keys. Contact Mappedin support to get the necessary permissions added.
### Can I customize the look of my directory Home Screen?
Various customizations of the home screen are supported depending on the type of directory application. Contact Mappedin support to learn more about customizations.
### Why does my directory load in portrait/landscape mode but crash in the other orientation?
If using Premium directories, layouts, including specific orientation that are supported, need to be customized with Mappedin support ahead of the directory deployment. If layouts are not configured, or the configured layout is not matched, the directories may fail to start.
### Mappedin Minimap
# Mappedin Minimap
Mappedin Minimap provides a static map, zoomed in on a specific location. It is designed to work in tandem with Mappedin Web. Clicking on the Minimap will link the user to the location profile within the Mappedin Web App. This guide demonstrates how to configure and integrate Minimap with a web page.
## Integration
The following HTML snippets are all that are necessary to include Minimap on a page.
Add a `div` element with an id of `mappedin-minimap` in the appropriate position in the HTML document.
```html
```
Include the below scripts to configure and download the Mappedin Minimap on page load.
```html
```
With the above snippets in the document, Minimap should initialize within the `mappedin-minimap` element. To read about each of the above properties in `window.mappedin`, see Required Properties. Replace `` in the URL with the unique identifier for the venue.
## Example
## Required Properties
The following properties are **required** in the `window.mappedin` configuration. Without them Minimap will fail to initialize.
- `clientId` is the Mappedin Web key for the venue.
- `clientSecret` is the Mappedin Web secret for the venue.
- `venue` is the unique identifier for the venue.
- `locationId` is the identifier for the location. Must be either `locationId` or `externalId` unless modified by the optional `dataKey` property.
- `fullMapUrl` is the URL to the Mappedin Web application. For example, `https://www.mappedin.com/demos/#/`.
## Styling
The Minimap will take up the entire space of it's parent container. It is recommended to put the above snippets in a wrapping container, and style that container to control position and size of the Minimap instead of the Minimap element itself.
## Frequently Asked Questions
### How do I display location names on the map?
Contact Mappedin to enable FloatingLabels for the venue to display the location name label on the Minimap.
### How can I use the location's name as the ID for Minimap?
To use the location's name rather than `locationId` or `externalId`, set the `dataKey` in `window.mappedin` configuration to specify `name`.
```html highlight={8}
window.mappedin = {
clientId: "",
clientSecret: "",
venue: "",
fullMapUrl: ""
dataKey: "name"
};
```
### How can the user get directions to or from a location when they click the Minimap?
By default, Minimap will send the user to the location profile. Customize the deep link by adding the `deepLink` property to the `window.mappedin` configuration.
```
html highlight={8}
window.mappedin = {
clientId: "",
clientSecret: "",
venue: "",
fullMapUrl: ""
deepLink: "/directions?to="
};
```
Use `/directions?to=` or `/directions?from=` to direct the user to the directions page with the `locationId`.
### What domains need to be included in our Content Security Policy?
Mappedin Web must be able to access the following domains. Please ensure they are allowed in your Content Security Policy (CSP).
- `*.mappedin.com`
### What Content Security Policy Directives are required?
As a mitigation for Cross-Site Scripting and other types of web security vulnerabilities, you may use a Content Security Policy (CSP) to specify security policies for your website. If you do, Mappedin Web requires the following CSP directives by default:
```
worker-src blob: ;
child-src blob: ;
img-src data: blob: ;
```
Failing to add these directives could result in unexpected behavior and an error similar to the following being logged in the browser console.
```
Refused to create a worker from 'blob:https://YOUR.URL' because it violates the following Content Security Policy directive: "default-src https: ws: data: 'unsafe-inline' 'unsafe-eval'". Note that 'worker-src' was not explicitly set, so 'default-src' is used as a fallback.
```
It is possible to implement a more restrictive CSP policy that does not include `worker-src blob: ;`. Doing so requires a transparent proxy be set up on your server that forwards requests from `https://YOUR.DOMAIN/mappedin-web-redirector/*` to `https://cdn.mappedin.com/web2/release/*`.
### Mappedin Web Plugin for WordPress
# Mappedin Web Plugin for WordPress
The following guide explains how to install and use the Mappedin Web Plugin for WordPress.
> Read more about Mappedin Web at https://www.mappedin.com/wayfinding/web-app/
The Mappedin Web Plugin for WordPress allows easily adding Mappedin Web to any WordPress page or post.
### Prerequisites
- WordPress Version: 2.9.0+
- PHP Version: 7.2+
Before installing Mappedin Web Plugin for WordPress, please ensure the following requirements have been met:
- Venue is fully mapped and tested (demo links will be provided to preview the front-end experience)
- Location data is up to date and ready for production
- Mappedin venue keys have been provided to you
### Installation
The Mappedin Web Plugin for WordPress can be obtained from the WordPress Plugin Store or downloaded directly from GitHub.
- WordPress Store: Mappedin Plugin for WordPress
- GitHub: Mappedin Plugin for WordPress
Please refer to the WordPress plugin installation documentation and follow the steps for your preferred method of installation.
### Venue Configuration
After installation of the Mappedin Web Plugin for WordPress it must be configured. To access the configuration page, open the WordPress Admin Dashboard and select Mappedin Web from the menu. Enter the client id, client secret and venue slug that has been provided from Mappedin.
!Admin Page of the Mappedin Web Plugin for WordPress
If you have not yet received your client id, secret and venue slug from Mappedin you can use a trial key
- Arabic (ar)
- Catalan (ca)
- Czech (cs)
- Danish (da)
- Dutch (nl)
- Estonian (et)
- Finnish (fi)
- French (fr)
- German (de)
- Greek (el)
- Hindi (hi)
- Hungarian (hu)
- Italian (it)
- Japanese (ja)
- Korean (ko)
- Norwegian (no)
- Portuguese (pt)
- Romanian (ro)
- Russian (ru)
- Slovak (sk)
- Spanish (es)
- Spanish - US (es-US)
- Swedish (sv)
- Tagalog (tl)
- Turkish (tr)
- Ukrainian (uk)
- Vietnamese (vi)
- Chinese Simplified (zh-CN)
### Usage
The Mappedin Web Plugin for WordPress allows the embedding of Mappedin Web into a WordPress page or post using the `[mappedin-web]` shortcode. The steps below explain this process.
1. Click on the Add Block button.
2. Select Shortcode !Mappedin Web Plugin for WordPress Add Shortcode
3. Use `[mappedin-web]` as the shortcode. !Mappedin Web Plugin for WordPress Shortcode
### Deep Linking
Mappedin Web offers a way to link directly to many pages. The same URL parameters supported by Mappedin Web can be used with the Mappedin Web Plugin for WordPress. For more information, refer to the Mappedin Web Deep Linking Guide
### Frequently Asked Questions
Refer to the Mappedin Web FAQ.
## mappedin-web
### Deep Linking
# Deep Linking
Mappedin Web offers a way to link directly to many pages. The following represents all of the deep linking routes that are possible, with a description of what it will do and any parameters you will need. These routes can be used to create URLs that can be used to open the map at a specific location, display a category page, search for a location, display directions, and more.
Mappedin Web deep linking URLs can be generated visually using the URL Configurator, by manually constructing the URL, or by copying the URL from the map while using the app.
## Location Page
`/profile?location=&my-section=true`
- `locationId`: Mappedin ID of the location to display
- `locationName`: Name of the location to display
- `externalId`: External ID of the location to display
- `my-section`: Optional parameter that sets this location as the user's section. Only applicable to stadiums.
Using any of the above will deep link to a specific location.
## Categories Page
`/categories`
List all available categories
## Specific Category Page
`/categories?category=`
- `categoryName`: Name of the category to display
- `categoryId`: Mappedin internal id of the category to display
- `externalId`: External ID of the category
Display a category page using one of the above identifiers. Defaults to show the name of the category in the URL.
## Search Page
`/search`
Display the search page
The search form can be populated with text by adding the `query` parameter to the URL.
`/search?query=`
- `query`: Search query text to populate the search form with
## Directions Page
`/directions`
Directions page
## Directions - From Page
`/directions?from=`
- `fromId`, `fromName`, `fromExternalId`, `fromPolygonId`, `fromNodeId`: Preset departure point to display directions page with a preset from field
## Directions - To Page
`/directions?to=`
- `toId`, `toName`, `toExternalId`, `toPolygonId`, `toNodeId`: Preset arrival point to display directions page with a preset to field
## Directions - From/To Page
`/directions?to=&from=&accessible=true&textDirectionsVisible=true`
- `from`: (Location ID, Name, External ID Polygon ID or Node ID) Preset departure point
- `to`: (Location ID, Name, External ID, Polygon ID or Node ID) Preset destination point
Optional:
- `accessible`: Default: `false`, can set this param to true to enable directions that will prioritize elevators and ramps
- `textDirectionsVisible`: Default: `false`, can set this param to true to show text directions alongside the wayfinding path upon initial load
## Directions - Multi Destination
`/directions?from=&to=&to=`
- `from`: (Location ID, Name, External ID Polygon ID or Node ID) Preset departure point
- `to`: (Location ID, Name, External ID, Polygon ID or Node ID) Preset destination points. Can be repeated to add multiple destination points.
## Language
`?lang=`
- `languageCode` A language code of a supported language.
This can be used to change the language of the map before or after it has been displayed.
## External Tracking ID
`?extId=`
- `trackingIdentifier`: An arbitrary string provided by the customer for external analytics correlation.
The `extId` parameter attaches a custom tracking identifier to every analytics event sent during the session. This is useful for correlating Mappedin analytics data with an external system — for example, linking a map session back to a specific marketing campaign, CRM record, or third-party tracking platform.
The parameter can be appended to any route and works independently of other tracking parameters like `origCtx` and `sessId`. When present, `extId` is automatically propagated through share links and QR codes generated during the session, so the identifier follows users across handoffs.
`/profile?location=guest-services&extId=campaign-summer-2026`
`/current-location?lat=33.94545&lon=-118.40413&floor=abc123&extId=crm-visitor-7842`
## Start From Here
Mappedin Web provides a way to open the map with a "You Are Here" style experience. This is useful for cases where the map should start from a specific location and provide location and directional context, such as when scanning a QR code printed on a sign or displayed on a digital screen.
The Start From Here experience can be delivered in two ways: on a Display screen or via a QR Code that opens on a visitor's phone. Both can be created manually using the URL parameters documented below, or visually using the URL Configurator.
:::tip
Start From Here URLs can be generated visually using the URL Configurator, which provides an interactive interface for configuring Display and Print QR settings.
:::
### Display
`/display?lat=&lon=&floor=&zoom=&heading=&tilt=&showQR=&showBlueDot=&showFloorInfo=&qrId=`
The Display route loads a fixed, non-interactive map view designed for passive viewing on a TV, kiosk, or digital signage display. The display can include a "You Are Here" Blue Dot and an optional QR code overlay that visitors can scan to open the map on their phone.
:::tip
Display URLs can be generated visually using the URL Configurator Display tab, which provides an interactive interface for configuring all display settings.
:::
#### Camera Parameters
These parameters control the map's viewport — what the viewer sees on screen.
| Parameter | Type | Required | Description | Format |
| --------- | ------ | -------- | ---------------------------------- | ----------------------------------- |
| lat | string | Yes | North-south position of the map center | Decimal degrees (-90 to 90) |
| lon | string | Yes | East-west position of the map center | Decimal degrees (-180 to 180) |
| floor | string | No | Floor/Map identifier | Alphanumeric string (map ID) |
| zoom | string | No | How close the map is zoomed in | 0 (world view) to 24 (extreme close-up) |
| tilt | string | No | The 3D tilt angle of the map | Degrees, 0 (top-down) to 90 (edge-on) |
| heading | string | No | Compass heading / rotation of the map | Degrees (0-360) |
#### Display Options
These parameters control the additional features shown on the display.
| Parameter | Type | Required | Description |
| ------------- | ------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| showBlueDot | boolean | No | When `true`, a Blue Dot (simulated user position) appears in front of the screen facing toward it, giving viewers a "You Are Here" reference point. |
| showQR | boolean | No | When `true`, a QR code is overlaid on the display so passersby can scan it to open the map on their phone. If `showBlueDot` is `false`, the QR code opens the general map homepage without a Blue Dot. |
| showFloorInfo | boolean | No | When `true`, a banner at the top of the display shows the current floor name, subtitle, and building or map group name. |
| qrId | string | No | An optional tracking identifier for the QR code (e.g., `lobby-tv-1`). Used for analytics to track which QR codes are being scanned. |
| lang | string | No | Sets the language for the display. Use a supported language code. |
#### Example Display URL
`https:///#/display?lat=43.4567&lon=-80.5234&floor=abc123&zoom=19&heading=180&tilt=45&showQR=true&showBlueDot=true&showFloorInfo=true&qrId=main-lobby-tv`
### QR Code
`/current-location?lat=&lon=&floor=&qrId=&origCtx=&zoom=&heading=&nearbyCategories=`
The QR Code route opens the map on a visitor's phone at a specific location with a "You Are Here" Blue Dot. This is designed for printed signs, parking lot posts, wayfinding totems, or any physical sign where visitors can scan a QR code to get directions from their current location.
:::tip
QR Code URLs and downloadable QR code images can be generated visually using the URL Configurator Print QR tab.
:::
#### Location Parameters
`/current-location?lat=33.94545&lon=-118.40413&floor=6475f7fea6e4f69c75e5b52d`
These parameters are required to position the map showing a specific origin.
| Parameter | Type | Required | Description | Format |
| --------- | ------ | -------- | -------------------- | ------------------------------------ |
| lat | string | Yes | Latitude coordinate | Decimal degrees (minimum 5 decimals) |
| lon | string | Yes | Longitude coordinate | Decimal degrees (minimum 5 decimals) |
| floor | string | No | Floor/Map identifier | Alphanumeric string (map ID) |
#### Camera Parameters
`/current-location?lat=33.94545&lon=-118.40413&floor=6475f7fea6e4f69c75e5b52d&zoom=18&heading=90`
These optional parameters control the initial view presentation:
| Parameter | Type | Required | Description | Format |
| --------- | ------ | -------- | --------------- | -------------------- |
| zoom | string | No | Zoom level | Numeric value (1-24) |
| heading | string | No | Camera rotation | Degrees (0-360) |
Heading Reference Values:
- **0** = North
- **90** = East
- **180** = South
- **270** = West
#### Tracking Parameters
`/current-location?lat=33.94545&lon=-118.40413&floor=6475f7fea6e4f69c75e5b52d&qrId=gate-a12&origCtx=physical&extId=campaign-45`
These parameters enable tracking and context identification and should be set when using the `current-location` route.
The `qrId` parameter can be used for any arbitrary tracking identifier like `campaign-45` or `parking-lot-pillar-3`.
The `origCtx` parameter is used to identify the context of the location where the QR code is placed. This value is logged to Mappedin analytics to track the source of the QR code scan. This should be set to `physical`, `digital` or `ad` depending on the where the QR code is being displayed.
The `extId` parameter attaches a custom external tracking identifier to every analytics event in the session. See External Tracking ID for details.
| Parameter | Type | Required | Description | Format |
| --------- | ------ | -------- | -------------------- | ---------------------- |
| qrId | string | No | Unique QR identifier | Custom tracking string |
| origCtx | string | No | Placement context | Context value |
| extId | string | No | External tracking ID for analytics correlation | Arbitrary string |
#### Nearby Categories
`/current-location?lat=33.94545&lon=-118.40413&floor=6475f7fea6e4f69c75e5b52d&nearbyCategories=id1,id2`
The `nearbyCategories` parameter controls which categories appear in the "What's nearby" section on the current-location page after a visitor scans the QR code.
| Parameter | Type | Required | Description |
| ------------------ | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| nearbyCategories | string | No | A comma-separated list of category IDs. When set, only locations in the specified categories appear in the "What's nearby" section. Set to `none` to hide the section entirely. When omitted, the venue's default categories are shown. |
The header text displayed above the nearby list adapts based on the selection:
- **One category selected** — "Nearby [Category Name]"
- **Multiple categories selected** — "Nearby locations"
- **Default (parameter omitted)** — "What's nearby"
:::tip
Nearby Categories can be configured visually using the URL Configurator Print QR tab, which provides a tag-style input for selecting categories.
:::
## URL Configurator
The URL Configurator is an admin tool that provides a visual interface for building deep link URLs. Rather than manually constructing URLs, the configurator allows the map to be set up exactly as it should appear — camera angle, zoom, location, visible categories, and tracking options — and then generates a ready-to-use link or downloadable QR code image.
:::info
Try out the URL Configurator using Mappedin Demo Mall.
:::
The URL Configurator supports three modes:
| Tab | Description | Use Case |
| --------- | ------------------------------------------------------ | --------------------------------------------------- |
| Display | Configure a fixed map view for non-interactive screens | Digital signage, kiosks, lobby TVs |
| Print QR | Generate a QR code for scan-and-go wayfinding | Printed signs, parking lot posts, wayfinding totems |
| Deep Link | Create a URL that opens the map to a specific screen or state | Emails, kiosk buttons, website embeds, digital campaigns |
### Accessing the URL Configurator
The URL Configurator is available at the following path on any deployed Mappedin Web instance:
`https:////#/display-admin`
At the top of the page, three tabs control which mode is active. The sidebar panel and available options change depending on which mode is selected.
### Display Tab
Use this tab to configure a Display URL for showing the indoor map on a TV, kiosk, or digital signage display. The generated URL loads a locked, non-interactive map view designed for passive viewing.
#### Camera Position
This section controls the map's viewport — what the viewer sees on screen. These values can be set by typing numbers into the fields or by directly interacting with the map (panning, zooming, tilting, and rotating). The fields update automatically as the map is moved.
| Field | Description | Range |
| --------- | -------------------------------------- | ------------------------------------ |
| Latitude | North-south position of the map center | -90 to 90 |
| Longitude | East-west position of the map center | -180 to 180 |
| Zoom | How close the map is zoomed in | 0 (world view) to 24 (extreme close-up) |
| Tilt | The 3D tilt angle of the map | 0° (top-down) to 90° (edge-on) |
| Rotation | Compass heading / rotation of the map | 0° to 360° |
#### Screen Position
This section controls where the physical screen or TV is located on the map and which direction it faces.
| Field | Description |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Facing Direction | A slider (0–360°) that sets which compass direction the TV screen faces. The tool also displays the "user-facing" direction — the opposite side of the TV, representing what the person standing in front of it sees. |
| Drag & Drop Marker | A TV icon appears on the map that can be dragged to the exact physical location of the screen. Right-clicking the map and selecting "Move Screen Here" repositions it instantly. |
#### Additional Settings
This collapsible section (collapsed by default) contains extra display options.
| Setting | Type | Description |
| ---------------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Show Blue Dot Facing Screen | Checkbox | When enabled, a Blue Dot (simulated user position) appears in front of the TV, facing toward the screen. This gives viewers a "You Are Here" reference point. |
| Show QR Code | Checkbox | When enabled, a QR code is overlaid on the display so passersby can scan it to open the map on their phone. If Blue Dot is not shown, this QR code opens the general map homepage without a Blue Dot. |
| Tracking ID | Text field | An optional identifier for the QR code (e.g., `lobby-tv-1`, `parking-lot-east`). Used for analytics to track which QR codes are being scanned. |
| Show Floor Header | Checkbox | When enabled, a banner at the top of the display shows the current floor name, subtitle, and building or map group name. |
| Language | Dropdown | Sets the language for the display. Only appears if the venue supports multiple languages. |
| Priority Categories | Tag input | Categories whose labels are given visual priority on the map and shown more prominently. Type to search and select from available categories. |
| Hidden Categories | Tag input | Categories whose labels are hidden from the map display entirely. Type to search and select from available categories. |
#### Generating the Display URL
At the bottom of the panel, two action buttons are available:
| Button | Action |
| -------- | ------------------------------------------------------------------------------------ |
| Copy URL | Copies the fully configured display URL to the clipboard. |
| Preview | Opens the configured display view in a new browser tab to verify the screen output. |
### Print QR Tab
Use this tab to generate a QR Code URL and downloadable QR code image. Visitors scan the QR code to open the map on their phone, pre-set to their current location with a "You Are Here" Blue Dot.
#### Location & Camera Settings
The following fields control where the Blue Dot appears and how the map is presented when a visitor scans the QR code. These values can be set by typing directly into the fields or by interacting with the map (panning, zooming, and rotating). The fields update automatically as the map is moved.
| Field | Description | Range |
| --------- | --------------------------------------------------------- | ----------- |
| Latitude | The latitude where the QR code sign is physically located | -90 to 90 |
| Longitude | The longitude where the QR code sign is physically located | -180 to 180 |
| Zoom | How zoomed-in the map appears when scanned | 0 to 24 |
| Rotation | The initial compass heading when the map opens | 0° to 360° |
#### QR Code Options
| Field | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------ |
| Show Bearing Cone | When enabled, the map shows a directional cone indicating which way the visitor is facing when they scan the code. |
| Tracking ID | An optional identifier for analytics (e.g., `entrance-A`, `gate-12`). Helps track which physical signs generate the most scans. |
| Language | Sets the language for the experience after scanning. Only appears if the venue supports multiple languages. |
#### Nearby Categories
The Nearby Categories field controls which categories appear in the "What's nearby" section that visitors see after scanning a QR code. This is different from Priority/Hidden Categories in the Display tab, which affect map label visibility.
| Field | Type | Description |
| ------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Nearby Categories | Tag input | Overrides which categories appear in the "What's nearby" section. Type to search and select from available categories. When set, only locations in the selected categories appear in the nearby list. When all categories are removed, the "What's nearby" section is hidden entirely. If left at the default, the venue's standard categories are shown. |
The corresponding URL parameter values:
| Parameter Value | Meaning |
| --------------------------------- | -------------------------------------------------- |
| `nearbyCategories=id1,id2,...` | Show only these categories in "What's nearby" |
| `nearbyCategories=none` | Hide the "What's nearby" section entirely |
#### Generating & Downloading the QR Code
The following actions are available at the bottom of the configuration panel:
| Button | Action |
| ---------------- | ---------------------------------------------------------------------------------------------- |
| Generate QR Code | Creates a QR code image in the panel based on the current configuration. |
| Preview as User | Opens the Start From Here URL in a new tab, simulating what a visitor would see after scanning. |
| Copy URL | Copies the generated URL to the clipboard. |
| Save Image | Downloads the generated QR code as a PNG image file, ready for printing. |
A phone frame preview also appears on the map showing approximately what the visitor will see on their mobile device after scanning the QR code.
### Deep Link Tab
Use this tab to create a URL that opens the map directly to a specific screen or state — a particular location profile, a category view, directions between two points, or the home screen with a specific tab selected. This is useful for embedding links in emails, digital signage buttons, kiosk menus, or anywhere a one-tap shortcut to a specific map experience is needed.
At the top of the Deep Link panel, select which screen the link should open:
| Target | What It Opens |
| ---------- | ------------------------------------------------------------------------------ |
| Home | The map home screen, optionally with a specific tab selected |
| Category | A category listing page (e.g., "Food & Drinks") |
| Location | A specific location's profile or an embeddable share card |
| Directions | Turn-by-turn directions between two locations, or an embeddable share card |
#### Target: Home
| Field | Description |
| ------------- | ---------------------------------------------------------------------------------------------------- |
| Tab | Which tab to open by default: Popular, Amenities, Deals, Events (only tabs available for the venue are shown) |
| Camera Fields | Latitude, Longitude, Floor, Zoom, Heading, Tilt — same behavior as Display mode |
| Language | Sets the language for the experience. Only appears if the venue supports multiple languages |
#### Target: Category
| Field | Description |
| ------------- | ---------------------------------------------------- |
| Category | Select a category from the venue's category list |
| Camera Fields | Latitude, Longitude, Floor, Zoom, Heading, Tilt |
| Language | Sets the language for the experience |
#### Target: Location
| Field | Description |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Location | Select a location from the venue |
| Instance | If the location spans multiple floors or areas, choose which instance to focus on |
| View Mode | **Interactive** — opens the full location profile inside the app. **Share Card** — opens a minimal embeddable card |
| Share Card Style | _(Only when View Mode is Share Card)_ **QR Code** — the card displays a QR code linking to the location. **Open Button** — the card displays a button that opens the full app |
| Language | Sets the language for the experience |
#### Target: Directions
| Field | Description |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------ |
| From | Starting location |
| To | Destination location |
| View Mode | **Interactive** — opens full turn-by-turn directions in the app. **Share Card** — opens a minimal embeddable card |
| Share Card Style | _(Only when View Mode is Share Card)_ **QR Code** or **Open Button** |
| Language | Sets the language for the experience |
#### Generating the Deep Link URL
At the bottom of the panel, two action buttons are available:
| Button | Action |
| -------- | ------------------------------------------------------------------------------------ |
| Copy URL | Copies the configured deep link URL to the clipboard. |
| Preview | Opens the URL in a new browser tab to verify the experience. |
### Lock / Unlock Fields
Each numeric camera field (Latitude, Longitude, Zoom, Tilt, Rotation) has a lock button (padlock icon) next to it.
| State | Behavior |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Unlocked (default) | The field updates automatically when interacting with the map. |
| Locked | The field value is frozen. Map interactions will not change it. This is useful for setting one value (e.g., zoom) and then adjusting others without losing it. |
For example, to keep zoom at 20 while panning to a different area, lock the zoom field at 20 and then pan the map freely — the zoom will remain at 20.
### Category Filtering
Both Priority Categories and Hidden Categories (available in the Display tab) use a tag-style input:
1. Click the input field and start typing a category name.
2. An autocomplete dropdown appears with matching categories from the venue.
3. Click a suggestion (or press Enter) to add it as a tag.
4. Click the **×** on a tag to remove it.
These settings affect which location labels are visible on the display:
- **Priority Categories** — labels for these categories are shown more prominently.
- **Hidden Categories** — labels for these categories are completely removed from the map.
### Tracking ID
The Tracking ID field (available in the Display and Print QR tabs) allows a human-readable identifier to be assigned to each URL or QR code. This ID is embedded in the URL as a `qrId` parameter.
Best practices for Tracking IDs:
- Use descriptive, location-based names: `lobby-entrance`, `parking-lot-A`, `gate-12-arrivals`
- Keep them lowercase with hyphens (no spaces)
- Make each ID unique per deployment so analytics can distinguish between scan sources
### Common Use Cases
#### Lobby TV Display
A mall wants a TV in their main lobby showing the directory map.
1. Open the URL Configurator and select the **Display** tab.
2. Pan and zoom the map to show the desired view of the mall.
3. Adjust **Tilt** to add a 3D perspective if desired.
4. Drag the TV marker to the lobby's physical location.
5. Set the **Facing Direction** to match which way the TV faces.
6. Enable **Show Blue Dot Facing Screen** so visitors see "You Are Here".
7. Enable **Show QR Code** so visitors can scan to get the map on their phone.
8. Set a **Tracking ID** like `main-lobby-tv`.
9. Enable **Show Floor Header** to display the floor name.
10. Click **Preview** to verify, then **Copy URL** and provide it for the display system.
#### Parking Lot QR Code Sign
An airport wants QR codes on posts in the parking garage so travelers can scan and navigate inside.
1. Open the URL Configurator and select the **Print QR** tab.
2. Pan the map to the parking lot entrance location.
3. Set the **Rotation** to match the direction visitors face when approaching the sign.
4. Enable **Show Bearing Cone** so visitors see their orientation after scanning.
5. Set the **Tracking ID** to `parking-garage-level-2`.
6. Click **Generate QR Code**.
7. Click **Save Image** to download the QR code PNG for printing.
#### Multi-Language Venue
A stadium supports English and French. Displays in the French section should render in French.
1. Open the URL Configurator and select the **Display** tab.
2. Configure the camera and screen position as usual.
3. In **Additional Settings**, select **French** from the **Language** dropdown.
4. Click **Copy URL** — the URL will include `lang=fr` and the display will render in French.
#### Kiosk Quick-Link Buttons
A mall wants a kiosk with buttons that jump directly to specific locations or categories.
1. Open the URL Configurator and select the **Deep Link** tab.
2. Set the target to **Location**.
3. Search and select the desired location (e.g., "Guest Services").
4. If the location has multiple instances, select the correct one.
5. Leave View Mode as **Interactive** so visitors get the full profile.
6. Click **Preview** to verify, then **Copy URL**.
7. Repeat for each button or location needed.
8. Provide the URLs to the kiosk software vendor for button configuration.
#### Embeddable Directions Card
An airport wants to embed a directions card on their website that shows how to get from Arrivals to a specific gate.
1. Open the URL Configurator and select the **Deep Link** tab.
2. Set the target to **Directions**.
3. Select the "From" location (e.g., Arrivals Hall) and the "To" location (e.g., Gate 12).
4. Set View Mode to **Share Card**.
5. Choose **Open Button** as the share card style.
6. Click **Preview** to verify the embed appearance.
7. Click **Copy URL** and embed it in an iframe on the website.
### FAQ
**Can multiple URLs be generated for the same venue?**
Yes. Each URL is independent. Different views, floors, languages, and configurations can each have their own URL. There is no limit to the number of URLs that can be generated.
**Does the generated URL expire?**
No. The URL is a set of parameters that the web app reads at load time. As long as the venue is deployed and accessible, the URL will work.
**What happens if venue data changes (stores added, floors renamed)?**
The URL uses camera coordinates and category names, not specific store IDs. If a category is renamed, the URL may need to be regenerated with the updated category name. Camera position and floor settings will remain valid.
**What is the difference between the Display QR code and the Print QR code?**
The Display QR (in the Display tab) is an on-screen overlay shown on the TV itself — visitors scan it while looking at the display. The Print QR (in the Print QR tab) is a standalone QR code image designed to be printed and placed on a physical sign independent of any screen.
**What is the difference between the Deep Link tab and the other two tabs?**
Display generates a non-interactive, locked map view for screens. Print QR generates a QR code image for physical signs that opens a "You Are Here" experience. Deep Link generates a URL that opens the map to a specific screen (home, category, location profile, or directions) — it is designed for digital links, not physical signs or passive displays.
**Can the Deep Link tab create an embeddable card?**
Yes. When the target is Location or Directions, the View Mode can be set to "Share Card", which generates a URL to a minimal embeddable card with either a QR code or an "Open" button. This is useful for iframes on websites or in email campaigns.
**What does `nearbyCategories=none` do in a QR Code URL?**
It hides the "What's nearby" section entirely on the current-location page. This is useful when the QR code is placed in a context where nearby suggestions are not relevant, such as a single-purpose sign directing visitors to a specific desk.
**Is any setup required on the customer's side?**
No special setup is needed. For displays, the customer loads the generated URL in a web browser on their display device (TV, kiosk, tablet). For QR codes, they print and place the image wherever it is needed.
**What does `origCtx=physical` mean in the QR Code URL?**
This parameter tells the app that the visitor arrived via a physical QR code scan (as opposed to a shared link or bookmark). It enables the "You Are Here" experience and can be used for analytics to distinguish physical scan traffic.
### FAQ
# FAQ
This page contains answers to frequently asked questions about Mappedin Web.
## Which browsers are supported?
Mappedin Web supports the recent versions of the major web browsers listed below. Some older version may work, however they are not supported.
- Chrome
- Edge
- Firefox
- Safari
- No IE support
## The map is not visible after following the integration guide
This can often be caused by a parent `` not having a height. The map fills the height and width available to it, so any wrapper or parent divs must have an adequate height set. To determine if this is the issue, modify the parent `div` in the browser's developer tools to have the following attributes:
```css
position: relative;
height: 1000px;
```
## The map element is obstructed on mobile by the URL bar
On mobile devices it's important to give the map as much space as possible for the best user experience. If the map is relatively positioned on mobile, and height is based on viewport and not a full screen height (i.e. 80vh), the map can be obstructed by the title bar of the browser. Using
Small Viewport Height (svh) can help to resolve this issue.
**Small Viewport Height (svh)** refers to the page space available when dynamic toolbars are visible. This value does not change when toolbars are shown or hidden.
By using svh instead of vh, it ensures that the map will be fully visible when initially loaded on a mobile device and not be blocked by the URL bar. To learn more about svh and lvh, look at the web.dev blog post: The large, small, and dynamic viewport units
An alternative proposed by CSS Tricks uses Javascript to calculate a custom viewport height value and then set an additional height value on the element, keeping the old one as a fallback if a browser doesn’t support CSS variables:
```js
function recalculateHeight() {
document.documentElement.style.setProperty('--vh', window.innerHeight / 100 + 'px');
}
window.addEventListener('resize', recalculateHeight);
recalculateHeight();
```
```css
element {
height: calc(100vh - 100px);
height: calc(calc(100 * var(--vh)) - 100px);
}
```
## Is it possible to disable mouse scrolling on the map?
No, this is not supported. The recommended approach is to place the map on a page with as little other content as possible. This ensures a better experience, especially on mobile devices where the map should have as much screen real estate as possible.
## How to integrate Mappedin Web into an Angular application
This StackOverflow post has several answers explaining different methods for loading dynamic scripts into an Angular application. As shown in the integration snippet, the following steps are required:
1. Import styles with `@import url("https://cdn.mappedin.com/web2/release/mappedin-web.css");` in the module CSS file.
2. `window.mappedin` object with appropriate information on the page.
3. The target HTML element ``.
4. Then load `mappedin-web.js` dynamically.
## How to fix conflicting behavior on mobile when pulling down to minimize store profile?
If Mappedin Web is integrated to be a full page integration or an integration where the map is entirely visible without scrolling the page, the pull down action on the store profile could interfere with mobile browsers’ “Pull down to Refresh” functionality. Disable “Pull to Refresh” functionality of the browser with the following CSS:
```css
body,
html {
overscroll-behavior-y: contain;
}
```
## The application UI is very small on mobile devices
To scale the UI properly on mobile devices, Mappedin Web requires the following meta tag in the ``:
```html
```
## Why is the font on the map very small?
Mappedin Web expects a base font size of 16px. Using a smaller or larger base font size will affect the font size of the map. Failing to import the mappedin-web.css file will also affect the font of the map.
## What configuration is required to use Mappedin's EU Servers?
Mappedin has cloud servers hosted in both North America and Europe. Additional configuration is required to access Mappedin infrastructure hosted in Europe.
> Maps are not mirrored in both locations. A single location must be chosen. Contact a Mappedin representative to change locations.
To use Mappedin's EU servers, `useEUServer: true` must be added as shown in the example below.
```html highlight={7}
window.mappedin = {
miKey: {
id: 'your-id',
key: 'your-key',
},
venue: 'your-venue',
useEUServer: true,
};
```
## How to prevent Mappedin app from breaking when navigating away from and back to a page in a React framework like Next.js
`init` and `teardown` functions on the `window` object help manage the Mappedin app's lifecycle in client-side rendered applications like those built with React (e.g., Next.js).
Use `window.mappedinManager.init` and `window.mappedinManager.teardown` to initialize and teardown the app appropriately.
The script id should be `id="mappedin-web"` so that the teardown can locate it correctly.
The following example demonstrates this approach in a React application using the `useEffect` hook:
```
tsx
export default function Map() {
useEffect(() => {
if (window.mappedinManager?.init) {
window.mappedinManager.init();
}
return () => {
window.mappedinManager?.teardown();
};
}, []);
return (
" rel="stylesheet" />
{`
window.mappedin = {
miKey: {
id: "5eab30aa91b055001a68e996",
key: "RJyRXKcryCMy4erZqqCbuB1NbR66QTGNXVE0x3Pg6oCIlUR1"
},
venue: "mappedin-demo-mall",
};
`}
"
id="mappedin-web"
>
Back
);
}
```
### Mappedin Hosted
# Mappedin Hosted
Mappedin hosted Mappedin Web is an instance of Mappedin Web that is hosted by Mappedin.
> Read more about Mappedin Web at https://www.mappedin.com/wayfinding/web-app/
When hosted by Mappedin, a web URL is provided that can be linked to from your website. The link provides a full screen interactive map experience. If you wish to embed Mappedin Web into a web page you host yourself, please refer to the Mappedin Web Integration Guide.
Both solutions offer similar features such as:
- An interactive 3D map
- Location search and category listing
- Turn by turn directions
- A details page for each location including deals, photo gallery, external links, and related locations
- A mobile first, app centric, responsive design
- Deep linking support
In addition to the features listed above, Hosted Mappedin Web offers the benefit of:
- Automatic updates and maintenance handled by Mappedin
- Faster time to launch
- Reduced load on your servers
## Get Started
Follow the steps below to implement Hosted Mappedin Web.
1. **Request Hosting** - Contact Mappedin customer support (support@mappedin.ca) to obtain a Mappedin Hosted Map URL. Include the map venue identifier in the request.
2. **Publish the URL** - Add the URL provided by Mappedin to your web site. It is recommended to open the URL in a new window.
## Try It Out
Click to try out Mappedin Hosted Mappedin Web showing Mappedin Demo Mall.
### Mappedin Web
# Mappedin Web
!Mappedin Web displayed on desktop and mobile devices
This section is for **developers and integrators** looking to embed Mappedin Web into a website. The guides below cover everything from initial setup to deep linking and common troubleshooting.
Mappedin Web is a fully packaged, enterprise-grade indoor mapping solution designed for complex venues such as malls, airports, stadiums, hospitals, and campuses. Once embedded, it is automatically updated as new features and data-driven improvements are released — no additional deployment steps are required.
## Key Features
- **Interactive 3D maps** — Branded, customizable map designs that match venue and tenant branding
- **Location search and categories** — Configurable search and category listings for location discovery
- **Turn-by-turn directions** — Multi-destination wayfinding with accessible routing options
- **Location details** — Profile pages with hours, deals, photo galleries, external links, and related locations
- **Deep linking** — URL-based navigation to specific locations, categories, search results, and directions
!Mappedin Web branded map experience
!Mappedin Web on desktop and mobile
- **Responsive design** — Mobile-first, app-centric layout that adapts from desktop down to small devices
- **40+ supported languages** — UI elements display in the chosen language for a localized experience
- **Accessibility** — WCAG-aligned content and accessible navigation for a barrier-free journey
- **Content Security Policy (CSP) support** — Compatible with strict CSP policies for secure integration
- **Draft and production data** — Toggle between draft and production data sources during development
## Developer Guides
| Guide | Description |
| --- | --- |
| Integration Guide | Step-by-step instructions for embedding Mappedin Web into a website, including HTML snippets, language configuration, CSP requirements, and responsive layout recommendations. |
| Hosted Mappedin Web | A Mappedin-hosted instance of Mappedin Web that provides a full screen map experience via a provided URL, with automatic updates and no server-side setup required. |
| Deep Linking | A complete reference for all supported deep link routes — link directly to locations, categories, search, directions, and QR-based start points. |
| FAQ | Answers to common integration questions covering browser support, mobile viewport issues, Angular integration, React lifecycle management, EU server configuration, and more. |
| Release Notes | A chronological log of Mappedin Web updates including new features, improvements, bug fixes, and breaking changes. |
## Learn More
For product details, demos, and sales inquiries, visit the Mappedin Web product page.
### Release Notes
# Release Notes
Mappedin Web App release notes are posted here and this page will be kept up-to-date as updates are released.
{
// Release notes template:
// https://keepachangelog.com/en/1.0.0/#how
// ## vXX.XX.XX - Month Day, Year
// - Added
// - Changed
// - Improved
// - Deprecated
// - Removed
// - Fixed
// - Security
// - Upgraded - Use when Mappedin JS version goes up. "Changed" when it goes down.
}
## v2.214.0 - May 28, 2026
- Improved Real View overview markers with a themed ring and center dot style
- Changed the camera to fit the full venue when enabling Real View overview
## v2.213.1 - May 28, 2026
- Upgraded the Mappedin JS SDK to fix floating labels drifting off their geometry after resizing on high-density displays
## v2.213.0 - May 27, 2026
- Added a privacy information button and popover to Real View
- Changed the floor-change confirmation button to primary styling during live navigation
- Fixed Blue Dot becoming inactive when getting directions from the current location
## v2.212.0 - May 26, 2026
- Added theme-driven zoom level support for 3D model fade on single-building venues without Dynamic Focus
- Fixed visible gap between 3D model fade-out and interior reveal on Dynamic Focus venues
- Fixed cropping of custom brand logos in floating labels
## v2.211.0 - May 25, 2026
- Improved Real View split-view minimap pose marker rendering using the Blue Dot package
## v2.210.0 - May 25, 2026
- Added live progress dot and continuous fill on the live navigation progress bar
- Fixed gap between Real View and minimap on mobile split view
## v2.209.0 - May 25, 2026
- Added Real View split-view minimap with live pose marker, bearing cone, floor synchronization, and a mobile Split View toggle persisted in the URL
- Improved performance by rendering stadium gate markers as SDK Labels when no logo is set
## v2.208.1 - May 22, 2026
- Changed Live Mode to be disabled on VPS-only venues
- Fixed Live Mode camera not always following the Blue Dot from behind
## v2.208.0 - May 21, 2026
- Added mobile-specific overrides on the venue camera setting theme configuration
- Fixed full-map camera override applying on non-default maps instead of only on the default map
## v2.207.0 - May 20, 2026
- Added Real View overview mode with clickable pose map overlay and pose-launched panorama viewer
- Added theme option to hide the Categories heading on location profile cards
- Fixed step-by-step directions landmark scoring on venues without popularity data
- Fixed Real View URL synchronization flooding browser history during pan
## v2.206.1 - May 15, 2026
- Fixed parking garage 3D shape visibility across floors for multi-polygon venues
## v2.206.0 - May 14, 2026
- Added shareable Real View URLs with pose, bearing, and pitch persistence across refresh and browser navigation
- Added theme-driven dashed path and connection rendering options for wayfinding
- Added theme-driven Dynamic Focus building interiors toggle for campus maps
- Fixed category-symbol icon color rendering on profile cards
## v2.205.1 - May 11, 2026
- Fixed Real View to respect proximityThreshold and prevent through-wall jumps between poses
## v2.205.0 - May 11, 2026
- Added FloatingLabels, interaction, and Real View support for Maker POIs and MapObjects
- Added enableIndoorOutdoorPaths option for navigation
- Fixed low accuracy toast layering and display issues
## v2.204.1 - May 7, 2026
- Fixed path drawing outside live mode by reverting to the Journey API
## v2.204.0 - May 7, 2026
- Fixed default SDK navigation markers appearing when calling Navigation.draw
## v2.203.0 - May 6, 2026
- Added live mode navigation that integrates step-by-step directions with the Blue Dot
## v2.202.0 - May 6, 2026
- Added locate prompt tooltip on the User Location Button
- Fixed Real View directions thumbnails to face the next step (or destination) so the panorama orientation matches the preview
- Fixed Real View remaining visible after closing the location profile pane
## v2.201.0 - May 6, 2026
- Added Azerbaijani language support
- Fixed camera to always recenter and rotate after a VPS scan
- Fixed FloatingLabels enabled state being lost from zoom config when deselecting a category
## v2.200.0 - May 5, 2026
- Fixed Real View loading on EU deployments
## v2.199.2 - May 4, 2026
- Fixed Blue Dot rendering at venues the user is not physically at
## v2.199.1 - May 4, 2026
- Fixed PostHog analytics cookies leaking to customer subdomains
## v2.199.0 - May 4, 2026
- Added Real View immersive perspective view, accessible from directions steps and profile gallery thumbnails
- Improved parking garage rendering with 3D shape overlays and empty lot handling
- Fixed gallery image scaling to viewport width on mobile
## v2.198.0 - April 30, 2026
- Added gray low accuracy toast when only the Blue Dot accuracy ring is shown
- Fixed camera and follow mode orchestration after VPS scan
- Fixed continuous zoom-in when centering on Blue Dot
- Security updates for vulnerable lodash and axios dependencies
## v2.197.0 - April 23, 2026
- Improved VPS camera flow on Android by removing unnecessary AR permission prompt
- Improved VPS camera to consistently request device orientation permission across all entry points
- Improved accessibility by restoring focus to QR code option after closing QR modal
- Improved VPS scanning performance by reducing camera memory usage
- Improved airport gate rendering performance
## v2.196.0 - April 20, 2026
- Added default language override support from theme configuration
- Fixed 3D models not preserving vertical position on floor-independent floors
## v2.195.1 - April 16, 2026
- Fixed geolocation tracking not resuming after VPS camera use
- Fixed blurry QR code export from Start From Here panel
## v2.195.0 - April 14, 2026
- Fixed VPS toast appearing on venues without VPS support
- Fixed search results list overflowing its container
## v2.194.0 - April 14, 2026
- Added Mappedin Maker map support with search, navigation, profile cards, directions, and floating labels
- Added snap-to-map functionality for Blue Dot positioning
- Changed Blue Dot to hide accuracy ring during tracking
- Improved outdoor map camera behavior to maintain full outdoor view during zoom reset
## v2.193.1 - April 8, 2026
- Fixed floating outdoor geometry
## v2.193.0 - April 8, 2026
- Added external tracking identifier support via extId query parameter
## v2.192.0 - April 7, 2026
- Added inactive floor visual effects and dynamic zoom thresholds for multi-floor venues
## v2.191.0 - April 6, 2026
- Added support for theme-configured legal text in mobile legal dropdown
- Added support for default camera position via venue camera settings
- Updated French translations
- Fixed Blue Dot freezing after using Find Me and starting step-by-step directions
- Fixed baggage claim location resolution for airport arrival flights
- Fixed SVG logo color collisions across browser zoom levels
## v2.190.0 - March 27, 2026
- Updated translations
- Fixed VPS bypass query parameter being lost during navigation
## v2.189.0 - March 26, 2026
- Added VPS scanning support outside venues via query parameter
## v2.188.0 - March 24, 2026
- Fixed VPS camera initial zoom and heading
- Fixed Blue Dot centering within safe area during Start From Here flow
## v2.187.1 - March 20, 2026
- Improved accessibility with ARIA live regions for search results
- Improved keyboard accessibility for drag-and-drop reordering in directions
- Improved nearby locations reading order with WAI-ARIA tabs pattern
- Improved focus order for dialogs
- Fixed VPS Find Me flow not completing after position found
- Security updated vulnerable dependencies
## v2.187.0 - March 12, 2026
- Improved default shadow appearance
## v2.186.0 - March 12, 2026
- Added shadow rendering for map display
- Added nearby categories display
## v2.185.1 - March 10, 2026
- Fixed Blue Dot GPS timeout handling during permission detection
- Fixed Blue Dot being locked during step-by-step directions when VPS is active
## v2.185.0 - March 5, 2026
- Added deep link builder tab in Display Mode for generating links to specific map states with configurable camera parameters
- Fixed polygon selection highlight to use the configured selection color
## v2.184.0 - March 3, 2026
- Added Display Mode for configuring non-interactive map views on static screens with QR code for mobile handoff
- Improved embed mode with button interaction option and instance-specific location subtitles
## v2.183.0 - February 27, 2026
- Added user location button with current location display and VPS heading support
- Fixed Blue Dot floor detection when floor level is undefined
## v2.182.0 - February 24, 2026
- Added location marker display in embed mode when a single location is specified
- Changed categories section to use two-line badge layout
- Fixed walking animation theme settings
## v2.181.0 - February 23, 2026
- Added walking man animation for directions
- Fixed Safari clipping SVG icons in category tiles
## v2.180.1 - February 19, 2026
- Fixed polygon height calculation for stadium venues
## v2.180.0 - February 18, 2026
- Added level selector on mobile during step-by-step directions
- Added Blue Dot display when using a target position as departure
- Fixed Dynamic Focus interrupting initial map animation
## v2.179.2 - February 13, 2026
- Fixed Dynamic Focus interrupting map change animations
## v2.179.1 - February 13, 2026
- Added Blue Dot support on desktop with zoom persistence
- Fixed Blue Dot not enabling for venues with only VPS enabled
- Fixed start from here rotation to respect true north
## v2.179.0 - February 11, 2026
- Added right-click context menu for map coordinates and directions on desktop
- Fixed Blue Dot behavior on Safari
## v2.178.0 - February 11, 2026
- Improved Blue Dot with unified implementation
- Fixed default theme color parsing
- Fixed button text color contrast
- Fixed initial map padding and centering on mobile
- Fixed camera zoom when selecting a location on the default map
## v2.177.0 - February 5, 2026
- Improved path rendering
## v2.176.1 - February 5, 2026
- Fixed label visibility in outdoor view and across map groups
## v2.176.0 - February 5, 2026
- Added multi-modal directions support
- Fixed FloatingLabels rendering position
## v2.175.0 - February 3, 2026
- Added support for venues with scale-accurate models
- Improved label display by avoiding duplicate labels at connections
- Fixed save my section for node-based locations
## v2.174.2 - January 30, 2026
- Improved Polish translations
- Fixed clicking on node FloatingLabels
## v2.174.1 - January 29, 2026
- Fixed Dynamic Focus behavior
## v2.174.0 - January 28, 2026
- Added level selector for stadium venues
- Changed FloatingLabels for stadium seating to text-only display
- Fixed map clipping for multi-building venues
- Fixed building focus zoom with Dynamic Focus
## v2.173.0 - January 26, 2026
- Added voids, shadows and overview path support
- Added ad banner support for stadium venues
- Fixed deep link directions when only a departure or destination is provided
- Fixed hidden locations appearing in landmarks
## v2.172.0 - January 14, 2026
- Added automatic gate routing for airport directions
- Fixed location state not showing when no categories are assigned
- Fixed location tile padding
## v2.171.0 - January 8, 2026
- Added VPS bearing support for step-by-step directions
## v2.170.0 - January 6, 2026
- Fixed malformed SVG in location labels
## v2.169.1 - December 17, 2025
- Fixed level selector for right-to-left languages
- Fixed language updates on Flat Labels
## v2.169.0 - December 17, 2025
- Added keyboard arrow and zoom controls for map navigation
- Added accessible location detection
- Fixed venue type detection for stadiums
- Fixed map text rotation
## v2.168.0 - December 15, 2025
- Improved step-by-step directions with venue-specific settings
## v2.167.1 - December 10, 2025
- Fixed flight times to display according to venue timezone
## v2.167.0 - December 8, 2025
- Added Swedish language support
- Fixed translated amenity category names
- Fixed building selector text for single building venues
## v2.166.5 - December 5, 2025
- Upgraded SDK with Dynamic Focus fix
## v2.166.4 - December 4, 2025
- Improved accessibility
- Fixed connection display
## v2.166.3 - December 3, 2025
- Fixed outdoor map detection
- Fixed path floor conflicts on non-dynamic venues
## v2.166.2 - December 2, 2025
- Added custom font weight support
- Fixed outdoor map reference handling
- Fixed 3D models scale
## v2.166.0 - December 1, 2025
- Added multiple destination support in embed mode
- Fixed label language updates when switching languages
## v2.165.1 - November 27, 2025
- Fixed Blue Dot configuration
## v2.165.0 - November 26, 2025
- Added connection filtering with closed connection handling
- Improved flight search with numeric flight number support
## v2.164.4 - November 25, 2025
- Upgraded Dynamic Focus
## v2.164.3 - November 24, 2025
- Fixed locations without navigation nodes
- Fixed Norwegian and Swedish language defaults on iOS
## v2.164.2 - November 21, 2025
- Added restart icon on final step of mobile step-by-step directions
- Fixed deals, events and promotion labels not displaying
- Fixed FloatingLabels icon display
## v2.164.1 - November 19, 2025
- Fixed location label ordering
## v2.164.0 - November 19, 2025
- Added profile card minimize states
- Fixed level selector positioning
- Fixed FloatingLabels visibility when selecting categories
## v2.163.1 - November 18, 2025
- Fixed stadium level selector styling
## v2.163.0 - November 18, 2025
- Added marker fading
- Added path overview for directions
- Added home screen layout variants
- Added ad banner support
- Added locations without navigation nodes to search results
- Improved underground level display
- Improved polygon color when using category focus
- Improved mall zoom level settings
- Updated icons
- Fixed flight subtitle alignment
- Fixed level selector layering
- Fixed building header display for single building venues
- Fixed content fade animation
- Fixed path width on smaller venues
- Fixed 3D model opacity display
- Fixed header scrolling
- Fixed building facade colors
## v2.162.0 - November 7, 2025
- Improved CMS uploaded icon styling
- Fixed rendering on iOS
## v2.161.4 - November 6, 2025
- Fixed language variant support
## v2.161.3 - November 4, 2025
- Fixed security wait times display flickering
## v2.161.2 - October 30, 2025
- Fixed Blue Dot nearest node detection
- Fixed gate marker translations
## v2.161.1 - October 27, 2025
- Fixed marker nodes displaying without location data
## v2.161.0 - October 23, 2025
- Changed parking integration colors
- Fixed security checkpoints handling empty data
- Fixed translation characters in embed mode
## v2.160.1 - October 9, 2025
- Fixed parking badge color when data is missing
## v2.160.0 - October 8, 2025
- Added Cirium flight data attribution
## v2.159.5 - October 7, 2025
- Fixed current location feature
## v2.159.4 - October 6, 2025
- Fixed step-by-step directions translations
## v2.159.3 - October 1, 2025
- Fixed duplicate stadium floors in level selector
- Fixed building locations crash
## v2.159.2 - September 30, 2025
- Improved button click area
- Fixed duplicate location instances
## v2.159.1 - September 26, 2025
- Fixed parent category sort order
## v2.159.0 - September 25, 2025
- Added flight status color support
- Upgraded Blue Dot implementation
- Fixed missing flight airline icons
## v2.158.0 - September 24, 2025
- Added VPS with WebXR support
## v2.157.0 - September 22, 2025
- Added primary category support for FloatingLabels and pins
- Fixed level selector showing on single floor venues
## v2.156.1 - September 17, 2025
- Fixed social media link locale
- Fixed directions button showing for unconnected locations
- Fixed legal links display on desktop
## v2.156.0 - September 16, 2025
- Fixed outdoor map styling from theme settings
## v2.155.1 - September 12, 2025
- Fixed flight feed not appearing in search results
## v2.155.0 - September 11, 2025
- Added custom FloatingLabels color option
- Improved location selection behavior for node-based locations
## v2.154.0 - September 9, 2025
- Added labels for prioritized amenities
- Fixed safe area padding for map UI elements
## v2.153.1 - September 8, 2025
- Fixed level selector padding on desktop
## v2.153.0 - September 8, 2025
- Added embeddable map mode
## v2.152.1 - September 5, 2025
- Upgraded SDK
## v2.152.0 - September 4, 2025
- Improved search results by filtering insignificant locations
- Improved VPS accessibility
- Fixed EU server URL configuration
## v2.151.0 - September 3, 2025
- Added Icelandic language support
## v2.150.3 - August 28, 2025
- Fixed shuttle direction icon
## v2.150.2 - August 25, 2025
- Upgraded SDK
## v2.150.1 - August 21, 2025
- Added language support for embedded snippets
- Fixed default map fallback
## v2.150.0 - August 20, 2025
- Added location-based QR code positioning
- Fixed Blue Dot centering
## v2.149.0 - August 18, 2025
- Added icons for same-level connections
- Improved VPS accessibility
- Fixed language detection from browser settings
## v2.148.0 - August 14, 2025
- Improved departure marker visibility
- Fixed path thickness
- Fixed directions time rounding
## v2.147.0 - August 13, 2025
- Upgraded SDK
- Fixed location context issues
## v2.146.2 - August 6, 2025
- Fixed mobile pinch zoom
## v2.146.0 - August 5, 2025
- Added security checkpoint feature
- Added clickable location markers
- Fixed save as my parking for building-type parking locations
- Fixed horizontal scroll containers
- Fixed mobile QR code display size
## v2.145.2 - July 14, 2025
- Fixed walking times displaying as 0 minutes
- Fixed theme overrides without default theme
- Fixed safe area inset calculation for level selector
- Fixed Blue Dot bearing with inconsistent GPS data
- Fixed Dynamic Focus during step-by-step directions
- Fixed duplicate gates in search results
## v2.145.1 - July 3, 2025
- Removed security checkpoint feature
## v2.145.0 - July 3, 2025
- Added wait times display for security locations
- Fixed shuttle time updates
- Fixed venue special hours parsing
- Fixed shuttle speed
## v2.144.0 - July 2, 2025
- Added analytics hook with sourceMeta for select-location
- Added sourceMeta for select-category and select-event
- Upgraded SDK and closest node logic
- Fixed nodes to be saved as parking
- Fixed analytics not considering polygon
- Fixed global card not expanding to maximum based on event card contents
## v2.143.1 - June 25, 2025
- Fixed label flickering when IPS and VPS enabled
## v2.143.0 - June 19, 2025
- Added name to select-event analytics event
## v2.142.1 - June 18, 2025
- Fixed selecting a location instance
- Fixed level selector subtitle when empty string set
## v2.142.0 - June 11, 2025
- Added search prioritization for airline locations over flights
## v2.141.1 - June 4, 2025
- Fixed cookie settings styles
## v2.141.0 - June 3, 2025
- Added airline icons from solutions bucket
## v2.140.0 - June 2, 2025
- Added updated translations from Phrase
## v2.139.0 - June 2, 2025
- Added flights logic to directions search
## v2.138.0 - May 29, 2025
- Added minimap in v6 SDK
- Added Playwright tests to run on live
- Fixed safe inset padding to all map UI elements
## v2.137.1 - May 22, 2025
- Fixed overview path height and misalignment issues
- Fixed level selector height on mobile
- Fixed level selector scroll issue
## v2.137.0 - May 16, 2025
- Added TAP icon for flight feed
## v2.136.0 - May 15, 2025
- Added overview path default map logic
- Added TikTok social link support
- Fixed focus when map changes for multibuilding venues
- Fixed location state showing on pin
- Fixed node operation hours
## v2.135.1 - May 6, 2025
- Fixed VPS endpoint environment support
- Fixed level selector height with subtitles
- Fixed all locations icons for node with multiple locations
## v2.135.0 - April 23, 2025
- Added updated Thai translations
- Fixed amenity category disable
## v2.134.0 - April 16, 2025
- Added shortName translations for map groups
- Upgraded SDK
## v2.133.0 - April 10, 2025
- Changed icon in preferences button when in airports vertical
## v2.132.1 - April 10, 2025
- Fixed Hebrew translation for top locations
- Fixed follow bluedot focus
- Removed custom font from app-level marker
- Security updated vulnerable dependencies
- Upgraded @emotion/styled from 11.13.0 to 11.14.0
## v2.132.0 - April 2, 2025
- Added single social button with links
- Fixed search category name translations
- Fixed inactive path update when step changes
## v2.131.1 - April 1, 2025
- Fixed SVGs to grow properly
## v2.131.0 - April 1, 2025
- Added icons rendered as SVGs in profile header
- Fixed language parameter for QR code
## v2.130.0 - March 27, 2025
- Added Hebrew and Haitian Creole language support
## v2.129.0 - March 26, 2025
- Added elevation maintenance across map groups
## v2.128.3 - March 25, 2025
- Fixed icon package for various fixes
## v2.128.2 - March 21, 2025
- Fixed nearby location text cutoff for larger text sizes
## v2.128.1 - March 18, 2025
- Fixed event card scrolling
## v2.128.0 - March 13, 2025
- Added multi layout on web
## v2.127.2 - March 10, 2025
- Fixed share menu
- Fixed autocomplete inputs disable
- Fixed new line support on event card descriptions
## v2.127.1 - March 4, 2025
- Fixed path overview
- Fixed drag scroll image gallery
- Fixed stadium polygon highlight for seating
## v2.127.0 - February 26, 2025
- Added custom icon on designated location card header
- Fixed Polish translations
## v2.126.0 - February 24, 2025
- Added gallery updates
## v2.125.0 - February 24, 2025
- Added location state badges
- Fixed search location description with intuitive search enabled
- Fixed navigation back from child category to parent
- Fixed unsupported language logic
- Fixed i18n importing regional language files
- Fixed floating label collision rank knocking off tooltips
- Fixed base URL check for EU
- Fixed sv-fl not loading
## v2.124.1 - February 10, 2025
- Fixed minimum text size for input
## v2.124.0 - February 10, 2025
- Added search result prioritization in departure map group
- Added categories event for custom categories
- Added bearer token for theme
- Added ramp icon
- Added Slovenian translations
- Fixed shuttle stop time of current shuttle trip
## v2.123.1 - February 4, 2025
- Fixed bluedot tooltip flicker
## v2.123.0 - February 3, 2025
- Added customer analytics setup
- Added overview path toggle
- Fixed logic to route from baggage claim if needed
- Fixed destination pins not showing for path overview
## v2.122.0 - January 29, 2025
- Added focus mode to highlight child category locations
- Removed campus map requirement for dynamic focus
## v2.121.0 - January 28, 2025
- Added directory URL params retrieval
- Fixed input disable on hidden tooltips
## v2.120.0 - January 27, 2025
- Removed header fixes for long names or alternate languages
## v2.119.0 - January 21, 2025
- Added higher resolution VPS images for scanning
- Added category filtering with no locations
- Added stadium requests, seating nearby locations, gate icon, polygon highlights
- Added bluedot bearing by default
- Fixed header for long names or alternate languages
- Fixed gate location pin
## v2.118.0 - January 16, 2025
- Added custom walking speed
- Added minimap
- Removed share options by apollo toggle
- Fixed wrong instruction on deep link directions load
## v2.117.0 - January 14, 2025
- Changed walking speed for airports
## v2.114.0 - December 20, 2024
- Improved Polish translations
- Fixed expanded card bug
- Fixed long accessible toggle text
## v2.113.0 - December 18, 2024
- Added Polish Translations
## v2.112.0 - December 17, 2024
- Improved VPS image quality
## v2.111.2 - December 11, 2024
- Fixed localStorage access error
- Fixed compatibility with replaceAll
- Fixed undefined language object error
## v2.111.1 - December 2, 2024
- Fixed minimized card height
## v2.111.0 - December 2, 2024
- Added sdk map worker support
- Bumped cross-spawn from 7.0.3 to 7.0.6
## v2.110.0 - November 28, 2024
- Added vps analytics events
- Improved vps prompts
- Fixed optional legal parameter
- Fixed size of listings
## v2.109.0 - November 26, 2024
- Added PostHog feedback UI
- Added logic to deepLink into unfinished directions
- Added link between posthog and sentry
- Added logic to send color images to vps
- Fixed campus maps level selector scrolling
- Fixed direction pill times
- Improved directions button in mobile parking profile card
## v2.105.0 - November 14, 2024
- Added blue dot focus on load
- Added IPS with VPS integration
- Fixed displaying multiple sets of total locations in profile card
- Bumped sentry/react from 8.35.1 to 8.37.1
## v2.104.0 - November 12, 2024
- Added PostHog
- Improved German translations
- Added Dynamic focus layers for all venue types
- Fixed update icon scaling values
- Fixed to only apply fullMap focusOn logic to overviewPath-enabled venues
- Fixed campus map level selector
- Improved parity with directory
## v2.103.2 - November 11, 2024
- Changed overview path changes behind airports flag.
- Fixed mui component styles.
## v2.103.0 - November 11, 2024
- Fixed to only display path overview for airports.
## v2.102.0 - November 8, 2024
- Improved translations.
## v2.101.4 - November 7, 2024
- Fixed connection icon issues.
- Fixed exit follow mode on mobile SBS interactions.
## v2.101.3 - November 6, 2024
- Improved VPS
- Changed locations inside translations to total.
- Changed to only use icon scaling on airports.
## v2.101.1 - November 5, 2024
- Removed showBearing.
- Fixed passing venue meta to mappedin theme.
## v2.101.0 - November 5, 2024
- Added airports beta features.
## v2.100.0 - November 4, 2024
- Added more descriptive event card badges and implement useCards hook.
- Fixed level selector when subtitle is an empty string.
## v2.99.0 - October 30, 2024
- Changed EU server configuration.
- Improved VPS with IPS.
- Fixed floating location pin.
## v2.98.0 - October 24, 2024
- Added VPS with IPS.
- Fixed zoom on VPS marker focus.
- Changed to use patched version of rollup.
## v2.97.1 - October 21, 2024
- Changed to migrate styled components.
- Changed to re-initialise locationsStore when language changes.
- Bumped floating labels package.
## v2.97.0 - October 16, 2024
- Changed to use apps SDK Mappedin logo.
- Bumped SDK.
## v2.96.0 - October 15, 2024
- Added support for Thai font.
- Bumped i18next-http-backend from 2.5.2 to 2.6.2.
- Bumped styled-reset from 3.0.3 to 4.5.2.
- Fixed styles, am pm text and directions text borders.
## v2.95.0 - October 11, 2024
- Added error boundary and sentry logging.
- Fixed listing focus states.
## v2.94.1 - October 8, 2024
- Bumped SDK.
- Added Thai language to mapping.
- Changed to use patched version of actions/downlaod-artifact.
## v2.94.0 - September 30, 2024
- Changed pin background and icon color for LAX custom icons.
## v2.93.0 - September 26, 2024
- Changed camera to not rotate if path segment is too short.
- Fixed location status text being all lowercase.
## v2.91.0 - September 24, 2024
- Bumped SDK.
- Bumped apps-sdk.
- Changed to hide share options in iFrame.
## v2.90.0 - September 16, 2024
- Changed to no update zoom limit when focusing on focusLayer.
- Fixed build old space size.
## v2.89.0 - September 13, 2024
- Bumped icons and floating labels.
- Improved VPS scan prompts.
- Fixed language letter alignment and Japanese translations.
## v2.88.0 - September 12, 2024
- Added events card.
- Added last scanned location icon.
- Changed to rotate camera to VPS marker direction.
- Improved VPS scanned image performance.
- Update icons and floating labels packages.
- Bumped micromatch from 4.0.4 to 4.0.8.
- Fixed zoom on VPS found.
- Fixed to focus on VPS location when found.
- Fixed to set marker always visible.
- Fixed focus selected location when user position.
- Fixed VPS last location item.
- Changed last scanned label.
- Removed default white color.
## v2.87.0 - September 4, 2024
- Added promotions card to Web.
- Added VPS camera overlay.
- Improved camera component for VPS.
- Added logic to determine location.
- Added last scanned locations list item.
- Changed camera to focus on VPS position once found.
- Changed to only show VPS pin if that is departure.
- Added quaternion rotation for VPS pin.
- Changed VPS pin rotation to quaternion values.
- Improved VPS pin styles.
- Added VPS pin.
- Updated icons package.
- Added notification for browser permission error.
- Added text to VPS marker.
- Added VPS sessionId.
- Updated icons package to 7.9.0.
- Added VPS progress bar.
- Bumped axios from 1.6.5 to 1.7.4.
- Changed staging url to baseURL.
- Improved find me flow.
- Changed to refocus on direction input when closing VPS states.
- Fixed VPS camera aspect ratio.
- Fixed get directions when found path.
- Fixed to try populating path correctly.
- Fixed to always show VPS button.
- Fixed dir find me.
- Improved VPS direction find me wrapper styles.
- Fixed the hours of operations for RTL languages.
- Changed to 1 day time limite to VPS camera permissions.
- Fixed box-shadow render on iOS.
## v2.86.0 - August 15, 2024
- Added VPS find me button.
## v2.85.0 - August 15, 2024
- Improved bluedot button.
## v2.84.3 - August 9, 2024
- Changed am and pm to uppercase.
## v2.84.2 - August 7, 2024
- Fixed Safari popup shadow.
- Web fixes.
## v2.84.1 - July 29, 2024
- Fixed subheading styles
- Improved lodash bundle size.
## v2.84.0 - July 25, 2024
- Improved language selector.
## v2.83.1 - July 24, 2024
- Fixed path focus bug.
## v2.83.0 - July 24, 2024
- Bumped SDK for basemap images.
## v2.82.0 - July 23, 2024
- Changed profile card header.
- Improved profile layout.
- Improved card buttons.
- Added dynamic stadium zoom.
- Fixed closed hours display.
- Fixed layout.
- Fixed text alignment to list items.
## v2.80.3 - July 10, 2024
- Bump ws from 8.12.1 to 8.18.0.
- Fixed inconsistency in direction pill calculation.
## v2.80.0 - July 3, 2024
- Added prevent zoom level change.
- Fixed empty tooltip.
## v2.79.0 - June 28, 2024
- Added random locations.
## v2.77.0 - June 26, 2024
- SDK version bump.
- Added display node names.
- Added prepend word gate on card.
- Bumped braces from 3.0.2 to 3.0.3.
## v2.76.0 - June 13, 2024
- Added airport watermark link override.
## v2.75.0 - June 10, 2024
- Added portal instructions.
- Fixed multi-destination location sorting.
## v2.74.0 - June 6, 2024
- Bump floating labels icons.
## v2.73.1 - June 5, 2024
- Bump floating labels package.
- Fix to remove setting safe area insets on recenter.
## v2.73.0 - June 3, 2024
- Return nearby locations in default language if current language is not supported.
- Update translations.
- Fix location-tile iOS issue.
- Fix to load embeded URLs in iframe.
- Improved search results to be more keyboard accessible.
- Bump floating labels package.
## v2.72.0 - May 29, 2024
- Changed to use APIv1 proxy for theme to simplify permissions.
- Changed to use api-gateway style URL for theme,
- Improved use of floating labels package.
## v2.71.0 - May 28, 2024
- Added text wrapping for categories.
- Fixed level selector pins not rendering with no path.
- Fixed accessible toggle.
- Improved flights and shuttles UI.
## v2.69.0 - May 21, 2024
- Updated location tile compoent & text wrapping.
- Fixed tooltip jumping.
## v2.68.0 - May 16, 2024
- Update icons and amenity icon map.
- Fixed multi-destination tooltip labels.
- Improved airport search.
## v2.67.0 - May 10, 2024
- Package bump.
## v2.66.0 - May 1, 2024
- Added shuttle estimations.
## v2.65.0 - April 30, 2024
- Added location from reference point node to location inside.
## v2.64.3 - April 29, 2024
- Fix init and teardown console errors.
## v2.64.2 - April 29, 2024
- Fixed campus maps zoom levels.
## v2.64.1 - April 25, 2024
- Fixed crash when referencing a location that doesn't exist.
## v2.64.0 - April 22, 2024
- Added shuttles directions card.
- Added shuttles step by step directions.
- Updated SDK version.
- Fixed Japanese keyboard issue on iOS.
## v2.63.0 - April 15, 2024
- Added shuttles placecard.
- Fixed hours display when using 24 hour time.
- Improved accessibility.
## v2.62.0 April 12, 2024
- Enable theme overrides.
## v2.61.1 - April 10, 2024
- Fixed some Spanish translations.
## v2.61.0 - April 9, 2024
- Upgraded Mappedin JS.
## v2.60.0 - April 9, 2024
- Improved flights keyboard accessibility.
## v2.59.0 - April 8, 2024
- Added language selection as a deep-link option.
- Added toggle to use flights integration on theme.
- Fixed an issue where directions could be dragged far outside the card limits.
## v2.58.1 - April 4, 2024
- Improved parking list.
## v2.58.0 - April 3, 2024
- Added `init` and `teardown` functions to reinitialize the map.
- Added parking as a list item.
- Added cards for parking places.
## v2.57.0 - March 26, 2024
- Added labels for shuttles.
- Fixed language selection on initial load.
- Fixed reference points not always showing on profile cards.
## v2.56.0 - March 26, 2024
- Added a language selector for supported maps.
- Improved accessibility of list boxes.
## v2.55.0 - March 25, 2024
- Improved profile card appearance for locations with multiple polygons.
- Improved flight check-in logic.
- Improved description keyboard accessibility.
- Fixed cases where subcategories were not all displaying.
## v2.54.0 - March 20, 2024
- Improved wait time display.
- Fixed appearance when location subtitle did not exist.
## v2.53.0 - March 19, 2024
- Upgraded Mappedin JS.
## v2.52.0 - March 18, 2024
- Added option for a new map appearance.
- Upgraded icons.
## v2.51.0 - March 14, 2024
- Added a "relocated" location state.
- Fixed unknown locations to now reroute app to the start.
## v2.50.0 - March 14, 2024
- Added nearby `referencePoint`.
## v2.49.0 - March 11, 2024
- Added ability to upload icons for categories.
- Improved flights category to only show when data is present.
- Improved naming of airport gates.
- Fixed icon for saved gates always appearing as an airplane.
## v2.48.0 - February 29, 2024
- Added feature to highlight all locations in a selected category.
- Added ability to see map while in category view on mobile.
- Added option to use venue icon instead of venue logo when available.
## v2.47.1 - February 27, 2024
- Fixed issue with Floating Labels in map editor demo.
## v2.47.0 - February 23, 2024
- Improved French translations.
- Fixed multi-destination routing behavior when locations had many polygons or nodes.
## v2.46.0 - February 20, 2024
- Added translations for Polish, Slovenian, and Croatian.
- Improved app navigation.
- Fixed website button not appearing on profile card.
- Fixed an issue where top locations may duplicate.
## v2.45.1 - February 14, 2024
- Improved security.
## v2.45.0 - February 12, 2024
- Added deep-linking option for `my-section=true`.
- Improved appearance of directions for some venues.
- Fixed the position of the amentity category in the list.
## v2.44.1 - February 9, 2024
- Fixed a potential crash when locations were missing categories.
## v2.44.0 - February 8, 2024
- Added back button to flight search.
- Improved appearance of OSM attribution.
- Fixed cases where categories would have no icon.
## v2.43.0 - February 5, 2024
- Added ability for line breaks in long profile card descriptions.
- Improved Japanese translations.
## v2.42.0 - February 2, 2024
- Added parking integration for some maps.
## v2.41.0 - February 1, 2024
- Fixed Floating Labels rendering at floor level.
## v2.40.2 - January 31, 2024
- Fixed cases where amenity logo would show incorrectly.
- Fixed rare issue preventing the map from rendering.
## v2.39.0 - January 29, 2024
- Added option to hide category icons based on theme.
- Changed the multi-destination feature to be more easily accessed.
- Fixed the share button on Android.
## v2.38.1 - January 25, 2024
- Improved animations.
## v2.38.0 - January 22, 2024
- Improved nearby locations.
- Changed optional path arrows to be static, instead of animated.
## v2.37.0 - January 17, 2024
- Added full screen navigation on mobile.
- Improved airport check-in routing logic.
- Upgraded icons.
- Fixed an issue where embedded gallery URLs without an image would error.
## v2.36.0 - January 15, 2024
- Added support for outdoor view for EU customers.
- Added a way to embed a gallery URL in an iframe.
- Upgraded Mappedin Mappedin JS version.
## v2.35.2 - January 8, 2024
- Fixed cases where the browser would scroll to the top of the page.
- Fixed cases where the level selector would cause the page to jump.
## v2.35.0 - January 4, 2024
- Added highlighted current step in directions view.
- Added routing from arrival flights.
- Improved accessibility announcements when directions change.
- Improved accessibility for tooltips.
- Improved airport baggage claim logic.
- Improved step by step navigation if tooltips are selected.
- Changed the accessible toggle to remain always visible.
- Changed verbiage to remove the term "Exit" on connections.
- Fixed location card width when opening categories.
- Fixed incorrect walking times on instructions.
- Fixed blue dot follow mode instructions getting out of sync.
- Fixed default map when selecting map groups.
- Fixed level selector not scrolling current map into view.
- Fixed camera focus when directions span multiple maps.
- Fixed three line category names.
- Fixed behavior when selecting instructions on a different map.
## v2.34.0 - December 14, 2023
- Added phone number display on web.
- Improved Japanese translations.
## v2.33.2 - December 4, 2023
- Fixed an issue where the search input would scroll the page on iOS.
## v2.33.1 - December 4, 2023
- Improved translations.
- Fixed focus on gallery images.
- Fixed mobile start button text contrast.
- Fixed step by step directions when nodes without names are included.
- Fixed some cases where floating labels were not showing.
## v2.33.0 - November 29, 2023
- Improved Japanese translations.
- Changed departure input placeholder to "Choose Departure".
- Changed background color of images.
## v2.32.0 - November 27, 2023
- Upgraded Mappedin icons package.
## v2.31.0 - November 27, 2023
- Added top down view option to theme.
- Improved social media logos.
- Fixed an issue where floating labels may render while a logo image is present.
- Fixed cases where the incorrect level was being shown in the selector.
- Fixed spacing when two images were shown in the gallery.
- Fixed path error message when connecting two nodes without names.
- Fixed cases of duplicate labels on polygons with multiple entrances.
## v2.30.0 - November 20, 2023
- Improved translations for all languages.
- Improved UI padding on mobile.
- Fixed instances where the list items icon was present when it shouldn't be.
- Fixed accessibility for keyboard close button.
## v2.29.1 - November 16, 2023
- Fixed Mobile UI styling.
## v2.29.0 - November 16, 2023
- Updated UI of entire app with a new look and feel.
## v2.28.0 - November 6, 2023
- Added Malaysian language/translation support.
## v2.27.2 - October 23, 2023
- Fixed visual clarity for Flat Labels, logos, and rendered text on map zoomed out
## v2.27.1 - October 10, 2023
- Upgraded Mappedin icons package to the latest version to use the new icon sets.
## v2.27.0 - August 21, 2023
- Added Top Locations to CMS.
## v2.26.3 - August 8, 2023
- Added interactivity to the multi-destination icons.
- Added a grey background to location list icons when using polygon image.
- Changed `pt` localization for "amenities".
- Fixed inconsistent styling for location list icons.
## v2.26.2 - July 27, 2023
- Fixed an issue where hovering polygons would occasionally crash
## v2.26.1 - July 27, 2023
- Upgraded Mappedin JS version.
## v2.26.0 - July 25, 2023
- Added `en-GB` localization.
- Added "Find Closest" button to locations dropdown.
- Changed level selector appearance.
- Upgraded Mappedin JS version.
- Fixed selected location tooltip not appearing when label icons are enabled.
- Fixed duplicate amenity and category headers.
## v2.25.5 - July 17, 2023
- Changed the pin for polygons with multiple locations to display the parent instead of the first in the list.
## v2.25.4 - July 12, 2023
- Upgraded Mappedin Mappedin JS version to v5.15.2.
## v2.25.3 - July 12, 2023
- Upgraded Mappedin Mappedin JS version to v5.15.1.
- Fixed warnings in console.
## v2.25.2 - July 10, 2023
- Added category icons for stadium venue type.
## v2.25.1 - July 6, 2023
- Changed `fr-CA` translation of "Amenities" to "Services".
- Upgraded Mappedin Mappedin JS version to v5.14.1.
## v2.25.0 - July 5, 2023
- Added French (Canada) translations `fr-CA`.
- Changed Mappedin Mappedin JS version to v5.10.1.
## v2.24.0 - June 28, 2023
- Added icons to FloatingLabels. These are automatically enabled for connections and must be configured for other amenities.
- Added experimental theme toggle for outdoor maps.
- Added experimental theme toggle for ambient occlusion.
- Added a locations accordion to the profile card of locations with sub-locations.
- Added polygon-specific selection to locations with sub-locations.
- Changed FloatingLabels so they are now clickable.
- Changed the height of the departure marker.
- Removed floor subheading on single-floor venues.
- Fixed console errors caused by Mappedin internal analytics.
- Fixed Estonian translations.
- Fixed alignment of top-amenities when there are less than 4.
- Fixed header title overflow in search results.
- Fixed alignment of Saved Location markers.
- Fixed appearance of search results with no logo attached.
## v2.23.2 - May 31, 2023
- Fixed the departure marker appearing to float above the map.
- Fixed an issue when selecting unique locations which share a common name.
## v2.23.1 - May 29, 2023
- Upgraded Mappedin JS version to v5.10.0.
## v2.23.0 - May 25, 2023
- Default text color on polygons now automatically adjusts to improve contrast
- Hover text color on polygons now automatically adjusts to improve contrast
- Improve Spanish localization
- Fix instances of scrollbar hijacking on iOS Safari
- Fix instances where selecting a polygon with multiple locations returned the wrong location
- Fix instances of location tag text being cut off
## 2.22.0 - May 11, 2023
- Improve operation hours appearance for locations open past midnight
- Update accessibility routing verbiage for venues without escalators
- Adapt the level selector for multi-destination directions
- Fix alignment of search icon in results
- Fix floating labels not showing when a location has an image
## v2.21.1 - May 4, 2023
- Fix locations without categories showing an empty tab
- Fix rendering of closing hours in some timezones
## v2.21.0 - May 2, 2023
- The departure icon has been changed with improved behavior for multi-destination directions
- Fix store closing time being truncated if it's not on the hour
- Fix polygon highlight color when using 3 digit hex codes
## v2.20.0 - April 27, 2023
- Text color on highlighted destination or departure will now adjust to improve readability
- Categories have been moved to their own row on the profile card
- Improvements to search results
- When viewing multiple destinations, inactive routes are now clickable
- Added drag and drop to reorder destinations in directions menu
- Fix labels on selected polygons changing after switching floors
- Fix path icon appearance when removing destinations from directions
## v2.19.1 - March 30, 2023
- Upgrade to Mappedin Mappedin JS to v5.6.1.
- Improved search and directions results sorting
- Fix category buttons displaying category locations
- Update the max width of the location tooltip text background
## v2.18.1 - March 15, 2023
- Adjustments to default theme
## v2.18.0 - March 15, 2023
- Select start and destination locations by clicking on polygons
- Fix two location labeling related crashes
## v2.16.0 - March 13, 2023
- Upgrade Mappedin Mappedin JS version
- Remove flat label when hovering a selected location
- Fix location description card being cut off on mobile
## v2.15.2 - March 8, 2023
- Improve filtering for featured locations
- The "x" button in search now returns to the home state
## v2.15.1 - March 3, 2023
- Downgrade Mappedin Mappedin JS to v5.1.4
## v2.15.0 - March 2, 2023
- Add support for custom featured locations
- Upgrade to Mappedin Mappedin JS v5.2.0
- Further improvements to polygon selection color handling
## v2.14.1 - February 10, 2023
- Upgrade Mappedin Mappedin JS to v5.1.4 fixing an issue with faded out floating labels caused by `focusOn`
## v2.14.0 - February 10, 2023
- Improvements to polygon selection color handling
- Fixed a delay after clicking "Locate me" -button
## v2.13.1 - February 9, 2023
- Upgrade Mappedin Mappedin JS version to add accessible zoom features
## v2.13.0 - February 6, 2023
- Add support for saving a parking spot for stadiums
- Profile card now displays categories within a map group
- Improvements to Estonian, Finnish, and Portuguese translations
- Back button no longer unexpectedly exits the map group
- Enabled expanding stadium location cards on mobile
- Hide directions button if there's only one building
- Add `/categories` route
## v2.12.1 - January 27, 2023
- Fix state card resize on mobile
## v2.11.1 - December 12, 2022
- Connection tooltips should always be visible
- Security updates
## v2.11.0 - December 7, 2022
- Support custom values for `data-key`
- Upgrade to Mappedin Mappedin JS v5.0.0
- Sort default search results by popularity
- Fix max card height logic
- Remove old resizeobserver dependency
- Improve handling of invisible geometry
## v2.10.5 - November 16, 2022
- Fixed a bug in analytics context setting
## v2.10.4 - October 31, 2022
- Fixed a bug where the new Amenities section would sometimes appear with 0 height
## v2.10.3 - October 26, 2022
- Improved the detection of amenities in the new amenities section
## v2.10.2 - October 24, 2022
- Improve amenities filtering for the new amenities category section
## v2.10.1 - October 21, 2022
- Fixed a bug where `OffscreenCanvas` would sometimes throw errors.
## v2.10.0 - October 17, 2022
- Categories list shows a special section for uncategorized amenities
- Updated Finnish translations
## v2.9.0 - October 11, 2022
- Quick location buttons now scroll horizontally on mobile
- Add a prefix option for `window.mappedin.legalLink`
- Enable showing operation hours in 24 hour time based on language
- Corrected some German translations
## v2.8.1 - September 22, 2022
- Ensure polygons are highlighted correctly after switching maps
## v2.8.0 - September 15, 2022
- Add screen reader support to lists such as directions, categories and search
- Support navigation button colour theming
- Switch line heights to `em` units
- Update selected location subheading when no instances are attached to polygons
## v2.7.3 - September 8, 2022
- Improved Japanese translations
- Fixed the screen space calculation incorrectly indicating no available space
## v2.7.2 - September 6, 2022
- Hide locations that are flagged as hidden in Mappedin CMS
- Make the entire directions breadcrumb clickable during multi-destination wayfinding
## v2.7.1 - September 1, 2022
- Improve profile card expanding behavior on iOS
- Improve step-by-step directions text when arriving at a location
## v2.7.0 - August 24, 2022
- Add support for Norwegian, Estonian, and Czech translations
- Prevent search results from flickering during exit animation
- Updated logic for when to display mobile UI when in portrait orientation
- Updated en-US, ja, fi, fr, and ru translations
## v2.6.0 - August 11, 2022
- Add support for `window.mappedin.useDraftData` option to pull draft mode data
- Minor CSS improvements
- Fix Offline Search properly considering diacritics in tags
### v2.5.2 - August 9, 2022
- Prevent creating two analytics instances and fix context on blue dot analytics
- Correctly populate directions UI when including nodes in navigation
### v2.5.1 - July 27, 2022
- Adjust camera animation when state card is expanded
- Adjust photo gallery image spacing
- Fix analytics configuration
## v2.5.0 - July 21, 2022
- Add proper “roles” to various elements to support screen readers
- Upgrade Mappedin Mappedin JS version to fix Blue Dot analytics events
- Switch maps when a location attached to a node on another floor is selected
- Prevent level selector from scrolling the whole page
### v2.4.1 - June 17, 2022
- Fixed a bug where special search results (e.g. My Location, My Section) couldn't be selected during navigation
## v2.4.0 - June 16, 2022
- Upgraded to v5.0.0-beta.0 of the Mappedin Mappedin JS
- Switched to using the new Offline Search API
### v2.3.2 - June 13, 2022
- Made the accessibility toggle more visible when viewing directions by swapping its position has been swapped with the Share button
- Better logic for determining how language is set by checking the document language and user language if `window.mappedin.language` is not set
- Fixed an issue where deals cards on store profiles and step by step text directions weren’t keyboard accessible
- Security fixes
## v2.3.0 - May 26, 2022
- Security fixes
- The profile card for a location now begins in a collapsed state and can be expanded or collapsed again by swiping, allowing for more of the map to be visible.
### v2.2.5 - May 20, 2022
- Upgraded to 4.0.19 of the SDK to fix a bug where floor change tooltips would sometimes not render
### v2.2.4 - May 19, 2022
- Improved accessibility when viewing location photos
- Improve time display for locations not re-opening for more than 1 day from the current date
- Upgraded to the latest SDK
### v2.2.3 - May 5, 2022
- Security fixes
- Upgraded to version `4.0.17` of the Mappedin Mappedin JS
- Allow CMS to override theme settings
- Fixed an issue where navigating from “My Location” would sometimes not properly populate in the UI or pan the camera
- Selecting “My Location” during navigation when it is already selected will now cause navigation to update to the most recent blue dot position instead of keeping the old one
### v2.2.2 - April 21, 2022
- Security fixes
- Improvements to the clarity of operation hours on locations
- Reduced the amount of logs and warnings in the console
- Fixed a bug where the level selector appeared above the full screen gallery image
### v2.2.1 - April 4, 2022
- Fixed a bug where the map group name was showing up on location profile cards for non-multi-building venues
## v2.2.0 - March 30, 2022
- Multi-building support
- Show a profile card for building locations with a “locations inside” section
- Improved navigation tooltips and text directions to handle map groups and door vortexes
- Level selector adjustments to support map groups
- Show the name of the current building on a location’s profile card
- The Find Route button should now always show up during multi-destination wayfinding
- Fixed a bug where the level selector would not show up on while searching in desktop
### v2.1.8 - March 23, 2022
- Upgraded to the latest Mappedin Mappedin JS to fix polygon image positioning issues
- Fixed an issue where focusing on some locations had incorrect/weird zoom behaviour on some devices
- Added a "Locations inside" profile section to building locations that lists all available locations in that building
- Added indicators on the level selector when Blue Dot is active to show what floor a user is currently on
- Indicate the location a user's saved position is inside if available on the profile card
- Show location pins before navigation starts when setting up a multi-destination route
### v2.1.7 - March 17, 2022
- Upgraded to the latest SDK to fix image flipping and labeling polygons with images
- Improvements to multi-building experience (automatic map group switching and improved direction tooltips/text directions)
- Fixed performance degradation when attempting to navigate to a location on venues with a large number of locations
### v2.1.5 - March 9, 2022
- Upgraded to the latest version of the SDK
### v2.1.4 - March 7, 2022
- Upgraded to the latest V4 SDK for performance improvements
- Fixed locations that required many tooltips to be drawn overlapping each other by allowing some to be hidden when appropriate
### v2.1.3 - March 3, 2022
- Fixed an issue where the Tap for options tooltip text was sometimes the wrong colour
- Fixed an issue where venue operation hours were showing incorrectly on the Dropped Pin location card
- Fixed an issue where the new level selector was not always updating its text correctly
### v2.1.2 - March 2, 2022
- Fixed a regression causing clicks not to be handled if a venue didn't have Blue Dot enabled
### v2.1.1 - March 2, 2022
- Fixed a crash caused by drawing too many location markers at the same time on some iOS devices
## v2.1.0 - March 1, 2022
- Add **Save My Location** feature to allow the user’s current Blue Dot position to be saved on the map and later navigated to and from
- Adjusted the colour of inactive paths during multi-destination navigation
- Security patches
## v2.0.0 - January 25, 2022
- Support data fetching with `accessToken` on the `window.mappedin` object
- Security fixes
- Use the path colour in the UI for multi-destination navigation
- Better ID validation for locations and nodes
### Self Hosted
# Self Hosted
Mappedin Web is a fully packaged enterprise solution that can be easily embedded into a website to provide access to the Mappedin Web platform. Learn how to integrate Mappedin Web into a web site.
## Prerequisites
Before embedding Mappedin Web, the following requirements must be met:
- Venue is fully mapped and tested (demo links are provided to preview the front-end experience)
- Location data is up to date and ready for production
- Mappedin venue keys have been provided
## Integration
!Mappedin Web - Implementation Diagram 1
Mappedin provides credentials and specific instructions. At a high level, the integration requires an HTML element, a JavaScript configuration object, and an external stylesheet.
Place the following external stylesheet in the ``:
```html
```
and include the following JavaScript snippet in the ``:
```html
```
The map expands to the maximum allowed size based on the parent `div` of the `#mappedin-map` element. Positioning and sizing that element for desktop and mobile, will ensure that the map is displayed correctly. If setting the CSS `position`, it must be set to `relative` and not `absolute` or `fixed`.
The page can also specify the source of the data loaded into Mappedin Web. A separate draft environment is available in the Mappedin CMS (Content Management System) for making changes, updates, or testing without affecting live production data. By default, production data is always loaded. To load draft data instead, set the optional property `window.mappedin.useDraftData = true` in the configuration snippet.
```html
```
Mappedin Web also supports specifying links for a privacy policy, terms of use, cookie policy, and cookie settings. These links are always visible on the app. Each can be specified as either a URL string or a callback function that is invoked when the link is clicked. The following properties are available:
```html
```
These are all optional properties. As long as one is specified, the appropriate link(s) will be displayed.
## Languages
The language for Mappedin Web is set via the `language` property in the JavaScript configuration object. The value set in `window.mappedin` determines the language on initial load. If no language is set, it defaults to the browser's language setting or English.
To change the language using JavaScript, modify `window.mappedin.language` — for example: `window.mappedin.language = "fr"`. This configuration must be set before the Mappedin script loads.
To change the language at runtime after the map is displayed, use the `lang` URL parameter — for example: `?lang=`.
Mappedin Web supports the languages listed below. UI elements provided by Mappedin Web are shown in the chosen language. However, store names, descriptions, and other custom data added to the map may appear in the map's default language if translations for those elements have not been added.
- English (en)
- Arabic (ar)
- Catalan (ca)
- Chinese (zh)
- Croatian (hr)
- Czech (cs)
- Danish (da)
- Dutch (nl)
- English (UK) (en-GB)
- English (US) (en-US)
- Estonian (et)
- Finnish (fi)
- French (fr)
- French (France) (fr-FR)
- French (Canada) (fr-CA)
- German (de)
- Greek (el)
- Hindi (hi)
- Hungarian (hu)
- Italian (it)
- Japanese (ja)
- Korean (ko)
- Maori (mi)
- Malay (ms)
- Norwegian (no)
- Polish (pl)
- Portuguese (pt)
- Romanian (ro)
- Russian (ru)
- Slovak (sk)
- Slovenian (sl)
- Spanish (es)
- Spanish - US (es-US)
- Swedish (Finland) (sv-FI)
- Tagalog (tl)
- Thai (th)
- Turkish (tr)
- Ukrainian (uk)
- Vietnamese (vi)
These translations are continuously improved. Feedback during the integration review process is welcome.
## Requirements
Mappedin Web is embedded as a web component, **not** an iFrame. It uses the Shadow DOM to hold the necessary HTML, meaning it can co-exist with the rest of a site without being affected by the site's CSS styling. For the best experience across mobile and desktop, the host site should already be designed to be responsive. On desktop, Mappedin Web can appear alongside other site content, though allowing the map to take up as much space as possible (up to a nearly full-screen experience) is recommended. On mobile, Mappedin Web fills the screen and provides its own toolbar on the bottom for a scroll-free, app-centric experience.
There are some specific details for integration that should be taken into account:
- Wrap Mappedin Web in its own container. This container should be styled to take up the whole screen on mobile (`<1024`) and fit into the site's responsive layout on desktop views.
- On desktop, the minimum width of the container should be 1024px
- On mobile, do not include any more page content than the header and the map; things like footers and other content should be excluded or hidden.
- If the host site utilizes hash navigation, Mappedin Web must live on a static page to not interfere.
### Content Security Policy (CSP)
As a mitigation for Cross-Site Scripting (XSS) and other types of web security vulnerabilities, a site may use a Content Security Policy (CSP). If a CSP is in place, Mappedin Web requires the following directives:
```
img-src 'self' *.mappedin.com data:;
worker-src 'self' blob:;
child-src 'self' blob:;
connect-src 'self' *.mappedin.com data:;
script-src 'self' 'unsafe-inline' *.mappedin.com;
```
Failing to add these directives could result in unexpected behavior and an error similar to the following being logged in the browser console.
```
Refused to create a worker from 'blob:https://YOUR.URL' because it violates the following Content Security Policy directive: "default-src https: ws: data: 'unsafe-inline' 'unsafe-eval'". Note that 'worker-src' was not explicitly set, so 'default-src' is used as a fallback.
```
It is possible to implement a more restrictive CSP policy that does not include `worker-src blob: ;`. Doing so requires a transparent proxy on the server that forwards requests from `https://YOUR.DOMAIN/mappedin-web-redirector/*` to `https://cdn.mappedin.com/web2/release/*`.
## Recommendations
These are not required, but to get the best possible experience there are a few extra steps that can be taken:
- Allow the map to take up as much space as possible on mobile and desktop
- On mobile, avoid adding too many elements that decrease the vertical space available for Mappedin Web (this is especially noticeable on smaller devices like the iPhone SE)
- Use a one column layout
- Use a traditional responsive style (CSS media queries, not JavaScript)
- A page can specify `data-key="externalId"` on the Mappedin `` to have external Ids used in the URL instead of internal Ids. The div would look similar to: ``.
- Avoid including unnecessary functionality on the map page that could impact load times of Mappedin Web
The demo page provided for each venue serves as a reference for how an integration should look. Following the demo experience is recommended.
## Full-page integration example
This example shows how to integrate Mappedin Web as a standalone page instead of inserting it in an existing page with other content.