Skip to main content

Introduction to Display Rules

What Are Display Rules?​

In this guide you will be introduced to the concept of Display Rules and how you can use Display Rules to change how Locations (POIs, Rooms and Areas) are displayed on the map.

The MapsIndoors CMS is used to control the initial appearance of Locations. However, the Display Rules—and thereby the appearance of Locations—can be changed from the application at runtime. This gives the application the power to change Locations based on events in the app. You can also use the Integration API to control Display Rules.

How Can I Use Display Rules?​

Display Rules offer many options on how to use them. We will provide you with a few examples, but there are a lot of other use cases besides these too.

  1. You can use Display Rules to match the colors of, for example, the Polygons in your Solution to your brand guidelines, to ensure a coherent visual expression throughout your company's applications.
  2. It is possible to connect your MapsIndoors Solution to an occupancy monitoring system, so the information about whether or not a room is occupied, and by how many people, is relayed to the MapsIndoors system. This information could then, for example, be used to color a Room red when it is occupied, or green if it is available.
  3. A similar concept could be applied to Icons. Instead of the color of the Polygon changing depending on occupancy status, the Icon used for the Location could change, based on whether or not the room is available.

Display Rule Hierarchy​

In each MapsIndoors SDK, a "Main Display Rule" outlines a list of sensible defaults for all geodata. Each Location Type inherits its values from this Main Display Rule, unless the value is specifically overridden.

Each Location (Room, Area or POI) uses the Display Rule from the Type, except for values that are specifically set for the individual Location.

Here's a visualization of the inheritance principle:

Display Rule Inheritance

As an example, you might want all polygons to be red. However, the Location Type for "Meeting Room" specifies that their polygons should be blue, while the "Executive Meeting Room" Location specifically has an orange polygon.

No matter what is specified in this hierarchy, you can override it at runtime in your app. That means, as an example, that all matches for a specific search query can be specified to have a polygon color that is pink, regardless of what exists in the defaults, on their Types, and for those Locations specifically.

To remove a value from the Display Rule (to make it inherit from further up the hierarchy) set the property to null.

⚠️ For Android SDK v3, you can not change Display Rules at runtime on the Location Types level to inherit for all Locations of that Type. To apply styling to all Locations of a Type, you need to filter all Locations of that Type, and update their Display Rules individually.

Display Rule Properties​

You can currently only edit Display Rules per Type. Editing Display Rules on single Locations will be added in an upcoming release.

NOTE: If you edit Display Rules in the CMS, but none (or only some) changes take place in your app, make sure you don't set any conflicting Display Rules in-app. Display Rules applied at runtime takes precedent over all others.

In the CMS, you can edit your Display Rules in Solution Details > Types > Edit [Location Type name] Display Rules. This will open an overview of all Display Rules properties.

General​

Display Rules

The "General" visibility switch determines whether Locations of this Type are visible on the map. Moreover, the Location data is not available to the SDKs when the general visibility is turned off. The system will accept a Boolean here, so either true or false.

The "Lock" icon present in all sections determines whether or not the Display Rule is inheriting from the Main Display Rule. Click the lock to enable overriding the value.

An example of in-app Display Rules using only the General Visibility option could look like this:

{
    "displaySetting": {
    "visible": true,
    }
}

Icon​

Display Rules

The "Icon" section contains options related to the appearance of the Icon.

  1. Visibility - Controls whether the Icon is visible on the map.
    • The system will accept a Boolean here, so either true or false.
  2. Zoom from - Sets the minimum Zoom Level at which the Icon is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  3. Zoom to - Sets the maximum Zoom Level at which the Icon is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  4. Icon - Use the Media Library in the CMS to control which Icon is shown on the map.
    • The Media Library is a tool to select the displayed Icon from either a pre-loaded selection of Icons, or for you to upload your own.
    • In-app, you can provide a URL to a desired Icon.
      • In-app, you can also define iconSize, by giving the desired size in pixels.

