Create Relationship class based on GLOBALID

2794
3
10-02-2016 11:18 PM
HiteshJilka
New Contributor III

Hello, we have two feature class of Polygon type and have identical geometry shapes, one of feature class has all the attributes filled and another one has attributes with NULL values. There is a common attribute field (say Property Number) where we would like to update that field from origin feature class.

 

Also, I am looking for a solution to update attribute field of another feature class automatically whenever a new insert or update happens in attribute of origin feature class within same geodatabase.

Using relationship class which delivers the same result but it requires referential integrity (Primary & Foreign Key) defined in both feature class. But we don't have a unique ID which can help to achieve the result. Spatial join option cant be used as it creates another join table.

With reference from "Enable  Attachment" Tool  in arcgis, as it copies the Global ID of origin feature class to attachment table with name REL_GLOBALID and maintains it till relationship class exist. 

Is there a way to use Global ID as primary key and copy this Global ID to another feature class based on identical geometry shapes so that update in attribute of particular polygon reflects the changes in same polygon of another feature class.

I would appreciate if someone can help and also give their alternate suggestions to get desired result.

Thanks,

Hitesh

0 Kudos
3 Replies
MitchHolley1
MVP Regular Contributor

So, the source feature and the target feature do not share any unique IDs?  The only relationship that these have are spatial?

0 Kudos
HiteshJilka
New Contributor III

Yes, we don't have a unique ID to create primary and foreign key relationship, only their spatial shape matches.

We have requirement of copying one of attribute field value from one of populated feature class to another feature class having same spatial geometry. 

Using Attribute transfer mapping tool, we can get the solution, but will have to manually select each of parcel to transfer attribute value and it is impractical for numerous parcels.

0 Kudos
MitchHolley1
MVP Regular Contributor

Can you do a spatial join to get the parent primary key.  Then join the spatial join feature back to the child table to populate the parent primary key?  You can then build a relationship. 

0 Kudos