When creating an elevation service of 32-bit GRID data, the pixel value of the source raster is not read correctly.
上次发布: August 25, 2014ImageServer
漏洞 ID 编号
NIM057979
已提交
June 3, 2010
上次修改时间
June 5, 2024
适用范围
ImageServer
找到的版本
9.3.1
操作系统
Windows OS
操作系统版本
2008
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
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.
解决办法
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.