Esri / crowdsource-reporter

An ArcGIS Online group application template authored by organization and made available to constituents to report a problem or observation.
http://solutions.arcgis.com/local-government/help/crowdsource-reporter/
Apache License 2.0
25 stars 32 forks source link

Search widget is not working with custom geocode locator #516

Closed aparveen closed 2 years ago

aparveen commented 3 years ago

Custom geocoder service is not working properly within the Crowdsource Reporter application. It worked before. It works well within web maps and other applications, but not in the Crowdsource Reporter. When an address is entered and result is chosen, it will not zoom to that address within the application. The ArcGIS World Geocoder is working fine within it, but it is cumbersome for our customers to use. Our geocoder service is: https://gis.whud.org/arcgis/rest/services/Public/SingleHouse/GeocodeServer.

Addresses Support tried are 109 Manor, 3053 Worsham Springs, 317 Rockland, and 200 Business Park I am seeing console error.

Test app: https://stategovernment.maps.arcgis.com/apps/CrowdsourceReporter/index.html?appid=6236a76e3a374232985b4444f9c840a1

image

aparveen commented 3 years ago

cc @skrishn

ashutoshverma-ct commented 3 years ago

@aparveen @skrishn

We checked the above geo-locator link, it is not accessible to us. So we checked the application and it is working without the geo-locator (screenshot attached)

We also tried with our local geo-locators (secured, removed) but were unable to reproduce the exact case, at our side, the service does not return results from the particular service.

image

skrishn commented 3 years ago

@ashutoshverma-ct @sumitzarkar

The app works with a custom geolocator on https://sampleserver6.arcgisonline.com/arcgis/rest/services/Locators/SanDiego/GeocodeServer, and there are some properties/parameters different in the user's geocode server and from the one in sample server6. I requested the analyst to test with other geocode servers to identify the issue. I'll keep you posted.

cc @aparveen

sumitzarkar commented 3 years ago

@skrishn @aparveen

Any updates on this ticket

skrishn commented 3 years ago

@sumitzarkar Please proceed with the solution you recommended. I don't want to wait any longer due to the shorter dev cycle we have. cc @aparveen

sumitzarkar commented 2 years ago

@aparveen

Root Cause

Here are the details of this issue:

Solution

aparveen commented 2 years ago

Verified in QA