Page cover

Web App

The MapsIndoors Web App allows you to get started with MapsIndoors within minutes. You can configure the appearance, features, and map settings with a few clicks in the CMS. You can embed the map in your solution using an iframe or share the direct link (map.mapsindoors.com/my-indoor-map) with colleagues, customers, and others.

The MapsIndoors Web App

Configuration

To configure your MapsIndoors Web App, navigate to navigate to 🔧 Solution DetailsApp SettingsApp Configuration, under the solution you want to deploy. Here, you can configure how your web app behaves regarding language, styling, load view, categories, and more.

App Configuration Page

General

Language: Set the default language in which the web app loads. By default, the web app adapts to the user's browser language settings (provided the browser language is supported; otherwise, it defaults to English).

For route details, the unit of measure will be metric, unless the user has set the browser language to English - United States, in which case the unit of measure will be imperial.

Note: If the language is set to "German", the web app's UI will be shown in German on load. However, location names and categories will only show in German if they have been translated to German in the CMS or via the Integration API.

Venue used on initial load: Allows you to set the default venue to load. This option is only available if more than one venue is available in the solution.

Map Markers Visibility: The MapsIndoors maps are layered on top of either Google or Mapbox basemaps. This setting allows you to:

  • Completely hide basemap markers (e.g., POIs)

  • Always make them visible

  • Use the default setting, which removes them at zoom level 17 or closer (or according to the MITransitionLevel set using Query Parameters) if your map uses Mapbox as basemap

Road Names Visibility: Similar to Map Markers Visibility, this setting controls basemap road names. You can:

  • Completely hide basemap road names

  • Always make them visible

  • Use the default setting, which removes them at zoom level 17 or closer (or according to the MITransitionLevel set using Query Parameters)) if your map uses Mapbox as basemap

View Selector visibility: The view selector allows users to quickly jump between buildings. This can only be enabled if there is more than one building on the map.

Map Provider

Input either your Mapbox Access Token or your Google Maps API key. Once you have successfully entered a key/token, you'll be able to open your Web App, ready for you and your customers to use.

If you don't have a Mapbox token/Google Maps API key yet, go here

Styling

Loading screen logo: Customize the logo that appears on the loading screen/splash screen by browsing through the MapsIndoors Media Library. You can upload any JPG, PNG, or SVG file to the Media Library (we recommend limiting the image file size to below 1 MB). By default, the MapsIndoors logo will be displayed on load.

Primary Color: Sets the primary color used in the web app's UI using hex color code.

Initial load view

Start Zoom Level: Sets the zoom level at which the map loads. Depending on the map size, values from 17 to 19 are most common. Zoom 22 is the maximum and very close, while any value of 15 and lower will be deemed too far away by most users.

Bearing: Controls the rotation of the map. Bearing=0 is due North, 90=East, 180=South, 270=West. Can only be used on Mapbox maps.

Pitch: Controls the angle at which the map is viewed. Pitch=0 is top-down. Pitch=85 is flat. Can only be used on Mapbox maps.

Center

Latitude and Longitude: Set the default center of the map. To find your desired latitudual and longitudual coordinates, you can find a location on your map close to the center of your map. Click on it and find the coordinates at the bottom of "Location Details".

App Title

Find more information in our CMS documentation.

Alias

Find more information in our CMS documentation.

App User Roles

Find more information in our CMS documentation.

App Categories

Find more information in our CMS documentation.

How Web App Configuration works with Query Parameters

In addition to the configurations applied directly in the CMS, you can also use query parameters to configure the Web App's behavior upon load. You can find an extensive overview of all configurable parameters here.

Using query parameters, you can override any setting that has been applied in the CMS. For instance, if you have set the "Center" option in the CMS, you can use the "center" query parameter to set a different center for a specific URL. This will not change the setting applied in the CMS, but will be limited to the specific URL you created.

Parameters Configurable in CMS vs Query Parameters Only

The table below shows which parameters can be configured from the MapsIndoors CMS and which parameters can only be configured through query parameters.

You can find an extensive overview of all configurable parameters here.

Parameters
Configurable in CMS

apiKey

venue

locationId

primaryColor

logo

appUserRoles

directionsFrom

directionsTo

externalIDs

tileStyle

mapboxAccessToken

gmApiKey

startZoomLevel

gmMapId

pitch

bearing

language

kioskOriginLocationId

timeout

useKeyboard

miTransitionLevel

category

searchAllVenues

useMapProviderModule

hideNonMatches

showRoadNames

showExternalIDs

searchExternalLocations

center

useAppTitle

Last updated

Was this helpful?