<?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: Generate Near Table in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/generate-near-table/m-p/1675743#M75039</link>
    <description>&lt;P&gt;You’re right. Generate Near Table ignores selections and definition queries and runs against the full dataset. This is a known, inconsistent behavior (especially compared to Generate Link Table) and isn’t well documented. Exporting the filtered input first is the correct workaround.&lt;/P&gt;</description>
    <pubDate>Sat, 03 Jan 2026 03:58:00 GMT</pubDate>
    <dc:creator>VenkataKondepati</dc:creator>
    <dc:date>2026-01-03T03:58:00Z</dc:date>
    <item>
      <title>Generate Near Table</title>
      <link>https://community.esri.com/t5/python-questions/generate-near-table/m-p/1675741#M75038</link>
      <description>&lt;P&gt;I think I have found a bug with Generate Near Table tool. I am using it with large table, but the generate the near table function does not honour a selection or Definition Query when calculating of the input table. This doesnt appear to be an issue with the generate link table. But I have had to resort to exporting the input table before running the function.&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jan 2026 03:05:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/generate-near-table/m-p/1675741#M75038</guid>
      <dc:creator>PaulPrevedoros1</dc:creator>
      <dc:date>2026-01-03T03:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: Generate Near Table</title>
      <link>https://community.esri.com/t5/python-questions/generate-near-table/m-p/1675743#M75039</link>
      <description>&lt;P&gt;You’re right. Generate Near Table ignores selections and definition queries and runs against the full dataset. This is a known, inconsistent behavior (especially compared to Generate Link Table) and isn’t well documented. Exporting the filtered input first is the correct workaround.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jan 2026 03:58:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/generate-near-table/m-p/1675743#M75039</guid>
      <dc:creator>VenkataKondepati</dc:creator>
      <dc:date>2026-01-03T03:58:00Z</dc:date>
    </item>
  </channel>
</rss>