An example of in-app Display Rules using only "Icon" Display Rules could look like this:

{
    "displaySetting": {
        "iconVisible": true,
        "zoomFrom": 16.0,
        "zoomTo": 22.0,
        "icon": "https://app.mapsindoors.com/mapsindoors/cms/assets/icons/misc/default-marker.png?71488",
        "iconSize": {
            "width": 20.0,
            "height": 20.0
        },
    }
}

Label​

Display Rules

The "Label" section contains options related to the appearance of the Label. The Label is the text associated with the Location on the map, often positioned next to the Icon.

  1. Visibility - Controls whether the Label is visible on the map.
    • The system will accept a Boolean here, so either true or false.
  2. Zoom from - Sets the minimum Zoom Level at which the Label is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  3. Zoom to - Sets the maximum Zoom Level at which the Label is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  4. Template - Controls the information the Label should contain. Only applies to the CMS, any change at runtime will overwrite the information set up by the Template.
    • Location Name - Only displays the name of the Location.
    • External ID - Only displays the External ID of the Location.
    • External ID & Location Name - Displays both the External ID and the Location Name, with the External ID first.
    • Location Name & External ID - Displays both the Location Name and the External ID, with the Location Name first.
  5. Max width - Specify how wide (in pixels) a Label can be before forcing a line-break.
    • A value of 0 will ensure no line-breaks for this label.

An example of in-app Display Rules using only "Label" Display Rules could look like this:

{
    "displaySetting": {
        "labelVisible": true,
        "label": "{{name}}",
        "labelZoomFrom": 16.0,
        "labelZoomTo": 22.0,
        "labelMaxWidth": 0,
    }
}

Polygon​

Display Rules

Polygons are independent from tiles. Tiles are drawn by MapsPeople and overlaid onto the mapping provider. Polygons are an overlay with customisable attributes that are then overlaid on top of the Tiles. Therefore, while you can edit the "Polygon" attributes of a Location connected to a Tile, be that an Area or a Room, you need to account for attributes such as the opacity of the Polygon in the resulting appearance. It is not currently possible to override the appearance of Tiles.

