Clipper - Attributes are not merged in Outside output
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.
+22- Contributor
- 2179 replies
If you have only one Clipper and need the attributes on the Outside port, I would use a FeatureMerger transformer after the Outside port, with the Supplier being the Clipper and join on 1 = 1 (always joining).
Use attributes only as a setting.
Hope this helps.
If you have only one Clipper and need the attributes on the Outside port, I would use a FeatureMerger transformer after the Outside port, with the Supplier being the Clipper and join on 1 = 1 (always joining).
Use attributes only as a setting.
Hope this helps.
Thank you for your help, im very new on fme , can you explain me how the feature merger work ?
+22- Contributor
- 2179 replies
Thank you for your help, im very new on fme , can you explain me how the feature merger work ?
It should look like this:
The the Merged output port of the FeatureMerger will contain the Data with the attributes from the Clipper merged to it.
The join on 1 = 1 means that every data record will be joined with the Clipper record.
The attributes only means that the Clipper geometry will not be on the data.
If an attribute is on both the data and the clipper geometry, the data attribute will be used.
It should look like this:
The the Merged output port of the FeatureMerger will contain the Data with the attributes from the Clipper merged to it.
The join on 1 = 1 means that every data record will be joined with the Clipper record.
The attributes only means that the Clipper geometry will not be on the data.
If an attribute is on both the data and the clipper geometry, the data attribute will be used.
Thank you very much for your help its works