You are here

Esri Domains 101

In my last blog post, I recommended that, when possible, data administrators restrict field data entry to domains.

In short, domains behave like drop-down menus (when using Coded Value) that allow users to just select the desired value for a particular field. This helps minimize errors by forcing full value selection versus physical typing of the field attribute.

Domains also promote data consistency by preventing unique spellings of the same word (i.e., Manhole, manhole, MH, etc.).

There are two types of domains:

  • Coded Value – Specific list of values. Probably the most common type.
  • Range – An allowable numeric range of acceptable values.

 Creating and/or modifying a domain is not difficult but does require exclusive, administrative access to the database. Assuming access, conduct the following procedures to create a domain:

  1. Open up ArcCatalog. 
  2. Navigate to the desired geodatabase. I am working with FieldCollection.gdb.
  3. Right-click on the geodatabase, and choose Properties (Figure1).Figure 1:  FGDB Properties
  4. The Database Properties window appears (Figure 2). On the Domains tab, click on the first open box in the Domain Name column and name the domain. In this example, I have named the domain "OverheadUnderground". The Description column is optional, but may help describe the domain’s purpose.Figure 2:  Creation of Domain

  5. Specify the field type (i.e., integer, text, etc.) based upon the anticipated assigned field.

  6. Determine whether the domain is a coded value or range.  For this example, the domain is a coded value domain.

  7. In the Coded Values section, for each row specify a Code (actually stored in the database for the feature) and a Description (what the user actually sees).  The values can be exactly the same for a text field (if desired).

  8. Click the OK button to save and dismiss the Database Properties Window.

  9. Assign the new domain to the desired field(s).  Note that the same domain can also be applied to multiple fields in multiple feature classes (assuming they are similar in nature).  Right-click the feature class and choose Properties. 

  10. In the Feature Class Properties Window (Figure 3), select the Fields Tab and select the desired field to add the domain.Figure 3:  Feature Class Properties Window

  11. In the Domain drop-down, select the newly created domain and click the OK Button.  When doing data entry or modification, the end user can now only select Overhead or Underground for the OHUG field.

From time to time, domains need to be modified.  For example, some clients of mine have added the value of “Bridge” to the OHUG domain to reflect when a fiber cable traverses a bridge culvert.  To update a domain, conduct the following procedure:

  1. In ArcCatalog, navigate to the geodatabase, right-click on it, and choose Properties.
  2. On the Domains tab, find the OverheadUnderground Domain.  Go down to the bottom of the list of Coded Values, add Bridge (Figure 4), and click the OK button.Figure 4:  Domain Update

From the Database Properties Window, there is no way to sort the values.  So in general, the values will appear to the end user in the order that they are input.  There is a hidden gem in the Esri tools that enables the sorting of domains.  Conduct the following procedure to add the tool to your tool bar:

  1. In ArcCatalog, go to the Customize menu, Toolbars option, then click Customize at the bottom.
  2. In the Customize Window (Figure 5), click the Commands Tab and choose the Data Management Tools Option.Figure 5:  Customize Window
  3. Click and drag the Sort Coded Value Domain Tool to a toolbar.
  4. Once added to the toolbar, click it to open the tool window (Figure 6).Figure 6:  Sort Coded Value Domain Tool
  5. Choose the database that contains the domain to be sorted.
  6. Choose whether to sort by the domain's code or the description.
  7. Select either ascending or descending order.
  8. Click the OK Button.
  9. Once sorted, a window will appear informing of completion.
  10. We now observe that the order has been altered (Figure 7).Figure 7:  Modified Domain Order

In conclusion, have a blast creating and modifying your very own domains!  I referenced modifying domains in the Associated Posts below:

Author Information

  • Brian Higgins

    Brian Higgins is a Senior Consultant at the Utility & Telecommunications GIS consulting company SSP Innovations in Centennial, Colorado.  He is a certified Geographic Information Systems Professional (GISP) with 22 years of experience in the design and development of GIS systems for the management of municipal infrastructure.

    See all items created by this author >

    Connect with me on:

Category Tags:

Brian HigginsDataGIS

Comments

Good stuff Brian. It appears that you now have domain over esri domains. It may be beneficial to next discuss esri subtypes as a subtype of subjects on data integrity. Someone stop me...please.

Hey, Keith. How's the shrimpin' in Jax?

Your humor could use a little improvement, but I love the idea. I am always looking for ideas like this write about. Plane trips can get a little long.

Hope things are going well for you, my friend!

Add new comment