topic Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS in Geoprocessing Questions

problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Wed, 18 Sep 2013 20:01:11 GMT

Original User: ElenaLZ

Hello everyone,

I have problems with the dissolve function.

I have a shapefile with multiple polygons, some are together and some are not. I want to use the dissolve function to create a new polygon shapefile where all adjacent polygons are aggregated into bigger polygons.

When I use the dissolve function it doesn't dissolve those polygons that only share a point with their neighbours.

A portion of my shapefile before the dissolve:
[ATTACH=CONFIG]27560[/ATTACH]

and after the dissolve
[ATTACH=CONFIG]27561[/ATTACH]

I think that the dissolve function doesn't understand that these polygons are also neighbours and, so, it creates two different polygons. Is there a way I can tell the dissolve function that those polygons are also neighbours?

Any help will be much appreciated.

Thank you.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

ShikoNjuno — Wed, 18 Sep 2013 20:18:25 GMT

Do you happen to have a field that they have in common?
I don't know how you are currently letting the tool know which is a neighbor (and which is not), but I'm pretty sure it's looking for a common field that it can base the dissolve off of.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Wed, 18 Sep 2013 20:28:09 GMT

Original User: rfairhur24

Hello everyone,

I have problems with the dissolve function.

I have a shapefile with multiple polygons, some are together and some are not. I want to use the dissolve function to create a new polygon shapefile where all adjacent polygons are aggregated into bigger polygons.

When I use the dissolve function it doesn't dissolve those polygons that only share a point with their neighbours.

A portion of my shapefile before the dissolve:
[ATTACH=CONFIG]27560[/ATTACH]

and after the dissolve
[ATTACH=CONFIG]27561[/ATTACH]

I think that the dissolve function doesn't understand that these polygons are also neighbours and, so, it creates two different polygons. Is there a way I can tell the dissolve function that those polygons are also neighbours?

Any help will be much appreciated.

Thank you.

What is the "Dissolve function"? Are you using the Dissolve tool? If so, are you checking the create multi-part option? What attributes are you using for the case fields, if any?

Your illustration does not make clear what your problem is. I would want the 2 polygon result you showed, since the attributes indicated (1,and 2) should not dissolve together regardless of whether or not they touch. If those numbers have nothing to do with the dissolve settings than they only confuse the issue.

Basically you cannot get what you want with a single dissolve if you have both touching and non-touching polygons that you want to keep separate at the end. The multi-part option will make one feature whether or not the original polygons touch, and the single part option will never make polygons join together that touch at just a corner point.

So don't start with a Dissolve. Start with the Buffer tool using an very small buffer to get what you consider to be touching to actually join together first (the buffer will make the touching point a touching polygon). Make the Buffer tool do a dissolve on the attribute you will ultimately use in the Dissolve at the end.

Then do a Spatial Join with the original polygons as the target and the Buffer polygons as the join features and use the One to Many option and keep all fields.

Select all features that match on your dissolve attribute from the case field(s).

Dissolve on the selection and include the JOIN_FID value derived from the Buffer as part of the dissolve case fields and the multi-part option. The corner touching polygons will now be joined together, but not polygons with no touching points in common, because the non-touching polygons will have different buffer IDs.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

ElenaLopez — Wed, 18 Sep 2013 20:31:36 GMT

Thanks Shiko.

I have a shapefile with more than 30000 polygons, so I'm trying to find a way to do it automatically and not manually.

I could do it manually but I have to repeat the process several times (I have 100 different shapefiles), so, it could be great if I find a way to solve that.

The dissolve field is optional, and if you don't specify any, then it dissolves the adjacent polygons into bigger ones (just whay I want BUT it doesn't consider as a neighbour the polygons that only share a point with the other ones).

Any additional idea ?

Thank you.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Wed, 18 Sep 2013 20:36:43 GMT

Original User: TKONG

Hello everyone,

I have problems with the dissolve function.

I have a shapefile with multiple polygons, some are together and some are not. I want to use the dissolve function to create a new polygon shapefile where all adjacent polygons are aggregated into bigger polygons.

...
I think that the dissolve function doesn't understand that these polygons are also neighbours and, so, it creates two different polygons. Is there a way I can tell the dissolve function that those polygons are also neighbours?

Any help will be much appreciated.

Thank you.

The Dissolve tool doesn't have more choices to indentify the neighbours, but the Aggregation tool can - just set up the distance between features is greater that feature class tolerance setting value.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