The "Polygon" section contains options related to the appearance of the Polygon.

  1. Visibility - Controls whether the Polygon is visible on the map.
    • The system will accept a Boolean here, so either true or false.
  2. Zoom from - Sets the minimum Zoom Level at which the Polygon is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  3. Zoom to - Sets the maximum Zoom Level at which the Polygon is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  4. Stroke color - Controls the stroke color of the Polygon.
    • In the CMS, you can select a color using the color picker displayed when clicking the color input field.
    • If setting the color in-app, the value provided must be in 6-digit HEX code (eg. #3071D9).
  5. Stroke width - Controls the stroke width (in pixels) of the Polygon.
  6. Stroke opacity - Controls the stroke opacity of the Polygon.
    • The value here should be between 0 and 1, for example a value of 1 gives 100% opacity, 0.2 gives 20% opacity, etc.
  7. Fill color - Controls the fill color of the Polygon.
    • In the CMS, you can select a color using the color picker displayed when clicking the color input field.
    • If setting the color in-app, the value provided must be in 6-digit HEX code (eg. #3071D9).
  8. Fill opacity - Controls the fill opacity of the Polygon.
    • The value here should be between 0 and 1, for example a value of 1 gives 100% opacity, 0.2 gives 20% opacity, etc.

An example of in-app Display Rules using only "Polygon" Display Rules could look like this:

{
    "displaySetting": {
        "polygon": {
            "visible": false,
            "zoomFrom": 18,
            "zoomTo": 22,
            "strokeWidth": 2.0,
            "strokeColor": "#3071D9",
            "strokeOpacity": 1.0,
            "fillColor": "#3071D9",
            "fillOpacity": 0.2
        },
    }
}

2D Model​

caution

Please note that this functionality needs to be enabled by MapsPeople. You can contact your MapsPeople representative to have the 2D model functionality enabled for your Solution(s).

Display Rules

2D models are a way of including images on the map, and customising their appearance. They are uploaded using the Media Library.

  1. Visibility - Controls whether the 2D model is visible on the map.
    • The system will accept a Boolean here, so either true or false.
  2. Zoom from - Sets the minimum Zoom Level at which the 2D model is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  3. Zoom to - Sets the maximum Zoom Level at which the 2D model is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  4. 2D Model - Open the Media Library, where you can choose which 2D model to display.
    • The Media Library is a tool to select the displayed Icon from either a pre-loaded selection of Icons, or for you to upload your own.
    • In-app, you can provide a URL to a desired Icon.
      • In-app, you can also define iconSize, by giving the desired size in pixels.
  5. Width x Height - Controls the width and height of the 2D model, measured in meters. These values cannot be changed individually, the 2D model must maintain its original aspect ratio.
  6. Bearing (rotation) - Controls the rotation of the 2D model. Measured in degrees, like a compass bearing. In the illustration below, the entered value would be 45, as the image would be placed at a 45 degree bearing.
An illustration that demonstrates how to interpret bearing

An example of in-app Display Rules using only "2D Model" Display Rules could look like this:

{
    "displaySetting": {
        "model2D": {
            "visible": true,
            "zoomFrom": 16.0,
            "zoomTo": 22.0,
            "model": null,
            "widthMeters": 0,
            "heightMeters": 0,
            "bearing":0
        }
    }
}
caution

Due to temporary technical limitations, it is currently not possible to directly delete a 2D model from a Location via the Display Rules panel. Instead, use one of the two following workarounds:

  1. Use the Visibility toggle on the Display Rules panel. This will leave the model displayed in the CMS, but your customers will not see it.

  2. Navigate to Solution Details -> Solution Settings -> 2D Model. Here you should find a preview image, and underneath, a button that says Remove. This removes any default 2D model on the Main Display Rule, and the Display Rule hierarchy will then ensure nothing is displayed if you inherit the 2D model setting from the Main Display Rules ("Locked" locks from Main to Type to Location level).

3D Walls​

caution

Please visit this page to see what the requirements are to use the 3D functionality in MapsIndoors.

Display Rules

The MapsIndoors CMS gives you the option of displaying your map in 3D. This is achieved by ensuring that any walls present in your solution are displayed as an extrusion, giving the usr the appearance of a 3D map. The appearance of the walls can be customised to match your desired visual identity.

  1. Visibility - Controls whether the 3D walls are visible on the map.
    • The system will accept a Boolean here, so either true or false.
  2. Zoom from - Sets the minimum Zoom Level at which the 3D walls are visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  3. Zoom to - Sets the maximum Zoom Level at which the 3D walls are visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  4. Wall color - Controls the color of the 3D walls.
    • In the CMS, you can select a color using the color picker displayed when clicking the color input field.
    • If setting the color in-app, the value provided must be in 6-digit HEX code (eg. #3071D9).
  5. Wall height - Controls the height of the 3D walls, measured in meters.

An example of in-app Display Rules using only "3D Walls" Display Rules could look like this:

{
    "displaySetting": {
        "walls": { 
            "visible": true,
            "color": "#707a89",
            "height": 2.0,
            "zoomFrom": 16.0,
            "zoomTo": 22.0
        },
    }
}

3D Room Extrusion​

caution

Please visit this page to see what the requirements are to use the 3D functionality in MapsIndoors.

Display Rules

In addition to the ability to extrude all walls, you can additionally extrude specific rooms or areas, for example, if you wish to highlight a specific meeting room where an important meeting is taking place.

  1. Visibility - Controls whether the extrusion is visible on the map.
    • The system will accept a Boolean here, so either true or false.
  2. Zoom from - Sets the minimum Zoom Level at which the extrusion is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  3. Zoom to - Sets the maximum Zoom Level at which the extrusion is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  4. Extrusion color - Controls the color of the extrusion.
    • In the CMS, you can select a color using the color picker displayed when clicking the color input field.
    • If setting the color in-app, the value provided must be in 6-digit HEX code (eg. #3071D9).
  5. Extrusion height - Controls the height of the room extrusion, measured in meters.

An example of in-app Display Rules using only "3D Extrusion" Display Rules could look like this:

{
    "displaySetting": {
        "extrusion": { 
            "visible": true,
            "color": "#aeb9cb",
            "height": 2.25,
            "zoomFrom": 16.0,
            "zoomTo": 22.0
        },
    }
}

3D models​

caution

Please visit this page to see what the requirements are to use the 3D functionality in MapsIndoors.

Display Rules

3D models are a way of including models on the map, and customising their appearance. They are uploaded using the Media Library.

  1. Visibility - Controls whether the 3D model is visible on the map.
    • The system will accept a Boolean here, so either true or false.
  2. Zoom from - Sets the minimum Zoom Level at which the 3D model is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  3. Zoom to - Sets the maximum Zoom Level at which the 3D model is visible.
    • The value should be a number between 1 and 22, with 1 being very far away, and 22 being very close (22 not available for all Solutions). In a general use case, most users will only need values between 15 and 22.
    • If you are developing using the JavaScript SDK for Google Maps, the value must be an integer. If you are developing for Android or iOS, or using a different map provider, the value may be fractional.
  4. 3D Model - Open the Media Library, where you can choose which 3D model to display.
    • The Media Library is a tool to select the displayed model from either a pre-loaded selection of models, or for you to upload your own.
    • In-app, you can provide a URL to a desired model.
  5. X-axis rotation - Controls the rotation of the model on the X-axis.
    • This value is the rotation on a given axis measured in degrees, and can be any value between 0 and 360.
  6. Y-axis rotation - Controls the rotation of the model on the Y-axis.
    • This value is the rotation on a given axis measured in degrees, and can be any value between 0 and 360.
  7. Z-axis rotation - Controls the rotation of the model on the Z-axis.
    • This value is the rotation on a given axis measured in degrees, and can be any value between 0 and 360.
  8. Scale - Control the scale of the model. Can be used to make the model larger or smaller on the map.
    • This value is a multiplier in relation to the original size of the uploaded model. The ability to deisgnate specific measurements will be added in a future update.

An example of in-app Display Rules using only "3D Model" Display Rules could look like this:

{
    "displaySetting": {
        "model3D": { 
            "visible": true,
            "zoomFrom": 16.0,
            "zoomTo": 22.0,
            "model": null,
            "rotationX": 0.0,
            "rotationY": 0.0,
            "rotationZ": 0.0
        },
    }
}
caution

Due to temporary technical limitations, it is currently not possible to directly delete a 3D model from a Location via the Display Rules panel. Instead, use one of the two following workarounds:

  1. Use the Visibility toggle on the Display Rules panel. This will leave the model displayed in the CMS, but your customers will not see it.

  2. Navigate to Solution Details -> Solution Settings -> 3D Model. Here you should find a preview image, and underneath, a button that says Remove. This removes any default 3D model on the Main Display Rule, and the Display Rule hierarchy will then ensure nothing is displayed if you inherit the 3D model setting from the Main Display Rules ("Locked" locks from Main to Type to Location level).

Conclusion​

Putting all this together, a sample set of Display Rules for a given Type could look like this (the values shown here are identical to the default Main Display Rule):


"displayRule": {
    "visible": true,
    "iconVisible": true,
    "zoomFrom": 16.0,
    "zoomTo": 22.0,
    "icon": "https://app.mapsindoors.com/mapsindoors/cms/assets/icons/misc/default-marker.png?71488",
    "iconScale": 1.0,
    "iconSize": {
        "width": 20.0,
        "height": 20.0
    },
    "labelVisible": true,
    "label": "{{name}}",
    "labelZoomFrom": 16.0,
    "labelZoomTo": 22.0,
    "labelMaxWidth": 0, //0 means infinite eg lines will not be broken based on width
    "polygon": {
        "visible": false,
        "zoomFrom": 18,
        "zoomTo": 22,
        "strokeWidth": 2.0,
        "strokeColor": "#3071D9",
        "strokeOpacity": 1.0,
        "fillColor": "#3071D9",
        "fillOpacity": 0.2
    },
    "walls": { 
        "visible": true,
        "color": "#707a89",
        "height": 2.0,
        "zoomFrom": 16.0,
        "zoomTo": 22.0
    },
    "extrusion": {
        "visible": true,
        "color": "#aeb9cb",
        "height": 2.25,
        "zoomFrom": 16.0,
        "zoomTo": 22.0
    },
    "model3D": { 
        "visible": true,
        "zoomFrom": 16.0,
        "zoomTo": 22.0,
        "model": null,
        "rotationX": 0.0,
        "rotationY": 0.0,
        "rotationZ": 0.0
    },
    "model2D": {
        "visible": true,
        "zoomFrom": 16.0,
        "zoomTo": 22.0,
        "model": null,
        "widthMeters": 0,
        "heightMeters": 0,
        "bearing":0
    }
}

All properties are optional.

PropertiesTypeValidationDescription
visiblebooleanMust be true for the location to be shown in the map. If not true all other parameters are ignored.
iconVisiblebooleanMust be true for the icon to be visible in the map. If this is not true the zoomFrom, zoomTo, iconUrl, iconScale and iconSize parameters are ignored.
zoomFromnumber1-21 (22 if applicable)The minimum zoom level the image/icon will be visible on the map.
zoomTonumber1-21 (22 if applicable)The maximum zoom level the image/icon will be visible on the map.
iconstringA URL to an image to represent the Location on the map.
iconScaledouble> 0⚠️ Deprecated
iconSizeobjectSpecifies the size that the image will appear on the map. {{ "{width: number, height: number" }}}.
iconSize.widthdouble> 0
iconSize.heightdouble> 0
labelVisiblebooleanControls the visibility of the label.
labelstringDescriptive text for the Location. This can either be a static text or a dynamic text, retrieved from a property on the Location, using double curly braces as delimiters. E.g. "{{ "{{ name " }}}}" or a combination "Room: {{ "{{ name " }}}}".
labelZoomFromnumber1-21 (22 if applicable)The maximum zoom level the image/icon will be visible on the map.
labelZoomTonumber1-21 (22 if applicable)The maximum zoom level the image/icon will be visible on the map.
labelMaxWidthdouble>= 0In pixels. 0 represents an unlimited max length.
polygonobjectEverything under this parameter apply only to locations that have polygon data defined such as Rooms and Areas, but not POIs.
polygon.visiblebooleanMust be true for the polygon to be visible on the map. If this is not true all parameters under polygon are ignored.
polygon.zoomFrom1-21 (22 if applicable)The lowest zoom level where the polygon will be shown.
polygon.zoomTo1-21 (22 if applicable)The highest zoom level where the polygon will be shown. This number must be higher than polygon.zoomFrom unless polygon.zoomFrom is equal to the highest available zoom level for the Solution (this is 22 in some cases).
polygon.strokeWidth>= 0The width of the outline of the polygon.
polygon.strokeColorValid hex colorThe color of the outline of the polygon.
polygon.strokeOpacity0-1The opacity of the outline of the polygon. Set this to 0 if only the interior is to be shown.
polygon.fillColorValid hex colorThe color of the interior of the polygon.
polygon.fillOpacity0-1The color of the interior of the polygon. Set this to 0 if only the outline is to be shown.

For further guides on how to use Display Rules in Practice, see the following guides.