Frequently asked question

What are the recommended naming conventions for geodatabase objects?

Last Published: April 25, 2020


Determining guidelines or naming conventions for geodatabase objects is important for creating consistency when setting up the database structure.

Recommendations for designing and implementing a geodatabase are provided below.

* Refer to feature and object classes as singular. For example, use 'TaxParcel' and not 'TaxParcels' to refer to a feature class.
* Name relationship objects so that the name is describing the relationship. For example, ‘AddressHasZones' or 'ParcelsHaveOwners'. On a conceptual level, name associations might be simplified to names like ‘Has’ or ‘Owns’; however, implementation in ArcGIS requires unique name associations. Many people use the name of the class at the ends of relationship classes. These names show up in ArcMap and ArcCatalog, and naming the ends of the relationship classes using this method makes the database structure easier to understand.

* Use consistency when capitalizing objects. For example, name objects with all capital letters (TABLE_NAME) or a consistent mixed case (TableName).

* Do not attempt to use spaces, SQL keywords or special characters in object names.

Article ID:000006254

  • ArcMap 8 x
  • ArcMap 9 x

Receive notifications and find solutions for new or common issues

Get summarized answers and video solutions from our new AI chatbot.

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options