POST
|
Hi, in my Android app, I'm using a locator (geocoding service) for the search functionality, i.e. Locator locator = Locator.createOnlineLocator(URL to a 10.2 ArcGIS Geocoding Service) etc. Moreover I'm using the same service in a Web application with ArcGIS for Javascript. In the Web application, I'm able to get a character-by-character auto-completion although I do not use the ArcGIS Server 10.3 "suggest" capability (I am still using esri/dijit/geocoding with autoComplete=true, not the new search widget). So I thought that auto-completion should also work in my Android app... I tried to use LocatorSuggestionParameters params = new LocatorSuggestionParameters(text input...);
and locator.suggest(params, new CallbackListener<List<LocatorSuggestionResult>>() {... as specified in the API reference but I'm not getting any results. Can somebody please tell me if the auto-completion for geocoding services in Android is only possible with the ArcGIS Server 10.3 "suggest" capability? Thanks! Claudia
... View more
10-28-2016
06:51 AM
|
0
|
0
|
951
|
POST
|
Hi, it would be great if you could help me with a problem with Geoportal / the GeoportalSearch widget. The short question is: How can I modify the URLs behind the "Details" and "Metadata" links in the GeoportalSearch widget that I'm using inside my Web AppBuilder application for the Esri Geoportal Server? The long explanation is here: I have set up Esri Geoportal Server on my own Windows 2012 server and replaced the default map viewer (flex viewer) with a custom Web AppBuilder application that is published on IIS 8 (/wwwroot/mapviewer). I also added the GeoportalSearch widget to my Web AppBuilder application as described here. So far, everything works fine... I can search the metadata catalog in my map viewer using the GeoportalSearch widget. However, I wanted my Geoportal to be accessible on the default HTTP port 80 instead of the tomcat port 8080. So I set up a reverse proxy server using Application Request Routing and URL Rewrite as described here. My regular expression for the inbound rule is (geoportal.+) and my rewrite URL http://[myserver]:8080/{R:0} . Again, this worked, i.e. now I can access my geoportal by typing http://myserver/geoportal/catalog/main/home.page, browse to different sites and search the catalog without seeing the :8080 port number in the URL. The only problem is that when I launch my custom map viewer (the Web AppBuilder application), search for data in the GeoportalSearch widget and then click on one of the links provided in the search results (e.g. "Details" or "Metadata"), I am directed to an URL that still contains the 8080 port (e.g. http://[myserver]:8080/geoportal/catalog/search/resource/details.page?uuid=....). Actually I don't really know where this URL is coming from; it is probably retrieved from somewhere within the widget code. I need to find out how to remove the :8080 in those URLs, because it will be rewritten to 8080 by the reverse proxy anyway, and users from outside are not able to open the URL if it contains the 8080 port. Or is there an alternative to modifying the URLs? I already tried to configure a new proxy that redirects URLs that contain 8080 to the same URL without 8080 (which will then again go through the other proxy, of course....) but it is not working. I'm quite new to working with proxies (and the Geoportal Server itself), so I hope someone can help me. Thank you! Claudia
... View more
09-07-2016
07:50 AM
|
0
|
0
|
1365
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|