Solved

How to Apply the Same Type of Merge 18 (or n number of) times without 18 Feature Merge Transformers

J
Badge

To Whom This May Concern:

I process fields and produce a table of 60 attributes. In another document, I have 18 different curves (numbered Curve #1 through to Curve #18) as per the screenshot attached to this document (e.g. ). I am able to apply a Feature Merger transformer to a single Curve (e.g. by using a Tester or Test Filter to isolate for any one curve).

What I hope to do is automate the process such that I can merge the 60 features from the one curve to the 50 attributes belonging to each individual curve in the other document (e.g. merge the 60 attribute document to 50 attributes n number of times based on the number of curves available in the other document I'm working from). Is it possible to automate this process using a single Feature Merger? Or would using InLineQuerier be more beneficial in this case? Any ideas or suggestions would be greatly appreciated.

Best Regards,

- J

icon

Best answer by takashi 11 June 2016, 00:55

View original

5 replies

J
Badge

Additionally, I wanted to separate each set of 60 attributes into different tables for processing within FME before reinserting them into the same document (e.g. using a single writer).

takashi
Rank
Userlevel 2
Badge +17

Hi @je6thoma, if all the Curve #1 - #18 features have a common attribute that can be used as the Join On parameter, send all the curve features to the Supplier port and check the "Generate List" option in the FeatureMerger parameters dialog. With this option, the transformer adds a list attribute to the resulting features, which stores all merged attributes from multiple supplier features. Then you can explode the features on the list with the ListExploder. Note: Make sure that "Using Incoming List" is set to the "Conflict Resolution" parameter of the ListExploder.

takashi
Rank
Userlevel 2
Badge +17

Additionally, I wanted to separate each set of 60 attributes into different tables for processing within FME before reinserting them into the same document (e.g. using a single writer).

you can do that with setting the "Feature Type Fanout", See here: Setting Feature Type Fanout

fmelizard
Rank
Userlevel 4
Badge +13

I think you can win here but maybe you can help us a bit more so we can see what is going on.

From the example, we see 60 requestors. Can you give us a tiny sample of what data is on a requestor and most importantly what "key" attribute it has that will connect with the suppliers.

Similarly, what is the data model of the suppliers. What Keys to do they have.

 

 

And lastly, what would you like the output to be. Do you need the requestor duplicated for each supplier it matches?

 

 

i.e.

 

 

Requestors look like:

keyAttr Val1 Val2

 

--------- ----- -----

 

3 a b

 

 

Suppliers look like:

...

 

 

Output should look like:

...

If you can give us that we can help.

 

 

Note -- I doubt you'll need the testfilter ultimately. I suspect that Group-ing in the FeatureMerger may accomplish the same thing...if it is necessary at all.

 

 

Good scenario!
G
Badge +3

also conditional attribute creator might be helpfull.

Depending on what it actually is you are using as criterium.

If there is no criteria, yu can just join em unconditionally.

Reply


Community Stats

28,666
Posts
109,343
Replies
36,535
Members
Terms & ConditionsCookie 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.