- URL:
- https://<root>/<serviceName>/RasterAnalysisTools/GPServer/Nibble
- Methods:
GET
- Version Introduced:
- 10.6
Description
The Nibble
task replaces the input cells corresponding to a mask with the values of the nearest neighbors.
This task can be used to replace a few individual cells with the values immediately nearby. With larger mask areas, larger swaths of cells can be replaced.
Cells that are NoData in the input
define which cells will be nibbled. Any locations in the input
that are not within the mask area will not be nibbled, and so the output value for them will be the same as the input value.
NoData cells in the input raster that are not within the mask are not nibbled. They will remain NoData regardless of the settings of the nibble
and nibble
parameters.
Request parameters
The following table lists the parameters with syntax and details for each:
Parameter | Details |
---|---|
(Required) | The input raster to nibble. The input raster can be either an integer or a floating-point type. Syntax: This parameter can be specified as a portal item ID, a URL to a raster image service layer, a cloud raster dataset, or a shared raster dataset. Examples:
|
(Required) | The input raster to use as the mask. Cells that are NoData in the mask raster identify the cells in Syntax: This parameter can be specified as a portal item ID, a URL to a raster image service layer, a cloud raster dataset, or a shared raster dataset. Examples:
|
(Required) |
The name of the output image service that will be created. You can specify the name, or you can create an empty service using Portal Admin Sharing API and use the return JSON object as input to this parameter. Syntax: A JSON object describes the name of the output or the output raster. Output name example:
Output raster examples:
|
| Specify whether or not NoData values in the input raster are allowed to nibble into the area defined by the mask raster. Syntax: A Boolean value as either
Example:
|
| Specify if NoData cells in the input raster will remain NoData in the output raster. Syntax: A Boolean value as either
Example:
|
| The input raster that defines the zones to use as the mask. Syntax: This parameter can be specified as a portal item ID, a URL to a raster image service layer, a cloud raster dataset, or a shared raster dataset. Examples:
|
|
Contains additional settings that affect task processing. This task has the following settings:
|
|
The response format. The default response format is Values: |
Response
When you submit a request, the task assigns a unique job ID for the transaction.
{
"jobId": "<unique job identifier>",
"jobStatus": "<job status>"
}
After the initial request is submitted, you can use the job
to periodically check the status of the job and messages as described in Checking job status. Once the job has successfully completed, you use the job
to retrieve the results. To track the status, you can make a request of the following form:
https://<raster analysis tools url>/Nibble/jobs/<jobId>
When the status of the job request is esri
, you can access the results of the analysis by making a request of the following form:
https://<raster analysis tools url>/Nibble/jobs/<jobId>/results/outputRaster
Example usage
Below is a sample request URL for Nibble
.
https://services.myserver.com/arcgis/rest/services/System/RasterAnalysisTools/GPServer/Nibble/submitJob
JSON Response syntax
The response returns the output
output parameter, which has properties for parameter name, data type, and value. The content of value
is always the output raster dataset item
and the image service URL.
{
"paramName": <parameter name>,
"dataType": "GPString",
"value": {
"itemId": <item Id>,
"url": <URL>
}
}
JSON Response example
{
"paramName": "outRaster",
"dataType": "GPString",
"value": {
"itemId": "f121390b85ef419790479fc75b493efd",
"url": "https://<server name>/arcgis/rest/services/Hosted/<service name>/ImageServer"
}
}