Create and modify floor-aware features

Available with the ArcGIS Indoors Pro or ArcGIS Indoors Maps extension.

Once you import floor plans, you can create and modify floor-aware features using editing tools in ArcGIS Pro, including adding or updating floor plan features such as units and details, or adding features in floor-aware layers to provide additional information in floor-aware maps.

For example, you can add features that represent occupant seating assignments and points of interest (such as an information kiosk, fixed and mobile assets, hardware, or equipment) that you want to find on a map. These features can be used for generating the indoor routable network (point features) and to create categories (point and polygon features) to make features searchable, explorable, and routable in the Indoors web and mobile apps.

Configure these features as floor-aware layers to create categories, visualize them using the floor filter, and integrate them with the Indoors web and mobile apps.

You can create custom-modeled features and configure them as floor-aware by including the following:

• A field that records the LEVEL_ID field value of the feature's associated level. This is used to identify the feature's associated level in floor-aware maps and scenes.
• The z-value of the associated floor in the feature's geometry. This value is based on the level selected in the floor filter when the feature is created.

Note:

Features you add to an Indoors workspace should be z-enabled and align vertically with the levels in your Indoors workspace. Because the network dataset is 3D, all features must be in the same x,y,z coordinate system so that they can snap to the network at the appropriate z-value for routing or closest facility analysis.

Create features in floor-aware layers

You can use editing tools in ArcGIS Pro to update an existing indoor workspace with new features without having to re-import floor plan data.

For example, if a new unit must be created on a level but remain aligned with a unit on the floor above or below it, you can first use the Copy tool to copy the unit, use the floor filter to change to the target level, and use the Paste tool to create a copy of the unit on the desired level. The new unit has the floor and z information automatically populated according to the target level.

Another example involves creating new pathways for navigation and routing in an existing indoor network without needing to run the Generate Indoor Network Features tool. You can use the Create tool to create new pathway features with automatically populated attributes, which are necessary for incorporating the features into the existing indoor network.

The sections below detail which fields are automatically populated by editing tools when creating features in ArcGIS Pro.

Note:

When creating or modifying level features, the NAME_SHORT and VERTICAL_ORDER fields are not automatically populated. These fields are used by the floor filter to filter the displayed data. Ensure that these fields are manually updated after editing level features.

Create tool

In floor-aware layers in a floor-aware map, when you create new features using the Create Features pane, certain fields are automatically populated. To open the Create Features pane, click Create on the Edit tab of the ribbon.

For Units, Details, Levels, Pathways, and other floor-aware features, the following fields are populated automatically:

• Configured floors field—Populated based on the level in which the feature is created. If the feature is created outside a level, the floors field is populated with a Null value.
• A z-value is assigned based on the level visible on the map when the floor filter is enabled.

Additional fields for Indoors layers are automatically populated as follows:

• Details: DETAIL_ID—Populated with a unique GUID.
• Units:
  • UNIT_ID—Populated with a unique GUID.
  • AREA_GROSS—Populated based on the shape area.
• Levels: AREA_GROSS—Populated based on the shape area.
• Facilities: FACILITY_ID—Populated with a unique GUID
• Pathways and Transitions:
  • FACILITY_ID and FACILITY_NAME—Populated based on the facility in which the beginning vertex is located.
  • VERTICAL_ORDER, VERTICAL_ORDER_FROM, VERTICAL_ORDER_TO—Populated with the vertical order of the level on which the start and end vertices are located. The VERTICAL_ORDER_FROM and VERTICAL_ORDER_TO attributes are only present in the Transitions layer.
  • LENGTH_3D—Populated based on the feature's 3D length.
  • LEVEL_NAME_FROM and LEVEL_NAME_TO—Populated with the short name of the level on which the start and end vertices are located.
  • HEIGHT_FROM and HEIGHT_TO—Populated with the z-value of the start and end vertices. This attribute is only present in the Transitions layer.

Copy, Cut, and Paste tools

When you create features using the Copy , Cut , and Paste tools from the ribbon, the following fields are populated automatically for floor-aware features:

• Configured floors field—Populated based on the level visible in the map when the floor filter is enabled.
• A z-value is assigned based on the level visible on the map when the floor filter is enabled.

Additional fields for Indoors layers are automatically populated as follows:

• Details: DETAIL_ID—Populated with a unique GUID.
• Units:
  • UNIT_ID—Populated with a unique GUID.
  • NAME—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.
  • NAME_LONG—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.
• Levels:
  • LEVEL_ID—Populated with a unique GUID.
  • NAME—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.
• Facilities:
  • FACILITY_ID—Populated with a unique GUID for newly created features.
  • NAME—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.

Duplicate Vertical tool

The Duplicate Vertical tool copies z-enabled features vertically by specifying the vertical distance between duplicated features and the number of features to create. The new features are constrained to the z-axis of the data.

The following fields are automatically populated for floor-aware features when using the Duplicate Vertical tool:

• Configured floors field—If the input z-value is associated with a level, this field is populated based on the specified z-value. For level features, a new unique GUID is populated.
• The z-value is updated based on the specified Vertical Offset value.

