<?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>idea Leverage Parallel Processing for Build Terrain tool in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/leverage-parallel-processing-for-build-terrain/idi-p/1011319</link>
    <description>&lt;P&gt;Often when building large terrain datasets, the processing time can be very long. Upwards of 2-4 weeks for a county wide terrain dataset derived from LiDAR.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be great if we could leverage parallel processing in this tool. I have a machine with an i7 CPU and 64 GB RAM and the terrain build for a county wide dataset takes at least 14 days. At most, ArcGIS Pro utilizes 3 GB of RAM until phase 3 of the tool where it jumps to about 18 GB.&amp;nbsp;&lt;/P&gt;&lt;P data-unlink="true"&gt;I've gone through this doc on &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/terrains/best-practices-for-building-terrain-datasets.htm" target="_self"&gt;Best Practices of Building Large Terrain Datasets&lt;/A&gt;&amp;nbsp;and &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/terrains/building-large-terrain-datasets.htm" target="_self"&gt;Fundamentals of Building large Terrain Datasets&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Good info here but I've found that building terrains in pieces doesn't always work. I've often gotten error 99999 when try to append multipoints so I ultimately build my terrain all at once using all my multipoints.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have 64GB of RAM and a good CPU on my machine, I would love if Pro could utilize this for the Terrain Build tool!&lt;/P&gt;</description>
    <pubDate>Sun, 25 Apr 2021 21:27:06 GMT</pubDate>
    <dc:creator>tigerwoulds</dc:creator>
    <dc:date>2021-04-25T21:27:06Z</dc:date>
    <item>
      <title>Leverage Parallel Processing for Build Terrain tool</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/leverage-parallel-processing-for-build-terrain/idi-p/1011319</link>
      <description>&lt;P&gt;Often when building large terrain datasets, the processing time can be very long. Upwards of 2-4 weeks for a county wide terrain dataset derived from LiDAR.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be great if we could leverage parallel processing in this tool. I have a machine with an i7 CPU and 64 GB RAM and the terrain build for a county wide dataset takes at least 14 days. At most, ArcGIS Pro utilizes 3 GB of RAM until phase 3 of the tool where it jumps to about 18 GB.&amp;nbsp;&lt;/P&gt;&lt;P data-unlink="true"&gt;I've gone through this doc on &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/terrains/best-practices-for-building-terrain-datasets.htm" target="_self"&gt;Best Practices of Building Large Terrain Datasets&lt;/A&gt;&amp;nbsp;and &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/terrains/building-large-terrain-datasets.htm" target="_self"&gt;Fundamentals of Building large Terrain Datasets&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Good info here but I've found that building terrains in pieces doesn't always work. I've often gotten error 99999 when try to append multipoints so I ultimately build my terrain all at once using all my multipoints.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have 64GB of RAM and a good CPU on my machine, I would love if Pro could utilize this for the Terrain Build tool!&lt;/P&gt;</description>
      <pubDate>Sun, 25 Apr 2021 21:27:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/leverage-parallel-processing-for-build-terrain/idi-p/1011319</guid>
      <dc:creator>tigerwoulds</dc:creator>
      <dc:date>2021-04-25T21:27:06Z</dc:date>
    </item>
  </channel>
</rss>

