## version-6.0 ### Additional Guides # Additional Guides > Additional guides for Mappedin SDK for Android v6 are coming soon. ### Annotations # Annotations > Map annotations add visual or textual elements to maps, providing extra information about specific locations or features. Map makers can choose from many annotations included in Mappedin Maker to add to a map and access them using Mappedin SDKs. :::tip A complete example demonstrating Annotations with icons can be found in the Mappedin Android Github repo: MarkersDemoActivity.kt ::: Annotations are organized into the following groups. These are just a few examples of annotations, each group contains many more. | Annotation Group | Examples | | ----------------- | -------------------------------------------- | | Access Features | Keybox, roof access | | Building Sides | Alpha, bravo, charlie, delta | | Equipment Rooms | Boiler Room, Sprinkler control room | | Fire Ratings | Fire and smoke wall 1 hour, firewall 3 hours | | Fire Safety | Fire Blanket, Fire Hose Reel | | General Systems | Emergency Generator, Smoke Control Panel | | Hazards | Biohazard, Explosive | | Safety | Accessible Elevator, Eyewash Station | | Utility Shutoff | Gas Valve, Main Water Valve | | Ventilation | Chimney, Exhaust Fan | | Water Connections | Sprinkler FDC, Public Hydrant | | Water Systems | Fire Pump, Pressurized Water Tank | Incorporating annotations help provide a safer space for all. It allows users to easily locate key elements in the map. !Mappedin v6 Annotations ## Using Annotations An app may choose to display all annotations, annotations of a specific group or no annotations at all. The following code sample logs the name of each annotation. ```kotlin mapView.mapData.getByType(com.mappedin.models.MapDataType.ANNOTATION) { r -> r.onSuccess { annotations -> // Add markers for all annotations that have icons. annotations.forEach { annotation -> Log.d("Annotation", annotation.name) } } } ``` ## Annotation Icons Mappedin provides a set of icons to represent annotations. The example below demonstrates using these icons and placing them as Markers on the map. `Annotation.icon.url` contains the URL of the icon to use. :::tip A complete example demonstrating Annotations with icons can be found in the Mappedin Android Github repo: MarkersDemoActivity.kt ::: ```kotlin {12} mapView.mapData.getByType(com.mappedin.models.MapDataType.ANNOTATION) { r -> r.onSuccess { annotations -> val opts = AddMarkerOptions( interactive = AddMarkerOptions.Interactive.True, placement = AddMarkerOptions.Placement.Single(MarkerPlacement.CENTER), rank = AddMarkerOptions.Rank.Tier(CollisionRankingTier.HIGH), ) // Add markers for all annotations that have icons. annotations.forEach { annotation -> val iconUrl = annotation.icon?.url val markerHtml = """ """.trimIndent() mapView.markers.add(annotation, markerHtml, opts) { } } // Remove markers that are clicked on. mapView.on(Events.Click) { clickPayload -> val clickedMarker = clickPayload?.markers?.firstOrNull() ?: return@on mapView.markers.remove(clickedMarker) { } } } } ``` ### API Reference # API Reference ## Latest Version Mappedin SDK for Android v6.2.0-alpha.1 ## Previous Versions v6.1.0-alpha.1v6.0.0-alpha.1 ### Building & Floor Selection # Building & Floor Selection > ## Floor Selection When mapping a building with multiple floors, each floor has its own unique map. These are represented by the Floor class, which are accessed using MapData.getByType(). The currently displayed Floor can be accessed using MapView.currentFloor. :::tip A complete example demonstrating Building and Floor Selection can be found in the Mappedin Android Github repo: BuildingFloorSelectionDemoActivity.kt ::: ### Changing Floors When initialized, MapView displays the Floor with the elevation that's closest to 0. This can be overridden by setting Show3DMapOptions.initialFloor to a Floor.id and passing it to MapView.show3dMap(). ```kotlin // Setting the initial floor to Floor.id 'm_123456789'. mapView.show3dMap(Show3DMapOptions(initialFloor = "m_123456789")) { r -> r.onSuccess { // Successfully initialized the map view. } r.onFailure { // Failed to initialize the map view. } } ``` The Floor displayed in a MapView can also be changed during runtime by calling MapView.setFloor() and passing in a Floor.id. ```kotlin // Set the floor to Floor.id 'm_987654321'. mapView.setFloor("m_987654321") { result -> result.onSuccess { Log.d("MappedinDemo", "Floor changed successfully") } } ``` ### Listening for Floor Changes Mappedin SDK for Android provides the ability to listen for floor changes on a MapView. The code below listens for the `floor-change` event and logs the new floor and building name to the console. ```kotlin mapView.on(Events.FloorChange) { payload -> payload?.let { Log.d( "MappedinDemo", "Floor changed to: ${it.floor.name} in building: ${it.floor.floorStack?.name}", ) } } ``` ## Building Selection Mappedin Maps can contain one to many buildings with each building having one to many floors. Each building has its floors organized into a FloorStack object. When multiple buildings are present, there are multiple FloorStack objects, one for each building. A FloorStack contains one to many Floor objects, each representing the map of each level of the building. The FloorStack object is accessed by using MapData.getByType(). ```kotlin // Get all floor stacks mapView.mapData.getByType(MapDataType.FLOOR_STACK) { result -> result.onSuccess { stacks -> floorStacks = stacks?.sortedBy { it.name } ?: emptyList() // Get all floors mapView.mapData.getByType(MapDataType.FLOOR) { floorsResult -> floorsResult.onSuccess { floors -> allFloors = floors ?: emptyList() Log.d("MappedinDemo", "Floors: $floors") } } } } ``` :::tip A complete example demonstrating Building and Floor Selection can be found in the Mappedin Android Github repo: BuildingFloorSelectionDemoActivity.kt ::: ### Camera # Camera > Controlling the view of the map allows apps to create visually rich experiences using Mappedin SDKs. This guide shows how to focus the map view on targets, move the camera and listen to camera events. :::tip A complete example demonstrating Camera can be found in the Mappedin Android Github repo: CameraDemoActivity.kt ::: !Mappedin v6 Camera :::tip Note that the MapView class instantiates the Camera class and exposes it as MapView.Camera. Use MapView.Camera to utilize Camera's methods. ::: ## Focus the Camera on Targets Mappedin SDK for Android built in functionality to focus the camera on one ore more targets using a single or array of FocusTarget objects. When multiple targets are used, the SDK will ensure that all targets are visible. The following sample code acts on the click event to focus on the Space the user clicked on. Note that the Space must be set to interactive to allow it to be clickable. Refer to the Interactivity guide for more information on how to set a space to interactive. ```kotlin // Focus the camera on the click location. mapView.on(Events.Click) { clickPayload -> clickPayload?.coordinate?.let { coordinate -> mapView.camera.focusOn(coordinate) } } ``` ## Controlling the Camera To control the camera, set it with new pitch, bearing or zoom using Camera.set(). It accepts a CameraTarget object that contains bearing, center coordinate, pitch and zoom level. These parameters are all optional, allowing the camera to by moved by adjusting one or more of these values. ### CameraTarget - **bearing:** Bearing for the camera target in degrees. - **center:** Center `Coordinate` for the camera target. - **pitch:** Pitch for the camera target in degrees. - **zoomLevel:** Zoom level for the camera target in mercator zoom levels. ```kotlin mapView.Camera.set( CameraTarget( bearing = 30, pitch = 80, zoomLevel = 19.5, center = e.coordinate, ) ) ``` ## Animation The camera can also be animated into position using the same transforms described in the Controlling the Camera section above. This is done using the Camera.animateTo() method. Similar to Camera.set(), the `animateTo` method accepts a CameraTarget object, but it is optional. This allows the camera to changed by adjusting its `bearing`, `pitch` or `zoomLevel` without specifying a new target to move to. In addition, `animateTo` also accepts CameraAnimationOptions that allow setting of the duration of the animation in milliseconds and setting the easing curve. The next code snippet animates to the center of the camera's current position and zooms in to a zoom level of 21.0, pitches the camera to 60.0 degrees and rotates the camera to 180.0 degrees over 3000 milliseconds using the easing function `ease-in-out`. ```kotlin mapView.camera.center { result -> result.onSuccess { center -> center?.let { val transform = CameraTarget( center = it, zoomLevel = 21.0, pitch = 60.0, bearing = 180.0 ) val options = CameraAnimationOptions(duration = 3000, easing = EasingFunction.EASE_IN_OUT) mapView.camera.animateTo(transform, options) {} } } } ``` The types of easing animations are defined in EasingFunction. ### EasingFunction - **Linear:** This function implies a constant rate of change. It means the animation proceeds at the same speed from start to end. There's no acceleration or deceleration, giving a very mechanical feel. - **Ease-in:** This function causes the animation to start slowly and then speed up as it progresses. Initially, there's gradual acceleration, and as the function moves forward, the rate of change increases. - **Ease-out:** Contrary to ease-in, ease-out makes the animation start quickly and then slow down towards the end. It begins with a faster rate of change and gradually decelerates. - **Ease-in-out:** This function combines both ease-in and ease-out. The animation starts slowly, speeds up in the middle, and then slows down again towards the end. It offers a balance of acceleration and deceleration. ## Resetting The Camera While there is no method in Mappedin SDKs to reset the camera to its default position, this can be easily built into an app. To do so, store the camera position after the map is shown and then use those values to reposition the camera at a later time. The code sample below stores the initial camera position. When a user clicks on a location it first focuses on that space. The next click will return the camera to its original position. ```kotlin private var defaultPitch: Double? = null private var defaultZoomLevel: Double? = null private var defaultBearing: Double? = null private var defaultCenter: Coordinate? = null ... // Store default camera values mapView.camera.pitch { result -> result.onSuccess { defaultPitch = it } } mapView.camera.zoomLevel { result -> result.onSuccess { defaultZoomLevel = it } } mapView.camera.bearing { result -> result.onSuccess { defaultBearing = it } } mapView.camera.center { result -> result.onSuccess { defaultCenter = it } } ... // Set the camera to the default position val transform = CameraTarget( zoomLevel = defaultZoomLevel, pitch = defaultPitch, bearing = defaultBearing, center = defaultCenter ) mapView.camera.set(transform) {} ``` ## Listening to Camera Events There are several camera events that can be acted on by setting a listener with mapView.on('camera-change'). The camera-change event contains a CameraTransform object. CameraTransform provides the bearing, center coordinate, pitch and zoom level. ```kotlin // Log camera change events to the console. mapView.on(Events.CameraChange) { cameraTransform -> cameraTransform?.let { Log.d( "MappedinDemo", "Camera changed to bearing: ${it.bearing}, pitch: ${it.pitch}, zoomLevel: ${it.zoomLevel}, center: Lat: ${it.center.latitude}, Lon: ${it.center.longitude}", ) } } ``` :::tip A complete example demonstrating Camera can be found in the Mappedin Android Github repo: CameraDemoActivity.kt ::: ### Enterprise Data # Enterprise Data > :::note > The Enterprise Data classes described in this guide are populated in Mappedin CMS, which requires a Solutions Tier subscription. ::: ## Enterprise Locations An EnterpriseLocation contains metadata about a location, such as its name, description, logo, phone number, social medial links, hours of operation and more. They can be accessed using the MapData.getByType() method as shown below. ```kotlin mapView.mapData.getByType(MapDataType.ENTERPRISE_LOCATION) { result -> result.onSuccess { enterpriseLocations -> } } ``` ## Enterprise Categories An EnterpriseCategory groups one or more EnterpriseLocation. These allow similar locations to be sorted in a logical fashion. For example a mall may group locations into Food Court, Footwear and Women's Fashion. They can be accessed using the MapData.getByType() method as shown below. ```kotlin mapView.mapData.getByType(MapDataType.ENTERPRISE_CATEGORY) { result -> result.onSuccess { enterpriseCategories -> } } ``` EnterpriseCategory can contain one or more sub EnterpriseCategory that are accessed from its `children` member. ## Enterprise Venue The EnterpriseVenue class holds metadata about the map, which includes the map name, supported languages, default language, top locations and more. It can be accessed using the MapData.getByType() method as shown below. ```kotlin mapView.mapData.getByType(MapDataType.ENTERPRISE_VENUE) { result -> result.onSuccess { enterpriseVenue -> } } ``` ## Search :::tip Note that the MapData class instantiates the Search class and exposes it as MapView.mapData.search. Use MapView.mapData.search to utilize Search' methods. ::: The Search functionality allows users to search for locations, categories, and other points of interest within the venue. :::tip A complete example demonstrating Search can be found in the Mappedin Android Github repo: SearchDemoActivity.kt ::: Here are two ways to enable search: 1. Enable Search on map initialization: ```kotlin // See Trial API key Terms and Conditions // https://developer.mappedin.com/docs/demo-keys-and-maps val options = GetMapDataWithCredentialsOptions( key = "5eab30aa91b055001a68e996", secret = "RJyRXKcryCMy4erZqqCbuB1NbR66QTGNXVE0x3Pg6oCIlUR1", mapId = "mappedin-demo-mall", search = SearchOptions(enabled = true) ) mapView.getMapData(options) { result -> ``` 2. Enable Search via method: ```kotlin mapView.mapData.search.enable { result -> result.onSuccess { runOnUiThread { setupSearch() } } } ``` ### Search Query Use Search.query to search for locations based on a string input: - EnterpriseLocationOptions: Specific places such as stores, restaurants, or washrooms. - EnterpriseCategoryOptions: Groups of locations, such as "Food Court" or "Electronics." - PlaceOptions: Any main objects that can be searched for such as Space, Door, PointOfInterest Search query returns a list of matching SearchResult based on the input string. SearchResult include information about the type of match, the score (relevance), and detailed metadata about the matching items. #### Example Search Query ```kotlin mapView.mapData.search.query(item.suggestion.suggestion) { result -> result.onSuccess { searchResult -> // Handle search results } } ``` ### Search Suggestions Use Search.suggest to fetch real-time suggestions based on partial input. This is useful for creating an autocomplete feature for a search bar. #### Example Code ```kotlin mapView.mapData.search.suggest(query) { result -> result.onSuccess { suggestions -> // Handle suggestions } } ``` :::tip A complete example demonstrating Search can be found in the Mappedin Android Github repo: SearchDemoActivity.kt ::: ### Getting Started # Getting Started > Mappedin SDK for Android helps to deliver the rich indoor mapping experience of a venue, inside Android apps. The Mappedin SDK for Android is a native interface to Mappedin JS. The SDK is a dependency built using Kotlin, and it automatically handles any authentication, network communication, fetching of map data, its display, and basic user interaction, such as panning, tapping, and zooming. The SDK allows a developer to build their own interactions. Additional layers can be rendered on top of the map. :::info Mappedin SDK for Android is supported on Android versions 8.0 and above. ::: ## Coding with AI Mappedin SDK for Android provides an llms-mappedin-android.txt file that can be used to help with coding when using Large Language Models (LLMs). ## Android Studio Project Setup ### Add Permissions Add the following permissions to the `AndroidManifest.xml` in the `application` tag. ```xml ``` Ensure that hardware acceleration is not turned off by setting it to `true`. ```xml ``` Ensure that the application has a large heap by setting it to `true`. ```xml ``` ### Add Application Dependency to Gradle Add the Mappedin SDK dependency to the application's `build.gradle`, `settings.gradle` or `libs.versions.toml` and sync the changes to download the SDK. The latest version can be found in in Maven Central. #### build.gradle or settings.gradle ``` implementation 'com.mappedin.sdk:mappedin:6.2.0-alpha.1' ``` #### libs.versions.toml ``` [versions] mappedin = "6.2.0-alpha.1" [libraries] mappedin = { module = "com.mappedin.sdk:mappedin", version.ref = "mappedin" } ``` :::tip The Mappedin Android Github repository contains a reference project that demonstrates how to use the Mappedin SDK for Android. ::: ### Display a Map The core class of the Mappedin SDK for Android is MapView, which is responsible for instantiating an Android WebView that loads Mappedin JS. MapView is the core class of which all other views and data models can be accessed. #### Load Map Data Call MapView.getMapData to load map data from Mappedin servers. This function must be called first and map data must be loaded before any other Mappedin functions can be called. ```kotlin // See Trial API key Terms and Conditions // https://developer.mappedin.com/docs/demo-keys-and-maps val options = GetMapDataWithCredentialsOptions( key = "mik_yeBk0Vf0nNJtpesfu560e07e5", secret = "mis_2g9ST8ZcSFb5R9fPnsvYhrX3RyRwPtDGbMGweCYKEq385431022", mapId = "64ef49e662fd90fe020bee61", ) // Load the map data. mapView.getMapData(options) { result -> result.onSuccess { Log.d("MappedinDemo", "getMapData success") } } ``` #### Show a Map Call MapView.show3dMap to display the map. ```kotlin mapView.show3dMap(Show3DMapOptions()) { result -> result.onSuccess { Log.d("MappedinDemo", "show3dMap success") } } ``` The following sample code combines the loading of map data and the display of the map and includes a function to be called when the map is ready. ```kotlin package com.mappedin.demo import android.os.Bundle import android.util.Log import android.view.Gravity import android.view.ViewGroup import android.widget.FrameLayout import android.widget.ProgressBar import androidx.appcompat.app.AppCompatActivity import com.mappedin.MapView import com.mappedin.models.GetMapDataWithCredentialsOptions import com.mappedin.models.Show3DMapOptions class DisplayMapDemoActivity : AppCompatActivity() { private lateinit var mapView: MapView private lateinit var loadingIndicator: ProgressBar override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) title = "Display a Map" // Create a FrameLayout to hold both the map view and loading indicator val container = FrameLayout(this) mapView = MapView(this) container.addView( mapView.view, ViewGroup.LayoutParams( ViewGroup.LayoutParams.MATCH_PARENT, ViewGroup.LayoutParams.MATCH_PARENT, ), ) // Add loading indicator loadingIndicator = ProgressBar(this) val loadingParams = FrameLayout.LayoutParams( ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT, ) loadingParams.gravity = Gravity.CENTER container.addView(loadingIndicator, loadingParams) setContentView(container) // See Trial API key Terms and Conditions // https://developer.mappedin.com/docs/demo-keys-and-maps val options = GetMapDataWithCredentialsOptions( key = "mik_yeBk0Vf0nNJtpesfu560e07e5", secret = "mis_2g9ST8ZcSFb5R9fPnsvYhrX3RyRwPtDGbMGweCYKEq385431022", mapId = "64ef49e662fd90fe020bee61", ) // Load the map data. mapView.getMapData(options) { result -> result .onSuccess { Log.d("MappedinDemo", "getMapData success") // Display the map. mapView.show3dMap(Show3DMapOptions()) { r -> r.onSuccess { runOnUiThread { loadingIndicator.visibility = android.view.View.GONE } onMapReady(mapView) } r.onFailure { runOnUiThread { loadingIndicator.visibility = android.view.View.GONE } Log.e("MappedinDemo", "show3dMap error: $it") } } }.onFailure { Log.e("MappedinDemo", "getMapData error: $it") } } } // Place your code to be called when the map is ready here. private fun onMapReady(mapView: MapView) { Log.d("MappedinDemo", "show3dMap success - Map displayed") } } ``` #### Result The app should display something that looks like this in the Android Emulator: And zooming in to have a closer look: ## Create a Key & Secret ## Debug Mode Use Debug Mode to get a closer look at how various map components behave and interact. Here's how to enable it: ### 1. Enable Debug Mode To activate the debug interface, call the following function in your code: ```kotlin mapView.enableDebug() ``` MapView.enableDebug displays a panel on the right side of the map, revealing several tools and controls for direct interaction with the map's elements. ### 2. Navigating the Debug Panel The debug panel provides access to a variety of controls: **Geometry Controls** - Adjust individual geometry settings, such as color, opacity, visibility. These controls make it easy to see how different elements respond to changes. **Interactivity** - Use toggles to turn interactivity on/off - Change colors and hover effects to highlight specific areas **Scene Controls** - Manage the overall scene settings, such as scaling, positioning, and group management. Toggle the visibility of groups or containers within the scene - Adjust padding, scale, and watermark positioning - Markers & Labels — Add, remove, or edit markers and labels directly through the panel **Camera Controls** - Fine-tune camera settings, including zoom levels, pitch, and center position - Set minimum and maximum zoom levels - Adjust the focus to a specific area or level !enable debug ### Interactivity # Interactivity > This guide explains how to enhance a map's interactivity by making components clickable. Interactivity can greatly improve the user experience and user engagement with a map. :::tip A complete example demonstrating interactivity can be found in the Mappedin Android Github repo: InteractivityDemoActivity.kt ::: !Mappedin v6 Interactivity ## Interactive Spaces A Space can be set to interactive to allow a user to click on it. When interactivity is enabled for a space, it enables a hover effect that highlights the space when the cursor is moved over the space. The following code enables interactivity for all spaces: ```kotlin // Set all spaces to be interactive so they can be clicked mapView.mapData.getByType(MapDataType.SPACE) { result -> result.onSuccess { spaces -> spaces.forEach { space -> mapView.updateState(space, mapOf("interactive" to true)) { } } } } ``` ## Interactive Labels A Label added to the map can be set to interactive to allow users to click on it and have the click event captured by an app. The code sample below adds a label to each space with a name and sets the label's interactivity to true. ```kotlin // Set all spaces to be interactive so they can be clicked mapView.mapData.getByType(.space) { [weak self] (result: Result<[Space], Error>) in guard let self = self else { return } if case .success(let spaces) = result { spaces.forEach { space in self.mapView.updateState(target: space, state: ["interactive": true]) { _ in } } } } ``` After enabling interactivity, click events on the label can be captured using Mapview.on(Events.Click). The Events object passed into the `on` method contains an array of labels that were clicked. The following code sample captures the click event and checks if the user clicked on a label. If they did, it logs the id of the label that was clicked and removes it from the map. ```kotlin mapView.on(Events.Click) { clickPayload -> val text = clickPayload?.labels?.firstOrNull()?.text text?.let { Log.d("MappedinDemo", "removing label: $it") } clickPayload?.labels?.firstOrNull()?.let { mapView.labels.remove(it) } } ``` ## Interactive Markers A Marker can be set to interactive, allowing it to be clickable and have an app act on the click event. The `interactive` property of a Marker can be set to `true`, `false` or `pointer-events-auto`. - `false` - The Marker is not interactive. - `true` - The Marker is interactive and the click event is captured by the `mapView.on(Events.Click)` event handler. - `pointer-events-auto` - The Marker is interactive and mouse events are passed to the Marker's HTML content. The code sample below adds a marker for each annotation and sets the marker's interactivity to true. ```kotlin mapView.mapData.getByType(com.mappedin.models.MapDataType.ANNOTATION) { r -> r.onSuccess { annotations -> val opts = AddMarkerOptions( interactive = AddMarkerOptions.Interactive.True, placement = AddMarkerOptions.Placement.Single(MarkerPlacement.CENTER), rank = AddMarkerOptions.Rank.Tier(CollisionRankingTier.HIGH), ) // Add markers for all annotations that have icons. annotations.forEach { annotation -> val iconUrl = annotation.icon?.url val markerHtml = """
${annotation.name}
""".trimIndent() mapView.markers.add(annotation, markerHtml, opts) { } } } } ``` After enabling interactivity, click events on the label can be captured using Mapview.on(Events.Click). The Events object passed into the `on` method contains an array of markers that were clicked. The following code sample captures the click event and checks if the user clicked on a marker. If they did, it logs the id of the marker that was clicked and removes it from the map. ```kotlin // Remove markers that are clicked on. mapView.on(Events.Click) { clickPayload -> val clickedMarker = clickPayload?.markers?.firstOrNull() ?: return@on mapView.markers.remove(clickedMarker) { } } ``` ## Handling Click Events Mappedin SDK for Android enables capturing and responding to click events through its event handling system. After enabling interactivity, click events can be captured using Mapview.on(Events.Click). The Events `click` event passes ClickPayload that contains the objects the user clicked on. It allows developers to obtain information about user interactions with various elements on the map, such as: 1. **coordinate** - A Coordinate object that contains the latitude and longitude of the point where the user clicked. 2. **facades** - An array of Facade objects that were clicked. 3. **floors** - An array of Floor objects. If the map contains multiple floors, floors under the click point are included. 4. **labels** - An array of Label objects that were clicked. 5. **markers** - An array of Marker objects that were clicked. 6. **models** - An array of Model objects that were clicked. 7. **objects** - An array of MapObject objects that were clicked. 8. **paths** - An array of Path objects that were clicked. 9. **pointerEvent** - A PointerEvent object that contains the pointer event data. 10. **shapes** - An array of Shape objects that were clicked. 11. **spaces** - An array of Space objects that were clicked. Use `Mapview.on(Events.Click)` to capture click events as shown below. ```kotlin // Set up click listener mapView.on(Events.CLICK) { event -> val clickPayload = event as? ClickPayload ?: return@on handleClick(clickPayload) } private fun handleClick(clickPayload: ClickPayload) { val title: String val message = StringBuilder() // Use the map name as the title (from floors) title = clickPayload.floors?.firstOrNull()?.name ?: "Map Click" // If a label was clicked, add its text to the message val labels = clickPayload.labels if (!labels.isNullOrEmpty()) { message.append("Label Clicked: ") message.append(labels.first().text) message.append("\n") } // If a space was clicked, add its location name to the message val spaces = clickPayload.spaces if (!spaces.isNullOrEmpty()) { val space = spaces.first() message.append("Space clicked: ") message.append(space.name) message.append("\n") } // If a path was clicked, add it to the message if (!clickPayload.paths.isNullOrEmpty()) { message.append("You clicked a path.\n") } // Add the coordinates clicked to the message message.append("Coordinate Clicked: \nLatitude: ") message.append(clickPayload.coordinate.latitude) message.append("\nLongitude: ") message.append(clickPayload.coordinate.longitude) Log.d("MappedinDemo", "title: $title, message: $message") } ``` :::tip A complete example demonstrating interactivity can be found in the Mappedin Android Github repo: InteractivityDemoActivity.kt ::: ### Labels # Labels > Labels display text and images anchored to specific points on a map. They rotate, show, or hide based on priority and zoom level, providing information about location names, points of interest, and more. Effective labels help apps convey additional information, such as room names, points of interest, main entrances, or other useful contextual details. :::tip A complete example demonstrating Labels can be found in the Mappedin Android Github repo: LabelsDemoActivity.kt ::: !Mappedin v6 Labels :::tip Note that the MapView class instantiates the Labels class and exposes it as MapView.labels. Use MapView.labels to utilize Labels' methods. ::: ## Adding & Removing Individual Labels Labels can be added individually to a map by calling Labels.add(). A label can be added to any Anchorable target. Refer to the Labels.add() documentation for the complete list of targets. The following code sample adds an interactive (clickable) label to each space that has a name: ```kotlin mapView.mapData.getByType(MapDataType.SPACE) { result -> result.onSuccess { spaces -> for (space in spaces) { if (space.name.isNotEmpty()) { val color = colors.random() val appearance = LabelAppearance( color = color, icon = space.images.firstOrNull()?.url ?: svgIcon, ) mapView.labels.add( target = space, text = space.name, options = AddLabelOptions(labelAppearance = appearance, interactive = true), ) } } } } ``` Labels can be removed by using the Labels.remove(label) method, passing in the label to be removed as shown below: ```kotlin mapView.labels.remove(label) ``` ## Interactive Labels Labels added to the map can be set to interactive to allow users to click on them. For more information, refer to the Interactive Labels section of the Interactivity Guide. ## Label Icons Icons can be added to labels in `SVG`, `PNG`, `JPEG` and `WebP` formats. Icons are clipped in a circle to prevent overflow. Three clipping methods of `contain`, `fill` and `cover` can be set in the LabelAppearance.iconFit parameter with `contain` being the default. | Fill | Contain | Cover (default) | | ----------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------- | | !Floating Label fill | !Floating Label contain | !Floating Label cover | The LabelAppearance.iconPadding property sets the amount of space between the icon and the border. The icon may shrink based on this value. | `padding: 0` | `padding: 10` | | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------- | | !Floating Label fill with 0 padding | !Floating Label fill with 10 padding | Label icons can be configured to be shown or hidden based on the current zoom level using LabelAppearance.iconVisibleAtZoomLevel. A value below 0 will result in the icon always being hidden. Setting this value to 0 ensures icons show up at maxZoom (fully zoomed in) and 1 configures them to always be displayed. ## Label Appearance Labels can have their appearance styled to match the visual theme of an app or to make groups of labels easily distinguishable from one another. The following declaration of LabelAppearance describes these customisable attributes. | Option | Type | Description | Default | |--------|------|-------------|---------| | `margin` | `number` | Margin around the label text and pin in pixels. This will affect label density. Minimum is 6px. | 6 | | `maxLines` | `number` | Number of lines to display when text spans multiple lines. | 2 | | `textSize` | `number` | Text size in pixels | 11.5 | | `maxWidth` | `number` | Maximum width of text in pixels. | 150 | | `lineHeight` | `number` | Line height sets the height of a line box. It's commonly used to set the distance between lines of text. | 1.2 | | `color` | ColorString | A ColorString for the label text and pin. | `#333` | | `outlineColor` | ColorString | A ColorString for the outline around the label text and pin. | `white` | | `textColor` | ColorString | A ColorString representing just the text color. Defaults to the same as `color`. | - | | `textOutlineColor` | ColorString | A ColorString representing just the text outline. Defaults to the same as `outlineColor`. | - | | `pinColor` | ColorString | A ColorString representing just the pin color. Defaults to the same as `color`. | - | | `pinOutlineColor` | ColorString | A ColorString representing just the pin outline. Defaults to the same as `outlineColor`. | - | | `pinColorInactive` | ColorString | A ColorString representing just the pin color when the label is inactive. Defaults to the same as `pinColor`. | - | | `pinOutlineColorInactive` | ColorString | A ColorString representing just the pin outline when the label is inactive. Defaults to the same as `pinOutlineColor`. | - | | `icon` | `string` | An icon to be placed inside the label pin. Can be an SVG string or a path to a PNG or JPEG. | - | | `iconSize` | `number` | Size of the icon in pixels. Requires `icon` to be set. | 20 | | `iconScale` | `number` \| Interpolation | Scale the icon uniformly. Specify a number or an Interpolation object. | 1 | | `iconPadding` | `number` | Padding between the icon and the marker's border in pixels. | 2 | | `iconFit` | `'fill'` \| `'contain'` \| `'cover'` | How the icon should fit inside the marker. Options: `fill` (stretch to fill), `cover` (maintain aspect ratio and fill), `contain` (maintain aspect ratio and fit inside). | `cover` | | `iconOverflow` | `'visible'` \| `'hidden'` | Whether the icon should overflow the circle of the marker. Options: `visible`, `hidden`. | `hidden` | | `iconVisibleAtZoomLevel` | `number` | Defines the zoom level at which the icon becomes visible. Infinity ensures never visible, -Infinity ensures always visible. | -Infinity | The code sample below demonstrates how to use some label styling options. Labels are added to each space with a name using the space's image if one is set, or a default SVG icon if one is not. It also sets the label text color to a random color from a list of colors. ```kotlin val svgIcon = """ """.trimIndent() val colors = listOf("#FF610A", "#4248ff", "#891244", "#219ED4") mapView.mapData.getByType(MapDataType.SPACE) { result -> result.onSuccess { spaces -> for (space in spaces) { if (space.name.isNotEmpty()) { val color = colors.random() val appearance = LabelAppearance( color = color, icon = space.images.firstOrNull()?.url ?: svgIcon, ) mapView.labels.add( target = space, text = space.name, options = AddLabelOptions(labelAppearance = appearance, interactive = true), ) } } } } ``` ## Label Ranking Ranking can be added to labels to control which label will be shown when more than one label occupies the same space. The label with the highest rank will be shown. If labels do not overlap, ranking will have no effect. Rank values are low, medium, high, and always-visible and are defined in CollisionRankingTier. The code below add a label with a high ranking where a user clicks on the map. ```kotlin mapView.on(Events.Click) { clickPayload -> mapView.labels.add( target = clickPayload.coordinate, text = "I'm a high ranking label!", options = AddLabelOptions(rank = CollisionRankingTier.HIGH), ) } ``` ## Enabling and Disabling Labels Labels can be dynamically enabled or disabled using `mapView.updateState()`. When a label is disabled, it will be hidden from view but remain in the map's memory. This is useful for managing label visibility based on conditions like zoom level or user interaction, without the overhead of repeatedly adding and removing labels. For Mappedin JS, use `mapView.getState()` to check a label's current state, which returns the label's current properties including its enabled status. Here's an example on how to enable/disable labels on click: ```kotlin private var label: Label? = null ... mapView.on(Events.Click) { clickPayload -> if (label == null) { // Add the label if it doesn't exist. mapView.labels.add( target = clickPayload.coordinate, text = "Click to Toggle", onResult = { it.onSuccess { label = it } }, ) } else { // Toggle the label. label?.let { currentLabel -> mapView.getState( currentLabel, onResult = { result -> result.onSuccess { state -> state?.let { mapView.updateState( currentLabel, LabelUpdateState(enabled = !it.enabled), ) } } }, ) } } } ``` :::tip A complete example demonstrating Labels can be found in the Mappedin Android Github repo: LabelsDemoActivity.kt ::: ### Location Profiles & Categories # Location Profiles & Categories > A Location refers to something that represents a physical position on the map, such as an annotation, area, connection (e.g. stairs or elevator), door, point of interest or space. Locations may have a LocationProfile attached to them. The profiles contain information about the location such as its name, description, social media links, opening hours, logo and more. A LocationProfile can have zero to many LocationCategory attached to it. A LocationCategory may have a child or parent category. For example, the parent `Food & Drink` LocationCategory has children such as `Bar`, `Cafe`, `Food Court` and `Mediterranean Cuisine`. !Location Profiles & Categories :::tip A complete example demonstrating location profiles and categories can be found in the Mappedin Android Github repo: LocationsDemoActivity.kt ::: ## LocationProfile A LocationProfile can be accessed by using the `locationProfiles` property of a location. For example, use Space.locationProfiles to access every LocationProfile of a space. Every LocationProfile can also be access using the MapData.getByType() method as shown below. ```kotlin mapView.mapData.getByType(MapDataType.LOCATION_PROFILE) { result -> result.onSuccess { locationProfiles -> } } ``` ## LocationCategory To access the LocationCategory of a LocationProfile, use the LocationProfile.categories property, which contains a list of IDs of its LocationCategory. Then use the MapData.getById() method to get the LocationCategory by its ID. Note that a LocationCategory can have either parent or child categories. These are accessible using the LocationCategory.parent and LocationCategory.children properties respectively. Every LocationCategory can also be access using the MapData.getByType() method as shown below. ```kotlin mapView.mapData.getByType(MapDataType.LOCATION_CATEGORY) { result -> result.onSuccess { locationCategories -> } } ``` :::tip A complete example demonstrating location profiles and categories can be found in the Mappedin Android Github repo: LocationsDemoActivity.kt ::: ### Markers # Markers > Mappedin SDK for Android allows adding and removing Marker on a map. Markers are elements containing HTML that the Mappedin SDK anchors to any Anchorable target. They are automatically rotated and repositioned when the camera moves. :::tip A complete example demonstrating Markers can be found in the Mappedin Android Github repo: MarkersDemoActivity.kt ::: !Mappedin JS v6 Markers :::tip Note that the MapView class instantiates the Markers class and exposes it as MapView.markers. Use MapView.markers to utilize Markers' methods. ::: ## Creating Markers Markers are added to the map by referencing a target that can be a Door, Space, Coordinate or any Anchorable target. The following code sample adds a marker to a coordinate. ```kotlin val opts = AddMarkerOptions( interactive = AddMarkerOptions.Interactive.True, placement = AddMarkerOptions.Placement.Single(MarkerPlacement.CENTER), rank = AddMarkerOptions.Rank.Tier(CollisionRankingTier.HIGH), ) val markerHtml = """
This is a Marker!
""".trimIndent() mapView.markers.add(coordinate, markerHtml, opts) { } ``` ## Placement Marker placement is set using the `options` argument of Markers.add(). Options accepts a AddMarkerOptions value, which has a member named `placement`. When provided, the point of the Marker described by the Placement is placed next to the target. For example, using `MarkerPlacement.CENTER` will place the Marker's center at the target. Both a single placement and an array of placements can be provided. When an array is provided, the Marker is placed at the first target that has space available to display the Marker. Placement positions are defined in MarkerPlacement which contains 9 values. The placement points are as follows, with the default being center. ### MarkerPlacement - `CENTER` - `TOP` - `LEFT` - `BOTTOM` - `RIGHT` - `top-left` - `TOP_RIGHT` - `BOTTOM_LEFT` - `BOTTOM_RIGHT` Marker content can be styled using CSS that references the placement of the marker. This can allow the creation of a tooltip or bubble-style marker that points to its target. This is done by using the CSS Selector: ```css .mappedin-marker[data-placement='']; ``` Where `` is the placement position. Here is an example of adding a triangle pointer to the Marker's target of `left`: ```CSS .marker:before { content: ''; width: 0; height: 0; top: calc(50% - 10px); left: -10px; z-index: 1; position: absolute; border-bottom: 10px solid transparent; border-top: 10px solid transparent; z-index: -1; } .mappedin-marker[data-placement="left"] .marker:before { left: auto; right: -5px; border-left: 10px solid #333333; } ``` ## Removing Markers Markers can be removed individually by using the Markers.remove(marker) method, passing in the marker to be removed as shown below. ```kotlin mapView.markers.remove(marker) { } ``` To remove all markers from a map, call Markers.removeAll(). ```kotlin mapView.markers.removeAll() { } ``` ## Marker Rank Ranking can be added to markers to control which marker will be shown when more than one marker occupies the same space. The marker with the highest rank will be shown. If markers do not overlap, ranking will have no effect. Rank values low, medium, high and always-visible as defined in CollisionRankingTier. The code below adds markers where a user clicks on the map. The marker rank is cycled with each click. If the user clicks and adds multiple markers in the same location, the marker with the highest rank is shown and lower ranking markers are hidden. ```kotlin // Ranks for marker collision priority - cycles through medium, high, always-visible private val ranks = listOf(CollisionRankingTier.MEDIUM, CollisionRankingTier.HIGH, CollisionRankingTier.ALWAYS_VISIBLE) private var rankIndex = 0 ... // Act on the click event and add a marker with a cycling rank. // Observe how higher ranking markers are shown when they collide with lower ranking markers. mapView.on(Events.Click) { clickPayload -> val currentRank = ranks[rankIndex] val rankName = currentRank.value val markerTemplate = """

