Indoor dataset and indoor network dataset schema—ArcGIS Pro

Available for an ArcGIS organization licensed with the Indoors extension.

The ArcGIS Indoors Information Model supports managing the indoor GIS information necessary to share floor-aware web maps, scenes, and mobile map packages for use with Indoor Viewer, Indoor Space Planner, ArcGIS Indoors for iOS, ArcGIS Indoors for Android, ArcGIS Field Maps, and other floor-aware apps.

A streamlined schema that conforms to the Indoors model can be applied to an existing workspace using a series of tools that establish basic visualization capabilities for floor plan mapping. These tools include the following:

Create Indoor Dataset (required)
Create Indoor Network Dataset (optional)

The schema created by these tools consists of two 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 available in ArcGIS Pro to maintain additional information required by your organization.

If you require support for routing, space planning, and workspace reservations in addition to floor plan mapping, use the Create Indoors Database tool to apply the Indoors model to an existing workspace. The Indoors geodatabase created by this tool contains additional fields and tables that are required for Space Planner, Indoor Viewer, and the Indoors mobile apps.

Feature datasets


Name	Description
Indoor dataset	Manages the indoor GIS data that defines floor plans for use with floor-aware maps and apps. These features are created using the Create Indoor Dataset tool in ArcGIS Pro and are organized by functional levels.
Indoor network dataset	Manages the network artifacts that are created to support routing between indoor spaces. These features are created using the Create Indoor Network Dataset tool in ArcGIS Pro. Note: This feature dataset should not be versioned when using an enterprise geodatabase. This feature dataset is optional.

Indoor dataset feature classes

The indoor feature dataset consists of feature classes that represent 2D floor plan information.

These feature classes are organized in a hierarchy with assumed spatial relationships defined in the following descending order:

Units and Details
Levels
Facilities
Sites


Name	Description
Details	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.
Facilities	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.
Levels	Describes the footprint of each occupiable floor contained in your managed facilities. Levels footprints must be contained in a Facilities feature.
Sites	Describes the boundaries of your managed sites and is used for visualization in mapmaking.
Units	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 network dataset feature classes


Name	Description
Landmarks	Describes easily recognizable features that are used as callouts in turn-by-turn directions when routing between locations in Viewer and the Indoors mobile apps.
Pathways	Describes the horizontal network pathways generated by the Indoors geoprocessing tools in ArcGIS Pro for routing between locations on the same level.
Transitions	Describes the vertical network transitions generated by the Indoors geoprocessing tools in ArcGIS Pro for routing between levels.

Indoor dataset feature class details

Click a link to go to a feature class details table.

Details


Field name	Type	Required	Description
DETAIL_ID	Text	Yes	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	Conditional	Defines the height of the feature relative to the bottom of the floor. Height is expected to be defined in meters. For example, Level 1 = 4.25 m, Level 2 = 4.25 m, and so on. Required if: This field is required to create a 3D feature from the 2D feature.
LEVEL_ID	Text	Yes	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.
USE_TYPE	Text	Yes	Distinguishes feature types used in tool processing and supports differences in symbology for mapmaking.

Facilities


Field name	Type	Required	Description
FACILITY_ID	Text	Yes	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	Conditional	Defines the height of the feature relative to the bottom of the floor. Height is expected to be defined in meters. For example, Level 1 = 4.25 m, Level 2 = 4.25 m, and so on. Required if: This field is required to create a 3D feature from the 2D feature.
NAME	Text	Yes	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	No	Defines a long name for a feature. Features created by the Import Floorplans To Indoors Geodatabase and Import BIM To Indoor Dataset geoprocessing tools will include an automatically generated long name. The long name is used to support descriptive capabilities in the Indoors web and mobile apps.
SITE_ID	Text	Yes	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	Required	Description
AREA_GROSS	Double	No	Records the total gross area of a feature.
FACILITY_ID	Text	Yes	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	Conditional	Defines the height of the feature relative to the bottom of the floor. Height is expected to be defined in meters. For example, Level 1 = 4.25 m, Level 2 = 4.25 m, and so on. Required if: This field is required to create a 3D feature from the 2D feature.
LEVEL_ID	Text	Yes	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	Yes	Records the facility-specific level number.
NAME	Text	Yes	Defines the name of the feature. The level name is used to support floor filtering in floor-aware apps.
NAME_SHORT	Text	Yes	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	Yes	Defines the order of display and reference to floors in the Indoor Positioning System (IPS). It uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero (0). Positive values represent floors above ground, while negative values represent floors below ground. Vertical Order values must be continuous and cannot skip a value in the sequence.

Sites


Field name	Type	Required	Description
NAME	Text	Yes	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	No	Defines a long name for a feature. Features created by the Import Floorplans To Indoors Geodatabase and Import BIM To Indoor Dataset geoprocessing tools will include an automatically generated long name. The long name is used to support descriptive capabilities in the Indoors web and mobile apps.
SITE_ID	Text	Yes	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	Required	Description
AREA_GROSS	Double	No	Records the total gross area of a feature.
HEIGHT_RELATIVE	Double	Conditional	Defines the height of the feature relative to the bottom of the floor. Height is expected to be defined in meters. For example, Level 1 = 4.25 m, Level 2 = 4.25 m, and so on. Required if: This field is required to create a 3D feature from the 2D feature.
LEVEL_ID	Text	Yes	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.
NAME	Text	Yes	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	Yes	Defines a long name for a feature. Features created by the Import Floorplans To Indoors Geodatabase and Import BIM To Indoor Dataset geoprocessing tools will include an automatically generated long name. The long name is used to support descriptive capabilities in the Indoors web and mobile apps.
UNIT_ID	Text	Yes	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	Yes	Distinguishes feature types used in tool processing and supports differences in symbology for mapmaking.

Indoor network dataset feature class details

Click a link to go to a feature class details table.

| Landmarks | Pathways | Transitions |

Landmarks


Field name	Type	Required	Description
DESCRIPTION	Text	Yes	Provides a description of the feature for use in turn-by-turn directions.
LEVEL_ID	Text	Yes	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.
VERTICAL_ORDER	Long	Yes	Defines the order of display and reference to floors in the Indoor Positioning System (IPS). It uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero (0). Positive values represent floors above ground, while negative values represent floors below ground. Vertical Order values must be continuous and cannot skip a value in the sequence.

Pathways


Field name	Type	Required	Description
DELAY	Long	No	Defines the elevator delay in the network for accurate routing time.
FACILITY_ID	Text	Yes	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	Yes	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	Yes	Describes the calculated length of the feature in 3D that is used to determine path cost when routing.
LEVEL_NAME_FROM	Text	Yes	Describes the name of the level as defined in the indoor feature dataset on which the feature originates.
LEVEL_NAME_TO	Text	Yes	Describes the name of the level as defined in the indoor feature dataset on which the feature terminates.
PATHWAY_RANK	Long	Yes	Defines the rank preference of one feature versus another for routing. The following domain is used to define allowed values: 1 = Primary 2 = Secondary 3 = Tertiary Route calculations prioritize primary pathways and ignore secondary or tertiary pathways unless they are required to reach the destination.
PATHWAY_TYPE	Long	Yes	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: 1 = Hallway / Sidewalk 2 = Stairs / Curb 3 = Ramp / Curb Ramp 4 = Elevator / Wheelchair Lift 5 = Escalator 6 = Moving Walkway
TRAVEL_DIRECTION	Long	Yes	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: 1 = Both Directions Allowed 2 = From-To Allowed 3 = To-From Allowed
VERTICAL_ORDER	Long	Yes	Defines the order of display and reference to floors in the Indoor Positioning System (IPS). It uses a zero (0)-based ordering system to define the floor order, with the ground level of each facility represented as zero (0). Positive values represent floors above ground, while negative values represent floors below ground. Vertical Order values must be continuous and cannot skip a value in the sequence.

Transitions


Field name	Type	Required	Description
FACILITY_ID	Text	Yes	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	Yes	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	Yes	Describes the starting height of the feature.
HEIGHT_TO	Double	Yes	Describes the ending height of the feature.
LENGTH_3D	Double	Yes	Describes the calculated length of the feature in 3D that is used to determine path cost when routing.
LEVEL_NAME_FROM	Text	Yes	Describes the name of the level as defined in the indoor feature dataset on which the feature originates.
LEVEL_NAME_TO	Text	Yes	Describes the name of the level as defined in the indoor feature dataset on which the feature terminates.
TRANSITION_RANK	Long	Yes	Defines the rank preference of one feature versus another for routing. The following domain is used to define allowed values: 1 = Primary 2 = Secondary 3 = Tertiary Route calculations prioritize primary transitions and ignore secondary or tertiary transitions unless they are required to reach the destination.
TRANSITION_TYPE	Long	Yes	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: 1 = Hallway / Sidewalk 2 = Stairs / Curb 3 = Ramp / Curb Ramp 4 = Elevator / Wheelchair Lift 5 = Escalator 6 = Moving Walkway
TRAVEL_DIRECTION	Long	Yes	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: 1 = Both Directions Allowed 2 = From-To Allowed 3 = To-From Allowed
VERTICAL_ORDER_FROM	Long	Yes	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 (0) and subsequent positive values representing floors above ground, while 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	Yes	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 (0) and subsequent positive values representing floors above ground, while negative values represent floors below ground. Vertical Order To values must be continuous and cannot skip a value in the sequence.

Feedback on this topic?