Skip to main content
Question

Return attribute name and value using updatedetector or matcher

M

I am new, so I appreciate your patience.

I have tried to search for my answer, but so far no luck.

I am attempting to compare the values from 2 datasets (no geometry at this point) with the same attribute names. I used the changedetector so we could see which attributes were non-matching and which were missing from one of the datasets (updated, inserted, deleted).

The features have dozens of attributes, so when something doesn't match it can be a process to determine the exact attribute that it failed on. How can we retain/build the relationhship back to the attribute name and value to pinpoint where the failed match occurred?

2 replies

debbiatsafe
Safer
Forum|alt.badge.img+20

Hi @mhollas

One possible way to find updated attributes is to use AttributeExploders and FeatureJoiner. You would need to join on attribute values in the FeatureJoiner. Every updated attribute will be a feature using this method. Please see screenshot below for an example workflow. In addition, instead of the ChangeDetector, I would recommend using the UpdateDetector (custom transformer) as it differentiates between updates and inserts.

If you would like to see information about updated attributes in the ChangeDetector, please consider voting on this following idea https://knowledge.safe.com/idea/19181/more-information-about-what-was-changed.html

I hope this helps!

M
  • mhollas
  • Author
  • June 6, 2018
debbiatsafe wrote:

Hi @mhollas

One possible way to find updated attributes is to use AttributeExploders and FeatureJoiner. You would need to join on attribute values in the FeatureJoiner. Every updated attribute will be a feature using this method. Please see screenshot below for an example workflow. In addition, instead of the ChangeDetector, I would recommend using the UpdateDetector (custom transformer) as it differentiates between updates and inserts.

If you would like to see information about updated attributes in the ChangeDetector, please consider voting on this following idea https://knowledge.safe.com/idea/19181/more-information-about-what-was-changed.html

I hope this helps!

Thanks @DebbiAtSafe. This gets me much closer to what I am trying to accomplish, but the featurejoiner's temp files are waaaaaay to big and I am running out of disk space. The tables im comparing now only contain about 20,000 features, with about 20 attributes. The temp file is over 40gb - I fear this wont be possible with my much larger datasets Ill need to work with soon.

 

 

Reply


Most helpful members this week

Community Stats

30,851
Posts
116,965
Replies
38,676
Members
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.