Available with the ArcGIS Indoors Pro or ArcGIS Indoors Maps extension.
The ArcGIS Indoors Information Model supports the management of indoor GIS information necessary to share properly configured web maps and mobile map packages for use with Indoor Viewer, Indoor Space Planner, Indoor Floor Plan Editor, Indoors mobile, and other apps that use floor-aware maps and scenes.
The Indoors model consists of three feature datasets, along with a collection of feature classes and three tables that maintain configuration information. You can use the Create Indoors Database tool to apply the Indoors model to an existing workspace. The Indoors workspace created by this tool contains all the fields and tables that are required to support space planning, routing, and workspace reservations in addition to basic floor plan mapping. If you plan to create a floor-aware scene, you can use the Create Indoor 3D Dataset tool to create a feature dataset with multipatch feature classes that conform to the Indoors model.
Note:
Alternatively, if you only require support for basic floor plan mapping, you can use the Create Indoor Dataset and Create Indoor Network Dataset tools to create datasets that use a streamlined schema of the Indoors model. These tools do not contain all the fields and tables required for space planning and workspace reservations.
If your Indoors geodatabase was created using a previous version of ArcGIS Pro, you can use the Upgrade Indoors Database tool to update your existing Indoors geodatabase schema to the latest version of the ArcGIS Indoors Information Model schema.
Data can then be loaded into the Indoors model from Revit files using the Import BIM To Indoor Dataset tool, IFC files using the Import IFC To Indoor Dataset tool, or CAD files using the Import CAD To Indoor Dataset or Import Floorplans To Indoors Geodatabase tool.
Updates to the Indoors model
The table below describes the changes that were made to the Indoors model in recent software updates:
ArcGIS Pro version | Schema item | Change | Description |
---|---|---|---|
3.3 | Workspace area management domains | New domain values added: Meeting Room added to DOM_ASSIGNMENT_TYPE domain Workspace added to DOM_AREA_TYPE domain | These domain values support workspace areas in the Indoors web and mobile apps. |
3.2 | Reservations feature class | New fields added: RECURRENCE_ID and RECURRENCE_CONFIG | These fields store information that supports the creation of recurring office hotel bookings in Indoor Viewer and Indoors mobile. |
3.0 | Reservations feature class | New fields added: RESERVED_BY_FULL_NAME and RESERVED_BY_USERNAME | These fields store information that enable reservation managers to book office hotels for other people in Indoor Viewer and Indoors mobile. |
Reservations feature class | New constraint attribute rule | The Reservations constraint attribute rule enhances security for reservation management in ArcGIS Enterprise. | |
Occupants feature class | New feature class | The Occupants feature class is used for maintaining occupant data. | |
Area Roles table | New table | The Area Roles table supports reservation management. | |
Pathways and PrelimPathways feature classes | New field added: LEVEL_ID | The Level ID field can be used to configure pathways layers as floor-aware and apply the floor filter to visualize pathway features. | |
Areas table | New field added: CONFIG | The configuration field supports hotel scheduling limits in the Indoors apps. | |
New domains for equipment filtering added: DOM_EQUIPMENT, DOM_EQUIPMENT_HOTEL, DOM_EQUIPMENT_MEETING | These domains can be applied to custom equipment fields to support filtering office hotels and meeting rooms by available equipment in Indoor Viewer and Indoors mobile. | ||
New feature dataset | The Indoor 3D dataset contains feature classes used for managing indoor GIS data that defines 3D floor plans for use in floor-aware scenes. |
Feature datasets
The Indoors model includes the following feature datasets:
Name | Description |
---|---|
Manages the GIS data that defines indoor spaces for use with Indoors apps. These features are created using the Indoors geoprocessing tools in ArcGIS Pro and are organized by functional levels. | |
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. Note:This feature dataset is optional when using the Create Indoors Database tool. It is created using the Create Indoors Database tool or the Create Indoor Network Dataset tool. | |
Stores preliminary network artifacts used in the process of generating the final network. These features are created using the Indoors geoprocessing tools in ArcGIS Pro. Note:This feature dataset is optional when using the Create Indoors Database tool. | |
Optional. This feature 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. Note:This feature dataset should not be versioned when using an enterprise geodatabase. Versioning is not supported when sharing editable web scene layers. |
Tables
The Indoors model includes the following tables:
Name | Description |
---|---|
Describes various settings that can be configured for sharing a location in the Indoors mobile apps with the option of opening it in an associated Indoor Viewer app. | |
Used to delineate sets of Units that share common space management characteristics such as department, scheduling limits, or cancellation policy. Types of areas include Hotels and Hot Desks. This table is populated and managed by Indoor Space Planner. | |
Provides data model support for configuring reservation managers in Indoor Space Planner. |
Indoors dataset feature classes
The Indoors feature dataset consists of feature classes that are organized into a hierarchy with assumed spatial relationships defined in the following descending order:
- Units/Details/Events/Occupants/Reservations
- Sections/Zones/TrackingZones
- Levels
- Facilities
- Sites
The Indoors dataset includes the following feature classes:
Name | Description |
---|---|
Describes linear assets, such as walls, doors, windows, and so on. Details are used to constrain generated network pathways and to support visualization. Details lines must be contained in a Levels feature. | |
Describes event locations and is used to support the search and explore capabilities, identification, routing, and identification of landmarks in routing. Events are manually loaded from other data sources. The Events feature class can contain both indoor and outdoor information. | |
Describes the footprints of managed buildings. | |
Describes the footprint of each level contained in managed facilities. Levels footprints must be contained in a Facilities feature. | |
Contains data about building occupants. This data is used to visualize person assignments on the map and is used for space planning and workspace reservations in the Indoors web and mobile apps. | |
A floor-aware and time-aware layer that contains reservation features. This editable layer is used to manage workspace reservations and visualize reservations on a map. | |
Describes the footprints of nonoverlapping areas of organization in a level, such as wings, and is used for visualization in mapmaking. Sections footprints must be contained in a Levels feature. | |
Describes the boundaries of managed sites and is used for visualization in mapmaking. | |
Describes geofences for device tracking, areas where device tracking should be enabled. Devices located in a tracking zone will be tracked if configured in your environment. | |
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. | |
Describes the footprints of possibly overlapping areas of organization in a level— such as security, functional, managerial, retail zones, and so on—and is used for visualization in mapmaking. Zones footprints must be contained in a Levels feature. |
Network feature classes
The Indoors model Network dataset includes the following feature classes:
Name | Description |
---|---|
Describes easily recognizable points that are used as callouts in directions when routing between locations in the Indoors web and mobile apps. | |
Describes the network pathways generated by the Indoors geoprocessing tools in ArcGIS Pro for routing between locations on the same level. | |
Describes the network transitions generated by the Indoors geoprocessing tools in ArcGIS Pro for routing between levels. |
PrelimNetwork feature classes
The Indoors PrelimNetwork dataset includes the following feature classes:
Name | Description |
---|---|
Describes the preliminary network pathways generated by the Indoors geoprocessing tools in ArcGIS Pro for routing between locations on the same level. | |
Describes the preliminary network transitions generated by the Indoors geoprocessing tools in ArcGIS Pro for routing between levels. |
Indoor 3D dataset feature classes
The Indoor3D feature dataset consists of multipatch feature classes that represent floor plan information in 3D for visualization purposes.
The feature classes are organized similar to the 2.5D schema, with some additional feature classes for common categories of features. When populating the dataset, you can choose to store multipatch features representing walls, doors, windows, and furniture together in the Details3D feature class or distributed among the Walls3D, Doors3D, Windows3D, and Furniture3D feature classes.
Name | Description |
---|---|
Describes any type of detailed architectural features, such as walls, doors, windows, and so on. This feature class is used to support visualization. | |
Describes different types of doors. This feature class is used to support visualization. | |
Describes your managed buildings and other structures. This feature class is used to support visualization. | |
Describes different types of furniture, such as desks, chairs, and so on. This feature class is used to support visualization. | |
Describes different types of transitions between floors, such as stairways, escalators, and ramps. This feature class is used to support visualization. | |
Describes individual functional areas such as workspaces, amenities, retail spaces, and so on. This feature class is used to support visualization. | |
Describes different types of walls. This feature class is used to support visualization. | |
Describes different types of windows. This feature class is used to support visualization. |
Indoors model feature class fields
Click a link to go to a feature class fields table.
Note:
All fields that have an Is nullable value of True are optional.
| Details | Events | Facilities | Levels | Occupants | Reservations | Sections | Sites | TrackingZones | Units | Zones |
Details
The Details feature class includes the following fields:
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. Note:This field is populated by the Import Floorplans To Indoors Geodatabase tool when you import floor plans from CAD data. If you import floor plans from BIM data using the Import BIM To Indoor Dataset tool, this field is not populated by default, but you can populate it manually. |
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. |
Events
The Events feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
DATE_END | Date | False |
Defines the end date for the event in coordinated universal time (UTC). |
DATE_START | Date | False |
Defines the start date for the event in coordinated universal time (UTC). |
DESCRIPTION | Text | True |
Provides a description of the feature for use in turn-by-turn directions. |
EVENT_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. |
IMAGE_URL | Text | True |
Provides a URL for displaying a single associated image in pop-ups in the Indoors web and mobile apps. |
LEVEL_ID | Text | True |
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. |
NAME_SUBTITLE | Text | True |
Defines a subtitle for a feature. A subtitle is required to support some capabilities in the Indoor Viewer app. |
UNIT_ID | Text | True |
Records the unique ID of the feature’s associated unit and can be used to identify the feature’s associated unit feature. A feature can only be related to a single unit using the Unit ID field. |
USE_TYPE | Text | False |
Distinguishes feature types used in tool processing and supports differences in symbology for mapmaking. |
Facilities
The Facilities feature class includes the following fields:
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. This field is used when creating a 3D scene. Note:This field is populated by the Import Floorplans To Indoors Geodatabase tool when you import floor plans from CAD data. If you import floor plans from BIM data using the Import BIM To Indoor Dataset tool, this field is not populated by default, but you can populate it manually. |
LEVELS_ABOVE_GROUND | Long | True | Defines the total number of floors in a facility that are above ground. 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
The Levels feature class includes the following fields:
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. Note:This field is populated by the Import Floorplans To Indoors Geodatabase tool when you import floor plans from CAD data. If you import floor plans from BIM data using the Import BIM To Indoor Dataset tool, this field is not populated by default, but you can populate it manually. |
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. In most cases, the NAME field of a feature is the most commonly used field for naming features. |
NAME_SHORT | Text | False |
Defines a short name for a feature. The short name is used to support the floor picker in the Indoors web and mobile apps. |
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. |
Occupants
The Occupants feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
KNOWNAS |
Text |
False |
The occupant's name, including first and last name. |
Text | False | The occupant's unique email address. Two occupants can have the same known name, but their email addresses should be different. | |
UNIT_ID | Text | True | The unique ID of the unit to which the occupant is assigned. |
LEVEL_ID | Text | True | The unique ID of the level on which the occupant's assignment is located. |
AREA_ID | Text | True | The unique ID of the hotel area to which the occupant is assigned. |
SITE_ID | Text | True | The unique ID of the site to which the occupant is assigned. |
CONTACT_PHONE | Text Text | True | The phone number where the occupant can be reached directly. |
CONTACT_EXTENSION | Text | True | The phone extension that must be added to the contact phone number to reach the occupant directly. |
JOB_TITLE | Text | True | The occupant's job title. |
ORG_LEVEL_1 | Text | True | The department to which the occupant is assigned. |
ORG_LEVEL_2 | Text | True | The team to which the occupant is assigned. |
START_DATE | Date | True | The occupant's start date. |
Reservations
The Reservations feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
ALL_DAY |
Long |
False |
Indicates whether a reservation is an all-day event. The following domain describes the allowed values:
|
CHECK_IN_TIME | Date | True | The date and time (in UTC) that the people for whom the reservation was made checked in. |
CHECK_OUT_TIME | Date | True | The date and time (in UTC) that the people for whom the reservation was made checked out. |
DESCRIPTION | Text | True | A description of the reservation or meeting. |
END_TIME | Date | False | The scheduled end date and time of the reservation (in UTC). |
LEVEL_ID | Text | True | The unique ID for the level on which the feature is located. |
RESERVED_BY_FULL_NAME | Text | True | The full name of the reservation manager who created a reservation on someone else's behalf. |
RESERVED_BY_USERNAME | Text | True | The ArcGIS organization username of the reservation manager who created a reservation on someone else's behalf. |
RECURRENCE_CONFIG | Text | True | Populated and managed by Indoor Viewer and Indoors mobile to support recurring bookings for office hotels. |
RESERVED_FOR_FULL_NAME | Text | False | The full name of the person for whom the reservation is held. This is useful for display and labeling. |
RESERVED_FOR_USERNAME | Text | False | The ArcGIS organization username of the person for whom the reservation is held. |
RECURRENCE_ID | Text | True | A GUID value populated and managed by Indoor Viewer and Indoors mobile to support recurring bookings for office hotels. This value can be shared by multiple reservations to indicate they belong to the same recurrence. |
START_TIME | Date Date | False | The scheduled start date and time of the reservation (in UTC). |
STATE | Long | False | The current state of the reservation. The following domain defines the allowed values:
|
TITLE | Text | True | Describes the reservation or meeting. |
UNIT_ID | Text | False | The unit ID of the reserved unit. |
UNIT_NAME | Text | True | The name of the reserved unit. This can be used for display and labeling. |
Sections
The Sections feature class includes the following fields:
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 | True |
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. |
SECTION_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. |
Sites
The Sites feature class includes the following fields:
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. |
TrackingZones
The TrackingZones feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
DESCRIPTION | Text | True |
Provides a description of the feature for use in turn-by-turn directions. |
LEVEL_ID | Text | True |
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. |
TRACK_TYPE | Long | True |
Defines the tracking rule for a feature. It uses a domain to define allowed values:
|
TRACKING_ZONE_ID | Text | True |
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
The Units feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
AREA_GROSS | Double | True |
Records the total gross area of a feature. |
AREA_ID | Text | True |
Records an ID string referencing a Space Planner area. |
ASSIGNMENT_TYPE | Text | True |
Describes the type of space planning use assigned to the unit. It's used by the Indoor Space Planner app. This field uses the following domain to define allowed values:
|
CAPACITY | Long | True |
Records the total capacity 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. |
RESERVATION_METHOD |
Long |
True |
Defines whether a unit is reservable as a meeting room. The following domain defines the allowed values:
Note:This field is only applicable for meeting rooms when using the Reservations layer and is not used for reservations with Microsoft 365. This field is also not used for office hotels or hot desks that are automatically reservable. |
SCHEDULE_EMAIL | Text | True |
Records the email address used to submit reservation requests for the item. |
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. |
Zones
The Zones feature class includes the following fields:
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 | True |
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. |
ZONE_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. |
Network feature class fields
The following subsections describe the landmarks, pathways, and transitions feature class fields.
Note:
All fields that have an Is nullable value of True are optional.
Landmarks
The Landmarks feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
DESCRIPTION | Text | True |
Provides a description of the feature for use in turn-by-turn directions. |
LEVEL_ID | Text | True |
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. |
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. |
Pathways
The Pathways feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
DELAY | Long | True |
Defines the elevator delay in the network for accurate routing time. |
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. |
FACILITY_NAME | Text | True |
Records the name of the feature’s associated facility. The facility name is used in routing to determine when a route leaves and enters a facility and triggers additional text in the turn-by-turn directions. |
LENGTH_3D | Double | False |
Describes the calculated length of the feature in 3D that is used to determine path cost when routing. |
LEVEL_ID | Text | True | 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. |
LEVEL_NAME_FROM | Text | False |
Describes the name of the level on which the feature originates as defined in the indoor feature dataset. |
LEVEL_NAME_TO | Text | False |
Describes the name of the level on which the feature terminates as defined in the indoor feature dataset. |
PATHWAY_RANK | Long | True |
Defines the rank preference of one feature versus another for routing. The following domain is used to define allowed values:
|
PATHWAY_TYPE | Long | True |
Describes the use type of the feature and is used to determine cost and restrictions when routing. The following domain is used to define allowed values:
|
TRAVEL_DIRECTION | Long | True |
Defines the direction of travel for a feature and is used to support restrictions when routing. The following domain is used to define allowed values:
|
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. |
Transitions
The Transitions feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
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. |
FACILITY_NAME | Text | False |
Records the name of the feature’s associated facility. The facility name is used in routing to determine when a route leaves and enters a facility and triggers additional text in the turn-by-turn directions. |
HEIGHT_FROM | Double | True |
Defines the starting height of the feature. |
HEIGHT_TO | Double | True |
Defines the ending height of the feature. |
LENGTH_3D | Double | False |
Describes the calculated length of the feature in 3D that is used to determine path cost when routing. |
LEVEL_NAME_FROM | Text | False |
Describes the name of the level on which the feature originates as defined in the indoor feature dataset. |
LEVEL_NAME_TO | Text | False |
Describes the name of the level on which the feature terminates as defined in the indoor feature dataset. |
TRANSITION_RANK | Long | True |
Defines the rank preference of one feature versus another for routing. The following domain is used to define allowed values:
|
TRANSITION_TYPE | Long | False |
Describes the use type of the feature and is used to determine cost and restrictions when routing. The following domain is used to define allowed values:
|
TRAVEL_DIRECTION | Long | True |
Defines the direction of travel for a feature and is used to support restrictions when routing. The following domain is used to define allowed values:
|
VERTICAL_ORDER_FROM | Long | False |
Defines the order of display and reference to floors in the IPS of the level as defined in the indoor feature dataset on which the feature originates. It uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero. Subsequent positive values represent floors above ground, and negative values represent floors below ground. Vertical Order From values must be continuous and cannot skip a value in the sequence. |
VERTICAL_ORDER_TO | Long | False |
Defines the order of display and reference to floors in the IPS of the level as defined in the indoor feature dataset on which the feature terminates. It uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero. Subsequent positive values represent floors above ground, and negative values represent floors below ground. Vertical Order To values must be continuous and cannot skip a value in the sequence. |
PrelimNetwork feature class fields
The following subsections describe PrelimPathways and PrelimTransitions feature class fields.
Note:
All fields that have an Is nullable value of True are optional.
PrelimPathways
The PrelimPathways feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
ANGLE | Long | True |
Describes the rotation angle of the preliminary pathways. It is used in the process of generating the final network. |
DELAY | Long | True |
Defines the elevator delay in the network for accurate routing time. |
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. |
FACILITY_NAME | Text | False |
Records the name of the feature’s associated facility. The facility name is used in routing to determine when a route leaves and enters a facility and triggers additional text in the turn-by-turn directions. |
LENGTH_3D | Double | False |
Describes the calculated length of the feature in 3D that is used to determine path cost when routing. |
LEVEL_ID | Text | True | 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. |
LEVEL_NAME_FROM | Text | False |
Describes the name of the level on which the feature originates as defined in the indoor feature dataset. |
LEVEL_NAME_TO | Text | True |
Describes the name of the level on which the feature terminates as defined in the indoor feature dataset. |
PATH_EDGE_DISTANCE | Double | True |
Describes the distance of the network edges represented by the pathways. It is used in the process of generating the final network. |
PATHWAY_RANK | Long | True |
Defines the rank preference of one feature versus another for routing. The following domain is used to define allowed values:
|
PATHWAY_TYPE | Long | True |
Describes the use type of the feature and is used to determine cost and restrictions when routing. The following domain is used to define allowed values:
|
TRAVEL_DIRECTION | Long | True |
Defines the direction of travel for a feature and is used to support restrictions when routing. The following domain is used to define allowed values:
|
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. |
PrelimTransitions
The PrelimTransitions feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
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. |
FACILITY_NAME | Text | False |
Records the name of the feature’s associated facility. The facility name is used in routing to determine when a route leaves and enters a facility and triggers additional text in the turn-by-turn directions. |
HEIGHT_FROM | Double | True |
Defines the starting height of the feature. |
HEIGHT_TO | Double | True |
Defines the ending height of the feature. |
LENGTH_3D | Double | False |
Describes the calculated length of the feature in 3D that is used to determine path cost when routing. |
LEVEL_NAME_FROM | Text | False |
Describes the name of the level on which the feature originates as defined in the indoor feature dataset. |
LEVEL_NAME_TO | Text | False |
Describes the name of the level on which the feature terminates as defined in the indoor feature dataset. |
PATH_EDGE_DISTANCE | Double | True |
Describes the distance of the network edges represented by the pathways. It is used in the process of generating the final network. |
TRANSITION_RANK | Long | True |
Defines the rank preference of one feature versus another for routing. The following domain is used to define allowed values:
|
TRANSITION_TYPE | Long | False |
Describes the use type of the feature and is used to determine cost and restrictions when routing. The following domain is used to define allowed values:
|
TRAVEL_DIRECTION | Long | True |
Defines the direction of travel for a feature and is used to support restrictions when routing. The following domain is used to define allowed values:
|
VERTICAL_ORDER_FROM | Long | False |
Defines the order of display and reference to floors in the IPS of the level as defined in the indoor feature dataset on which the feature originates. It uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero. Subsequent positive values represent floors above ground, and negative values represent floors below ground. Vertical Order From values must be continuous and cannot skip a value in the sequence. |
VERTICAL_ORDER_TO | Long | False |
Defines the order of display and reference to floors in the IPS of the level as defined in the indoor feature dataset on which the feature terminates. It uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero. Subsequent positive values represent floors above ground, and negative values represent floors below ground. Vertical Order To values must be continuous and cannot skip a value in the sequence. |
Table fields
The following subsections describe Areas, Area roles, and IndoorsConfig table fields.
Note:
All fields that have an Is nullable value of True are optional.
Areas
The Areas table includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
AREA_ID | Text | False |
Records an ID string referencing a Space Planner area. |
AREA_TYPE | Text | False |
Describes the type of space planning use assigned to the area. It is used by the Indoor Space Planner app. This field uses a domain to define allowed values:
|
AREA_NAME | Text | False |
Describes the name of an Indoor Space Planner area. |
CONFIG | Text | True | Populated and managed by Indoor Space Planner. It is used by Indoor Viewer and Indoors mobile apps to manage configuration information such as cancellation policies and scheduling limits. |
RESTRICTED | Long | True | Describes whether an area can be booked by anyone or only booked by occupants who are assigned to the area. This field uses a domain to define allowed values:
Features with a null field value are treated as unrestricted in Indoor Viewer. |
Area Roles
The Area Roles table includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
AREA_ID | Text | False |
Records an ID string referencing a Space Planner area. |
USERNAME | Text | True |
The reservation manager's associated username in the ArcGIS organization. |
Text | False |
The reservation manager's associated email address in the ArcGIS organization. | |
ROLE | Long | False | This field uses a domain value of 1 to define a Reservation Manager. |
IndoorsConfig
The IndoorsConfig table includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
CONFIG_KEY | Text | True |
Describes the configurable parameter as required by Indoors. |
CONFIG_VALUE | Text | True | Required for configurable items in an implementation. Records the configurable entry as defined by the implementation requirements. |
Indoor 3D dataset feature class fields
Click a link to go to a feature class fields table.
Note:
All fields that have an Is nullable value of True are optional.
| Details3D | Doors3D | Facilities3D | Furniture3D | Transitions3D | Units3D | Walls3D | Windows3D |
Details3D
The Details3D feature class includes the following fields:
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. |
LEVEL_ID | Text | True |
Records the unique ID of the feature's associated level and can be used to identify the feature's associated 2D level feature in floor-aware scenes. A feature can only be related to a single level using the Level ID field. |
SOURCE_ID | Text | True | Records the stable unique ID of the source feature, if available. For features sourced from Revit data, this field will hold the value of the source element's UniqueID property. For features sourced from CAD data, this field will be Null. |
USE_TYPE | Text | True |
Distinguishes feature types to support differences in symbology for visualization. |
Doors3D
The Doors3D feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
DOOR_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. |
DOOR_TYPE | Text | True |
Distinguishes feature types to support differences in symbology for visualization. |
LEVEL_ID | Text | True |
Records the unique ID of the feature's associated level and can be used to identify the feature's associated 2D level feature in floor-aware scenes. A feature can only be related to a single level using the Level ID field. |
SOURCE_ID | Text | True |
Records the stable unique ID of the source feature, if available. For features sourced from Revit data, this field will hold the value of the source element's UniqueID property. For features sourced from CAD data, this field will be Null. |
Facilities3D
The Facilities3D feature class includes the following fields:
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. |
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 2D site feature in floor-aware scenes. A feature can only be related to a single site using the SITE_ID field. |
Furniture3D
The Furniture3D feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
FURNITURE_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. |
FURNITURE_TYPE | Text | True |
Distinguishes feature types to support differences in symbology for visualization. |
LEVEL_ID | Text | True |
Records the unique ID of the feature's associated level and can be used to identify the feature's associated 2D level feature in floor-aware scenes. A feature can only be related to a single level using the Level ID field. |
SOURCE_ID | Text | True |
Records the stable unique ID of the source feature, if available. For features sourced from Revit data, this field will hold the value of the source element's UniqueID property. For features sourced from CAD data, this field will be Null. |
Transitions3D
The Transitions3D feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
LEVEL_ID | Text | True |
Records the unique ID of the feature's associated level and can be used to identify the feature's associated 2D level feature in floor-aware scenes. A feature can only be related to a single level using the Level ID field. |
SOURCE_ID | Text | True |
Records the stable unique ID of the source feature, if available. For features sourced from Revit data, this field will hold the value of the source element's UniqueID property. For features sourced from CAD data, this field will be Null. |
TRANSITION_ID | Text | False |
Records the unique ID of the feature. This value must be unique in the table. The uniqueness of this field is not enforced by the geodatabase. |
TRANSITION_TYPE | Long | True |
Distinguishes feature types to support differences in symbology for visualization. |
Units3D
The Units3D feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
AREA_GROSS | Double | True |
Records the total gross area of a feature. |
LEVEL_ID | Text | True |
Records the unique ID of the feature's associated level and can be used to identify the feature's associated 2D level feature in floor-aware scenes. 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. |
SOURCE_ID | Text | True |
Records the stable unique ID of the source feature, if available. For features sourced from Revit data, this field will hold the value of the source element's UniqueID property. For features sourced from CAD data, this field will be Null. |
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 to support differences in symbology for visualization. |
Walls3D
The Walls3D feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
LEVEL_ID | Text | True |
Records the unique ID of the feature's associated level and can be used to identify the feature's associated 2D level feature in floor-aware scenes. A feature can only be related to a single level using the Level ID field. |
MATERIAL_TYPE | Text | True | Distinguishes feature types to support differences in symbology for visualization. |
SOURCE_ID | Text | True |
Records the stable unique ID of the source feature, if available. For features sourced from Revit data, this field will hold the value of the source element's UniqueID property. For features sourced from CAD data, this field will be Null. |
WALL_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. |
WALL_TYPE | Text | True |
Distinguishes feature types to support differences in symbology for visualization. |
Windows3D
The Windows3D feature class includes the following fields:
Field name | Type | Is nullable | Description |
---|---|---|---|
LEVEL_ID | Text | True |
Records the unique ID of the feature's associated level and can be used to identify the feature's associated 2D level feature in floor-aware scenes. A feature can only be related to a single level using the Level ID field. |
SOURCE_ID | Text | True |
Records the stable unique ID of the source feature, if available. For features sourced from Revit data, this field will hold the value of the source element's UniqueID property. For features sourced from CAD data, this field will be Null. |
WINDOW_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. |
WINDOW_TYPE | Text | True |
Distinguishes features to support differences in symbology for visualization. |
Indoors model coded value domains
The Indoors model schema includes coded value domains applied to specific fields to enable functionality in Indoors apps. For example, there are domains to prioritize paths in an indoor routable network during navigation, as well as domains that determine which rooms are assigned to office hotels and are available for booking in Indoor Viewer and Indoors mobile.
Some of these coded value domains are managed by the user in ArcGIS Pro, while others are managed by Indoors apps.
The following table describes the Indoors model coded value domains:
Domain name / Coded Values | Feature class / Table: Field | Description |
---|---|---|
DOM_ALL_DAY
| Reservations: ALL_DAY | Indicates if an all-day booking has been made for a unit. Managed by Indoor Viewer. |
DOM_AREA_ROLE
| AreaRoles: ROLE | Indicates if an occupant is a reservation manager. Reservation managers can book or cancel bookings for others using the Reservations layer in Indoor Viewer and Indoors mobile. Managed by Space Planner. |
DOM_AREA_TYPE
| Areas: AREA_TYPE | Defines office hotel, hot desk, and workspace areas. Managed by Space Planner. |
DOM_ASSIGNMENT_TYPE
| Units: ASSIGNMENT_TYPE | Defines the assignment type of a unit as follows:
|
DOM_EQUIPMENT
| Units: Defined by user | Defines fields with available equipment types. This domain should be used if the equipment type applies to both meeting rooms and office hotels. Fields that include this domain will appear as options in the equipment filter in Indoor Viewer and Indoors mobile. Managed by the user. Assign this domain to equipment fields added to the Units layer. |
DOM_EQUIPMENT_HOTEL
| Units: Defined by user | Defines fields with available equipment types. This domain should be used if the equipment type applies to office hotels only. Fields that include this domain will appear as options in the equipment filter in Indoor Viewer and Indoors mobile. Managed by the user. Assign this domain to equipment fields added to the Units layer. |
DOM_EQUIPMENT_MEETING
| Units: Defined by user | Defines fields with available equipment types. This domain should be used if the equipment type applies to meeting rooms only. Fields that include this domain will appear as options in the equipment filter in Indoor Viewer and Indoors mobile. Managed by the user. Assign this domain to equipment fields added to the Units layer. |
DOM_NETWORK_RANK
| Transitions, PrelimTransitions: TRANSITION_RANK Pathways, PrelimPathways: PATHWAY_RANK | Defines the pathway rank preference of features for routing with Indoor Viewer and Indoors mobile. Managed by the user in ArcGIS Pro using the Classify Indoor Pathways tool. |
DOM_NETWORK_TYPE
| Transitions, PrelimTransitions: TRANSITION_TYPE Pathways, PrelimPathways: PATHWAY_TYPE | Describes the use type of the feature and is used to determine cost and restrictions during routing. This field is populated when you create a network using Indoors geoprocessing tools, but it can be modified if necessary. |
DOM_RESERVATION_METHOD
| Units: RESERVATION_METHOD | Defines whether the unit is a meeting room and can be booked for reservations using Indoor Viewer and Indoors mobile. Managed by the user in ArcGIS Pro when configuring meeting rooms with the Reservations layer. |
DOM_RESERVATION_STATE
| Reservations: STATE | Describes the current booking status of a unit in Indoor Viewer and Indoors mobile. Managed by Indoor Viewer and Indoors mobile. |
DOM_RESTRICTED
| Areas: RESTRICTED | Defines whether an office hotel is restricted to bookings by assigned occupants. Occupants must be assigned to the restricted hotel in Space Planner before they can book it in Indoor Viewer and Indoors mobile. Managed by Space Planner. |
DOM_TRACK_TYPE
| TrackingZones: TRACK_TYPE | Defines the rule for device tracking within a specific area. Managed by the user in ArcGIS Pro when configuring tracking zones. |
DOM_TRAVEL_DIRECTION
| Transitions, PrelimTransitions: TRAVEL_DIRECTION Pathways, PrelimPathways: TRAVEL_DIRECTION | Defines the direction of travel for a feature and is used to support navigation restrictions such as one way paths and route barriers when routing in Indoor Viewer. Managed by the user in ArcGIS Pro. |