-
Notifications
You must be signed in to change notification settings - Fork 51
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
Incorporating a custom address locator #4
Comments
There is currently a bug we have with this scenario and we are investigating a fix. An alternate workflow is to set the custom geocoder in your organization's settings >utility services. Then update the sharingurl of your application to point to your org's home url instead of arcgis.com. |
The fix for this issue has been checked in, so you should be able to approach the custom geocoder scenario in one of two ways: 1) as described in the comment above; or 2) configuring the placefinder in the index.html by providing values for "url" and "singleLineFieldName" parameters. |
Thanks so much for the quick response! Both of your suggestions worked. I have an ArcGIS Online for Organizations account, so I went with the 'sharingurl' route as I like how users are offered suggestions as they start typing an address into the search field. |
Hi, I haven't had much luck adding customizing the basic viewer with another geocoder.
My goal is to replace the default Esri World Geocoder with my own.
When I edit the commonConfig.js file and refresh the app, it looks like the viewer's still pointing at the default geocoder. (Screenshot attached)
I saw this comment in the layout.js file: "only use geocoders with a singleLineFieldName that allow placefinding". I added a place name alias locator service to my composite address locator, but it didn't make a difference. My locator already supports single line fields.
At this point I'm not certain if this is an issue with the viewer, if I'm getting my syntax wrong, or if the viewer has an issue with my own custom geocoder?
The text was updated successfully, but these errors were encountered: