<?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 AutoML Importance Table should display Distance Feature names instead of DIST_X in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/automl-importance-table-should-display-distance/idi-p/1682632</link>
    <description>&lt;P&gt;When using the &lt;STRONG&gt;Train Using AutoML&lt;/STRONG&gt; tool, the Importance Table should display Distance Feature variables using their source Feature Class name (or alias) instead of generic names such as DIST_1, DIST_2, etc.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/148029iFB14FD466C31560B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Currently, the Importance Table generated by the &lt;STRONG&gt;Train Using AutoML&lt;/STRONG&gt; geoprocessing tool:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Correctly displays raster explanatory variable names&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Displays Distance Feature variables as generic labels:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;DIST_1, DIST_2, DIST_3, …&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;When training models with multiple distance features (for example, 10 or more), it becomes difficult to interpret model importance results because users must manually map each DIST_X variable back to its original source feature class.&lt;/P&gt;&lt;P&gt;This manual mapping process is time-consuming, redundant, and introduces risk of human error.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Proposed Solution&lt;/STRONG&gt;&lt;BR /&gt;Update the Importance Table output to display:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Feature Class Name or&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Feature Class Alias (if available)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This would make the output more data-driven and consistent with how raster explanatory variables are handled.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Benefits&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Improves model interpretability&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Reduces manual post-processing work&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Minimizes risk of user error&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Improves usability for complex ML workflows&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Creates consistency across explanatory variable types&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Use Case Example&lt;/STRONG&gt;&lt;BR /&gt;Training suitability or risk models using multiple distance-based drivers such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Distance to roads&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Distance to rivers&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Distance to urban areas&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Distance to infrastructure&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Fri, 06 Feb 2026 05:04:24 GMT</pubDate>
    <dc:creator>kntr</dc:creator>
    <dc:date>2026-02-06T05:04:24Z</dc:date>
    <item>
      <title>AutoML Importance Table should display Distance Feature names instead of DIST_X</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/automl-importance-table-should-display-distance/idi-p/1682632</link>
      <description>&lt;P&gt;When using the &lt;STRONG&gt;Train Using AutoML&lt;/STRONG&gt; tool, the Importance Table should display Distance Feature variables using their source Feature Class name (or alias) instead of generic names such as DIST_1, DIST_2, etc.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/148029iFB14FD466C31560B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Currently, the Importance Table generated by the &lt;STRONG&gt;Train Using AutoML&lt;/STRONG&gt; geoprocessing tool:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Correctly displays raster explanatory variable names&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Displays Distance Feature variables as generic labels:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;DIST_1, DIST_2, DIST_3, …&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;When training models with multiple distance features (for example, 10 or more), it becomes difficult to interpret model importance results because users must manually map each DIST_X variable back to its original source feature class.&lt;/P&gt;&lt;P&gt;This manual mapping process is time-consuming, redundant, and introduces risk of human error.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Proposed Solution&lt;/STRONG&gt;&lt;BR /&gt;Update the Importance Table output to display:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Feature Class Name or&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Feature Class Alias (if available)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This would make the output more data-driven and consistent with how raster explanatory variables are handled.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Benefits&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Improves model interpretability&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Reduces manual post-processing work&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Minimizes risk of user error&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Improves usability for complex ML workflows&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Creates consistency across explanatory variable types&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Use Case Example&lt;/STRONG&gt;&lt;BR /&gt;Training suitability or risk models using multiple distance-based drivers such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Distance to roads&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Distance to rivers&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Distance to urban areas&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Distance to infrastructure&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Fri, 06 Feb 2026 05:04:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/automl-importance-table-should-display-distance/idi-p/1682632</guid>
      <dc:creator>kntr</dc:creator>
      <dc:date>2026-02-06T05:04:24Z</dc:date>
    </item>
  </channel>
</rss>

