CAD floor plan template file

Available for an ArcGIS organization licensed with the Indoors extension.

The Config_CAD_Indoors_Template file stores a set of configuration options for the Import Floorplans To Indoors Geodatabase tool. The template file is included with the ArcGIS Pro installation at <installation location>Program Files\ArcGIS\Pro\Resources\Indoors\MappingFile\Config_CAD_Indoors_Template.xlsx.

Learn more about populating the configuration spreadsheet

Note:

Many fields in the configuration template are not required if you are importing CAD data into the indoor dataset (created using the Create Indoor Dataset tool), which uses a streamlined schema that conforms to the Indoors model. You can still use them with the Indoors geodatabase (created using the Create Indoors Database tool).

The following tables describe the values to store in the columns on each sheet of the template:

Layer to Feature Class sheet

The Layer to Feature Class worksheet maps the CAD layers in the CAD files to their corresponding features in your indoor feature classes.

ColumnDescription
FACILITIES

One or more CAD polygon layers that define the extent of all the floors of a building.

Required: Either the FACILITIES or FACILITY_LINES column must be populated.

FACILITY_LINES

One or more CAD polyline layers that define the extent and edges of all the levels of a facility from which a polygon will be created.

Required: Either the FACILITIES or FACILITY_LINES column must be populated.

LEVELS

One or more CAD polygon layers that define the extent of each floor of a building.

Required: Either the LEVELS or LEVEL_LINES column must be populated.

LEVEL_LINES

One or more CAD polyline layers that define the edges and extent of each floor of a building.

Required: Either the LEVELS or LEVEL_LINES column must be populated.

ZONES

One or more CAD polygon layers that define a collection of spaces on a floor. Zones may define security, access, or the extent of building systems, such as HVAC or sprinkler coverage. A unit space can belong to multiple zones.

Note:

This column is only applicable if you are using an Indoors geodatabase.

ZONE_LINES

One or more CAD polyline layers that define the edges of a collection of spaces on a floor from which a polygon will be created. Zones may define security, access, or the extent of facility systems, such as HVAC or sprinkler coverage.

Note:

This column is only applicable if you are using an Indoors geodatabase.

SECTIONS

One or more CAD polygon layers that define the extent of a section. Also referred to as wings, sections represent a collection of spaces that include a logical subdivision of a floor. Unlike in zones, spaces typically belong to only one section, for example, the west wing.

Note:

This column is only applicable if you are using an Indoors geodatabase.

SECTION_LINES

One or more CAD polyline layers that define the edges and extent of a section. Also referred to as wings, sections represent a collection of spaces that include a logical subdivision of a floor from which a polygon will be created. Unlike zones, spaces typically belong to only one section, for example, the west wing.

Note:

This column is only applicable if you are using an Indoors geodatabase.

UNITS

One or more CAD polygon layers that define the usable spaces in a building, such as offices, hallways, and stairwells.

Required: Either the UNITS or UNITS_LINES column must be populated.

UNIT_LINES

One or more CAD polyline layers that define the edges and extent of the usable spaces in a building, from which polygons will be created.

Required: Either the UNITS or UNITS_LINES column must be populated.

DETAILS

One or more CAD polylines that define interior details that show the partitioning of spaces and entry and exit locations for each space and building, such as the location of walls, doors, windows, and so on, on an indoor map.

OPENINGS

One or more CAD polyline layers that define doors that should be treated as closed to create cleaner unit polygons from the layers in the UNIT_LINES column.

Note:

The OPENINGS column must be populated for the Door Close Buffer parameter to have any effect when you run the Import Floorplans To Indoors Geodatabase tool.

Annotation to Field sheet

The Annotation to Field sheet maps annotation in your CAD layers to attributes in your indoor feature classes. The configuration template includes default values for Indoors feature classes and attribute fields. You can delete any rows you do not need, and you can add rows as needed to map CAD annotation into additional indoor feature class attributes.

ColumnDescription

SOURCE_ANNOTATION

The name of the CAD layer containing the annotation to be mapped.

Note:

This column supports special syntax for parsing long or multiline CAD annotation, or for extracting block annotation.

TARGET_FEATURE_CLASS

The name of the feature class to which the annotation will be mapped.

The target feature class must be one of the following polygon feature classes from the Indoors model: Facilities, Levels, Units, Sections, or Zones.

TARGET_FIELD_NAME

The name of the attribute field in the target feature class to which the annotation will be mapped.

The field’s data type must be one of the following: Text, Short, Long, Float, or Double.

Note:

If the target field is populated based on information elsewhere in the configuration file, the Annotation to Field mapping is ignored for that field.

Facility Properties sheet

The Facility Properties sheet stores metadata about the facility or facilities to be imported, such as each facility's name and height. This metadata is applied to features and attributes in the indoor dataset during the import process.

ColumnDescription

SITE_ID

A unique identifier string for the site. This should be 50 characters or less.

A value is required.

SITE_NAME

A common name for the site. This should be 100 characters or less.

FACILITY_ID

A unique identifier string for the facility. The string consists of the SITE_ID, a delimiter, and a string unique to that facility, such as the facility's name. This should be 50 characters or less.

FACILITY_NUMBER

A unique identifier integer for the facility.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

NAME

The short name for the facility. This should be 100 characters or less.

A value is required.

NAME_LONG

The long name for the facility. This should be 255 characters or less.

DESCRIPTION

A description of the facility. This should be 255 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

ADDRESS

The address of the facility. This should be 255 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

UNIT

The unit or suite designation of the facility. This should be 10 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

LOCALITY

The city or town of the facility. This should be 100 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

PROVINCE

The state, territory, or province of the building. This should be 50 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

