Skip To Content ArcGIS for Developers Sign In Dashboard

Dissolve Boundaries

Dissolve Boundaries workflow diagram

The Dissolve Boundaries task finds polygons that intersect or have the same field values and merges them to form a single polygon.

You can choose how polygons are merged by specifying one or more fields. For example, if you have a layer of study areas and each study area has a Soil_Type field, you can dissolve boundaries using the Soil_Type field. Adjacent study areas will be merged if they have the same value for Soil_Type. The end result is a layer of study areas classified by soil type.

Note:

Dissolve Boundaries was introduced in ArcGIS Enterprise 10.7.

Request URL

http://<analysis url>/DissolveBoundaries/submitJob

Request parameters

ParameterDescription

inputLayer

(Required)

The layer containing polygon features that will be dissolved.

Syntax: As described in Feature input, this parameter can be one of the following:

  • A URL to a feature service layer with an optional filter to select specific features
  • A URL to a big data catalog service layer with an optional filter to select specific features
  • A feature collection

REST web example:

  • {"url" : "https://myportal.domain.com/server/rest/services/Hosted/hurricaneTrack/FeatureServer/0", "filter": "Month = 'September'"}

REST scripting example:

  • "inputLayer" : {"url": "https://myportal.domain.com/server/rest/services/Hosted/hurricaneTrack/FeatureServer/0", "filter": "Month = 'September'"}

dissolveFields

One or more fields in the inputLayer that determine how polygons are merged based on field value.

If you don't specify fields, polygons that intersect will be dissolved into one polygon by default.

If you do specify fields, polygons that share the same value for each of the specified fields will be dissolved into one polygon.

REST web example:

  • State_Name
  • State_Name, District

REST scripting example:

  • "dissolveFields": "State_Name"
  • "dissolveFields": "State_Name, District"

summaryFields

A list of field names and statistical summary types you want to calculate. Note that the count is always returned. By default, all statistics are returned.

Syntax: [{"statisticType" : "<statistic type>", "onStatisticField" : "<field name>" }, ...]

fieldName is the name of the fields in the input point layer.

statisticType is one of the following for numeric fields:

  • Count—Totals the number of values of all the points in each polygon.
  • Sum—Adds the total value of all the points in each polygon.
  • Mean—Calculates the average of all the points in each polygon.
  • Min—Finds the smallest value of all the points in each polygon.
  • Max—Finds the largest value of all the points in each polygon.
  • Range—Finds the difference between the Min and Max values.
  • Stddev—Finds the standard deviation of all the points in each polygon.
  • Var—Finds the variance of all the points in each polygon.

statisticType is one of the following for string fields:

  • Count—Totals the number of strings for all the points in each polygon.
  • Any—Returns a sample string of a point in each polygon.

REST scripting examples:

  • "summaryFields" : [{"statisticType" : "Mean", "onStatisticField" : "Annual_Sales"},{"statisticType": "Sum", "onStatisticField": "Annual_Sales"}]
  • Only return count: "summaryFields" : []

REST web examples:

  • [{"statisticType" : "Mean", "onStatisticField" : "Annual_Sales"},{"statisticType": "Sum", "onStatisticField": "Annual_Sales"}]
  • Only return count: []

multipart

Specifies whether multipart features are allowed in the output feature class. The default is false.

Values: true | false

  • true: Specifies multipart features are allowed.
  • false: Specifies multipart features are not allowed. Instead of creating multipart features, individual features will be created for each part.

REST web example: true

REST scripting example: "multipart": false

outputName

The task will create a feature service of the results. You define the name of the service.

REST scripting example: "outputName" : "myOutput"

REST web example: myOutput

context

Syntax:
{
"extent" : {extent},
"processSR" : {spatial reference},
"outSR" : {spatial reference},
"dataStore":{data store},
"defaultAggregationStyles": {true|false}
}

f

The response format. The default response format is html.

Values: html | json

Response

When you submit a request, the service assigns a unique job ID for the transaction.

Syntax:
{
"jobId": "<unique job identifier>",
"jobStatus": "<job status>"
}

After the initial request is submitted, you can use jobId to periodically check the status of the job and messages as described in Checking job status. Once the job has successfully completed, use jobId to retrieve the results. To track the status, you can make a request of the following form:

https://<analysis url>/DissolveBoundaries/jobs/<jobId>

Accessing results

When the status of the job request is esriJobSucceeded, you can access the results of the analysis by making a request of the following form:

http://<analysis url>/DissolveBoundaries/jobs/<jobId>/results/output?token=<your token>&f=json

ParameterDescription

output

output returns the dissolved features as polygons. If a summaryFields parameter is specified in the task request, the layer will compute the Count statistics, as well as anything in the summaryFields. These statistics are only calculated on the dissolved fields.

Example:
{"url": 
"http://<analysis url>/DissolveBoundaries/jobs/<jobId>/results/output"}

The result has properties for parameter name, data type, and value. The contents of value depend on the outputName parameter provided in the initial request. The value contains the URL of the feature service layer.

{
"paramName":"output", 
"dataType":"GPRecordSet",
"value":{"url":"<hosted featureservice layer url>"}
}

See Feature output for more information about how the result layer is accessed.