Marker Rank: $rankName

""".trimIndent() // Add a marker with the current rank at the clicked coordinate. mapView.markers.add( target = clickPayload.coordinate, html = markerTemplate, options = AddMarkerOptions(rank = AddMarkerOptions.Rank.Tier(currentRank)) ) // Cycle to the next rank rankIndex++ if (rankIndex == ranks.size) { rankIndex = 0 } } ``` ## Moving Markers Markers can be repositioned after they have been added to a map. There are two ways of doing this: - Markers.setPosition() instantly repositions a Marker - Markers.animateTo() animates a Marker to a new position The Marker's position can be set to a Coordinate, Space or Door. The `animateTo` method takes an `options` parameter of AnimationOptions that defines the animation duration and EasingFunction, which can be EasingFunction.LINEAR, EasingFunction.EASE_IN, EasingFunction.EASE_OUT or EasingFunction.EASE_IN_OUT. - **Linear**: This function implies a constant rate of change. It means the animation proceeds at the same speed from start to end. There's no acceleration or deceleration, giving a very mechanical feel. - **Ease In**: This function causes the animation to start slowly and then speed up as it progresses. Initially, there's gradual acceleration, and as the function moves forward, the rate of change increases. - **Ease Out**: Contrary to ease-in, ease-out makes the animation start quickly and then slow down towards the end. It begins with a faster rate of change and gradually decelerates. - **Ease In Out**: This function combines both ease-in and ease-out. The animation starts slowly, speeds up in the middle, and then slows down again towards the end. It offers a balance of acceleration and deceleration. The code samples below displays a custom Marker when the map is first clicked. When the map is clicked again, the Marker is animated to the clicked location using the default animation options. ```kotlin private var marker: Marker? = null ... mapView.on(Events.Click) { clickPayload -> if (marker != null) { // Animate existing marker to new position mapView.markers.animateTo(marker!!, clickPayload.coordinate) } else { // Add new marker at clicked position val options = AddMarkerOptions( interactive = AddMarkerOptions.Interactive.True, placement = AddMarkerOptions.Placement.Single(MarkerPlacement.RIGHT) ) mapView.markers.add(clickPayload.coordinate, "Marker", options) { result -> result.onSuccess { newMarker -> marker = newMarker } } } } ``` ## Enabling and Disabling Markers Markers can be dynamically enabled or disabled using MapView.updateState(). When a marker is disabled, it will be hidden from view but remain in the map's memory. This is useful for managing marker visibility based on conditions like zoom level or user interaction, without the overhead of repeatedly adding and removing markers. Use MapView.getState() to check a marker's current state, which returns the marker's current properties including its enabled status. Here's an example on how to enable/disable markers on click: ```kotlin private var marker: Marker? = null ... mapView.on(Events.Click) { clickPayload -> if (marker == null) { // First click - add marker Log.d("MappedinDemo", "Adding marker at: $clickPayload.coordinate") mapView.markers.add( clickPayload.coordinate, "
Enabled Marker!
" ) { result -> result.onSuccess { newMarker -> marker = newMarker } } } else { // Get current state of marker mapView.getState(marker!!) { result -> result.onSuccess { markerState -> Log.d("MappedinDemo", "Current Marker State: $markerState") // Toggle enabled state val newState = !(markerState?.enabled ?: true) mapView.updateState(marker!!, MarkerUpdateState(enabled = newState)) Log.d("MappedinDemo", "Marker is now ${if (newState) "enabled" else "disabled"}") } } } } ``` :::tip A complete example demonstrating Markers can be found in the Mappedin Android Github repo: MarkersDemoActivity.kt ::: ### Migration Guide # Migration Guide Mappedin SDK for Android version 6.0 is a major release that includes a number of changes to the SDK. It uses a GeoJSON-based rendering engine, rebuilt from the ground up. It works in unison with MapLibre which enables outdoor base maps as well as data visualization features. By using GeoJSON as the core data format, v6 can integrate with existing external data sources. This guide explains the steps needed to migrate from version 5. ## Initialization Changes The options for getting a map have changed. `getVenue()` has been replaced by `getMapData()`. v5 Initialization ```kotlin // See Trial API key Terms and Conditions // https://developer.mappedin.com/api-keys/ mapView.loadVenue( MPIOptions.Init( "5eab30aa91b055001a68e996", "RJyRXKcryCMy4erZqqCbuB1NbR66QTGNXVE0x3Pg6oCIlUR1", "mappedin-demo-mall", ), MPIOptions.ShowVenue( shadingAndOutlines = true, multiBufferRendering = true, outdoorView = MPIOptions.OutdoorView(enabled = true), ), ) { Log.e(javaClass.simpleName, "Error loading map view") } ``` v6 Initialization ```kotlin // See Trial API key Terms and Conditions // https://developer.mappedin.com/docs/demo-keys-and-maps val options = GetMapDataWithCredentialsOptions( key = "5eab30aa91b055001a68e996", secret = "RJyRXKcryCMy4erZqqCbuB1NbR66QTGNXVE0x3Pg6oCIlUR1", mapId = "mappedin-demo-mall", ) // Load the map data. mapView.getMapData(options) { result -> result .onSuccess { Log.d("MappedinDemo", "getMapData success") // Display the map. mapView.show3dMap(Show3DMapOptions()) { r -> r.onSuccess { Log.d("MappedinDemo", "show3dMap success") } r.onFailure { Log.e("MappedinDemo", "show3dMap error: $it") } } }.onFailure { Log.e("MappedinDemo", "getMapData error: $it") } } ``` ## Component Access `MPIData.` has been replaced by `MapData.getByType()` For example: In v5 access nodes using `MPIData.nodes`, which contains an array of `Node` objects. In v6 access nodes using `mapData.getByType(MapDataType.Node)`, which returns an array of `Node` objects. `Mappedin.getCollectionItemById` is replaced by `mapData.getById(, id)` The following classes have been redesigned. Refer to the chart below for a mapping of similar classes. | v5 Component | v6 Component | | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | MPIPolygon | Space | | MPIMapGroup | FloorStack | | MPIMap | Floor | | MPICoordinate | Coordinate | | MPINode | Node | MPIState no longer exists. ## UI Components MPIFloatingLabelsManager has been replaced with Labels. MPIFloatingLabelsManager.labelAllLocations() will be replaced with `MapView.auto()`. MPIMarkerManager has been replaced with Markers. Tooltips have not been carried over from v5 and Markers should be used instead. ## Updating UI Components `setPolygonColor`, `clearPolygonColor` and other methods of changing the state of UI objects on the map is now performed using MapView.updateState(), which also supports `initial` for returning properties to their original state. MPICameraManager.animate() has been renamed to Camera.animateTo(). MPIMarkerManager.animate() has been renamed to Markers.animateTo(). ## Interactivity MapView.addInteractivePolygonsForAllLocations() has been replaced by updating the state of each space to be interactive as shown below. ```kotlin // Set all spaces to be interactive so they can be clicked mapView.mapData.getByType(MapDataType.SPACE) { result -> result.onSuccess { spaces -> spaces.forEach { space -> mapView.updateState(space, GeometryUpdateState(interactive = true)) { } } } } ``` Event names passed from `MapView.on()` have been changed: | v5 Event | v6 Event | | --------------------------------------------------------------- | --------------------- | | `E_SDK_EVENT.CLICK` | `Events.Click` | | `E_SDK_EVENT.MAP_CHANGED , E_SDK_EVENT.MAP_CHANGED_WITH_REASON` | `Events.FloorChange` | | `E_SDK_EVENT.OUTDOOR_VIEW_LOADED` | `Events.OutdoorViewLoaded` | ## Stacked Maps Stacked Maps APIs have been replaced with Multi Floor View along with the ability to control the visibility and altitude of floors. Refer to the Multi Floor View and Stacked Maps guides for more information. ## Map Metadata Classes containing enterprise map metadata have been renamed. | v5 Component | v6 Component | | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | | MPICategory | EnterpriseCategory | | MPILocation | EnterpriseLocation | | MPIVenue | EnterpriseVenue | ## Wayfinding & Directions MapData.getDirections() only supports getting directions between two locations. For multi destination directions, use MapData.getDirectionsMultiDestination(). MPIJourneyManager is now Navigation. ## Camera v5 MPICameraManager.tilt in radians is replaced by v6 Camera.pitch in degrees. `Camera.minPitch` and `Camera.maxPitch` are now available to set the minimum and maximum pitch values. v5 MPICameraManager.rotation in radians is replace in v6 by Camera.bearing in degrees Clockwise rotation is now positive. v5 `Camera.zoom`, `Camera.minZoom` and `Camera.maxZoom` used meters from ground level. In v6 these now use mercator zoom level units. The following camera methods and accessors have been renamed. | v5 Method | v6 Method | | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- | | MPICameraManager.position() | Camera.center() | | MPICameraManager.setSafeAreaInsets() | Camera.setScreenOffsets() | | MPICameraManager.safeAreaInsets() | Camera.screenOffsets() | | MPICameraListener | MapView.on(...) | ## Search MPISearchManager has been changed to Search. The results returned in SearchResult are more structured: ```kotlin data class SearchResult( val enterpriseCategories: List? = null, val enterpriseLocations: List? = null, val places: List ) ``` ## Multi Language The methods to work with maps in multiple languages have been changed. v6 ```kotlin // Specify a non default language when getting map data val options = GetMapDataWithCredentialsOptions( key = "5eab30aa91b055001a68e996", secret = "RJyRXKcryCMy4erZqqCbuB1NbR66QTGNXVE0x3Pg6oCIlUR1", mapId = "mappedin-demo-mall", language = "en" ) // Get supported languages mapData.getByType(MapDataType.ENTERPRISE_VENUE) { result -> result.onSuccess { venue -> venue.languages.forEach { language -> Log.d("MapData", "Language: ${language}") } } } // Change language mapData.changeLanguage("es") { result -> result.onSuccess { Log.d("MapData", "Map language changed to Spanish") } } ``` ## Blue Dot Blue Dot will be coming soon in v6.0. ## Dynamic Focus Dynamic Focus will be coming soon in v6.0. ### Multi Floor View & Stacked Maps # Multi Floor View & Stacked Maps > ## Multi Floor View Multi Floor View is a feature that displays all floors in a building stacked vertically below the active floor, allowing users to see the building's vertical structure and navigate between floors. The active floor is fully rendered while lower floors appear as semi-transparent footprints. !MultiFloor View :::tip A complete example demonstrating Multi Floor View can be found in the Mappedin Android Github repo: MultiFloorViewDemoActivity.kt ::: Multi Floor View is enabled by default. It can be controlled using the Show3DMapOptions.multiFloorView option when initializing the map view as shown in the code sample below. In this example, the map view is initialized with the `initialFloor` set to `m_952cd353abcb1a13`, which is ID of the 10th floor of the building. Other Multi Floor View options are defined in MultiFloorViewOptions and include the ability to set the gap between floors as well as whether the camera should move when the active floor changes. ### Code Sample ```kotlin // Display the map with multi-floor view enabled. val show3dMapOptions = Show3DMapOptions( multiFloorView = Show3DMapOptions.MultiFloorViewOptions( enabled = true, floorGap = 10.0, updateCameraElevationOnFloorChange = true, ) ) mapView.show3dMap(show3dMapOptions) { r -> r.onSuccess { Log.d("MappedinDemo", "show3dMap success") } r.onFailure { Log.e("MappedinDemo", "show3dMap error: $it") } } ``` It is possible to set multiple floors to be visible at once, which can be useful for overlaying data within the building, such as the locations of security cameras or other assets. This can be done by setting the visible property to true for each floor that should be shown, using FloorUpdateState as shown in the code sample below. ```kotlin // Get all floors and find the ones needed. mapView.mapData.getByType(MapDataType.FLOOR) { result -> result.onSuccess { floors -> // Set the current floor to the one with elevation 9. val floor9 = floors.find { it.elevation == 9.0 } if (floor9 != null) { mapView.setFloor(floor9.id) { Log.d("MappedinDemo", "Set floor to elevation 9: ${floor9.name}") } } // Show the 6th floor (elevation 6) as well. val floor6 = floors.find { it.elevation == 6.0 } if (floor6 != null) { mapView.updateState( floor6, FloorUpdateState( geometry = FloorUpdateState.Geometry(visible = true) ) ) { Log.d("MappedinDemo", "Made floor with elevation 6 visible: ${floor6.name}") } } } result.onFailure { Log.e("MappedinDemo", "Failed to get floors: $it") } } ``` When displaying multiple floors, by default content such as labels, markers, paths and images are only visible on the active floor. These can be displayed on additional visible floors by enabling them for the floor using FloorUpdateState as shown below. ```kotlin mapView.updateState( floor, FloorUpdateState( visible = true, altitude = 0.0, geometry = FloorUpdateState.Geometry(visible = true), images = FloorUpdateState.Images(visible = true), labels = FloorUpdateState.Labels(enabled = true), markers = FloorUpdateState.Markers(enabled = true), paths = FloorUpdateState.Paths(visible = true) ) ) { result -> result.onSuccess { // Handle success } result.onFailure { // Handle failure } } ``` ## Stacked Maps Stacked Maps consist of individual layers that represent different floors of a multi-story building. These layers are conceptually or digitally stacked to create a complete view of the structure, allowing users to visualize, navigate, and interact with multiple floors in an integrated way. !Stacked Maps :::tip A complete example demonstrating Stacked Maps can be found in the Mappedin Android Github repo: StackedMapsDemoActivity.kt ::: Stacked Maps can be enabled by setting the visibility of floors that should appear in the stack to `true` and altering their altitude defined in FloorUpdateState, so that each floor is raised above the previous floor. There are two ways to modify the visibility and altitude of a floor: 1. MapView.animateState() gradually moves the floor to the new altitude over a specified duration of time. 2. MapView.updateState() instantly snaps the floor to the new altitude. Alternative visualization methods can also be created by using variations of this technique. For example, an app may wish to only show the top and bottom floors of a building, or only show the floors that are currently accessible to the user by setting the visibility of the floors to `true` or `false` based on the app's requirements. When displaying multiple floors, by default content such as labels, markers, paths and images are only visible on the active floor. These can be displayed on additional visible floors by enabling them for the floor using FloorUpdateState as shown below. ```kotlin mapView.updateState( floor, FloorUpdateState( images = FloorUpdateState.Images(visible = true), labels = FloorUpdateState.Labels(enabled = true), markers = FloorUpdateState.Markers(enabled = true), paths = FloorUpdateState.Paths(visible = true) ) ) { result -> result.onSuccess { // Handle success } result.onFailure { // Handle failure } } ``` When using Stacked Maps with Dynamic Focus (coming soon) or Navigation, the `MapView.manualFloorVisibility` property should be set to `true` to ensure that the floors remain visible. Otherwise they could be hidden by the Dynamic Focus or Navigation features, which by default will hide all floors that are not the active floor. ### Stacked Maps Utility Class The following utility class can be used to expand and collapse the stacked maps view using the `animateState` or `updateState` methods. ```kotlin package com.mappedin.demo import com.mappedin.MapView import com.mappedin.data.MapData import com.mappedin.models.Floor import com.mappedin.models.FloorUpdateState import com.mappedin.models.MapDataType /** * Options for expanding floors in a stacked view. * * @param distanceBetweenFloors The vertical spacing between floors in meters. Default: 10 * @param animate Whether to animate the floor expansion. Default: true * @param cameraPanMode The camera pan mode to use ("default" or "elevation"). Default: "elevation" */ data class ExpandOptions( val distanceBetweenFloors: Double = 10.0, val animate: Boolean = true, val cameraPanMode: String = "elevation", ) /** * Options for collapsing floors back to their original positions. * * @param animate Whether to animate the floor collapse. Default: true */ data class CollapseOptions( val animate: Boolean = true, ) /** * Utility object for managing stacked floor views. * * Provides functions to expand all floors vertically (stacked view) and collapse them back * to a single floor view. This creates a 3D exploded view effect where all floors are visible * at different altitudes. * * Example usage: * ``` kotlin * // Expand floors with default options * StackedMapsUtils.expandFloors(mapView) * * // Expand floors with custom gap * StackedMapsUtils.expandFloors(mapView, ExpandOptions(distanceBetweenFloors = 20.0)) * * // Collapse floors back * StackedMapsUtils.collapseFloors(mapView) * ``` */ object StackedMapsUtils { /** * Expands all floors vertically to create a stacked view. * * Each floor is positioned at an altitude based on its elevation multiplied by the * distance between floors. This creates a 3D exploded view where all floors are visible. * * @param mapView The MapView instance * @param options Options controlling the expansion behavior */ fun expandFloors( mapView: MapView, options: ExpandOptions = ExpandOptions(), ) { // Set camera pan mode to elevation for better navigation in stacked view mapView.camera.setPanMode(options.cameraPanMode) // Get the current floor ID to identify the active floor mapView.currentFloor { currentFloorResult -> val currentFloorId = currentFloorResult.getOrNull()?.id // Get all floors mapView.mapData.getByType(MapDataType.FLOOR) { result -> result.onSuccess { floors -> floors.forEach { floor -> val newAltitude = floor.elevation * options.distanceBetweenFloors val isCurrentFloor = floor.id == currentFloorId // First, make sure the floor is visible mapView.getState(floor) { stateResult -> stateResult.onSuccess { currentState -> if (currentState != null && (!currentState.visible || !currentState.geometry.visible) ) { // Make the floor visible first with 0 opacity if not current mapView.updateState( floor, FloorUpdateState( visible = true, altitude = 0.0, geometry = FloorUpdateState.Geometry( visible = true, opacity = if (isCurrentFloor) 1.0 else 0.0, ), ), ) } // Then animate or update to the new altitude if (options.animate) { mapView.animateState( floor, FloorUpdateState( altitude = newAltitude, geometry = FloorUpdateState.Geometry( opacity = 1.0, ), ), ) } else { mapView.updateState( floor, FloorUpdateState( altitude = newAltitude, visible = true, geometry = FloorUpdateState.Geometry( visible = true, opacity = 1.0, ), ), ) } } } } } } } } /** * Collapses all floors back to their original positions. * * Floors are returned to altitude 0, and only the current floor remains fully visible. * Other floors are hidden to restore the standard single-floor view. * * @param mapView The MapView instance * @param options Options controlling the collapse behavior */ fun collapseFloors( mapView: MapView, options: CollapseOptions = CollapseOptions(), ) { // Reset camera pan mode to default mapView.camera.setPanMode("default") // Get the current floor ID to identify the active floor mapView.currentFloor { currentFloorResult -> val currentFloorId = currentFloorResult.getOrNull()?.id // Get all floors mapView.mapData.getByType(MapDataType.FLOOR) { result -> result.onSuccess { floors -> floors.forEach { floor -> val isCurrentFloor = floor.id == currentFloorId if (options.animate) { // Animate to altitude 0 and fade out non-current floors mapView.animateState( floor, FloorUpdateState( altitude = 0.0, geometry = FloorUpdateState.Geometry( opacity = if (isCurrentFloor) 1.0 else 0.0, ), ), ) // After animation, hide non-current floors if (!isCurrentFloor) { // Use a handler to delay hiding the floor android.os.Handler(android.os.Looper.getMainLooper()).postDelayed({ mapView.updateState( floor, FloorUpdateState( visible = false, altitude = 0.0, geometry = FloorUpdateState.Geometry( visible = false, opacity = 0.0, ), ), ) }, 1000) // Default animation duration } } else { mapView.updateState( floor, FloorUpdateState( altitude = 0.0, visible = isCurrentFloor, geometry = FloorUpdateState.Geometry( visible = isCurrentFloor, opacity = if (isCurrentFloor) 1.0 else 0.0, ), ), ) } } } } } } } ``` :::tip A complete example demonstrating Stacked Maps can be found in the Mappedin Android Github repo: StackedMapsDemoActivity.kt ::: ### Points of Interest # Points of Interest > Points of Interest (POIs) are specific locations or features on a map that users find useful or informative. POIs serve as landmarks or markers, highlighting key places, services, or objects to enhance the map's utility and user experience. They are contained in the PointOfInterest class, which contains a coordinate, name, description, images, links and the floor the point of interest exists on. All of these elements are configured in Mappedin Maker. !Mappedin JS v6 POIs PointOfInterest.name could be used to create labels to show users helpful information. The following sample code demonstrates one possible use for PointOfInterest. It labels each PointOfInterest and uses Camera.animateTo() to create a flyby of each one. ```kotlin package com.mappedin.demo import android.os.Bundle import android.os.Handler import android.os.Looper import android.util.Log import android.view.Gravity import android.view.ViewGroup import android.widget.FrameLayout import android.widget.ProgressBar import androidx.appcompat.app.AppCompatActivity import com.mappedin.MapView import com.mappedin.models.Annotation import com.mappedin.models.Area import com.mappedin.models.CameraAnimationOptions import com.mappedin.models.CameraTarget import com.mappedin.models.Connection import com.mappedin.models.Door import com.mappedin.models.EasingFunction import com.mappedin.models.EnterpriseCategory import com.mappedin.models.EnterpriseLocation import com.mappedin.models.EnterpriseVenue import com.mappedin.models.Facade import com.mappedin.models.Floor import com.mappedin.models.FloorStack import com.mappedin.models.GetMapDataWithCredentialsOptions import com.mappedin.models.LocationCategory import com.mappedin.models.LocationProfile import com.mappedin.models.MapDataType import com.mappedin.models.MapObject import com.mappedin.models.Node import com.mappedin.models.PointOfInterest import com.mappedin.models.Show3DMapOptions import com.mappedin.models.Space import kotlin.math.atan2 import kotlin.math.cos import kotlin.math.floor import kotlin.math.sin class DisplayMapDemoActivity : AppCompatActivity() { private lateinit var mapView: MapView private lateinit var loadingIndicator: ProgressBar override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) title = "Display a Map" // Create a FrameLayout to hold both the map view and loading indicator val container = FrameLayout(this) mapView = MapView(this) container.addView( mapView.view, ViewGroup.LayoutParams( ViewGroup.LayoutParams.MATCH_PARENT, ViewGroup.LayoutParams.MATCH_PARENT, ), ) // Add loading indicator loadingIndicator = ProgressBar(this) val loadingParams = FrameLayout.LayoutParams( ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT, ) loadingParams.gravity = Gravity.CENTER container.addView(loadingIndicator, loadingParams) setContentView(container) // See Trial API key Terms and Conditions // https://developer.mappedin.com/docs/demo-keys-and-maps val options = GetMapDataWithCredentialsOptions( key = "mik_yeBk0Vf0nNJtpesfu560e07e5", secret = "mis_2g9ST8ZcSFb5R9fPnsvYhrX3RyRwPtDGbMGweCYKEq385431022", mapId = "65c0ff7430b94e3fabd5bb8c", ) // Load the map data. mapView.getMapData(options) { result -> result .onSuccess { Log.d("MappedinDemo", "getMapData success") // Display the map. mapView.show3dMap(Show3DMapOptions()) { r -> r.onSuccess { runOnUiThread { loadingIndicator.visibility = android.view.View.GONE } onMapReady(mapView) } r.onFailure { runOnUiThread { loadingIndicator.visibility = android.view.View.GONE } Log.e("MappedinDemo", "show3dMap error: $it") } } }.onFailure { Log.e("MappedinDemo", "getMapData error: $it") } } } // Place your code to be called when the map is ready here. private fun onMapReady(mapView: MapView) { Log.d("MappedinDemo", "show3dMap success - Map displayed") val animationDuration = 4000 // Get the map center as the starting point for bearing calculations. mapView.mapData.mapCenter { centerResult -> centerResult.onSuccess { mapCenter -> if (mapCenter == null) { Log.e("MappedinDemo", "Map center is null") return@onSuccess } // Get all points of interest. mapView.mapData.getByType(MapDataType.POINT_OF_INTEREST) { result -> result.onSuccess { pois -> // Start iterating through POIs with initial position from map center. animateThroughPOIs( mapView = mapView, pois = pois, index = 0, startLat = mapCenter.latitude, startLon = mapCenter.longitude, animationDuration = animationDuration, ) } result.onFailure { error -> Log.e("MappedinDemo", "Failed to get POIs: $error") } } } centerResult.onFailure { error -> Log.e("MappedinDemo", "Failed to get map center: $error") } } } /** * Recursively animates through each point of interest. */ private fun animateThroughPOIs( mapView: MapView, pois: List, index: Int, startLat: Double, startLon: Double, animationDuration: Int, ) { if (index >= pois.size) { Log.d("MappedinDemo", "Finished animating through all POIs") return } val poi = pois[index] // Label the point of interest. mapView.labels.add(target = poi.coordinate, text = poi.name) // Calculate the bearing between the current position and the POI. val bearing = calcBearing( startLat, startLon, poi.coordinate.latitude, poi.coordinate.longitude, ) // Animate to the current point of interest. mapView.camera.animateTo( target = CameraTarget( bearing = bearing, pitch = 80.0, zoomLevel = 50.0, center = poi.coordinate, ), options = CameraAnimationOptions( duration = animationDuration, easing = EasingFunction.EASE_OUT, ), ) // Wait for the animation to complete before moving to the next POI. Handler(Looper.getMainLooper()).postDelayed({ animateThroughPOIs( mapView = mapView, pois = pois, index = index + 1, startLat = poi.coordinate.latitude, startLon = poi.coordinate.longitude, animationDuration = animationDuration, ) }, animationDuration.toLong()) } /** * Calculate the bearing between two points. */ private fun calcBearing( startLat: Double, startLng: Double, destLat: Double, destLng: Double, ): Double { val startLatRad = toRadians(startLat) val startLngRad = toRadians(startLng) val destLatRad = toRadians(destLat) val destLngRad = toRadians(destLng) val y = sin(destLngRad - startLngRad) * cos(destLatRad) val x = cos(startLatRad) * sin(destLatRad) - sin(startLatRad) * cos(destLatRad) * cos(destLngRad - startLngRad) var brng = atan2(y, x) brng = toDegrees(brng) return (brng + 360) % 360 } /** Converts from degrees to radians. */ private fun toRadians(degrees: Double): Double = degrees * Math.PI / 180 /** Converts from radians to degrees. */ private fun toDegrees(radians: Double): Double = radians * 180 / Math.PI } ``` ### Release Notes # Release Notes Mappedin SDK for Android 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 // _ Deprecated // _ Removed // _ Fixed // _ Security } ## 6.2.0-alpha.1 - December 30, 2025 - Upgraded to Mappedin JS v6.9.1. - Added - `Show3DMapOptions.preloadFloors` option to preload floors. - Added -`MultiFloorViewOptions.floorGap` option to set the gap between floors. - Fixed - `Show3DMapOptions.initialFloor` should accept only a string. ### ⚠️ Breaking Changes - Changed - Strongly type MapView.on parameters and return values ```kotlin // ❌ Before mapView.on("click") { payload -> val clickPayload = payload as? ClickPayload } // ❌ Before mapView.on(Events.CLICK) { payload -> val clickPayload = payload as? ClickPayload } // ✅ After mapView.on(Events.Click) { clickPayload -> } ``` ## 6.1.0-alpha.1 - December 19, 2025 - Added - LabelAppearance.iconScale property to control the scale of the icon. - Fixed - `MapData.getById` not returning the correct type. ### ⚠️ Breaking Changes - Fixed - Removed duplicate inline implementation of Interpolation and Width. ```kotlin // ❌ Before AddPathOptions( width = AddPathOptions.Width.Fixed(1.0), ) // ✅ After AddPathOptions( width = Width.Value(1.0), ) ``` - Fixed - `MapView.getState` and `MapView.updateState` should use data classes and not plain objects. ```kotlin // ❌ Before mapView.updateState(space, mapOf("interactive" to true)) { } // ✅ After mapView.updateState(space, GeometryUpdateState(interactive = true)) { } ``` ## 6.0.0-alpha.1 - December 4, 2025 - Upgraded to Mappedin JS v6.7.0. ## 6.0.0-alpha.0 - December 3, 2025 - Initial release of Mappedin SDK for Android v6. ### Spaces # Spaces > A Space represents an area enclosed by walls, such as a hall or room. Spaces can be Interactive and have Labels and Markers added to them. Spaces can also be customized with a color and texture. ## Spaces Example The example below loops through all spaces and makes them interactive. Refer to the Textures & Colors (coming soon) section for more information on how to set the texture or color of a space. ```kotlin // Set all spaces to be interactive so they can be clicked mapView.mapData.getByType(MapDataType.SPACE) { result -> result.onSuccess { spaces -> spaces.forEach { space -> mapView.updateState(space, mapOf("interactive" to true)) { } } } } ``` ## Doors By default, a Door is not visible and drawn as a gap in a wall. An app can set the `visible` property to `true` to make the door visible. Other properties of a door can also be set, such as color, texture, interactivity and more. Refer to DoorsState for the complete list of properties. Refer to the Textures & Colors (coming soon) section for more information on how to set the texture or color of a door. Doors are grouped into DOORS.Interior and DOORS.Exterior doors, based on whether they are on an interior or exterior wall. ```kotlin // Make interior doors visible and brown. mapView.updateState( Doors.INTERIOR.value, mapOf( "visible" to true, "color" to "#5C4033", "opacity" to 0.6, ), ) { } // Make exterior doors visible and black. mapView.updateState( Doors.EXTERIOR.value, mapOf( "visible" to true, "color" to "black", "opacity" to 0.6, ), ) { } ``` The screenshot below shows brown interior and black exterior doors with labels added to depict the status of the door. !Visible Doors