<?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: tools: generate near table - performance issues in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/tools-generate-near-table-performance-issues/m-p/1576762#M92071</link>
    <description>&lt;P&gt;didn't usse parallel processing settings up to now. thought if not set all ressources are going to be used..&lt;BR /&gt;no vpn no ondrive. just a superfast 2 years old machine.&lt;BR /&gt;the option of runnng a 1500m select sounds pretty promising -- thx for the hint !!! will try that !&lt;BR /&gt;&lt;BR /&gt;i would use EPSG 3035 since the data covers whole area of europe. but this one is equal area and at the outer areas of the extent of epsg 3035 i would have reasonable problems with distance values then&lt;/P&gt;&lt;P&gt;so i stepped back to the geodetic-mode. since i know that postgis doesn't use spatial indices for ST_DISTANCE geodetic version, i thougth that coud be an issue in argis pro too ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Jan 2025 13:56:30 GMT</pubDate>
    <dc:creator>robertkalasek</dc:creator>
    <dc:date>2025-01-17T13:56:30Z</dc:date>
    <item>
      <title>tools: generate near table - performance issues</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/tools-generate-near-table-performance-issues/m-p/1575732#M91977</link>
      <description>&lt;P&gt;i am about to generate a near table. the input is a metric CRS and the output distance unit is set to meters, the method is set to "Geodesic" - in order to get non-projected distances. the origins are about 6.7 mio points all over Europe, near features are about 30 mio polygons. everything is spatially indext - of course. and a search radius is set to a pretty low value of 1500m ...&lt;BR /&gt;&lt;BR /&gt;everything works fine, so far on sub-samples. but the performance is deeply disappointing with the 6.7mio points and definitely not up to any reasonable standard.&lt;BR /&gt;especially when considering that the machine is a i9-13900K, 24 core, 128 GB RAM device.&lt;BR /&gt;according to the windows ressourcemonitor.app exactly 3 % of the cpu performance are used to do my calculations. ... three percent !&lt;BR /&gt;&lt;BR /&gt;are there any ideas for workarounds, multithread settings or anything like this to incerase performance ?&lt;BR /&gt;best robert&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 11:09:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/tools-generate-near-table-performance-issues/m-p/1575732#M91977</guid>
      <dc:creator>robertkalasek</dc:creator>
      <dc:date>2025-01-15T11:09:40Z</dc:date>
    </item>
    <item>
      <title>Re: tools: generate near table - performance issues</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/tools-generate-near-table-performance-issues/m-p/1575977#M91997</link>
      <description>&lt;P&gt;Possibly play with the parallel processing factor environment setting and see how the changes compare on the subset timings.&lt;BR /&gt;&lt;BR /&gt;Possibly increase the spatial index levels, and data is local (not on OneDrive or making database transactions over a VPN or something!).&lt;/P&gt;&lt;P&gt;Possibly run a select by location of polygons within1500m and export them out, as I would guess the others are irrelevant to the analysis.&amp;nbsp; However the spatial index should really be good enough to very quickly filter these out.&amp;nbsp; However maybe worth a try.&lt;/P&gt;&lt;P&gt;What kind of scale distortion do you have across your extent?&amp;nbsp; I'm guessing you have something like Lambert Conformal Conic as the projection.&amp;nbsp; Wondering if you can trade a bit of accuracy for speed with a Planar computation.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 21:14:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/tools-generate-near-table-performance-issues/m-p/1575977#M91997</guid>
      <dc:creator>DavidPike</dc:creator>
      <dc:date>2025-01-15T21:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: tools: generate near table - performance issues</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/tools-generate-near-table-performance-issues/m-p/1576762#M92071</link>
      <description>&lt;P&gt;didn't usse parallel processing settings up to now. thought if not set all ressources are going to be used..&lt;BR /&gt;no vpn no ondrive. just a superfast 2 years old machine.&lt;BR /&gt;the option of runnng a 1500m select sounds pretty promising -- thx for the hint !!! will try that !&lt;BR /&gt;&lt;BR /&gt;i would use EPSG 3035 since the data covers whole area of europe. but this one is equal area and at the outer areas of the extent of epsg 3035 i would have reasonable problems with distance values then&lt;/P&gt;&lt;P&gt;so i stepped back to the geodetic-mode. since i know that postgis doesn't use spatial indices for ST_DISTANCE geodetic version, i thougth that coud be an issue in argis pro too ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2025 13:56:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/tools-generate-near-table-performance-issues/m-p/1576762#M92071</guid>
      <dc:creator>robertkalasek</dc:creator>
      <dc:date>2025-01-17T13:56:30Z</dc:date>
    </item>
  </channel>
</rss>

