Address locator not working
I'm attempting to get address matching capabilities working in my viewer. My locator works as expected in my Esri Flex viewer app as well as via the REST services directory. When I load the HTML5 viewer, the console viewer in Firefox gives me the following two messages:
"esri.config.defaults.io.proxyUrl is not set. If making a request to a CORS enabled server, please push the domain into esri.config.defaults.io.corsEnabledServers."
init.js:1816:246
"[error]: 09:43:54.389: Unable to retrieve geocode server information at: 'http://<server name>/arcgis/rest/services/geocode_services/Streets102/GeocodeServer':
esri.config.defaults.io.proxyUrl is not set. If making a request to a CORS enabled server, please push the domain into esri.config.defaults.io.corsEnabledServers."
Where does one find and set the esri.config.defaults.io.proxyUrl attribute?
If I attempt to search for an address I get the following console message, but I believe this is due to the above error:
"[error]: 09:58:42.706: ArcGIS Geocode Search Provider: Cannot perform search with a service that doesn't support single address line queries." Index.html:260:16
I appreciate any guidance you might have.
Brian
-
Brian,
Have you added the location of your Address Locator to your proxy.config file?
inetpub\wwwroot\Html5viewer\proxy.config
bjc
0 -
Bobby Jo, I had not. Is that documented somewhere in the Admin Guide? I either missed it or it isn't in there. Regardless, adding the location does not seem to have any effect.
0 -
Bobby Jo, your reply yesterday got me thinking about how my services are referenced. My knowledge base is built heavily upon how the Esri Flex viewer consumes the various map services, pdf documents, etc. that my users have come to rely on. Transitioning to the GE platform has been relatively straightforward but not without a few hiccups. It appears that GE prefers to have server paths fully qualified, so even though it has been happily serving up my map services with a less-than-fully-qualified server name, certain things have not seemed to work--or work quite right.
On a hunch I created a new test site and also created a new connection to my ArcGIS Server, fully qualifying the server name. I added my street layer and my composite locator and address matching worked flawlessly. I've since tested a few other "quirks" that have been nagging me and so far all have been successfully resolved. I now need to rebuild my site but I've learned enough with my original test site that the rebuild should go fairly quickly.
So for the benefit of anyone that might also be experiencing something similar, fully qualify your map server and IIS virtual directory paths (for pdfs on your network). I kept the edits to the proxy.config file that you suggested. That may or may not have contributed to the success.
0 -
Brian,
I am glad everything is working now and thank you for adding your resolution to the forum!
bjc
0
Please sign in to leave a comment.
Comments
4 comments