ArcGIS filtering of table results

[ajerovich]

Hi All,

I have a ArcGIS map based upon a composite address field (street address, suburb, postcode, state and country).

We also have a table that shows these addresses along with the related record details (e.g. name, record type, etc.).

We are trying to have the ArcGIS map filter the table results.

What we have found is that ArcGIS will try its best to map the address even when some of the data is dirty (some of this can be cleaned but some of it cannot).

For example, if the street address does not exist but it can locate the suburb, postcode, state and country it will plot a dot where the suburb is.

We have found that although it will plot unknown street addresses to a common point (e.g. suburb) it still considers them unique locations, creating what I would call pages for that single point. This is demonstrated at the top right of the point details popup where it will say: . Each page representing a unique (non-existent) location for that point.

When clicking on these points that have been clustered as part of the report UI but are still considered unique locations, the table is filtered to only the first page of the point, with the other point pages not being selected. Using the multiselect will filter the table by all the entries for that point (so there is a work around it but it would require user vigilance).

Our question is, is there a way to change this behaviour so that when using the "select individual locations" function of the ArcGis maps and clicking on a single point (even if it potentially has non-existent unique locations) it will filter the table to show all the results for that single point.

We have considered removing the street address component of the address composite (thus removing the unique component of the address composite) but it would be great if we could keep it so we can be accurate with the location of records.

Thanks!

[v-lili6-msft · Accepted solution]

hi, @ajerovich 

I think may remove the street address component of the address composite, you could also use that workaround and add a tip flag in the report for user vigilance.

Best Regards,

Lin