Skip to main content
Archived

Feature Merger Type as NONE on the FeatureMerger

Related products:Transformers
  • January 13, 2017
  • 3 replies
  • 26 views
jpvo
Contributor
Forum|alt.badge.img+2

In many occasions I use a FeatureMerger to verify the match of ID between two datasets.

In this situation I really don't want to merge attributes at all. I use the Feature Merge Type "geometry" but then I need to restor the original geometry of the requestor (GeometryExtractor / Replacer).

My life would be much easier with an option "None" which checks the match between two dataset but leave untouched both requestor and suppliers so I don't have to worry about attribute accumulation.

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.

3 replies

takashi
Celebrity
  • takashiCelebrity
  • January 13, 2017

Agree. In the interim, you can also use the InlineQuerier with a SQL statement like this.

select * from Requestor where ID in (select ID from Supplier)
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
david_r
Celebrity
  • david_rCelebrity
  • January 13, 2017
I agree, but I must say my experience with the InlineQuerier has been less than fantastic when there is a lot of data, for some reason it seems to eat up memory at a rate that can create problems for the FME process later on in the workspace.

 

jpvo
Contributor
Forum|alt.badge.img+2
  • jpvoContributor
  • Author
  • Contributor
  • January 20, 2017
It's a good idea but the InlineQuerrier does not immediatelly offer the same funcitonalities as the FeatureMerger.

 

Beeing forced to use the InlineQuerrier in place of a FM because you're scared of overwriting attributes doens'nt seem a good justification to me.

 

 

Community Stats

32,711
Posts
124,124
Replies
41,193
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.