2D/3D Visibility Switch
This article is intended to present the new map visualisation options to switch between 2D and 3D maps, allowing you to deliver performant solutions based on the device or use case.
Last updated
This article is intended to present the new map visualisation options to switch between 2D and 3D maps, allowing you to deliver performant solutions based on the device or use case.
Last updated
The Map Template allows you to seamlessly switch between the two different view modes (2D / 3D), based on your use case.
This feature allows you to:
Transition effortlessly - switch between detailed 3D views and streamlined 2D layouts with a simple click. (Calling the SDK functions) + link to the SDK implementation page
Optimise performance - enabling the 2D view which is tailored for speed and clarity, providing a fast and responsive mapping experience on older devices.
Adjust camera - enjoy the best viewing angle automatically, as the feature adjusts the camera position to suit the selected map mode (top-down for 2D maps and a 45-degree angle for 3D — the camera position is not locked, just adjusted).
Enabling the 2D/3D Visibility Switch on your own Map Template
In order to view the 2D/3D Visibility Switch in your own app, you need to have the following modules enabled: Mapbox
, 3D Walls
and 2D Walls
in the CMS.
Below you can find a step by step guide to how you can enable the previously mentioned modules:
Go to the CMS and select your own solution (the API Key used in the Map Template)
Go to the Deployment tab -> Solutions tab
In the search field placed at the top right of the page, search for the name of your solution
When you found your solution, click on the pen icon placed at the beginning of the row
Scroll down to the Modules
section and enable the Mapbox
, 3D Walls
and 2D Walls
modules
When having them enabled, press Save and close
and refresh the Map Template. The expected behaviour is to see the 2D/3D Visibility Switch on the top left corner.
Note! This feature is only available on Mapbox.
Read more about the SDK methods that enable this implementation here.