Skip to main content
Question

Match the Matched Inputs !!!

  • December 26, 2014
  • 4 replies
  • 54 views
parashari
Forum|alt.badge.img+2
Hi,

 

I am working with FME 14 on a Win7 machine (8Gb).

 

I have temopral data of same dataset where the columns are 'Official Name', 'Brand Name', 'FeatureId' etc.

 

So, what I need to do is-

 

1) Find out how many FeatureId are matching.

 

2) Only if the FeatureId is matching, then how many Official Names, Brand Names, etc are matching.

 

 

I tried doing it with Matcher. I got the FeatureIds correct. Now, if I connect the output of FeatureID to check for Brand Names, the output is wrong. But, when I connect Brand Names with reader, the output is awesome.

 

Is there a way to get it correct? ):
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.

4 replies

takashi
Celebrity
  • takashiCelebrity
  • December 26, 2014
Hi,

 

 

I'm not sure what is the exact requirement...

 

If you need to find features that have identical combination of Feature ID and Brand Name, specify the two attributes to the "Selected Attributes" parameter of the Matcher.

 

 

Takashi
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
parashari
Forum|alt.badge.img+2
  • parashari
  • Author
  • December 29, 2014
Hi Takashi. PFA for more detailed description.

 

I have two inputs of same dataset but different releases.

 

- Using Matcher, I matched FeatureId.

 

- Now, in the next step, I want to match 'OfficialName', but only those number of 'OfficialName' where 'FeatureId' is already matched.

 

 

Applying another Matcher in series is not giving the desired o/p. Neither selecting FeatureId and OfficialName in one Matcher.

 

takashi
Celebrity
  • takashiCelebrity
  • December 29, 2014
How about using the ChangeDetector?

 

Send the PRE features to the Original port; send the POST features to the Revised port.

 

Match Geometry: NONE

 

Attribute Matching Strategy: Match Selected Attributes

 

Selected Attributes: FeatureID, OfficialName

 

 

Then,

 

- Matched features go to the Unchanged port.

 

- Unmatched POST features go to the Added port.

 

- Unmatched PRE features go to the Deleted port.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
parashari
Forum|alt.badge.img+2
  • parashari
  • Author
  • December 31, 2014
Hi Takashi. Thanks for your help.

 

The problem with ChangeDetector I felt was that, it gives a count of Added and Deleted attributes only on the basis of a field (FeatureId in my case) and I wanted the count of those field which were edited.

 

So, for that I used a different method, long and hectic, but still working.

 

I copied the attributes from one dataset to another, making sure that all fields are in a single dataset. Now, I used FuzzyStringComparer. On the basis of that, I got the unmatched components (the edited ones).

 

This method is a bit long. Any other instances to resolve this issue?

Community Stats

32,629
Posts
123,840
Replies
41,000
Members
Terms & ConditionsAccessibility statement
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.