Timeline for Setting Map Algebra/Raster Calculator's pixel depth
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2017 at 3:02 | comment | added | Aaron♦ | Related post: gis.stackexchange.com/q/85657/8104 | |
| May 10, 2017 at 2:27 | answer | added | fatih_dur | timeline score: 3 | |
| May 10, 2017 at 1:25 | comment | added | fatih_dur | I think I have found the issue, just my ignorance. In the same help page references in the question, there is only one option for Floating data, which is Floating-point 32 bit. Obviously if ArcGIS sees a float raster is coming, it sets the depth 32 bit automatically. Most probably I need to scale up/down my float values and round to nearest integer to avoid this issue. | |
| May 10, 2017 at 1:21 | comment | added | fatih_dur | @ahmadhanb, Most probably this is related to the overall mechanism of Spatial Analyst or Raster Processing toolsets, somehow it promotes the depth. Thanks for the hint anyway. | |
| May 10, 2017 at 1:04 | comment | added | ahmadhanb | As far as I know, if you clip the raster using a feature class, the output will be a raster depth with a pixel depth of 32 bit even if the raster pixels values can be within 16 or 8 bit pixel depth. The problem might be due to the clipping of raster image rather than the raster calculator. | |
| May 9, 2017 at 23:32 | comment | added | fatih_dur | @ahmadhanb, depending on the problem, both. | |
| May 9, 2017 at 5:41 | comment | added | ahmadhanb | Are you doing NDVI analysis on a full raster scene, or did you clip the raster using feature class before doing NDVI analysis? | |
| May 9, 2017 at 5:20 | history | asked | fatih_dur | CC BY-SA 3.0 |