+2In 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.
Hi JP, I agree that would be helpful. Maybe post it as an idea?
I'm sure you've thought about this too, but I often use the Referenced output port for this scenario, rather than the Merged port. That way the output features remain untouched.
+2Hi David,
My mistake, I was thinking I had posted it as an idea. using the Referenced is usefull but less logic, less "readable" and therefore less maintainable over time.
+53You can use an InlineQuerier in place of a featuremerger to do this which would remove the need to rebuild any geometry
e.g. SELECT req.* FROM Requestor req, Supplier sup WHERE req.name = sup.name
+26Hi David,
My mistake, I was thinking I had posted it as an idea. using the Referenced is usefull but less logic, less "readable" and therefore less maintainable over time.
+19Optionally that is if you are using database formats, the joiner\\SQLexecutor can also be used.
+2Optionally that is if you are using database formats, the joiner\\SQLexecutor can also be used.
I use something like this but I don't really like it: Merge Result and Initiator based on ID.
+2You can use an InlineQuerier in place of a featuremerger to do this which would remove the need to rebuild any geometry
e.g. SELECT req.* FROM Requestor req, Supplier sup WHERE req.name = sup.name
demo-inlinequerier.fmw
+19I use something like this but I don't really like it: Merge Result and Initiator based on ID.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