ElenaLopez — Wed, 18 Sep 2013 20:55:07 GMT

That was a good idea, but I don't know why it doesn't perform well. It keeps on creating two different polygons.

The weird thing is that when I calculate the distance to nearest polygon (Genereate Near Table Tool) you see that the distance between both polygons are 0 meters. Why does this happen ?? I mean ... if the distance between both polygons are 0m and I use the aggregation tool with an aggregation distance of 100m why it doesn't aggregate both polygons ??

Any idea ??

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Wed, 18 Sep 2013 21:00:24 GMT

Original User: TKONG

That was a good idea, but I don't know why it doesn't perform well. It keeps on creating two different polygons.

The weird thing is that when I calculate the distance to nearest polygon (Genereate Near Table Tool) you see that the distance between both polygons are 0 meters. Why does this happen ?? I mean ... if the distance between both polygons are 0m and I use the aggregation tool with an aggregation distance of 100m why it doesn't aggregate both polygons ??

Any idea ??

I had a chance to use Aggregation Tool to merge the polygons that distance is 0 (share one point) and it worked well.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

ElenaLopez — Wed, 18 Sep 2013 21:07:53 GMT

What is the name of the tool you are using ?? I'm using ArcGis 10 and the tool is called Aggregate Polygons. Is it the same one as yours ??

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Wed, 18 Sep 2013 21:26:03 GMT

Original User: rfairhur24

What is the name of the tool you are using ?? I'm using ArcGis 10 and the tool is called Aggregate Polygons. Is it the same one as yours ??

There is a tool called Dissolve and the Aggregate Polygons tool technically is not the Dissolve function. In any case, the Dissolve tool is the commonly used tool available for all license levels and the Aggregate Polygon tool is only available with an Advanced license, so I did not consider it likely to be the one you were using.

The Aggregate Polygons Tool is slow and cannot use a case field to separate polygons based on attributes, so it has to be iterated to deal with attribute based aggregations (it also crashes ArcMap after about 600 iterations). The Buffer Tool, Spatial Join Tool and Dissolve Tool are all very fast and observe case field attribute distinctions when creating shapes, so they can process everything in a single step and those are the tools I would use, especially since you do not seem to be eliminating enclosed holes in your output.

For the Buffer I forgot to mention that after you created the buffers using the List option, you would then need to process that result through the Multipart to Singlepart Tool to separate non-touching buffers with the same attributes before applying the Spatial Join tool.

The Aggregate Polygons tool creates single part polygons. To be a single part, a polygon can only have one contiguous enclosed area. It is impossible to have area cross through just a single point, so to maintain single part polygons, two polygons have to be created. With the Dissolve tool you have the option of specifying if you want singlepart or multipart features, but it follows the same rule for single part polygons. So my method tricks ArcMap into creating a hybrid multipart polygon that requires that the polygons must at least touch at a point, which normally is not required by multipart features.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

RichardFairhurst — Wed, 18 Sep 2013 22:57:02 GMT

Here is the model I ran and a test set of data. The screenshots got a little out of order. The first screenshot is the model. The third screenshot shows the input polygons (CornerTouch layer shown). The second screenshot shows the 1 foot buffer distance output which creates a single shape (MapBuffer layer shown). Then after using the multipart to single part tool and the Spatial Join tool (MapBuffer2 layer and MapParcels layers respectively, not shown) I used the Dissolve tool (4th screenshot with MapDissolve layer shown) to achieve the final result.

The central green polygon in the MapDissolve layer is one multipart polygon feature that contains 3 polygon parts that only touch each other at a single point. The other two shapes are separate single part polygon features because they do not touch any other polygon at even a point. The final output has no buffer, so it is a pure dissolve of the original input shapes.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Wed, 18 Sep 2013 23:10:18 GMT

Original User: rfairhur24

Here is a screenshot showing the buffer output as compared to the final output. Just to prove that the final multipart polygon only has each part touching at a point but has the parts joined together in the same way that the buffer overlap joined the polygons.

Although in this particular case all of the polygons shared the same attributes and therefore dissolved together as long as they touched at a point or along a boundary, I could have done this with a larger set of features and used a case field that would have limited the dissolve to polygons that shared the same case attributes as well as touched at a point or along a boundary line. The model I have constructed would complete much faster than an Iterator used with the Aggregate Polygons tool (by a factor of about 10 times faster) and it would not be as likely to crash ArcMap.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Tue, 24 Sep 2013 20:02:20 GMT

Original User: ElenaLZ

