Available with the ArcGIS Indoors Pro or ArcGIS Indoors Maps extension.
The Indoor dataset schema is a streamlined schema that conforms to the ArcGIS Indoors Information Model. The Indoor dataset schema supports managing the indoor GIS information necessary to establish basic visualization and routing capabilities for floor plan mapping. The Indoor dataset schema can be applied to an existing workspace using a series of tools that include the following:
- Create Indoor Dataset (required)
- Create Indoor 3D Dataset (optional)
- Create Indoor Network Dataset (optional)
The schema created by these tools consists of feature datasets with a collection of feature classes between them to use for floor plan mapping. This schema is extensible and can be modified using the tools in ArcGIS Pro to maintain additional information required by your organization.
Note:
If you require support for space planning, workspace reservations, or advanced floor plan mapping and routing, use the Create Indoors Database tool to apply the full Indoors model to an existing workspace. The full Indoors model created by this tool contains additional feature classes, fields, and tables that support the Space Planner app and advanced functionality in the Indoor Viewer and Indoors mobile apps, such as conference room and office hotel booking.
If you have an existing Indoor dataset or workspace and want to upgrade it to the full version of the Indoors model schema, use the Upgrade Indoors Database tool to automatically add any remaining feature classes, fields, tables, and domains that are created by the Create Indoors Database tool.
Feature datasets
| Name | Description |
|---|---|
Required. This dataset manages the indoor GIS data that defines 2.5D floor plans for use with floor-aware maps and apps. This feature dataset is created using the Create Indoor Dataset tool in ArcGIS Pro and contains feature classes organized by functional levels. | |
Optional. This dataset manages the indoor GIS data that defines 3D floor plans for use with floor-aware maps and apps. This feature dataset is created using the Create Indoor 3D Dataset tool in ArcGIS Pro and contains multipatch feature classes organized by functional levels. | |
Optional. This dataset manages the network artifacts that are created to support routing between indoor spaces. These features are created using the Indoors geoprocessing tools in ArcGIS Pro. | |
Optional. This dataset stores preliminary network artifacts used in the process of generating the final network. |
Indoor dataset feature classes
The indoor feature dataset consists of feature classes that represent floor plan information in 2.5D for visualization and analysis purposes.
These feature classes are organized in a hierarchy with assumed spatial relationships defined in the following ascending order:
- Units and Details
- Levels
- Facilities
- Sites
| Name | Description |
|---|---|
Describes your linear architectural features, such as walls, doors, windows, and so on. Details are used to constrain generated network pathways and to support visualization. Details features should be contained in a Levels feature. | |
Describes the footprints of your managed buildings and other structures. A facility can represent any occupiable structure, such as an office or campus building, retail setting, warehouse, generator or pump house, silo, or any industrial structure. It is recommended that Facilities features be contained in a Sites feature. | |
Describes the footprint of each occupiable floor contained in your managed facilities. Levels footprints must be contained in a Facilities feature. | |
Describes the boundaries of your managed sites and is used for visualization in mapmaking. | |
Describes the footprints of nonoverlapping individual functional areas such as workspaces, amenities, retail spaces, elevators and stairways, and so on. Unit footprints must be contained in a Levels feature. |
Indoor dataset feature class details
Click a link to go to a feature class details table.
| Details | Facilities | Levels | Sites | Units |
Details
| Field name | Type | Is nullable | Description |
|---|---|---|---|
DETAIL_ID | Text | False |
Defines a unique ID for the feature. This value must be unique in the table. The uniqueness of this field is not enforced by the geodatabase. |
|
HEIGHT_RELATIVE | Double | True |
Defines the height of the feature relative to the bottom of the floor. Define height in meters—for example, Level 1 = 4.25 m, Level 2 = 4.25 m, and so on. |
LEVEL_ID | Text | False |
Records the unique ID of the feature’s associated level. This ID 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. |
|
USE_TYPE | Text | True |
Distinguishes feature types used in tool processing and supports differences in symbology for mapmaking. |
Facilities
| Field name | Type | Is nullable | Description |
|---|---|---|---|
FACILITY_ID | Text |
False |
Defines a unique ID for the feature. This value must be unique in the table. The uniqueness of this field is not enforced by the geodatabase. |
HEIGHT_RELATIVE | Double | True |
Defines the height of the facility compared to the bottom of the ground floor of the facility. Define height in meters. Required if: This field is used when creating a 3D scene. |
NAME | Text | False |
Defines the name of the feature. In most cases, the NAME field of a feature is the most commonly used field for naming features. |
NAME_LONG | Text | True |
Defines a long name for a feature. The long name is used to support descriptive capabilities in the Indoors web and mobile apps. |
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. |
Levels
| Field name | Type | Is nullable | Description |
|---|---|---|---|
AREA_GROSS | Double |
True |
Records the total gross area of a feature. |
FACILITY_ID | Text | False |
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. |
HEIGHT_RELATIVE | Double | True |
Defines the height of the feature relative to the bottom of the floor. Define height in meters—for example, Level 1 = 4.25 m, Level 2 = 4.25 m, and so on. |
LEVEL_ID | Text | False |
Defines a unique ID for the feature. This value must be unique in the table. The uniqueness of this field is not enforced by the geodatabase. |
LEVEL_NUMBER | Long | False |
Records the facility-specific level number. |
|
NAME | Text | False |
Defines the name of the feature. The level name is used to support floor filtering in floor-aware apps. |
NAME_SHORT | Text | False |
Defines a short name for a feature. The short name is used to support floor filtering in floor-aware apps. Some floor-aware apps only display a short name in the level filter, while some may use the name or allow the user to switch between the name and the short name. |
VERTICAL_ORDER | Long | False |
Uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero. Positive values represent floors above ground, and negative values represent floors below ground. Vertical order values must be continuous and cannot skip a value in the sequence. |
Sites
| Field name | Type | Is nullable | Description |
|---|---|---|---|
NAME | Text | False |
Defines the name of the feature. In most cases, the NAME field of a feature is the most commonly used field for naming features. |
NAME_LONG | Text | True |
Defines a long name for a feature. The long name is used to support descriptive capabilities in the Indoors web and mobile apps. |
SITE_ID | Text | False |
Defines a unique ID for the feature. This value must be unique in the table. The uniqueness of this field is not enforced by the geodatabase. |
Units
| Field name | Type | Is nullable | Description |
|---|---|---|---|
AREA_GROSS | Double | True |
Records the total gross area of a feature. |
HEIGHT_RELATIVE | Double | True |
Defines the height of the feature relative to the bottom of the floor. Define height in meters—for example, Level 1 = 4.25 m, Level 2 = 4.25 m, and so on. |
LEVEL_ID | Text | False |
Records the unique ID of the feature’s associated level. This ID 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. |
NAME | Text | False |
Defines the name of the feature. In most cases, the NAME field of a feature is the most commonly used field for naming features. |
NAME_LONG | Text | True |
Defines a long name for a feature. The long name is used to support descriptive capabilities in the Indoors web and mobile apps. |
UNIT_ID | Text |
False |
Defines a unique ID for the feature. This value must be unique in the table. The uniqueness of this field is not enforced by the geodatabase. |
USE_TYPE | Text | True |
Distinguishes feature types used in tool processing and supports differences in symbology for mapmaking. |