Identify operations on Raster not working from service published from Pro

Chris Roberts

• July 27, 2022 02:26

We are now using Pro 3.0 to publish our services to a 10.8 ArcGIS Server for our Geortex applications.

I have noticed that identifying on Raster Layers no longer works.

When you look at the f12 result returned from service published from ArcMap it shows this as the fields:

{"results":[{"layerId":0,"layerName":"Mean Annual Rainfall 1976 - 2005","displayFieldName":"","attributes":{"Class value":"0","Pixel Value":"178","OBJECTID":"519","COUNT":"925527"},"geometryType":"esriGeometryPoint","geometry":{"x":15153629.346027553,"y":-3629514.4991344623,"spatialReference":{"wkid":102100,"latestWkid":3857}}}]}

I manually parse the {Pixel Value} field as a field token in the Feature Description display in Essentials Manager and it works fine.

When you identify  a service published from Pro  it shows this:

{"results":[{"layerId":0,"layerName":"Mean Annual Rainfall 1976 - 2005","displayFieldName":"","attributes":{"Classify.Pixel Value":"237","Classify.Class value":"1","Raster.OBJECTID":"578","Raster.COUNT":"381783"},"geometryType":"esriGeometryPoint","geometry":{"x":15581676.704255763,"y":-3784834.5408201423,"spatialReference":{"wkid":102100,"latestWkid":3857}}}]}

Note the new prefix.  If I add {Classify.Pixel Value}  to Feature Description it still doesn’t work.  An f12 isnt showing any errors in fact it is returning the results, they are just not being reflected in the popup.

As a workaround I have published the Raster Layers from ArcMap however this means a little more management overhead and given that the next version of ArcGIS server will not support the ArcMap runtime, we need to find a solution to this.

We are currently running the latest 4.14 GXE and HTML5 version.

0

• 

  Nina Rihn

  • October 07, 2022 17:29

  I am also experiencing this problem after republishing map services with ArcGIS Pro that contain rasters, including for a raster that has attributes, in this case, a vegetation type.     The field names are returned using Identify, but all of the values say N/A instead of their actual value.  

  0
• 

  Chris Roberts

  • October 09, 2022 20:33

  I have been told by our reseller that this is a bug with 4.14.  Unfortunately there is no workaround.   They couldnt give me a timeframe on if/when this will be fixed.

  0

Please sign in to leave a comment.