Hi,

Your methodology seems to work rfairhur24 but I have few questions about it and I would really appreciate your help !!

1. You said: "Make the Buffer tool do a dissolve on the attribute you will ultimately use in the Dissolve at the end." What does it mean? In your example, which was the attribute ?? Was it the Shape Area ?? All polygons had different areas ... so how did it perform the dissolve function ??
The problem I have is that I don't want to create a dissolve field since I have a shapefile with more than 120000 polygons and it will take me a looooong time to do that. I would like to find a way the program dissolve all neighbour polygons.

2. What did you mean by "Select all features that match on your dissolve attribute from the case field(s)" ??

I tried several times different things but it doesn't work with my data.

Thank you for you time and help !!

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

ElenaLopez — Tue, 24 Sep 2013 21:08:28 GMT

Hi everyone,

I have found the solution, and here are the steps I have followed:

0. Original Data: a shapefile with polygons (data.shp)

1. Create a BUFFER of small distance (name of the new shapefile: data_buffer.shp)
2. DISSOLVE the new shapefile (unchecked create multipart features) (name of the new shapefile: data_buffer_dissolve.shp)
3. Use the INTERSECT tool: intersect data.shp + data_buffer_dissolve.shp (name of the new shapefile: data_buffer_dissolve_intersect.shp)
4. DISSOLVE data_buffer_dissolve_intersect.shp. The dissolve field is the FID of data_buffer_dissolve.shp and this time you do checked create multipart features. Name of the final shapefile (data_def.shp)

Thanks rfairhur24 for suggesting using buffers to solve the problems !!

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

Anonymous User — Tue, 24 Sep 2013 22:32:30 GMT

Original User: rfairhur24

Hi everyone,

I have found the solution, and here are the steps I have followed:

0. Original Data: a shapefile with polygons (data.shp)

1. Create a BUFFER of small distance (name of the new shapefile: data_buffer.shp)
2. DISSOLVE the new shapefile (unchecked create multipart features) (name of the new shapefile: data_buffer_dissolve.shp)
3. Use the INTERSECT tool: intersect data.shp + data_buffer_dissolve.shp (name of the new shapefile: data_buffer_dissolve_intersect.shp)
4. DISSOLVE data_buffer_dissolve_intersect.shp. The dissolve field is the FID of data_buffer_dissolve.shp and this time you do checked create multipart features. Name of the final shapefile (data_def.shp)

Thanks rfairhur24 for suggesting using buffers to solve the problems !!

In essence this is the same as what I suggested. If you have only one grouping (i.e., there are no fields involved in step 1 to separate different buffers that are side by side), then you are correct that this is all you should need.

However, if you have many different groups of parcels close together based on an attribute field of the original parcels that will form separate groupings, the buffer could interact with more than one parcel attribute group and the FID of the buffer could be larger than what you want. So if a grouping attribute is involved I would add a step to select only the records where the case fields that grouped the buffers in step 1 matched the same group field from the intersecting parcels in step 3 before doing step 4. Spatial Join or Intersect basically do the same thing in either case. I just prefer Spatial Join because there are no sliver polygons to deal with.

Re: problems with DISSOLVE function when aggregating NEIGHBOUR POLYGONS

RichardFairhurst — Tue, 24 Sep 2013 22:47:50 GMT

Hi,

Your methodology seems to work   rfairhur24 but I have few questions about it and I would really appreciate your help !!

1. You said: "Make the Buffer tool do a dissolve on the attribute you will ultimately use in the Dissolve at the end." What does it mean? In your example, which was the attribute ?? Was it the Shape Area ?? All polygons had different areas ... so how did it perform the dissolve function ??
The problem I have is that I don't want to create a dissolve field since I have a shapefile with more than 120000 polygons and it will take me a looooong time to do that. I would like to find a way the program dissolve all neighbour polygons.

2. What did you mean by "Select all features that match on your dissolve attribute from the case field(s)" ??

I tried several times different things but it doesn't work with my data.

Thank you for you time and help !!

My Dissolve field was SUBDIV_NAME, but to keep my example simple it did not play a real role, since there was only one subdivision. However, in reality if I ran the tool I would process the 50,000 subdivision values through the process in my 3/4 million parcels. Most of the subdivisions would be right next to each other and I would not want them to bleed together even by the smallest buffer distance, so I added a step to keep the bleeding from occuring. In any case, I think you found that the time spent on dissolving 120000 polygons was less than you thought, and even if it took time, it got the job done.