arcpy.management.CreateDomain(in_workspace, domain_name, {domain_description}, {field_type}, {domain_type}, {split_policy}, {merge_policy})
|
Name
|
Explanation
|
Data type
|
|
in_workspace
|
The geodatabase that will contain the new domain.
|
Workspace
|
|
domain_name
|
The name of the domain that will be created.
|
String
|
|
domain_description
(Optional)
|
The description of the domain that will be created.
|
String
|
|
field_type
(Optional)
|
Specifies the type of attribute domain that will be created. Attribute domains are rules that describe the accepted values of a field type. Specify a field type that matches the data type of the field to which the attribute domain will be assigned.
SHORT—The field type will be short. Short fields support whole numbers between -32,768 and 32,767.
LONG—The field type will be long. Long fields support whole numbers between -2,147,483,648 and 2,147,483,647.
BIGINTEGER—The field type will be big integer. Big integer fields support whole numbers between -(253) and 253.
FLOAT—The field type will be float. Float fields support fractional numbers between -3.4E38 and 1.2E38.
DOUBLE—The field type will be double. Double fields support fractional numbers between -2.2E308 and 1.8E308.
TEXT—The field type will be text. Text fields support a string of characters.
DATE—The field type will be date. Date fields support date and time values.
DATEONLY—The field type will be date only. Date only fields support date values with no time values.
TIMEONLY—The field type will be time only. Time only fields support time values with no date values.
|
String
|
|
domain_type
(Optional)
|
Specifies the domain type that will be created.
CODED—A coded type domain will be created that contains a valid set of values for an attribute. This is the default. For example, a coded value domain can specify valid pipe material values such as CL—cast iron pipe, DL—ductile iron pipe, or ACP—asbestos concrete pipe.
RANGE—A range type domain will be created that contains a valid range of values for a numeric attribute. For example, if distribution water mains have a pressure between 50 and 75 psi, a range domain specifies these minimum and maximum values.
|
String
|
|
split_policy
(Optional)
|
Specifies the split policy that will be used for the created domain. The behavior of an attribute's values when a feature that is split is controlled by its split policy.
DEFAULT—The attributes of the two resulting features will use the default value of the attribute of the given feature class or subtype.
DUPLICATE—The attribute of the two resulting features will use a copy of the original object's attribute value.
GEOMETRY_RATIO—The attributes of resulting features will be a ratio of the original feature's value. The ratio is based on the proportion into which the original geometry is divided. If the geometry is divided equally, each new feature's attribute gets one-half the value of the original object's attribute. The geometry ratio policy only applies to range domains.
|
String
|
|
merge_policy
(Optional)
|
Specifies the merge policy that will be used for the created domain. When two features are merged into a single feature, merge policies control attribute values in the new feature.
DEFAULT—The attribute of the resulting feature will use the default value of the attribute of the given feature class or subtype. This is the only merge policy that applies to nonnumeric fields and coded value domains.
SUM_VALUES—The attribute of the resulting feature will use the sum of the values from the original feature's attribute. The sum values policy only applies to range domains.
AREA_WEIGHTED—The attribute of the resulting feature will be the weighted average of the attribute values of the original features. This average is based on the original feature's geometry. The area weighted policy only applies to range domains.
|
String
|
Derived output
|
Name
|
Explanation
|
Data type
|
|
out_workspace
|
The updated input workspace.
|
Workspace
|
Code sample
CreateDomain example 1 (Python window)
The following Python window script demonstrates how to use the CreateDomain function in immediate mode.
import arcpy
arcpy.env.workspace = "C:/data"
arcpy.management.CreateDomain("montgomery.gdb", "Materials",
"Valid pipe materials", "TEXT", "CODED")
CreateDomain example 2 (stand-alone script)
This stand-alone script uses the CreateDomain function as part of a workflow to create an attribute domain, assign values to it, and assign the domain to a field in a feature class.
# Name: MakeDomain.py
# Description: Create an attribute domain to constrain pipe material values
# Import system modules
import arcpy
# Set the workspace (to avoid having to type the full path to the data
# every time)
arcpy.env.workspace = "C:/data"
# Set local parameters
domName = "Material4"
gdb = "montgomery.gdb"
inFeatures = "Montgomery.gdb/Water/Distribmains"
inField = "Material"
# Process: Create the coded value domain
arcpy.management.CreateDomain("montgomery.gdb", domName, "Valid pipe materials",
"TEXT", "CODED")
# Store all the domain values in a dictionary with the domain code as the "key"
# and the domain description as the "value" (domDict[code])
domDict = {"CI":"Cast iron", "DI": "Ductile iron", "PVC": "PVC",
"ACP": "Asbestos concrete", "COP": "Copper"}
# Process: Add valid material types to the domain
# use a for loop to cycle through all the domain codes in the dictionary
for code in domDict:
arcpy.management.AddCodedValueToDomain(gdb, domName, code, domDict[code])
# Process: Constrain the material value of distribution mains
arcpy.management.AssignDomainToField(inFeatures, inField, domName)