Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search widget is not working with custom geocode locator #516

Closed
aparveen opened this issue Oct 12, 2021 · 7 comments
Closed

Search widget is not working with custom geocode locator #516

aparveen opened this issue Oct 12, 2021 · 7 comments
Assignees
Labels
Milestone

Comments

@aparveen
Copy link
Contributor

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 aparveen added this to the AGOL 9.4 milestone Oct 12, 2021
@aparveen
Copy link
Contributor Author

cc @skrishn

@ashutoshverma-ct
Copy link

@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
Copy link
Contributor

skrishn commented Oct 26, 2021

@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
Copy link
Contributor

@skrishn @aparveen

Any updates on this ticket

@skrishn
Copy link
Contributor

skrishn commented Nov 9, 2021

@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 added a commit to sumitzarkar/crowdsource-reporter that referenced this issue Nov 19, 2021
### Implemented following git hub tickets
 - Esri#510
 - Esri#512
 - Esri#513
 - Esri#516
aparveen pushed a commit that referenced this issue Dec 2, 2021
@sumitzarkar
Copy link
Contributor

@aparveen

Root Cause

Here are the details of this issue:

  • This issue is reproduced with the services which do not have singleLineAddresField name as 'SingleLine' and have Suggest capability. When the user clicks on the suggestion in the list this issue is reproduced.
  • Currently, we are only able to reproduce this issue with the service (https://gis.whud.org/arcgis/rest/services/Public/SingleHouse/GeocodeServer)
  • In this, we found that the singleLineAddressFieldName is different, it is 'Single Line Input'
 "singleLineAddressField": {
  "name": "Single Line Input",
  "type": "esriFieldTypeString",
  "alias": "Full Address",
  "required": false,
  "length": 150
 }
  • The application fetches the locations of selected suggestion candidates once the user clicks on them. Also, the application was assuming that the singleLineAddressField name should be 'SingleLine'

Solution

  • We have updated the code to fetch the address using the singleLineAddressFeild name defined in the service

sumitzarkar added a commit to sumitzarkar/crowdsource-reporter that referenced this issue Dec 3, 2021
aparveen pushed a commit that referenced this issue Dec 3, 2021
@aparveen
Copy link
Contributor Author

aparveen commented Dec 3, 2021

Verified in QA

@aparveen aparveen closed this as completed Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants