Hi,
I have a dataset with a class called drains, I no longer want drains to appear in the dataset and would like to merge/dissolve these on their nearest neighbour. When I do this at the moment, many dissolve and the neighbours attributions wins out, but in some cases (it appears to be when the drain is the bigger feature) the drains attribution remains. Is it possible to dissolve all drains into their neighbour and always have the neighbours attribution remaining?
Thanks for any help.
B
What do you have the accumulation mode set to?
If the drain attributes are not important I would remove all attributes except from those required in a group by and then choose Merge Incoming Attributes
What do you have the accumulation mode set to?
If the drain attributes are not important I would remove all attributes except from those required in a group by and then choose Merge Incoming Attributes
Hi @ebygomm
I've tried all accumulations, but generally go with 'Use attributes from one feature'. Results seem to be similar no matter which one I use, except 'Drop incoming features' which drops everything.
How can I define that the drain is the incoming attribute. There are multiple (35) other classes that the drain could be merging onto. Right now, I have a spatial relator which creates a relationship between the drain and its neighbouring class and then I merge using this group by ID. But I still get drains out.
Thanks for your help.
B
Hi @ebygomm
I've tried all accumulations, but generally go with 'Use attributes from one feature'. Results seem to be similar no matter which one I use, except 'Drop incoming features' which drops everything.
How can I define that the drain is the incoming attribute. There are multiple (35) other classes that the drain could be merging onto. Right now, I have a spatial relator which creates a relationship between the drain and its neighbouring class and then I merge using this group by ID. But I still get drains out.
Thanks for your help.
B
Have you tried just removing all the attributes from the drain features?
Hi @ebygomm
I've tried all accumulations, but generally go with 'Use attributes from one feature'. Results seem to be similar no matter which one I use, except 'Drop incoming features' which drops everything.
How can I define that the drain is the incoming attribute. There are multiple (35) other classes that the drain could be merging onto. Right now, I have a spatial relator which creates a relationship between the drain and its neighbouring class and then I merge using this group by ID. But I still get drains out.
Thanks for your help.
B
Yes, this ^
As per the Help/Documentation:
Attribute Accumulation Mode
Merge Attributes merges all attributes from overlapping segments. If there are conflicts, attributes from input polygons will be preserved in a two-step process:
If you remove all the Drain Feature Attributes with say, an AttributeRemover, then the Second step in the Merge Attribute process will not have any Attribute conflicts to resolve, so all Attributes in the output will be from a Neighbor Feature
Hi @ebygomm
I've tried all accumulations, but generally go with 'Use attributes from one feature'. Results seem to be similar no matter which one I use, except 'Drop incoming features' which drops everything.
How can I define that the drain is the incoming attribute. There are multiple (35) other classes that the drain could be merging onto. Right now, I have a spatial relator which creates a relationship between the drain and its neighbouring class and then I merge using this group by ID. But I still get drains out.
Thanks for your help.
B
Thanks @ebygomm and @bwn. Removing the attributes worked. Thanks I appreciate your concise and prompt help.
B