Skip to main content
Solved

Relate Records and update a field

  • December 1, 2022
  • 2 replies
  • 11 views

vxn43
Supporter
Forum|alt.badge.img+18

I have two Geodatabase Feature Classes, FC1 and FC2.

 

I want to relate the GIS_ADDR field in FC1 to the ADDR_BASE field in FC2.

 

Once the relate is established, for the matching (selected) records in GIS_ADDR in FC1, I will then update the ADDR_SRCE field which is currently empty with the value "ADS"; for the records that do not match I will add the value "Res".

 

I know how to do this in ArcGIS Pro. What is the best approach to do this in FME?

Best answer by dustin

I would use a FeatureMerger. FC1 would go into the Requestor port, FC2 would go into the Supplier port. You will need to set the GIS_ADDR and ADDR_BASE fields in the Join On parameters of the FeatureMerger. Then from the Merged and UnmergedRequestor ports, feed those into 2 separate AttributeCreators. In each of those you can set the ADDR_SRCE field to your values.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

dustin
Influencer
Forum|alt.badge.img+31
  • Influencer
  • 627 replies
  • Best Answer
  • December 1, 2022

I would use a FeatureMerger. FC1 would go into the Requestor port, FC2 would go into the Supplier port. You will need to set the GIS_ADDR and ADDR_BASE fields in the Join On parameters of the FeatureMerger. Then from the Merged and UnmergedRequestor ports, feed those into 2 separate AttributeCreators. In each of those you can set the ADDR_SRCE field to your values.


vxn43
Supporter
Forum|alt.badge.img+18
  • Author
  • Supporter
  • 48 replies
  • December 1, 2022

@dustin​ thank you. I also tried it using AttributeManager instead of AttributeCreator. That also worked. Your suggestion seems more logical.