<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic prevent automatic bit-depth promotion? in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/prevent-automatic-bit-depth-promotion/m-p/600301#M19907</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have 2 rasters:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1) 2-bit .tif with 3 as the NoData value.&amp;nbsp; Only needs to express 0,1,NoData&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) 1-bit .tif with 0 as the NoData value. Only needs to express 1,NoData&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No matter what sort of analysis I perform on these, they are always promoted to 8-bit with a noData value of 255. This is unacceptable because the file size balloons to 7gb with the promotion.&amp;nbsp; I have found no solution to ensure bit depth is preserved. Having to use copy raster between every operation is not an option. I don't understand why this is happening, because I am not introducing any new values into the rasters through analysis.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Aug 2013 18:46:11 GMT</pubDate>
    <dc:creator>kevinbrown1</dc:creator>
    <dc:date>2013-08-13T18:46:11Z</dc:date>
    <item>
      <title>prevent automatic bit-depth promotion?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/prevent-automatic-bit-depth-promotion/m-p/600301#M19907</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have 2 rasters:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1) 2-bit .tif with 3 as the NoData value.&amp;nbsp; Only needs to express 0,1,NoData&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) 1-bit .tif with 0 as the NoData value. Only needs to express 1,NoData&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No matter what sort of analysis I perform on these, they are always promoted to 8-bit with a noData value of 255. This is unacceptable because the file size balloons to 7gb with the promotion.&amp;nbsp; I have found no solution to ensure bit depth is preserved. Having to use copy raster between every operation is not an option. I don't understand why this is happening, because I am not introducing any new values into the rasters through analysis.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any ideas?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Aug 2013 18:46:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/prevent-automatic-bit-depth-promotion/m-p/600301#M19907</guid>
      <dc:creator>kevinbrown1</dc:creator>
      <dc:date>2013-08-13T18:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: prevent automatic bit-depth promotion?</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/prevent-automatic-bit-depth-promotion/m-p/600302#M19908</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Possibly set the geoprocessing environment NoData to PROMOTION. It's in the raster storage section. Based on the help, and if I'm understanding it correctly, that may do it. In the help, search for "nodata environment" (without quotes). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Melita&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Aug 2013 20:15:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/prevent-automatic-bit-depth-promotion/m-p/600302#M19908</guid>
      <dc:creator>MelitaKennedy</dc:creator>
      <dc:date>2013-08-13T20:15:37Z</dc:date>
    </item>
  </channel>
</rss>

