Operations Dashboard Spatial Filter Action Includes Edge Features

1273
5
05-12-2020 02:18 AM
by Anonymous User
Not applicable

When using the spatial filter action in the list or the header panel features around the boundary of the intended filter area are captured also. The features are not inside the filtered boundary but are surrounding features. In the image below only the green area should be shown but additional areas are selected. This affects the visual appearance of the dashboard and looks untidy when using it to show areas of interest.  

0 Kudos
5 Replies
JohnSolly4
Esri Contributor

Hello Will Atkin

I haven't been able to reproduce this on my side. Can you confirm that it works in the production dashboard (not the beta). If you can provide a map where you can make this happen, that would help a lot.

Thanks!

0 Kudos
by Anonymous User
Not applicable

Hi,

This is done using the production dashboard and not the beta: ArcGIS Dashboards  

Thanks,

Will

0 Kudos
JohnSolly4
Esri Contributor

Hey Will Atkin‌.

I think this is a bit of an optical illusion. I can also reproduce this in the map viewer.

If you zoom in, it shows that these points are actually inside the polygon

I suggest you reach out to the Map Viewer Beta forum as this is an issue that would be solved on their end if they address it. From my assessment, the points are in the right place, but they could visually be placed in a better spot at smaller scales.

by Anonymous User
Not applicable

Hi John,

Thank you and I did think the points were a bit of an optical illusion. However, the original question was more to do with when you select an area in the filter panel (say the green area in the photos) the sub-catchments do not filter to the same shape. The original photo should only show the same outline for the subcatchments and not for example Cam Ely & Ouse or Upper and Middle Lea around the edges.

0 Kudos
JohnSolly4
Esri Contributor

Sorry about that Will! I got too focused and wasn't reading as clearly as I could have.

I think I understand now. You are seeing additional polygon features selected around the the spatially filtered polygon boundary. I believe this is caused by the polygons having overlapping features. By default, the spatial selection does an INTERSECT, so even if the boundaries are overlapping by just a few pixels, it will be captured.

We have open enhancements to include additional operators such as 'completely contains' which I think would solve this issue.

A workaround would be to set up a foreign/primary key between these two polygon layers and use field filtering instead of spatial filtering.

Are we on the same page now?

0 Kudos