Additional fields for Indoors layers are automatically populated as follows:

• Details: DETAIL_ID—Populated with a unique GUID.
• Units:
  • UNIT_ID—Populated with a unique GUID.
  • NAME—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.
  • NAME_LONG—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.
• Levels: NAME—The word Copy is appended to the name of the newly created feature to maintain uniqueness in the table.
• Pathways and Transitions:
  • LEVEL_NAME_FROM and LEVEL_NAME_TO—Populated with the short name of the level on which the start and end vertices are located.
  • VERTICAL_ORDER, VERTICAL_ORDER_FROM, VERTICAL_ORDER_TO—Populated with the vertical order of the level on which the start and end vertices are located. The VERTICAL_ORDER_FROM and VERTICAL_ORDER_TO attributes are only present in the Transitions layer.
  • HEIGHT_FROM and HEIGHT_TO—Populated with the z-value of the start and end vertices. This attribute is only present in the Transitions layer.

Modify features in floor-aware layers

You can use editing tools in ArcGIS Pro to modify floor plans during the quality control process after importing or creating floor plans or to make updates to floor plans as they change over time (for example, if a building wing is remodeled). When using certain editing tools to modify features in floor-aware layers in a floor-aware map, some attributes are automatically populated.

Note:

If any calculation attribute rules are in place that populate fields that Indoors automatically populates, the calculation attribute rule result is honored. If any constraint attribute rules make the automatically populated value invalid, an error appears and the feature edit does not occur.

The sections below detail which fields are automatically populated by editing tools when modifying features in ArcGIS Pro.

Split tool

The Split tool allows you to split a polyline or polygon feature into two or more features. When splitting features in a floor-aware map, consider the following:

• With the exception of the fields that Indoors automatically populates, attribute values from the original feature are copied to the new features. Attributes constrained by attribute domains are determined by the domain split policy defined by the source geodatabase.
• After splitting a unit feature, examine fields used by Indoors Space Planner, such as AREA_ID and SCHEDULE_EMAIL, to ensure that the fields are populated as desired to support workspace reservations and organization areas.
• The Split tool includes an Allow splitting without a selection option. With this option enabled, the split is applied to all enabled layers in the map including Levels and Facilities. The split is also applied to features on all floors and is not z-enabled.

  Note:

  It is recommended that you disable the Allow splitting without a selection option when splitting features in a floor-aware map.

The following fields are populated automatically. You can change these field values and other field values after completing the split operation.

Units

The following fields are automatically populated in the Units layer:

• UNIT_ID—Populated with a unique GUID.
• AREA_GROSS—Populated based on the shape area.
• NAME—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.
• NAME_LONG—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.

Details

DETAIL_ID is populated with a unique GUID.

Levels

• LEVEL_ID is populated with a unique GUID.
• NAME—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.

Facilities

• FACILITY_ID is populated with a unique GUID for newly created features.
• NAME—The text Copy is appended to the name of the newly created feature, to maintain uniqueness in the table.

Pathways and Transitions

The following fields are automatically populated in the Pathways and Transitions layers:

• FACILITY_ID and FACILITY_NAME—Populated based on the facility in which the beginning vertex is located.
• VERTICAL_ORDER, VERTICAL_ORDER_FROM, VERTICAL_ORDER_TO—Populated with the vertical order of the level on which the start and end vertices are located. The VERTICAL_ORDER_FROM and VERTICAL_ORDER_TO attributes are only present in the Transitions layer.
• LENGTH_3D—Populated based on the feature's 3D length.
• LEVEL_NAME_FROM and LEVEL_NAME_TO—Populated with the short name of the level on which the start and end vertices are located.
• HEIGHT_FROM and HEIGHT_TO—Populated with the z-value of the start and end vertices. This attribute is only present in the Transitions layer.

Move and Move To tools

The Move tool moves features by dragging them, and the Move To tool moves selected features to a coordinate location or by a specified offset direction and distance.

For Units, Details, and other floor-aware features, the following fields are populated automatically when using these tools with the floor filter enabled. You can change these field values and other field values after completing the move operation:

• Configured floors field—Populated based on the level to which the feature is moved. If the feature is moved outside of a level, the floors field is populated with a Null value.
• The z-value is updated to match the level to which the feature is moved.

For Levels, the FACILITY_ID field is populated based on the facility to which the level is moved. If the Level feature is moved outside a facility polygon, the field is populated with a Null value.

For Pathways and Transitions, the following fields are populated:

• FACILITY_ID and FACILITY_NAME—Populated based on the facility to which the feature is moved.
• LEVEL_ID—Populated based on the level to which the feature is moved.
• LEVEL_NAME_FROM and LEVEL_NAME_TO—Populated with the short name of the level to which the start and end vertices are moved.
• VERTICAL_ORDER, VERTICAL_ORDER_FROM, and VERTICAL_ORDER_TO—Populated with the vertical order of the level to which the start and end vertices are moved.
• HEIGHT_FROM and HEIGHT_TO—Populated with the z-value of the start and end vertices. This attribute is only present in the Transitions layer.