<?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 Allow users to validate topology within a defined extent via python in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idi-p/921870</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With the current 'Validate Topology' geoprocessing tool, there is an option to use the 'visible extent' parameter to validate only the current extent of your data. If I were to create a python script to validate topology, I would still need to execute the script from within ArcMap if I wanted to validate portions of the data at a time (using the visible extent).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;The reason I want to be able to validate portions of the topology of a time is because if I were to validate the entire dataset I would exceed the error threshold for topology. The reason I have so many errors is because I am creating a topology to load into a parcel fabric, and my staging data has a significant number of connection lines that must be marked as exceptions.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;My ideal is to build the topology and validate it all within a stand alone python script, but with the current Validate Topology tool, I have to run the process from within ArcMap. I think it would be very helpful if instead of a simple "visible extent" checkbox, I could manually specify the extent (either by typing in the coordinates, or by loading a polygon feature class to define the extent). This would make the tool much more robust when being run from a stand alone python script.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Apr 2016 13:34:10 GMT</pubDate>
    <dc:creator>SarahMoussadji</dc:creator>
    <dc:date>2016-04-05T13:34:10Z</dc:date>
    <item>
      <title>Allow users to validate topology within a defined extent via python</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idi-p/921870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With the current 'Validate Topology' geoprocessing tool, there is an option to use the 'visible extent' parameter to validate only the current extent of your data. If I were to create a python script to validate topology, I would still need to execute the script from within ArcMap if I wanted to validate portions of the data at a time (using the visible extent).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;The reason I want to be able to validate portions of the topology of a time is because if I were to validate the entire dataset I would exceed the error threshold for topology. The reason I have so many errors is because I am creating a topology to load into a parcel fabric, and my staging data has a significant number of connection lines that must be marked as exceptions.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;My ideal is to build the topology and validate it all within a stand alone python script, but with the current Validate Topology tool, I have to run the process from within ArcMap. I think it would be very helpful if instead of a simple "visible extent" checkbox, I could manually specify the extent (either by typing in the coordinates, or by loading a polygon feature class to define the extent). This would make the tool much more robust when being run from a stand alone python script.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Apr 2016 13:34:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idi-p/921870</guid>
      <dc:creator>SarahMoussadji</dc:creator>
      <dc:date>2016-04-05T13:34:10Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users to validate topology within a defined extent via python - Status changed to: Under Consideration</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1237021#M22350</link>
      <description />
      <pubDate>Thu, 01 Dec 2022 21:27:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1237021#M22350</guid>
      <dc:creator>SSWoodward</dc:creator>
      <dc:date>2022-12-01T21:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users to validate topology within a defined extent via python</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1418874#M29904</link>
      <description>&lt;P&gt;This is critical for the Forest Service to have the capability to input an extent through arcpy for processing. We are migrating our land records system national extent data into the ArcGIS Parcel Fabric, which crashes the topology engine when running the Validate Topology tool on the entire dataset. We used the Validate Parcel Fabric tool in 3.2 but that is deprecated in Pro 3.3, with the suggestion of using Validate Topology as a replacement. However, the replacement tool does not currently allow for processing by an input extent, so it is not a viable replacement for our large dataset.&lt;/P&gt;&lt;P&gt;It was listed above as Under Consideration in 2022 and here we are in 2024 and it is still not implemented. We will be in a bind soon, when 3.2 is replaced on our systems with 3.3, and we cannot validate the topology for our migration into Parcel Fabric.&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 17:50:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1418874#M29904</guid>
      <dc:creator>ChristalHigdon_USFS</dc:creator>
      <dc:date>2024-05-03T17:50:36Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users to validate topology within a defined extent via python</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1463584#M30173</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/604859"&gt;@SSWoodward&lt;/a&gt;&amp;nbsp;- In Pro 3.3, the Validate Topology help indicates there is a visible extent parameter that can be used if you are executing the process on a topology that is open in a map, but I don't see any additional parameters, and nothing is listed under the Environments tab either.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/validate-topology.htm" target="_blank"&gt;Validate Topology (Data Management)—ArcGIS Pro | Documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This would still not be entirely what I am after (would love an option that doesn't require me to open Pro), but with some ability to specify extent, I could at least make it work (thinking a script will zoom to different extents and then kick off the Validate Topology at each new extent).&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have 20 MILLION parcels to migrate, so I absolutely cannot run Validate Topology on all 20 million parcels in my parcel fabric at one time. I think my computer might explode. As it is, I tried to run Validate Topology on about 400k parcels and a File Geodatabase failed after 2.5 h ("a failure was detected inside the Topology Engine Overlay Processor") and a Mobile Geodatabase ran for 15h and stayed at 3% before I killed it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2024 04:27:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1463584#M30173</guid>
      <dc:creator>SarahSibbett</dc:creator>
      <dc:date>2024-05-14T04:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users to validate topology within a defined extent via python - Status changed to: In Product Plan</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1518549#M31510</link>
      <description />
      <pubDate>Mon, 12 Aug 2024 18:55:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1518549#M31510</guid>
      <dc:creator>SSWoodward</dc:creator>
      <dc:date>2024-08-12T18:55:57Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users to validate topology within a defined extent via python</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1518611#M31519</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/604859"&gt;@SSWoodward&lt;/a&gt;&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":party_popper:"&gt;🎉&lt;/span&gt;&amp;nbsp;Hooray! Thank you for the update.&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":party_popper:"&gt;🎉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2024 20:41:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1518611#M31519</guid>
      <dc:creator>ChristalHigdon_USFS</dc:creator>
      <dc:date>2024-08-12T20:41:30Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users to validate topology within a defined extent via python</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1518650#M31520</link>
      <description>&lt;P&gt;Always happy to deliver good news!&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2024 21:55:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1518650#M31520</guid>
      <dc:creator>SSWoodward</dc:creator>
      <dc:date>2024-08-12T21:55:14Z</dc:date>
    </item>
    <item>
      <title>Re: Allow users to validate topology within a defined extent via python - Status changed to: Implemented</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1558581#M32849</link>
      <description>&lt;P&gt;&lt;SPAN&gt;This is implemented in ArcGIS Pro 3.4. Go to&amp;nbsp;&lt;/SPAN&gt;&lt;A title="https://community.esri.com/t5/arcgis-ideas-blog/your-ideas-in-arcgis-pro-3-4/bc-p/1556503" href="https://community.esri.com/t5/arcgis-ideas-blog/your-ideas-in-arcgis-pro-3-4/bc-p/1556503" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable" data-linkindex="1" data-ogsc=""&gt;Your Ideas in ArcGIS Pro 3.4&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;to see other ideas implemented this release and check out the&amp;nbsp;&lt;/SPAN&gt;&lt;A title="https://pro.arcgis.com/en/pro-app/3.4/get-started/whats-new-in-arcgis-pro.htm" href="https://pro.arcgis.com/en/pro-app/3.4/get-started/whats-new-in-arcgis-pro.htm" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable" data-linkindex="2" data-ogsc=""&gt;What's New&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;help to learn about everything that is new and improved in ArcGIS Pro 3.4.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KoryKramer_0-1731592642958.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/119524iE2CE0006C768317F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="KoryKramer_0-1731592642958.png" alt="KoryKramer_0-1731592642958.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Nov 2024 13:57:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/allow-users-to-validate-topology-within-a-defined/idc-p/1558581#M32849</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2024-11-14T13:57:32Z</dc:date>
    </item>
  </channel>
</rss>

