Indoor positioning

ArcGIS IPS is an indoor positioning system that allows you to locate yourself and others inside a building in real time. Similar to GPS, it puts a blue dot on indoor maps and uses location services to help you navigate to any point of interest or destination.

ArcGIS IPS supports:

• Real-time indoor wayfinding
• Real-time indoors location tracking and sharing
• Real-time indoor location data collection
• Indoor analytics

Your ArcGIS Runtime app can work with ArcGIS IPS to show device location using an indoor location data source.

How ArcGIS IPS works

ArcGIS IPS provides geoprocessing tools for setting up and authoring your IPS environment in ArcGIS Pro. It also includes ArcGIS Setup, a mobile app to collect radio signals from Bluetooth Low Energy (BLE) Beacons inside your building(s) to enable the indoor positioning system. It can make use of an existing or new beacon infrastructure and is beacon vendor agnostic.

See Get started with ArcGIS IPS in the ArcGIS Pro documentation for detailed instructions for setting up an indoor positioning system.

At version 100.14, ArcGIS Runtime supports Wi-Fi for indoor positioning on Android devices. ArcGIS IPS does not support BLE and Wi-Fi systems in the same facility but a mix of these systems can be deployed in different facilities within the same site.

Android 9 introduced Wi-Fi scan throttling to limit the number of Wi-Fi scans. To use Wi-Fi IPS, Android devices (9 or higher) must enable developer mode and disable Wi-Fi scan throttling (Developer Options > Networking > Wi-Fi scan throttling).

Floor-aware maps

ArcGIS Setup supports two types of floor-aware maps:

• ArcGIS Indoors floor-aware maps created according to the ArcGIS IPS Information Model.
• ArcGIS IPS floor-aware maps created using the guidelines described in the ArcGIS Pro Create floor plan data topic. Creating this type of floor-aware map does not require an ArcGIS Indoors license.

The ArcGIS Setup app automatically displays a floor picker when one of the two supported floor-aware maps is used. The floor picker is a custom component that you might want to implement in your own ArcGIS Runtime app. For an ArcGIS Indoors map, you can use the FloorManager class to expose available sites, facilities, and levels in your floor picker. For an ArcGIS IPS map, you'll need to also implement a custom floor manager component to manage those datasets in a floor picker.

IPS positioning table

An IPS positioning feature table is stored with an IPS-enabled map. Each row in the table contains an indoor positioning file. The positioning file is created when setting up the IPS environment using the Generate positioning file geoprocessing tool. The tool processes one or more indoor surveys and creates a new row in the IPS positioning table with the positioning file (as an attachment) along with the date and time it was created. When working with an indoor location source in your ArcGIS Runtime app, the most recent positioning file is used unless you specify a different one, as described in the following section.

Indoor location data source

Your app can work with indoor positioning by using a location data source and the geoview's location display. The basics are the same as working with any other LocationDataSource . The IndoorsLocationDataSource wraps the logic to find location using an indoor positioning file, Bluetooth signals, and information from device sensors. The IndoorsLocationDataSource provides the geographic location along with other metadata, such as the floor.

To work with ArcGIS IPS, the constructor for the IndoorsLocationDataSource requires an IPS positioning table. Optionally, you can provide the following.

• Row ID: A globally unique ID that identifies a row in the IPS positioning table. The positioning file associated with this row will be used to find indoor locations. If not specified in the constructor, the positioning file from the most recent survey is used.

• Pathways table: An ArcGISFeatureTable with line features that represent paths through the indoor space. Locations provided by the IndoorsLocationDataSource are snapped to the lines in this feature class.

In the image below, the red + represents raw locations determined by the IPS. These locations are snapped to the nearest line feature in the pathways feature table before being displayed. This provides a more consistent display of the blue dot as it moves across the map.

You can handle a status changed event for the IndoorsLocationDataSource to be notified when the location data source starts, stops, or fails to start.

Caching the positioning file

Upon creation, an IndoorsLocationDataSource caches its positioning file on the device. The next time an indoors location data source is created for the same positioning table, the cached version of the file will be used under any of these circumstances:

• The cached positioning file is requested in the constructor (by row ID).
• A row ID isn't provided in the constructor and the cached positioning file is determined to be the most recent one available.
• No internet connection is available.

Handle location change

You can handle the location changed event for the IndoorsLocationDataSource to read information about the current LocationDataSource.Location .

An IPS location populates additional properties with the current floor and the transmitter (beacon) count. When the floor changes, you can update the map to filter the display of features for the current floor. The floor value returned with the location is an integer that represents the vertical offset, where 0 is the ground floor. This value increases by one for each floor above the ground floor and decreases by one for each floor below.

Use code like the following to read additional properties for the location when it changes.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
private fun updateMetadata(location: LocationDataSource.Location) {
    if (location.additionalSourceProperties["floor"] != null) {
        val floor = location.additionalSourceProperties["floor"]
        // Call a function to filter layers for the current floor (level).
        if (mMapView!!.map != null && mMapView!!.map.loadStatus == LoadStatus.LOADED) {
            val newFloor = floor.toInt()
            setupLayers(newFloor)
        }
    }
}

In addition to getting the floor, you can get the position source, which will be BLE (Bluetooth Low Energy) when using IPS and GNSS (Global Navigation Satellite Systems) when using GPS. You can also get the count of transmitters (beacons) or satellites used to determine the location.

You can use a definition expression to filter layers in the map to only show features for the current floor. For efficiency, you should only filter features when the floor changes rather than with each location update. Depending on the schema for your floor-aware data, you may need to map the vertical offset value to a level ID in order to filter features by floor (level).

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
private fun setupLayers(floor: Int) {
    // Check that the floor is valid and has changed.
    mCurrentFloor = if (mCurrentFloor == null || mCurrentFloor != floor) {
        floor
    } else {
        return
    }
    val layerList = mMapView!!.map.operationalLayers
    for (layer in layerList) {
        val name = layer.name
        // Filter applicable layers to show features for the current floor (level).
        if (layer is FeatureLayer && (name == "Details" || name == "Units" || name == "Levels")) {
            layer.definitionExpression = "VERTICAL_ORDER = " + floor
        }
    }
}

Examples

1
2
3
android.permission.BLUETOOTH_ADMIN
android.permission.BLUETOOTH
android.permission.ACCESS_FINE_LOCATION

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
// Get the positioning table from the map.
val featureTables = mMapView!!.map.tables
val positioningTable = featureTables.stream()
            .filter { ft: FeatureTable -> ft.tableName == "ips_positioning" }
            .findFirst()
if (positioningTable==null) {
        Toast.makeText(this@MainActivity, "Positioning table not found", Toast.LENGTH_LONG).show()
        return
    }

// Get the pathways layer (optional for creating the IndoorsLocationDataSource).
// This enables path snapping of locations (to hallway centerlines, for example).
val resultPathwaysLayer = mMapView!!.map.operationalLayers.stream()
            .filter { opLayer: Layer -> opLayer.name == "Pathways" }
            .findFirst()
if (resultPathwaysLayer.isPresent) {
    // If there's a pathways layer, use its ArcGISFeatureTable to create the indoors location data source.
    val pathwaysLayer = resultPathwaysLayer.get() as FeatureLayer
    val pathwaysTable = pathwaysLayer.featureTable as ArcGISFeatureTable

    mIndoorsLocationDataSource = IndoorsLocationDataSource(
        this@MainActivity,
        positioningTable,
        pathwaysTable
    )
}else {
    // If no pathways, create the IndoorsLocationDataSource with the positioning table only.
    mIndoorsLocationDataSource = IndoorsLocationDataSource(
        this@MainActivity,
        positioningTable,
        null
    )
}

// The listener which will receive location, heading, and status updates from the data source.
mIndoorsLocationDataSource!!.addLocationChangedListener(this@MainActivity)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
    private fun setupLocationDisplay() {
        mLocationDisplay = mMapView!!.locationDisplay
        mLocationDisplay!!.setAutoPanMode(LocationDisplay.AutoPanMode.COMPASS_NAVIGATION)
        // Assign the IndoorLocationDataSource.
        mLocationDisplay!!.setLocationDataSource(mIndoorsLocationDataSource)
        // Asynchronously start the location display which will trigger IndoorsLocationDataSource to start receiving IPS updates.
        mLocationDisplay!!.startAsync()
    }