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.