Highlight Gaps and Overlaps in multiple parcel layers simultaneously

1199
10
06-01-2023 05:55 AM
Status: Implemented
SusanLMoore
New Contributor III

Currently, the Highlight tool requires the user to validate each layer one at a time. We would like to be able to select multiple layers at once. 

Our workflow is to perform all validation (topology, attribute rules, Highlight tool) in the area of the "job" before it is reconciled/posted to Default. A job generally impacts all polygon layers, which means that in order to fully validate, we have to select the feature layers one-by-one in the Highlight tool drop-down. If we could highlight issues in all of the layers at once, it would prevent us from accidentally missing a layer. 

I'm picturing a layer list that would allow you to toggle the layers you want to highlight off and on. 

10 Comments
AmirBar-Maor

@SusanLMoore 
Thanks for your comment on the other idea.

Can you please change the title of this idea to say something like "Highlight Gaps and Overlaps in multiple parcel layers simultaneously?

When a gap or overlap is identified, would it be challenging to know which layer it belongs to?

Should the layers be visible when it runs?

 

We are looking to introduce multiple enhancements to the Highlight tool, so it's great timing to collect the business requirements and design them all at once.

Thank you!

SusanLMoore

@AmirBar-Maor , we appreciate that chance to share our thoughts! Here are some overall suggestions on the Highlight tool.

  1. We agree that if you are showing the gaps and overlaps on multiple layers at once, it could be challenging to know which layer it is in. We would suggest having a way to navigate the errors (like how the Error Inspector allows the ability to zoom, flash, etc.). This would solve the initial problem of not knowing which layer the problem is in, and it would also make it easier to find the errors when validating a larger area. Consider the scenario of showing Highlights on a new subdivision. The Highlight tool currently doesn’t indicate how many errors exist in the area being validated, and the area is large enough that small, highlighted areas could be easily overlooked. I'm attached 2 pics that hopefully illustrate that. 
  2. We’d suggest that only visible layers be available in the drop-down list (and hopefully in the future, the multi-select list).
  3. Have a toggle on the gaps and overlaps options so you could choose to see just gaps, just overlaps, or both gaps and overlaps at the same time.
  4. Make the Maximum Width a min-max range (e.g., show gaps/overlaps that are a minimum = 0 and a maximum = 5 or a minimum = 3 and a maximum = 20). Maybe it’s just us, but we spent about 20 minutes playing with the numbers in that box to figure out what to enter to show us the gaps and overlaps we expected to see, and I still don't think we have it down. For example, an overlap over 7 ft did not show up when searching with the maximum width set at 3 ft.  but did when we set it to 6 ft.

Essentially, what we need is the functionality topology rules provide but the ability to run them against feature layers (so the definition-queried layers in the map) vs the underlying feature classes.

common extent we would validatecommon extent we would validatevery easy to miss the error on the east sidevery easy to miss the error on the east side

AmirBar-Maor
Status changed to: In Product Plan
 
JasonCamerano

Hello @SusanLMoore 

I'm happy to inform that this request has been implemented in ArcGIS Pro 3.2!

SusanLMoore

@JasonCamerano , thank you so much for listening! We look forward to trying it out!

AmirBar-Maor
Status changed to: Implemented

Implemented with ArcGIS Pro 3.2

CathyAppleton

@JasonCamerano   Thank you!    This will really help!!

JasonCamerano

Hey @SusanLMoore and @CathyAppleton  ,

I have a couple follow up questions on this enhancement. 

First, hopefully you all have been able to try out the new enhancement in 3.2?  If so what has been y'alls experience?

Second, when comparing between multiple layers, how many layers are you usually comparing between? Is it just two separate layers, is it three separate layer? 

Thanks,

-Jason

SusanLMoore

@JasonCamerano , sorry it has taken so long to get back to you. We were going live with our fabric right when you posted! We have finally had a chance to play with the changes in 3.2. We are noticing some inconsistencies with how the gaps are overlaps are being highlighted (e.g., when you are working with a single layer, it shows the gaps and overlaps correctly but then when you switch to Use Visible Layers, only the gaps display). What's the best way for us show/communicate to Esri what we are seeing? 

To answer your other question, we are generally comparing between 2 separate layers (specifically, we are looking for areas where tax parcel polys overlapped the right of way (type = dedicated). 

Thanks,

Susan 

AmirBar-Maor

@SusanLMoore 

Jason is busy in the developer summit right now... so here is the answer:

The 3.2 implementation tries to find gaps and overlaps by unioning all the visible layer to a single polygon layer, which is not what you wanted. This is why you see the results you see.

The good news: we have changed it for ArcGIS Pro 3.3!

In ArcGIS Pro 3.3 checking the option will basically check EACH parcel layer on its own.

For those who want to check for gaps and overlaps between multiple layers, for example between Lots and Tax parcels, we are implementing a new geoprocessing tool that will be released with ArcGIS Pro 3.4.