Available for an ArcGIS organization licensed with the IPS extension.
The ArcGIS IPS Information Model supports the management of indoor positioning information necessary to share properly configured web maps and mobile map packages for use with the ArcGIS IPS Setup app and other indoor positioning-enabled apps.
The IPS model consists of the IPS Positioning table, IPS Recordings feature class, and Beacons feature class. Use the Enable Indoor Positioning tool to create the required table and feature classes, which contain all the fields required for IPS-enabled apps.
You can then add data to the IPS Recordings feature class using the IPS Setup app and visualize the trajectories of survey recordings in ArcGIS Pro. The Generate Indoor Positioning File tool processes the survey data into a positioning file that is stored in the IPS Positioning table. The positioning file contains all the information necessary to enable indoor positioning. Each positioning file contains data for a single site.
The Beacons feature class contains data including beacon locations and configuration.
ArcGIS IPS also leverages additional data that comes from the ArcGIS Indoors Information Model, including the following:
- Floor plan data—Includes the Sites, Facilities, Levels, Units, and Details feature classes, which contain data that describes floor plans and indoor spaces.
- Transitions—In the Indoors model, the Transitions feature class contains features representing transitions between floors, such as stairs and elevators. The IPS model extends this feature class by using a domain to include transitions between indoor and outdoor spaces.
- Pathways—Linear features that represent traversable space. When marked for use with ArcGIS IPS, path snapping is enabled to enhance the blue dot experience.
Feature classes
Name | Description |
---|---|
IPS Recordings | A linear feature class used by the ArcGIS IPS Setup app to store indoor positioning survey recordings. This feature class is also the input for the Generate Indoor Positioning tool. |
Beacons | A point feature class that describes the geographic location and attributes of beacons located in a facility. |
Table
Name | Description |
---|---|
IPS Positioning | The output table that is populated by the Generate Indoor Positioning File tool and contains file attachments to enable indoor positioning within IPS Setup and custom IPS apps using ArcGIS Runtime. |
IPS model feature class details
IPS recordings
Field name | Type | Is nullable | Description |
---|---|---|---|
SITE_ID | Text | True |
Records the unique ID of the feature’s associated site and can be used to identify the feature’s associated site feature in floor-aware maps. A feature can only be related to a single site using the Site ID field. |
FACILITY_ID | Text | True |
Records the unique ID of the feature’s associated facility and is used to identify the feature’s associated facility feature in floor-aware maps. A feature can only be related to a single facility using the Facility ID field. |
LEVEL_ID | Text | True |
Records the unique ID of the feature’s associated level and is used to identify the feature’s associated level feature in floor-aware maps. A feature can only be related to a single level using the Level ID field. |
SURVEY_DATE | Date | False |
Records the date on which the survey path was recorded in the IPS Setup app. |
COMMENT | Text | True |
Records the user’s comment about the recording when it was created and uploaded to the table using the IPS Setup app. |
SURVEYOR | Text | True | Records the username of the user logged in to the IPS Setup app. |
DEVICE | Text | True |
Records the device name and model with which the recording was created. |
APP_VERSION | Text | False |
Records the version of the IPS Setup app used to create the recording. |
RECORDING_TYPE | Text | True | Specifies the type of survey recording. The DOM_IPS_RECORDING_TYPE domain defines the following allowed field values:
|
BLUETOOTH | Long | True | Records if the survey recording contains Bluetooth data. The DOM_BOOLEAN domain defines the following allowed field values:
|
WIFI | Long | True | Records if the survey recording contains Wi-Fi data. The DOM_BOOLEAN domain defines the following allowed field values:
|
GLOBALID | Global ID | False |
Uniquely identifies a feature or table row in a geodatabase and across geodatabases. It’s a store registry-style string consisting of 36 characters enclosed in curly brackets in a geodatabase. |
PLANNING_DATE | Date | False | Records the date the survey path was created. This field is automatically populated by a calculation attribute rule with the current date when a new feature is created in the feature class. |
Beacons
Field name | Type | Is nullable | Description |
---|---|---|---|
VENDOR | Text | True |
The name of the beacon vendor. |
BEACON_ID | Text | True |
Uniquely identifies a Bluetooth beacon. This value may also be called a vendor ID. |
UUID | Text | True |
A Universal Unique Identifier consists of 32 hexadecimal characters split into five groups separated by hyphens. The length of each group is 8-4-4-4-12, for example: aa72426e-955d-41fb-9aaa-d67c749198a6 UUIDs can be generated locally (there is no central authority for coordination or registration) and are configurable for Bluetooth beacons. As per the iBeacon protocol, the same UUID is associated to a subset of a beacon network and is part of their advertised message. The triplet (UUID, MAJOR, MINOR) identifies a specific beacon in a network. |
MAJOR | Long | True |
A 2-byte unsigned integer that is associated to a Bluetooth beacon. As per the iBeacon protocol, this can be used to further distinguish a group of beacons in a network and is part of the advertised message. The triplet (UUID, MAJOR, MINOR) identifies a specific beacon in a network. |
MINOR |
Long | True |
A 2-byte unsigned integer that is associated to a Bluetooth beacon. As per the iBeacon protocol, this can be used to further distinguish a group of beacons in a network and is part of the advertised message. The triplet (UUID, MAJOR, MINOR) identifies a specific beacon in a network. |
PROTOCOL | Text | True | The Bluetooth protocol used by the beacons. Only iBeacon is supported at the current release. |
RSSI_1M | Float | True |
The Received Signal Strength Indicator at 1 meter distance. This value is specified by the Bluetooth beacon vendor. |
ADVERTISING_INTERVAL_MS | Float | True |
The interval in milliseconds at which the beacon broadcasts its messages. |
LEVEL_ID | Text | True | The Level ID of the level feature on which the beacon is located. |
BATTERY_LEVEL | Float | True |
The residual battery level of the beacon as a percentage of total battery. |
LAST_SEEN | Date | True | The date and time at which a beacon's signal was last observed. |
PLACEMENT_DATE | Date | True | The date and time at which a beacon was deployed. |
GLOBALID | Global ID | False |
Uniquely identifies a feature or table row in a geodatabase and across geodatabases. It’s a store registry-style string consisting of 36 characters enclosed in curly brackets in a geodatabase. |
IPS model table details
IPS positioning
Field name | Type | Is nullable | Description |
---|---|---|---|
SITE_ID | Text | True |
Records the unique ID of the feature’s associated site and can be used to identify the feature’s associated site feature in floor-aware maps. A feature can only be related to a single site using the Site ID field. |
DATE_CREATED | Date | False |
Records the date the Generate Indoor Positioning File tool was run, and IDM file was created. |
DATA | Text | False |
Records the name of the IDM file, which is added as an attachment to that record. |
COMMENT | Text | True |
Records comments specified in the Generate Indoor Positioning File tool. |
BLUETOOTH | Long | True | Records if the positioning file supports Bluetooth positioning. The DOM_BOOLEAN domain defines the following allowed field values:
|
WIFI | Long | True | Records if the positioning file supports Wi-Fi positioning. The DOM_BOOLEAN domain defines the following allowed field values:
|
GLOBALID | Global ID | False |
Uniquely identifies a feature or table row in a geodatabase and across geodatabases. It’s a store registry-style string consisting of 36 characters enclosed in curly brackets in a geodatabase. |