NIM057979 for ImageServer

Numéro d’ID de bogue	NIM057979
Envoi	June 3, 2010
Dernière modification	June 5, 2024
S’applique à	ImageServer
Version trouvée	9.3.1
Système d’exploitation	Windows OS
Version du système d’exploitation	2008
Statut	Will Not Be Addressed

Informations supplémentaires

We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.

Solution de contournement

One workaround is to convert the imagery to 32-bit Float (Presently, it's Unsigned 32-bit Int), then it will be handled correctly in the Elevation ISDef. -- This will result in the correct values in the TOC and when using Identify.Another is to create an image service definition using the Advanced option > Create NewChoose Custom and define: 1 band, UInt32, 32, UnknownAdd data using Elevation -> ESRI Binary Grid raster typeUsing a batch Editor (or using the Editor wizard and replacing the XPaths), open the RPDef file and edit two nodes to change the pixel type://ImageServer/RasterProcessDefinition/PixelType – change ‘Elevation’ to ‘Uint32’//ImageServer/RasterProcessDefinition/Rasters/Raster/FormatInto/PixelType – change ‘Int32’ to ‘Uint32’Build – using the defaultsThen open the Image Service Definition, change the Output Definition > Pixel Type, to ‘Unsigned 32-bit Integer’.You will not see the correct values in the TOC, but they will be correct when using identify.SEE the workaround in the doc placed in the test path location.