COUNTRY

The country of the facility. This must be two characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

POSTAL_CODE

The mail sorting code of the facility. This should be 50 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

DATE_BUILT

The date the facility was built.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

LEVELS_TOTAL

Total number of levels in the facility.

Note:

This column is only applicable if you are using an Indoors geodatabase.

ELEVATION_RELATIVE

The z-value of the base of the building relative to a flat terrain surface. The value is typically 0.

Note:

A value is required if you are using an Indoors geodatabase. If you are using an indoor dataset you can skip this field.

ELEVATION_ABSOLUTE

The absolute z-value of the base of the facility relative to sea level.

Note:

This column is only applicable if you are using an Indoors geodatabase.

HEIGHT_RELATIVE

The z-value of the top of the facility relative to a flat terrain surface.

A value is required.

HEIGHT_ABSOLUTE

The maximum height of the top of the facility relative to sea level. For example, a 100-meter-tall facility with an absolute elevation of 350 meters has an absolute height of 450 meters.

Note:

This column is only applicable if you are using an Indoors geodatabase.

ROTATION

The geographic rotation (left west=0 advancing clockwise) of the facility. A valid value range is 0–180.

Note:

This column is only applicable if you are using an Indoors geodatabase.

MERGE_LEVELS

Specifies whether to generate the facility's polygon by merging its levels' polygons.

  • Y—Merge the facility's level polygons (above and below ground) by performing a Union to generate the facility polygon.
  • N—Use the CAD layers listed in the Layer to Feature Class sheet's FACILITIES or FACILITY_LINES columns to generate the facility polygon.

A value is required.

Level Properties sheet

The Level Properties sheet stores metadata and configuration options for the floors to be imported.

ColumnDescription

FACILITY_ID

The facility's unique identifier string from the Facility Properties sheet.

Note:

This value should match the FACILITY_ID for the corresponding building on the Facility Properties sheet.

A value is required.

LEVEL_ID

The unique identifier string for the floor. The string consists of the FACILITY_ID, a delimiter, and a string unique to that level, usually the level number. This should be 50 characters or less.

A value is required.

NAME

The common name of the floor. This should be 255 characters or less.

Note:

The NAME value is used to populate the LEVEL_NAME field for the Details and Units feature classes.

A value is required.

NAME_SHORT

The short name of the level.

Note:

The NAME_SHORT value is used for the floor filter in ArcGIS Pro and the floor picker in the Indoorsweb and mobile apps. Using a short name that is four characters or less is recommended to optimize the filtering experience.

A value is required.

DESCRIPTION

The description of the level. This should be 255 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

ACCESS_TYPE

The access type of the level (such as visitor, employee, or public). This should be 50 characters or less.

Note:

This column is only applicable if you are using an Indoors geodatabase created in ArcGIS Pro 2.6 or earlier.

LEVEL_NUMBER

An integer representing the floor number for each floor, as might be seen on an elevator in the building. Unlike the VERTICAL_ORDER column, integers in the LEVEL_NUMBER column do not need to be ordinal.

A value is required.

VERTICAL_ORDER

An ordinal integer representing the vertical order of each floor. The vertical order of the ground floor is zero (0). Floors above the ground floor have positive vertical order values, while floors below the ground floor have negative values.

A value is required.

ELEVATION_RELATIVE

The z-value of each level relative to a flat terrain surface. For example, the relative elevation of the ground floor is 0 meters, the level above it (floor 2) may have a relative elevation of 4.25 meters, and the level below it (the basement) may have a relative elevation of -4.5 meters.

Note:

A value is required if you are using an Indoors geodatabase. If you are using an indoor dataset you can skip this field.

ELEVATION_ABSOLUTE

The absolute z-value of each floor relative to sea level. For example, floor 1 is 254 meters and floor 2 is 258.25 meters.

Note:

This column is only applicable if you are using an Indoors geodatabase.

HEIGHT_RELATIVE

The height of the top of each level relative to the bottom of that level. For example, the ground floor may have a relative height of 4.25 meters, the level above it (floor 2) may have a relative height of 4.25 meters, and the level below it (the basement) may have a relative height of 4.5 meters.

A value is required.

HEIGHT_ABSOLUTE

The absolute height of each floor relative to sea level. For example, floor 1 is 258.25 meters and floor 2 is 262.5 meters.

Note:

This column is only applicable if you are using an Indoors geodatabase.

CLOSE_DOORS

Specifies whether doors should be treated as closed when generating polygons from CAD polylines.

  • Y—Yes. Doors should be treated as closed when generating polygon features from CAD polylines.
  • N—No.

A value is required.

Note:

The CLOSE_DOORS value only has an effect when CAD polyline layers are listed in the UNIT_LINES and OPENINGS columns of the Layer to Feature Class sheet.

The tool may not detect CAD door polylines that are positioned too far away from the CAD wall polylines. The Close Door Buffer parameter in the Import Floorplans To Indoors Geodatabase tool determines the maximum detection distance in inches.

PROCESS

Specifies whether the tool will process the level.

  • Y—Yes. The level will be processed.
  • N—No. The level will be skipped when you run the tool.

A value is required.

Source Files sheet

The Source Files sheet stores file paths to the CAD drawings and relates each drawing to a level defined on the Level Properties sheet. If the CAD data for a single level resides in multiple drawings that overlay one another, you can define the source path for each of the drawing files and relate them to a single level.

ColumnDescription

SOURCE_PATH

The file path to a source CAD file on the local machine or network.

A value is required.

LEVEL_ID

The unique identifier string for the related level.

A value is required.

Note:

This value must match the LEVEL_ID for the corresponding level in the Level Properties sheet.