Use Spatial Analyst Toolbox on Portal Imagery Layers

[Jeff-Reinhart]

Can tools from the Spatial Analyst toolbox be used on Portal Imagery Layers?

I am having a hard time finding definitive documentation on this.

Testing:

• Store CRF file in Azure Storage Account.
• Publish CRF to Portal as referenced Imagery Layer.
• Add Imagery Layer to ArcGIS Pro 3.3.
• Add layer from Pro Contents to Spatial Analyst | Extract by Mask tool.
• Displays "Error 001491 Not running inside a server process".

I have tried the same Imagery Layer in multiple Spatial Analyst tools, they all return the same error.

I have read about other causes for Error 001491. This is not related to the "cannot process above the size limits of the image service" variant. We have the "Max image size per request (rows x columns)" set at 1000000 x 1000000 and the raster is under 30k x 30k.

I am aware that I can use Raster Functions for raster analysis of Imagery Layers. The issue is there are so many tools built on Spatial Analyst. I am also aware that users can extract the raster to a local copy and then run Spatial Analyst tools on that local copy. If I am going to promote that extra step, it would help to have confirmation that it is necessary.

[GlenterpriseUK]

Hi @Jeff-Reinhart,

I just tried to run the Extract by Mask from ArcGIS Pro on an Imagery Layer in ArcGIS Enterprise 12 and I was able to run the tool without any issue

Might be worth reaching out to Esri Support for further troubleshooting

Regards,

Glen

[Jeff-Reinhart]

@GlenterpriseUK, looks like your raster data is hosted on an enterprise machine rather than referenced. I have to wonder if that is the difference.

[wizgis]

Hi @Jeff-Reinhart 

I published a referenced imagery layer (PostgreSQL GDB) to ArcGIS Enterprise and the ran the tool of Extract By Mask and it ran successfully.

Perhaps it could be something related to data

[Jeff-Reinhart · Accepted solution]

This is specific to raster datasets hosted in containers such as Azure Storage Account Blob Containers. There is a bug: BUG-000178846. The initial bug submission was in relation to a TIF, so it does not seem the file type is the issue. The workaround is to access the raster dataset directly in the storage account (we'll be using ACS files for that). Looking forward to seeing a fix from Esri.