nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create One to Many Relationship with Table and Parcel Polygon

ABishop

Hello Fellow GIS'ers,

Not sure if I am posting this in the right spot on the community site, but I have tried everything to make this work and to no avail.

I am in ArcGIS Pro 3.0.3 and I have a table and a polygon feature class in the same file geodatabase. I want to join the table to the polygon feature class and create a one to many relationship. Then, I would like to export the join or relationship to a new polygon or point feature class to be able to use the values as a label in my service.

Any ideas on how to accomplish this? For context, below is a list of things I have tried thus far:

1. Join Field (this only joins to the first record of the one to many relationship from the table to the feature layer)

2. Add Join (this only gives me the option to keep all records in either the polygon or table, but not both and then there is no way to create a feature class for use in the label layer)

3. Add Relate (this is only a temporary relationship and there is no way to extract the data into a tangible feature class to use in label layer).

4. Create Relationship Class (this creates a relationship class but I didn't see a way to extract the relationship into a feature class to use in the label layer).

Find more posts tagged with

Accepted answers

ABishop

Thank you @JoshKalov and @jcarlson

I did go back to my first solution which was "Join Field", but added some extra steps to end up with a final result of a point feature class.

These are the steps I took:

1. Copied table for join to FGDB.

2. Copied polygon for join to FGDB.

3. Used "Feature to Point" to make the polygon feature class a point feature class then used "Add XY Coordinates" to add the X,Y fields to the point feature class.

3. Used "Join Field" to join the table to the point feature class (in that order to preserve the one to many relationship, doing the join the other way didn't preserve the one to many relationship, it simply joined the first record in the table).

4. Used "XY Table to Point" to create a feature class from the joined table w/ feature class (this gave me a point feature class to use in my service for labeling which preserved the one to many relationship).

Amanda

All comments

jcarlson

I think you're on the right track with your first approaches. Consider a very simple example: 1 polygon and 2 associated rows.

If I use Join Field on these two tables, the output is close to what you want. It appears and behaves a bit strangely because of the multiple values in the standalone table, which you can see in the attribute table and the polygon labels.

On the one hand, the polygon layer only has a single objectid, and it is impossible to select one without selecting the other. But on the other hand, the table and labels show two distinct features. Pro will give you a little warning when you've got a layer that's in this state.

But the key here is that if you export the layer from this point, the output will be precisely what you are looking for.

I now have two distinct features in my output for each match in the initial join.

ABishop

Hello @jcarlson

I appreciate the quick response. In your join, are you using a table and a polygon?

jcarlson

Yes. Polygon as the input table, standalone table as the "join table" when running the GP tool. But the order shouldn't matter in a case like this, I think.

ABishop

I did this and I am still getting the same result. The Join Field with polygon to table is maintaining a one to one relationship, but preserves the feature class. The Join Field with the table to polygon creates the one to many relationship, but does not preserve the feature class. ugh.

JoshKalovGIS

Are you trying to join multiple table rows to a single polygon? Is your desired output having that polygon duplicated in your output feature class; one copy of the polygon for each table record it was joined to? If so, we have accomplished this using "Make Query Table". That will create the query table in memory but you can export it out as a feature class.

ABishop

Thank you @JoshKalov and @jcarlson

I did go back to my first solution which was "Join Field", but added some extra steps to end up with a final result of a point feature class.

These are the steps I took:

1. Copied table for join to FGDB.

2. Copied polygon for join to FGDB.

3. Used "Feature to Point" to make the polygon feature class a point feature class then used "Add XY Coordinates" to add the X,Y fields to the point feature class.

Amanda

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.