Mapwize Web App

We are providing a standard web application to view indoor maps, search for places and get directions.

The application is available at maps.mapwize.io.

Features

• Browse venue maps: Simply zoom in to enter a venue. Change floor using the floor selector on the bottom right.
• Search: Search for venues when you are viewing the world map, and search for places when you are inside a venue.
• Get directions: Use the direction button to compute directions from one point to another. If your precise indoor location is known (see below), it can be used as starting point.

Private maps

By default, only public buildings are visible on the map. To view private buildings, a custom API key or an access key is required.

Access keys can be entered using the top left menu, or with an url parameter.

The use of access key requires the app to use cookie sessions. To avoid the need for cookies, and therefore simplify the deployment accross browsers, the use of the custom API keys is prefered. Please note that custom API keys can only be provided through URL parameters.

iFrame or WebView embed

maps.mapwize.io is perfect to be used in an iFrame or in a WebView on any website or mobile application. The Mapwize url parameters allow the map to be loaded according to your needs.

You can use the embed=true and menu=false URL parameters to prevent the "Open in Mapwize app" pop-up and the Mapwize side menu if you want.

Unfortunately, it is not possible to catch map events on your website or in your app if you use an iFrame embed. For deeper integration, use the JS, iOS or Android SDKs.

URL Format

Use the URL to center the map at a given position, show a place or even show a direction. The URL is provided after the # of https://maps.mapwize.io/#/.

A URL generator is available in Mapwize Studio to help you generate those URLs.

User position

An URL refering to a beacon (like for example a QR-code) displayes the map centered on the user with the user position defined by the position of the beacon.

A beacon can be refered in 2 ways:

• by a code with at least 3 characters
• by an alias linked to the venue

Format:

https://maps.mapwize.io/#/{code}
https://maps.mapwize.io/#/b/{venueAlias}/{beaconAlias}

Example:

https://maps.mapwize.io/#/idk
https://maps.mapwize.io/#/b/myvenue/display1

Venue

An URL refering to a venue centers the map on the venue, Optionnaly on a specific floor. The venue is refered by it's alias. The alias is a string that has to be unique accross all venues on the Mapwize platform.

Format:

https://maps.mapwize.io/#/v/{venueAlias}
https://maps.mapwize.io/#/v/{venueAlias}/{floor}

Example:

https://maps.mapwize.io/#/v/myvenue
https://maps.mapwize.io/#/v/myvenue/2

Place

An URL refering to a place centers the map on the place, on the right floor inside its venue, and selects the place. The place is refered by it's alias and the alias of the venue it belongs to. The place alias is a string that has to be unique accross all places inside a venue.

Format:

https://maps.mapwize.io/#/p/{venueAlias}/{placeAlias}

Example:

https://maps.mapwize.io/#/p/myvenue/myplace

Coordinates

A position can be specified using geographic coordinates: latitude, longitude, floor. The floor is optional.

Format:

https://maps.mapwize.io/#/c/{latitude}/{longitude}
https://maps.mapwize.io/#/c/{latitude}/{longitude}/{floor}

Example:

https://maps.mapwize.io/#/c/50.633034048250735/3.0200868844985957
https://maps.mapwize.io/#/c/50.633034048250735/3.0200868844985957/2

Directions

URLs can also be generated to encode the starting and ending point of a direction. Beacon codes, places or coordinates can be used for the from and to.

Format:

https://maps.mapwize.io/#/f/.../t/...

https://maps.mapwize.io/#/f/{code}/t/p/{venueAlias}/{placeAlias}
https://maps.mapwize.io/#/f/b/{venueAlias}/{beaconAlias}/t/p/{venueAlias}/{placeAlias}
https://maps.mapwize.io/#/f/p/{venueAlias}/{placeAlias}/t/p/{venueAlias}/{placeAlias}
https://maps.mapwize.io/#/f/c/{latitude}/{longitude}/{floor}/t/p/{venueAlias}/{placeAlias}

Example:

https://maps.mapwize.io/#/f/idk/t/p/myvenue/myplace
https://maps.mapwize.io/#/f/b/myvenue/display1/t/p/myvenue/myplace
https://maps.mapwize.io/#/f/p/myvenue/myplace/t/p/myvenue/secondplace
https://maps.mapwize.io/#/f/c/50.633034048250735/3.0200868844985957/2/t/p/myvenue/secondplace

URL parameters

• z the zoom at which to display the map. Value should be between 0 and 22 and can be decimal.
  
https://maps.mapwize.io/#/?z=19


• k the accessKey to grant access to restricted venues. Using access keys requires the use of user sessions. To prevent that, you can use the apiKey parameter.
  
https://maps.mapwize.io/#/?k=YOURACCESSKEY


• apiKey the Mapwize API key to use. This is the ideal option to access private buildings as it does not require the use of session cookies.
  
https://maps.mapwize.io/#/?apiKey=YOURAPIKEY


• venueId the identifier of a Mapwize venue to restrict the map to only showing that venue
  
https://maps.mapwize.io/#/?venueId=56c2ea3402275a0b00fb00ac // Demo


• organizationId the identifier or a Mapwize organization to restrict the map to only showing venues of that organization
  
https://maps.mapwize.io/#/?organizationId=55acc650e967a7e30c523214 // Mapwize


• menu true/false. Set to false to prevent the Mapwize side menu from opening.
  
https://maps.mapwize.io/#/?menu=false


• embed true/false. Set to true to specify that maps is embed in an iFrame or VewView and, in particular, prevent the "Open in Mapwize app" pop-up.
  
https://maps.mapwize.io/#/?embed=true


• follow true/false. Set to true to start follow user mode on map start.
  
https://maps.mapwize.io/#/?follow=true


• color a hexadecimal string with the color to use. The entire interface as well as the pin used on the map is changed based on the selected color.
  
https://maps.mapwize.io/#/?color=C51586


• indoorLocationSocketUrl the url to the emitter server. URL must be escaped and should not contain any protocol. The server must comply with the the Indoor Location Socket Emitter specifications.
  
https://maps.mapwize.io/#/? indoorLocationSocketUrl=myserver.mydomain.com& indoorLocationUserId=192.168.1.2


• indoorLocationUserId the user identifyer to use to retrieve the location from the server. For WiFi based Indoor Location systems like Cisco, the userId is either a local IP address or a MAC address.
  
https://maps.mapwize.io/#/? indoorLocationSocketUrl=myserver.mydomain.com& indoorLocationUserId=192.168.1.2


• locationControl true/false. set to false to hide user location button
  
https://maps.mapwize.io/#/?locationControl=false


• ignoreBrowserSupported true/false. set to true to ignore browser compatibility check
  
https://maps.mapwize.io/#/?ignoreBrowserSupported=true


Parameters can be combined using &

https://maps.mapwize.io/#/?organizationId=55acc650e967a7e30c523214&menu=false


Indoor Location

The location of the user can come from 3 different sources:

• The approximate location provided by the browser. This is often based on the GPS on mobile devices and on IP location on desktop. This location is not suitable to be used for computing directions.
• If the app is opened from scanning a QR-Code, the location of the QR-Code is used to set the user location.
• The location can also be retrieved from a socket emitter server using the Indoor Location framework. The socket server url and the userId need to be provided as url parameter. This allows for example to use WiFi based location solutions like Cisco CMX or Meraki.

Browser support

Mapwize Maps is tested against the following browsers:

• Chrome 62+
• Firefox 63+
• Safari 11+
• iOS Safari 11+
• Edge 79+

IE 11 is not supported