Exercise 4: Creating relationships between objects

Complexity: Beginner Data Requirement: ArcGIS Tutorial Data Setup Goal: Create a relationship class between a feature class and a nonspatial table.

In Exercise 2: Importing data into your geodatabase, you imported an INFO table containing owner objects into the Montgomery geodatabase. The geodatabase already has a feature class, Parcels, that contains parcel objects. You will now create a relationship class between the parcels and the owners so that when you use the data in ArcMap, you can easily find out which owners own which parcels.

  1. Right-click the Landbase feature dataset in the Montgomery geodatabase, point to New, then click Relationship Class.

    The New Relationship Class wizard opens.

  2. The first panel of the wizard is used to specify the name, origin, and destination feature class or table for the new relationship class.

  3. Type ParcelOwners in the Name of the relationship class text box.
  4. Click Owners in the Origin table/feature class list.
  5. Double-click the Landbase feature dataset in the Destination table/feature class list.
  6. Click Parcels.

    This designates the Parcels feature class as the destination feature class.

    Name the relationship and choose the participating feature classes.

  7. Click Next.
  8. The next panel is used to specify the type of relationship class you are creating. You are creating a simple relationship class, since owners and parcels can exist in the database independently of each other. You can, therefore, accept the default type—Simple (peer to peer) relationship.

  9. Click Next.
  10. You must now specify the path labels and the message notification direction. The forward path label describes the relationship as it is navigated from the origin class to the destination class—in this case, from Owners to Parcels. The backward path label describes the relationship when navigated in the other direction—from Parcels to Owners.

    The message notification direction describes how messages are passed between related objects. Message notification is not required for this relationship class; therefore, you can accept the default of None.

  11. Type owns for the forward path label.
  12. Type is owned by for the backward path label.

    Name the relationship class labels.

  13. Click Next.
  14. You will now specify the cardinality of the relationship. The cardinality describes the possible number of objects in the destination feature class or table that can be related to an object in the origin feature class or table.

  15. Click 1-M (one-to-many) to specify that one owner can own many parcels.
  16. Click Next.
  17. You must now specify whether your new relationship class will have attributes. In this example, the ParcelOwners relationship class does not require attributes, which is the default.

  18. Click Next.
  19. The next step is to specify the primary key in the origin table (Owners) and the embedded foreign key field in the destination feature class (Parcels). Owners and Parcels that have the same value in these fields will be related to each other.

  20. Click the first drop-down arrow under Select the primary key field in the origin table/feature class and click PROPERTY_ID.
  21. Click the second drop-down arrow on the dialog box and click PROPERTY_I for the embedded foreign key in the destination feature class.

    Choose the primary key fields.

  22. Click Next.

    A summary page appears.

  23. Review the summary page to make sure the information is correct.
  24. Click Finish.

You have now added a second kind of behavior to the geodatabase—relationships.

Next, you will continue to add behavior to the geodatabase by creating a geometric network and defining connectivity rules. See Exercise 5: Building a geometric network.

Related Topics