Esri ArcGIS Desktop Professional Certification Study Guide. Mike Flanagan

a geodatabase topology.

      Prepare

      These topics in the documentation provide details about geodatabase fundamentals.

      Gain a thorough understanding of these ArcGIS Pro Help topics:

       Help > Data > Geodatabases > The geodatabase >Fundamentals of the geodatabaseTypes of geodatabasesFeature class basicsTable basics

        Help > Data > Geodatabases > Define data properties > Geodatabase table properties > ArcGIS field data types

        Help > Data > Geodatabases > Create a geodatabase (and all subtopics)

       Help > Data > Geodatabases > Add datasets to a geodatabase >Create datasets in a geodatabaseCopy feature datasets, feature classes, and tables to a geodatabaseImport data

        Help > Data > Geodatabases > Data design (and all subtopics)

        Help > Data > Geodatabases > Versioned data > Overview of versioning

        Help > Data > Data types > Feature datasets > Feature datasets in ArcGIS Pro

      Gain a thorough understanding of these ArcMap Help topics:

       Manage data > Geodatabases > An overview of the geodatabase >A quick tour of the geodatabaseTypes of geodatabasesFeature class basicsTable basics

        Manage data > Data types > Tables > Designing a table > ArcGIS field data types

        Manage data > Data types > Subtypes (and all subtopics)

        Help > Data > Geodatabases > Designing a geodatabase > An overview of geodatabase design (and all subtopics)

        Manage data > Geodatabases > Adding datasets and other geodatabase elements > An overview of adding datasets to the geodatabase (and all subtopics)

        Manage data > Geodatabases > Defining the properties of data in a geodatabase > Domains (and all subtopics)

        Manage data > Geodatabases > Working with versioned data > An overview of versioning

        Manage data > Data types > Feature datasets > An overview of working with feature datasets

      Associating features and records

      In some cases, you may want to associate features or records in one dataset with features or records in another. With ArcGIS, you can make associations using table joins and relates, relationship classes, and spatial joins. Table joins, relates, and relationship classes use a common field, known as a key, to associate records in one table with records in another table. ArcGIS supports one-to-one, one-to-many, many-to-one, and many-to-many relationships, making it easy to associate tables regardless of the nature of your data. If your data lacks a common key field, you can use a spatial join to create a relationship that is based on the location of features in your input layers.

      Joins and relates are most useful when you need to create temporary associations. With a table join, the attributes from one table are virtually appended to the attributes of another table. After the join is established, you can use the information from the appended table for symbology, field calculation, and more. For example, you could associate a table of soil sample values to a land parcels layer based on a shared parcel ID field. After this association is made, you can symbolize the land parcels layer based on the soil sample values in the soil samples table. Joined tables can be exported to preserve the join in a new feature class or nonspatial table, or they can be removed if they are no longer needed. Relates allow you to identify a record in one table and see all the related records from a related table. Unlike a table join, a relate defines a relationship, but it does not append the attributes of one table to the other. Rather, it allows you to access related information by selecting features or records in your layer or table using the Explore tool in ArcGIS Pro or the Identify tool in ArcMap.

      If you want to create a more permanent association, you can use a relationship class. Relationship classes are stored in a geodatabase, making them accessible to anyone using the geodatabase. They can be used to enforce referential integrity between related objects (so that when one object is modified, the related object is updated automatically), and they support all cardinalities. ArcGIS supports both simple and composite relationship classes. In a simple relationship class, the related objects are loosely coupled. For example, when you delete a record in the origin table, the key field in the destination record is nulled. You should use simple relationship classes when you have related objects that are completely independent of one another. Conversely, you should use a composite relationship class when working with related objects that cannot exist independently. In a composite relationship class, when one object is deleted, the second object (a related object) is also deleted. This approach can save you time that might otherwise be spent performing attribute edits.

      Prepare

      These topics in the documentation provide details about associating features and records.

      Gain a thorough understanding of these ArcGIS Pro Help topics: