<?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 Re: Unable to allocate memory bug? in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58258#M2472</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://pro.arcgis.com/en/pro-app/tool-reference/tool-errors-and-warnings/010001-020000/tool-errors-and-warnings-10001-10025-010005.htm"&gt;&lt;STRONG&gt;Error 010005..&lt;/STRONG&gt;&lt;/A&gt;.. the message is even in the Pro help, meaning that it has been seen and possible.&amp;nbsp; The options are to use a larger cell size and or partition your data.&amp;nbsp; Maybe not what you want to hear, but it is worth a test of whatever if palatable for your workflow.&amp;nbsp; I have also seen references not specific to Pro that point the finger at a variety of things such as running anything other pro/map (even browsers which can suck huges amount given the chance) and complex/convoluted file paths.&lt;/P&gt;&lt;P&gt;Good luck... tile/parse in half would be the quick check to see if it is indeed memory (run Resource Monitor to see what is actually being used prior to, and during a run)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Nov 2017 03:42:42 GMT</pubDate>
    <dc:creator>DanPatterson_Retired</dc:creator>
    <dc:date>2017-11-28T03:42:42Z</dc:date>
    <item>
      <title>Unable to allocate memory bug?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58257#M2471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, I am using the latest version of arcgis pro and am attempting to reclassify a 2 meter, 32 bit, thematic raster with 3800 records and 15 classes. I am getting an error that suggests that there is not enough available memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ERROR 010005: Unable to allocate memory.&lt;BR /&gt;Failed to execute (Reclassify).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 32 GB or ram and no other resource heavy programs running.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am able to reclassify other rasters in the same project that have more records and higher resolutions. What can I do to troubleshoot this particular raster?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Nov 2017 03:08:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58257#M2471</guid>
      <dc:creator>BobChristensen</dc:creator>
      <dc:date>2017-11-28T03:08:53Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to allocate memory bug?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58258#M2472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://pro.arcgis.com/en/pro-app/tool-reference/tool-errors-and-warnings/010001-020000/tool-errors-and-warnings-10001-10025-010005.htm"&gt;&lt;STRONG&gt;Error 010005..&lt;/STRONG&gt;&lt;/A&gt;.. the message is even in the Pro help, meaning that it has been seen and possible.&amp;nbsp; The options are to use a larger cell size and or partition your data.&amp;nbsp; Maybe not what you want to hear, but it is worth a test of whatever if palatable for your workflow.&amp;nbsp; I have also seen references not specific to Pro that point the finger at a variety of things such as running anything other pro/map (even browsers which can suck huges amount given the chance) and complex/convoluted file paths.&lt;/P&gt;&lt;P&gt;Good luck... tile/parse in half would be the quick check to see if it is indeed memory (run Resource Monitor to see what is actually being used prior to, and during a run)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Nov 2017 03:42:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58258#M2472</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2017-11-28T03:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to allocate memory bug?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58259#M2473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #222222; background-color: #ffffff; font-size: large;"&gt;Thanks Dan. I think the issue had to do with the field being text rather than numeric, though I do not understand why this should cause trouble. I created a new field and assigned numeric values to use instead of the text classes and then reclassified on that field and it worked. Is this just the way it works? I could have sworn that I have reclassified on text fields in the past... Does it take less resources to reclassify numeric fields than text fields?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #222222; background-color: #ffffff; font-size: large;"&gt;b&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Nov 2017 16:46:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58259#M2473</guid>
      <dc:creator>BobChristensen</dc:creator>
      <dc:date>2017-11-28T16:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to allocate memory bug?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58260#M2474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Only conjecture, but it may be holding the text version in memory as well as a conversion to numeric before the actual reclassification begins.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Nov 2017 17:20:34 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/unable-to-allocate-memory-bug/m-p/58260#M2474</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2017-11-28T17:20:34Z</dc:date>
    </item>
  </channel>
</rss>

