Select to view content in your preferred language

Allow users to validate topology within a defined extent via python

1035
6
04-05-2016 06:34 AM
Status: In Product Plan
Labels (1)
SarahMoussadji
Deactivated User

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). 

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. 

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. 

6 Comments
SSWoodward
Status changed to: Under Consideration
 
ChristalHigdon_USFS

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.

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.

SarahSibbett

@SSWoodward - 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. 

Validate Topology (Data Management)—ArcGIS Pro | Documentation

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). 

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. 

SSWoodward
Status changed to: In Product Plan
 
ChristalHigdon_USFS

@SSWoodward 🎉 Hooray! Thank you for the update. 🎉

SSWoodward

Always happy to deliver good news!