<?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 Improve Usability of arcpy.da.walk in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idi-p/925858</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The addition of the arcpy walk fuction at 10.1 was a great help in replacing the ListFeatureClasses and ListDatasets functionality which&amp;nbsp;are incredibly slow for large numbers of datasets within a workspace.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, the results of the walk are not particularly intelligent. They don't contain useful properties such as dataset type. Therefore to ascertain type you have to put a filter on the walk function (rather than filtering the results)&amp;nbsp;which has a&amp;nbsp;massively detrimental effect on speed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example&amp;nbsp;when running on a sample gdb containing ~5000 datasets&amp;nbsp;arcpy.da.walk&amp;nbsp;will return a dataset list in approx. 10 seconds when run without a dataset type filter. However, once the filter&amp;nbsp;is added to the walk it takes several hours (somewhat counter-intuitive as it returns a smaller list)!&lt;BR /&gt;&lt;BR /&gt;There must be a way to quickly access this information without deep diving into every dataset (which is what I suspect it is doing), as ArcCatalog displays this information within seconds in the "Type" column.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be very useful to have a more&amp;nbsp;efficient pythonic way to get at dataset type!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Jul 2019 09:39:58 GMT</pubDate>
    <dc:creator>RichardHowe</dc:creator>
    <dc:date>2019-07-05T09:39:58Z</dc:date>
    <item>
      <title>Improve Usability of arcpy.da.walk</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idi-p/925858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The addition of the arcpy walk fuction at 10.1 was a great help in replacing the ListFeatureClasses and ListDatasets functionality which&amp;nbsp;are incredibly slow for large numbers of datasets within a workspace.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, the results of the walk are not particularly intelligent. They don't contain useful properties such as dataset type. Therefore to ascertain type you have to put a filter on the walk function (rather than filtering the results)&amp;nbsp;which has a&amp;nbsp;massively detrimental effect on speed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example&amp;nbsp;when running on a sample gdb containing ~5000 datasets&amp;nbsp;arcpy.da.walk&amp;nbsp;will return a dataset list in approx. 10 seconds when run without a dataset type filter. However, once the filter&amp;nbsp;is added to the walk it takes several hours (somewhat counter-intuitive as it returns a smaller list)!&lt;BR /&gt;&lt;BR /&gt;There must be a way to quickly access this information without deep diving into every dataset (which is what I suspect it is doing), as ArcCatalog displays this information within seconds in the "Type" column.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be very useful to have a more&amp;nbsp;efficient pythonic way to get at dataset type!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jul 2019 09:39:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idi-p/925858</guid>
      <dc:creator>RichardHowe</dc:creator>
      <dc:date>2019-07-05T09:39:58Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Usability of arcpy.da.walk</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/925859#M1264</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;An additional piece of usability would be to all arcpy.da.walk to return workspaces within the top directory and allow us to specify which type of workspace we'd like returned (e.g. return only file geodatabases).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2020 18:14:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/925859#M1264</guid>
      <dc:creator>AJR</dc:creator>
      <dc:date>2020-03-23T18:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Usability of arcpy.da.walk - Status changed to: Under Consideration</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/1332264#M26322</link>
      <description>&lt;P&gt;This is valid, and thanks for bringing it to our attention. In the future, for issues of this nature (significant performance regression when asking for less data) are bugs and should be submitted via support requests. However given this has a number of Kudos and a clear story, keeping this idea open to track its progress.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Cheers, Shaun&lt;/P&gt;</description>
      <pubDate>Tue, 26 Sep 2023 04:35:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/1332264#M26322</guid>
      <dc:creator>ShaunWalbridge</dc:creator>
      <dc:date>2023-09-26T04:35:52Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Usability of arcpy.da.walk - Status changed to: In Product Plan</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/1366324#M27854</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We're working on this!&amp;nbsp; This status does not guarantee that the functionality will be in the next release, but development work has begun. Release cycles vary by product so make sure to check&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;the&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://support.esri.com/en/other-resources/product-life-cycle" target="_blank" rel="noopener nofollow noreferrer"&gt;&lt;SPAN&gt;product&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;life cycle information&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;to get an idea of when to expect the next release.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jan 2024 16:12:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/1366324#M27854</guid>
      <dc:creator>HannesZiegler</dc:creator>
      <dc:date>2024-01-04T16:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: Improve Usability of arcpy.da.walk - Status changed to: Implemented</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/1432129#M30067</link>
      <description>&lt;P&gt;This is implemented in ArcGIS Pro 3.3. See &lt;A href="https://community.esri.com/t5/arcgis-ideas-blog/your-ideas-in-arcgis-pro-3-3/bc-p/1431910" target="_blank"&gt;Your Ideas in ArcGIS Pro 3.3&lt;/A&gt; for a full list of all user ideas you can look forward to! And be sure to check out the &lt;A href="https://www.esri.com/arcgis-blog/products/arcgis-pro/announcements/whats-new-in-arcgis-pro-3-3/" target="_blank"&gt;release blog&lt;/A&gt; and what’s new &lt;A href="https://pro.arcgis.com/en/pro-app/latest/get-started/whats-new-in-arcgis-pro.htm" target="_blank"&gt;help topic and video&lt;/A&gt; to learn more about all the new features and functionality in the release.&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 15:21:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/improve-usability-of-arcpy-da-walk/idc-p/1432129#M30067</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2024-05-10T15:21:18Z</dc:date>
    </item>
  </channel>
</rss>

