Find existing locations is ignoring filter

[KendellRyan]

I'm using the Find existing locations tool in my web map.  I first set a filter in my later to select only 1 County Park. I then run the tool building a query to select all parcels with 0.5 miles of the Park. However it is clearly ignoring my filter and checking all parks.  I tried another work around to build a complex query right in the tool (select that park AND select the relevant parcels) but that doesn't work either.  Is there no way to make that analysis run on only selected/filtered features? This would would be a no brainer in ArcMap of course.

[KellyGerrow · Accepted solution]

HI Kendell,

Try the following steps. I did run into a few issues when I received errors from your service, so you may want to check your server logs to see what is happening with the service. I made the buffer just to ensure that the results were in the correct area.

1. Open web map

2. Set filter on the county parks location using the filter tool.

     Park Name is Three Lakes Park

3. Hit apply filter

4. Select Analysis tools> Find Locations>Find Existing locations

5. Choose Tax parcels as the layer containing the features for the attribute and spatial queries

6. Open the Add Expression and set the where attribute to within a distance of

7. Set up your query to look like the screenshot below:

8. Ensure that an appropriate result layer name is added

9. Select Run Analysis

Let me know if this works for you,

Kelly

[KendellRyan]

OMG!! it was working all the time.  The show credits tool clearly doesn't work. I was using that as a guide. The show credits was ignoring the filters. Is that a bug? Did that happen for you?

[XiaolongFeng1 · Accepted solution]

Hi Kendell,

Actually for this analysis tool (and similarly Derive New Locations tool), Credit Estimator(show credits tool) will only give you an assumption of the maximum credits this task may consume. What we do for this tool is counting every input layer's feature within the map extent(if you checked ) or within the whole map to give you the assumption.

The reason why we do this is because user can set customized expressions to the query, and the query can get really complicated, that without actually running the analysis job(which will use our Spatial Analysis service and will consume credits), the credit estimator is not able to give you the exact number of features returned in the query.

In other words, if you want to see the exact credit the job will consume, we have to execute this job first. This may take really long time, which is a bad user experience. This will also lead to "shall we charge user credits for this" dilemma.

I think in our help doc, for these specific tools the part for credit consumption is not clear. Also in Credit Estimator, the UI maybe bit misleading. We can make those info more clear in the future.

Thanks,

Xiaolong

[KendellRyan]

Thank you, that is very helpful. It is unfortunate that it doesn't work since I wanted to add that step into my workflow. I'd rather have it take longer but actually calculate true credits. otherwise it's misleading and confusing. hopefully in the future that will be improved?  Thanks again, at least i know it's not just my map!

[KellyGerrow]

HI Kendell,

I kept getting an error message about your service being unavailable, but it did work several times. Are you receiving any errors on your service in your server logs?

I will test the credit estimation functionality further.

-Kelly

[KendellRyan]

Yeah, I am getting them periodically. We had an unreal storm last night and running on generators and having intermittent issues. I'll look into the errors though.