<?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: Arcpy Near Tool in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/arcpy-near-tool/m-p/1671913#M100744</link>
    <description>&lt;P&gt;I have the same problem. I think, that's a bug.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Dec 2025 10:04:53 GMT</pubDate>
    <dc:creator>OlafErnst1</dc:creator>
    <dc:date>2025-12-10T10:04:53Z</dc:date>
    <item>
      <title>Arcpy Near Tool</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/arcpy-near-tool/m-p/1669113#M100444</link>
      <description>&lt;P&gt;Hello again,&lt;/P&gt;&lt;P&gt;Another post about ArcGIS Pro v3.6 - this one about the Near tool in Arcpy.&lt;/P&gt;&lt;P&gt;I ran the following code in previous versions before and it managed to give updated field names of "Distance_M" and "Bearing" derived from NEAR_DIST and NEAR_ANGLE properties in the tool.&lt;/P&gt;&lt;LI-CODE lang="python"&gt;arcpy.analysis.Near(
    in_features="points",
    near_features="lines",
    search_radius=None,
    location="NO_LOCATION",
    angle="ANGLE",
    method="GEODESIC",
    field_names=[["NEAR_FID", "NEAR_FID"], ["NEAR_DIST","Distance_M"], ["NEAR_ANGLE","Bearing"]],
    distance_unit="Meters",
    match_fields=None
)&lt;/LI-CODE&gt;&lt;P&gt;However, in the latest update, it appears to have kept the field names as NEAR_DIST and NEAR_ANGLE instead (see screenshot below).&lt;/P&gt;&lt;P&gt;From my understanding of the &lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/analysis/near.htm" target="_self"&gt;Near tool documentation&lt;/A&gt;, the tool calls for a value table for field_names in the form of [property, fieldname]. So I'm not too certain where it went wrong in my code.&lt;/P&gt;&lt;P&gt;I can think of ways to work around this to get to my desired output, but I just want to flag this as a potential bug - that's all. Thank you!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KenHo_CL_0-1764308023554.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/144559iAD61BC6D36857886/image-size/medium?v=v2&amp;amp;px=400" role="button" title="KenHo_CL_0-1764308023554.png" alt="KenHo_CL_0-1764308023554.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2025 05:40:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/arcpy-near-tool/m-p/1669113#M100444</guid>
      <dc:creator>KenHo_CL</dc:creator>
      <dc:date>2025-11-28T05:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: Arcpy Near Tool</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/arcpy-near-tool/m-p/1671913#M100744</link>
      <description>&lt;P&gt;I have the same problem. I think, that's a bug.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 10:04:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/arcpy-near-tool/m-p/1671913#M100744</guid>
      <dc:creator>OlafErnst1</dc:creator>
      <dc:date>2025-12-10T10:04:53Z</dc:date>
    </item>
  </channel>
</rss>

